Engagement & investment

You commit one package at a time.

Pricing is modular by design, so approval stays simple and progression stays your decision. We share the figures in a short call, once we know which process we would be working on — because that is the thing that actually determines the number.


Three packages, in order

Start here

1 · Diagnose + Pilot

One process or department: readiness review, friction and ROI map, one working automation, and before/after measurement. A fixed price, because the scope is fixed.

Then

2 · Expansion

Priced per additional process, and it gets cheaper as you go — each expansion reuses the templates and backbone already built. Committing several together reduces the per-process price.

Long term

3 · Ongoing Transformation

A monthly retainer for department-by-department rollout, a shared AI backbone, staff enablement, governance and KPI reporting. For companies that have already proven the model and want it to keep moving.


What actually moves the price

These are the questions we ask on the first call — they are also the answer to why two companies get two different numbers.

How many processes

One process behaves very differently from a department-wide rollout. The first is a fixed scope; the second is priced per process and gets cheaper each round.

How messy the starting point is

A process that already has a defined owner and a form is faster to model than one that lives in three spreadsheets and one person's memory. We fix the process before automating it, and that fix is part of the work.

What has to be connected

Marketplace connectors, payroll and e-invoicing are included rather than billed as add-ons. A bespoke integration into an unusual internal system is the case that genuinely adds cost.

How many people it touches

Enablement is part of delivery. A workflow used by four people and one used by forty are not the same amount of work, even if the automation is identical.


What you will not find here

There is no lock-in contract and no minimum term. At every decision point you choose whether to continue, and stopping after the first package leaves you with a working automation and a documented process — not a dependency.

And there is no promised timeline on this page. Every engagement depends on how quickly your own people can answer the discovery questions and approve the pilot — which is not something we can commit to on your behalf.


Related

See it running on your own process.

Tell us which process hurts most and we will tell you what it would take.

Request a demoRead the FAQ