M3CloudSlam

Predict & verify · Predictor Preview

See what M3 will do, before you press enter

Pick an action (a screen, an API call or a job) and a record from your own M3. The Predictor shows step by step what M3 will check, which records it will write and with which values, and where it would stop.

Predictor · release for pickingPreview
If I do this
Release delivery 55156 for pickingAPI
Deliverylines allocatedall linesallocated?Released forpicking✕Refused · stop A02
  • 1Reads the delivery and its 4 lines from your M3read
  • 2Checks: are all lines fully allocated?check
  • !Line 30 is allocated 6 of 10found
M3 will refuse this: “Not all lines fully allocated”.Refused

Why it matters

Today

  1. 1Try it in a test environment, if it is up to date
  2. 2Or try it in production, and hope
  3. 3Ask someone who knows what M3 will do

You find out what M3 does after it has done it.

With Predictor

  1. 1Choose the action and the record
  2. 2See every check, and every record written with its values
  3. 3Know where it would stop, and why

Know what M3 will do, before it does it.

How it works

From an action to M3's answer, before anything changes

  1. 1 / 4

    Choose the action and the record

    A screen action, an API call or a job, and a record from your M3: here, releasing delivery 55156 for picking.

    Predictor · release for pickingPreview
    If I do this
    Release delivery 55156 for pickingAPI
  2. 2 / 4

    See the predicted path

    On the process flow: the step M3 will take, and the decision where it may stop.

    Predictor · release for pickingPreview
    If I do this
    Release delivery 55156 for pickingAPI
    Deliverylines allocatedall linesallocated?Released forpicking✕Refused · stop A02
  3. 3 / 4

    Read every step

    What M3 will read and check, in words. Where the outcome depends on something it can't read, it names that as an open question.

    Predictor · release for pickingPreview
    If I do this
    Release delivery 55156 for pickingAPI
    Deliverylines allocatedall linesallocated?Released forpicking✕Refused · stop A02
    • 1Reads the delivery and its 4 lines from your M3read
    • 2Checks: are all lines fully allocated?check
    • !Line 30 is allocated 6 of 10found
  4. 4 / 4

    Get the verdict

    M3 will refuse this: not all lines are fully allocated. The same answer M3 itself gives.

    Predictor · release for pickingPreview
    If I do this
    Release delivery 55156 for pickingAPI
    Deliverylines allocatedall linesallocated?Released forpicking✕Refused · stop A02
    • 1Reads the delivery and its 4 lines from your M3read
    • 2Checks: are all lines fully allocated?check
    • !Line 30 is allocated 6 of 10found
    M3 will refuse this: “Not all lines fully allocated”.Refused
On your own M3. Answers come from one knowledge graph of how M3 behaves, applied to your configuration and data. When something can’t be known, M3CloudSlam says so.

What it brings you

Change with confidence, on your own records

  1. 1“You don’t need a consultant for that anymore”Your own team sees what M3 will do, instead of asking someone to test it for them.
  2. 2No more testing in productionSee the outcome without touching a live record.
  3. 3Every record, every valueKnow which records M3 will write, and with which values.
  4. 4Honest by designWhen something can't be known, it says so instead of guessing.

Coming next Roadmap

Scenario Lab

Change a setting on paper, replay last month through it, and compare before and after: the Predictor applied to a whole period.

See the roadmap →

Use Predictor on your own M3, first

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows