Engagement overview
An engagement runs in three stages: the Discovery Sprint, the Embedded Build and Operate & Automate. This page puts them on one timeline, then covers what you decide at each boundary, who is involved on both sides and how you can stop.
The timeline
Section titled “The timeline”Before stage one comes the first conversation: a call with one of our forward-deployed engineers about your ERP and the three workflows that hurt most.
Discovery Sprint Embedded Build Operate & Automate 2 weeks on site typically 3 to 6 months monthly, after the build|----------------| |----------------------| |-----------------------> ^ ^ Boundary 1 Boundary 2 the readout the end of the build| Stage | Our engineers | What happens | What you have at the end |
|---|---|---|---|
| Discovery Sprint | 2, on site for 2 weeks | They shadow the people who do the work and map how orders, materials and money move. Then they prototype the top workflow. | Operations Map, Systems and Data Audit, Automation Backlog, Working Prototype |
| Embedded Build | Typically 2, for 3 to 6 months, with a 3-month minimum | They build software around your workflows, attached to your ERP, and release every week. Agents come in one workflow at a time. | Software your people use every day on the workflows at the top of the backlog |
| Operate & Automate | On call, with 1 on-site week per quarter | We run, monitor and support the software and the agents. Promotion reviews move workflows up the autonomy ladder. | Software and agents that are run and supported, each workflow at the level it has earned |
How each stage is priced is in Stages and terms. The figures are on the pricing page.
What you decide at each boundary
Section titled “What you decide at each boundary”Boundary 1: the readout
Section titled “Boundary 1: the readout”The Discovery Sprint ends with a readout of its four deliverables. You decide whether to continue to an Embedded Build, and you do not have to decide in the room. You keep the deliverables either way. The proposal our engineers present at the readout names four things, and if you continue they are agreed before the build starts:
- Which workflows the build will cover, from the top of the Automation Backlog, and the level each is planned to reach.
- Who the workflow owner is for each one.
- How many engineers, and for how many months.
- The on-site schedule. Engineers are on site by default.
Boundary 2: the end of the build
Section titled “Boundary 2: the end of the build”You choose one of three paths, or combine them:
- Operate & Automate. We run, monitor and support what was built.
- Handover. An in-house team or another vendor takes it over.
- More build time. The next workflows in the backlog are scheduled as further Embedded Build time.
During Operate & Automate
Section titled “During Operate & Automate”This stage is monthly, so its decisions come up as the work goes on, not at a boundary:
- Whether a workflow moves up one level of the autonomy ladder. A promotion review decides, with the workflow owner’s sign-off. Moving a workflow back down is the workflow owner’s decision alone and needs no review.
- Whether to add a workflow from the backlog, by scheduling more Embedded Build time.
- Whether to keep the stage running or to hand over.
Who is involved
Section titled “Who is involved”On your side:
| Role | Who it usually is | What they do |
|---|---|---|
| Sponsor | The executive who owns operations: the COO or VP of operations, or the owner or CEO | Sets the order of the backlog, names the workflow owners, clears access, settles decisions that cross departments |
| Workflow owner | One named employee per workflow, such as the customer service manager for sales order entry | Decides how the workflow should work and signs off changes to it |
| The people who do the work | The order desk, buyers, accounts payable, the scheduler, customer service | Are shadowed, try each release, approve what agents prepare, handle exceptions |
| IT manager or ERP administrator | Whoever controls accounts and the ERP | Creates accounts, grants access, runs your change control |
| ERP partner | Your reseller or implementation partner, if you have one | Makes changes inside the ERP when a workflow needs one |
On our side there are the engineers. Two run the Discovery Sprint. An Embedded Build typically has two. In Operate & Automate your engineers stay on call and come back on site for one week each quarter. In every stage you deal with the engineers who do the work.
What we need from you lists what each role is asked for.
Stopping after any stage
Section titled “Stopping after any stage”You can stop after any stage.
| If you stop after | You keep |
|---|---|
| The Discovery Sprint | All four deliverables |
| The Embedded Build | The four deliverables, plus the custom code and the data built for you, with the documentation and runbooks |
| Operate & Automate | The same, as it stands on the day we hand it over |
We keep our reusable tooling, and your contract gives you the right to keep running and changing the copy inside your software after we leave. Handover and exit covers what is handed over and how.