Stages and terms
An engagement is sold in three stages, and each is priced a different way. This page describes the stages and the terms in words, lists what your contract records, then covers what is fixed, what varies and what happens between stages. It leaves the figures to the pricing page.
The three stages
Section titled “The three stages”| Stage | How it is priced | Length | Who | Figures |
|---|---|---|---|---|
| Discovery Sprint | Fixed fee | 2 weeks on site | 2 forward-deployed engineers | Pricing |
| Embedded Build | Per engineer per month | Typically 3 to 6 months, with a 3-month minimum | Typically 2 engineers | Pricing |
| Operate & Automate | Monthly fee, from a starting price | Monthly, after the build | Your engineers on call, with 1 on-site week per quarter | Pricing |
What each stage includes:
- Discovery Sprint: the Operations Map, the Systems and Data Audit, the Automation Backlog and the Working Prototype of the top workflow on your real data.
- Embedded Build: software built around your workflows and attached to your ERP, a release every week to the people who use it, and agents introduced workflow by workflow, starting at the lower levels of the autonomy ladder.
- Operate & Automate: monitoring and support for the software and the agents, promotion reviews that move workflows up the autonomy ladder and one on-site week per quarter.
The terms
Section titled “The terms”- Travel is billed at cost. That covers our engineers’ trips to your site: the two weeks of the Discovery Sprint, the on-site schedule of the build and the quarterly on-site week. The on-site schedule is agreed before the build starts, so you can see the travel it implies in advance.
- AI model usage is billed at cost. That holds in every stage. The Working Prototype calls an AI model, and so does every agent after it. The provider charges for the usage, and we pass that charge on as it is. In the Discovery Sprint that is only the prototype’s usage. A workflow at Level 0 (Recorded) has no agent, so it has no usage until an agent is tested on its recorded work ahead of a move to Level 1 (Assisted).
- Hosting and extra ERP licenses are not in our prices. That means hosting for the software, and any extra licenses your ERP vendor requires for the accounts our engineers and agents use. Your contract covers them.
- You own the custom code and the data built for you. We keep our reusable tooling. Common parts of what we build come from it: the work queue, the approval screens, the audit trail and the stop switch. Your contract gives you the right to keep running and changing the copy inside your software after we leave, with no license fee.
- You can stop after any stage.
- The rest is agreed in each contract, including support response times, hosting location and security terms. These docs state no specifics for them. The next section lists what your contract records.
What your contract records
Section titled “What your contract records”Where these docs say “agreed in your contract”, they mean this list. It carries no values, because each one is set with you.
- Who hosts the software, and where.
- Who holds the administrator accounts, the AI model provider account and the hosting account.
- Backups, and how long records are kept.
- Support response times.
- How incidents are reported.
- Liability and insurance.
- The Operate & Automate fee, its term and its notice period.
- Your right to keep running the reusable tooling inside your software.
What is fixed and what varies
Section titled “What is fixed and what varies”The first two stages have fixed rates. Operate & Automate has a starting price: the fee depends on how many workflows we run and support, and the proposal states it before you commit.
| Stage | Fixed | Varies |
|---|---|---|
| Discovery Sprint | The fee, the 2 weeks, the 2 engineers and the 4 deliverables | The day plan, which is fitted to your shifts and your calendar. Travel, and the AI model usage of the Working Prototype. |
| Embedded Build | The monthly rate per engineer, the 3-month minimum and a release every week, unless your calendar or an open decision holds it | The number of engineers, the number of months, the on-site schedule and the workflows built. Travel and AI model usage. |
| Operate & Automate | Monthly billing and 1 on-site week per quarter | The monthly fee: the pricing page shows where it starts, and the proposal states yours before you commit. Travel and AI model usage. |
The fee for an Embedded Build is the monthly rate multiplied by the number of engineers and the number of months. Travel and AI model usage come on top, at cost. The pricing page works through one illustrative engagement.
What happens between stages
Section titled “What happens between stages”Before the Discovery Sprint
Section titled “Before the Discovery Sprint”The first conversation is a call with an engineer about your ERP and the three workflows that hurt most.
After the Discovery Sprint
Section titled “After the Discovery Sprint”You have the four deliverables, and you keep them whether or not you continue. The proposal our engineers present at the readout names four things, and if you continue they are agreed before the build starts:
- The workflows the build will cover, from the top of the Automation Backlog, and the level each is planned to reach.
- A workflow owner for each.
- The number of engineers and months.
- The on-site schedule.
The Working Prototype stays a prototype in the meantime. Turning it into software your team can rely on is the first work of the build.
After the Embedded Build
Section titled “After the Embedded Build”You choose one of three paths, or combine them:
- Operate & Automate, where we run, monitor and support what was built.
- A handover to an in-house team or another vendor.
- More Embedded Build time for the next workflows in the backlog.
During Operate & Automate
Section titled “During Operate & Automate”New workflows are added by scheduling more Embedded Build time, which is priced as Embedded Build time. When the stage ends, the handover in Handover and exit applies.