The MIRAI Method

Map. Move. Manage. Measure.

One method, applied to one workflow at a time. It is deliberately narrow: we would rather prove a measurable improvement in one place than run a transformation programme across your whole company.

01

Map

MIRAI Blueprint · weeks 1–2

What happens

We follow one workflow end to end — every system it touches, every handoff, every rule and every delay. Nothing is assumed from a template.

What you get

A measured baseline: current cost, cycle time, volume, error rate and the points where work waits.

Who is involved

The people who actually do the work, plus whoever owns the outcome. Usually four to six hours of their time.

02

Move

Configuration · weeks 3–6

What happens

MIRAI OS is connected to the systems involved and configured to advance the routine steps you approved — retrieve, check, prepare, send, update.

What you get

A working workflow, run in parallel with your current process until it is trusted.

Control

Automation starts narrow. Steps are only released once they behave correctly on your real cases.

03

Manage

Human control · continuous

What happens

Exceptions and decisions that need judgment are routed to a named person with the context already assembled.

What you get

Clear ownership of every case, and an approval record that stands up to review.

The rule

Automate the routine. Escalate the exception. Keep accountability human.

04

Measure

Proof · weeks 7–13 and onward

What happens

The workflow is compared with its own baseline — capacity, speed, quality and cash — using the definitions agreed in the Blueprint.

What you get

A result you can take to a board: what improved, by how much, and what it is worth.

Then

Expand to the next workflow only when this one has earned it.

Where it begins

The MIRAI Blueprint

A scoped, paid piece of work that ends in a usable operating blueprint — not a proposal, and not an open-ended discovery engagement.

What the document contains
01 The workflow as it actually runsEvery step, every system it touches, every point where it waits — mapped with the people who run it, not from a process document.
02 What it costs you todayCoordination hours, elapsed time and rework, quantified from your own volumes. This becomes the baseline everything afterwards is measured against.
03 The automation and approval splitWhich steps are safe to automate, which must stay with a person, and who holds authority at each approval — agreed in writing before anything is built.
04 Integration constraints, named earlyWhich of your systems will cooperate, which will not, and what we would do about the ones that will not.
05 A rollout plan with a fixed priceThe 90 days below, scoped to your workflow, with the measures agreed and the figure quoted before work starts.
How it is bought
Operations ReviewNo charge · 45 minutes
BlueprintScoped and quoted first
ImplementationFixed price, from the Blueprint

There is no price list, because a three-step approval and a twelve-system onboarding process are not the same piece of work. The figure is agreed before the work, and it does not move afterwards.

The document is yours

The Blueprint is written to be useful whether or not you build it with us. If you take it to another supplier, or use it to fix the process yourself, that is a legitimate outcome — and it has happened.

Start with the Operations Review
Implementation

A controlled 90 days, not an open-ended programme.

Each phase has a decision point. If the numbers do not support continuing, we stop and say so.

Weeks 1–2

Blueprint

Workflow mapped, baseline measured, automation and control boundaries agreed in writing.

Decision: proceed or stop
Weeks 3–6

Build and connect

Systems connected, workflow configured, approvals and escalation paths set with named owners.

Decision: release step by step
Weeks 7–10

Run in parallel

Real cases run through MIRAI alongside the current process. Your team keeps the final say throughout.

Decision: hand over the routine
Weeks 11–13

Measure and decide

Result compared with the baseline, documented and reviewed. Then choose the next workflow — or stop here.

Decision: expand or hold

What we need from you

One workflow that genuinely costs you something.
Access to the people who do the work, not only the people who describe it.
Read access to the systems involved, under your own controls.
A named decision-maker for approvals and exceptions.

What you will not get

A company-wide transformation programme.
A migration off the software you already use.
Automation of decisions that should stay with your team.
Improvement claims without a baseline behind them.

Start with the workflow that costs you most.

The Blueprint is the first step, and the only commitment.

Map one critical workflow