Pricing
Find the package that fits your work.
Every engagement is scoped before we quote it. See the path from diagnosis to ongoing operation below. Five questions show a proposed package before you share contact details; a person then sends the scope and figure.
Package matcher
Start with the work you want done.
Tell us what you want true in ninety days and where you are starting. Those answers shape a provisional package. Your other answers help a person scope the work, its approval rules and a written figure.
Find my packageNo commitment. A person replies with a scope and figure, or tells you it is not a fit.
The offer
Diagnose. Build. Operate.
Start with the smallest useful step. Each step ends with a result you can review before you decide what comes next.
- 01 · Diagnose
The X-Ray
Typically two to three weeks
Measure your starting point, identify repeat work and map which actions need a person.
- 02 · Build
Choose the size of the build
Bootcamp: prove one workflow with approval rules, typically in one week.
Pilot: build a complete system with a shadow run and scorecard, typically in six to eight weeks.
- 03 · Operate
Managed operations
Ongoing, reviewed quarterly
We monitor the agents, tune the rules and give you a monthly governance report.
Engagement scale
Which scale fits your work?
The last question asks what scale you are considering. Your goal and starting point shape the proposed package; this answer helps us scope the figure.
An exploratory review
A focused review may be the right first step when the workflow or operating case is not defined yet.
One workflow
One defined workflow and its relevant tools and approval rules. The written scope says whether diagnosis, build or ongoing operation is included.
A complete system
One complete system spanning several workflows or channels. The written scope sets its build, scorecard and any ongoing operation separately.
Several systems or a rollout
Several systems, a regulated or multi-entity rollout, or a programme with your own team embedded — with the deployment and evidence work that regulated buyers need alongside it.
We have not set one yet
Fine, and common. We will size it from the workflow rather than the other way round, and you will have a figure before anyone asks you to commit to it.
See a proposed package before sharing contact details. A person then reviews your answers and sends a scope and figure.
What moves the number
Four things shape the figure.
Your answers give us a starting point. A person checks these scope drivers before sending a written figure.
- 01
What the agent is allowed to touch. Reading and drafting is light work. Anything that reaches a customer or moves money needs approvals and a record, and that is most of the scoping.
- 02
How many systems it connects to. Each connection is a permission to manage as well as an integration, so the fifth costs more than the first.
- 03
Whether your rules and approved wording already exist. If they are written down, we configure them. If not, we help you write them.
- 04
Whether we run it afterwards. A system you run and one we run have different monthly shapes. You can switch either way later.
Before you commit
The scope is in writing.
Your proposal names the work, the approval points, the result you can inspect, who operates it and the figure. You can accept, change or decline the scope before work starts.
Questions
Questions about the process.
Get a figure for your work.
Five quick questions. See a package, then ask a person for a scoped figure.
