How it works
Three stages, and you can stop after any
An engagement starts with a fixed-fee Discovery Sprint, continues as an Embedded Build and settles into Operate & Automate. This page covers what our engineers do in each stage, what you provide and what you keep if you stop.
01 The engagement
One engagement, two decisions
Every stage ends with something you can use. You decide after the readout whether to build, and at the end of the build who runs what was built.
-
The first call
A call with an engineer about your ERP and the three workflows that hurt most. That is the whole first conversation.
-
The readout
Day 10 of the Discovery Sprint. You decide whether to continue to an Embedded Build, and you do not have to decide in the room. You keep the four deliverables either way.
-
The end of the build
A build ends on the date agreed before it started. Then you choose: Operate & Automate, a handover to an in-house team or another vendor, or more build time. You can combine them.
02 Discovery Sprint
They learn the work before they build
The first stage is for seeing the work as it is. By the end you hold a map of how orders, materials and money really move, a ranked list of what to fix and a working prototype of the first item on it.
Week 1
See the work as it is
-
Day 1 Sponsor needed.
Safety orientation and kickoff, then one order followed end to end
-
Day 2
Shadow the order desk and customer service
-
Day 3
Shadow purchasing and accounts payable
-
Day 4
Shadow scheduling
-
Day 5
List every system and spreadsheet, confirm read access, walk the draft map back
Week 2
Measure, rank and build the prototype
-
Day 6
Measure where the hours go
-
Day 7 Sponsor needed.
Rank the workflows, review the backlog with the sponsor, start the prototype
-
Day 8
Build the Working Prototype on real data
-
Day 9
Run the prototype beside the person who does the work, finish the other deliverables
-
Day 10 Sponsor needed.
Present the findings at the readout
- The sponsor is needed on days 1, 7 and 10: the kickoff, the backlog review and the readout.
The four deliverables
01
Operations Map
How the work actually flows, step by step, including the spreadsheets, inboxes and workarounds.
02
Systems and Data Audit
Every system involved, what data it holds, how to get data in and out, and how clean it is.
03
Automation Backlog
The workflows ranked by hours spent, cost of errors and how feasible they are to automate.
04
Working Prototype
The top workflow from the backlog, running on your real data.
Read access only
The sprint runs on read access. The Working Prototype reads your data and writes nothing to your ERP.
It shows what the workflow can look like on your data. It is not yet software to run a desk on.
Stage 01
Discovery Sprint
Two engineers spend two weeks on your floor and in your front office. They map how the work really gets done and show the first automation working on your own data.
$25,000 fixed fee
- Duration
- 2 weeks on site
- Team
- 2 forward-deployed engineers
You get
- Operations Map
- Systems and Data Audit
- Automation Backlog, ranked
- Working Prototype of the top workflow, on your real data
03 Embedded Build
Working software every week
Work comes from the top of the Automation Backlog. Each workflow gets a workflow owner, and every week ends with a release to the people who use it.
The weekly rhythm
-
Plan with the workflow owner
On Monday they look at last week's measurements together, then agree on this week's change and on how they will know it worked.
-
Build beside the people it touches
Our engineers build the change and show work in progress to the people whose work it touches, on their own documents.
-
Release to the people who use it
The workflow owner signs off first. The release goes out at an hour agreed with them, away from the desk's busy times, and our engineers are at the desk for the first real work that goes through it.
-
Measure what went through
How many orders or invoices, how long they waited and how many needed a correction. The result opens next Monday's plan.
Stage 02
Embedded Build
Engineers work alongside your team and ship working software every week, starting from the top of the Automation Backlog.
$32,000 per engineer per month
- Duration
- Typically 3 to 6 months, with a 3-month minimum
- Team
- Typically 2 forward-deployed engineers
You get
- Software built around your workflows and attached to your ERP
- A release to the people who use it, every week
- Agents introduced workflow by workflow, starting at the lower levels of the autonomy ladder
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: a named employee of yours who decides how it should work and signs off changes
- The number of engineers and months
- The on-site schedule. Engineers are on site by default.
The proposal our engineers present at the readout names all four. Nothing starts until you have agreed to them.
Where agents start
Agents are introduced one workflow at a time, at the low levels of the autonomy ladder. That means Level 0 (Recorded), where people do the work and the software captures it, then Level 1 (Assisted), where an agent drafts and people still do the work.
Every move up, during the build or after it, takes a promotion review. How the autonomy ladder works
04 Operate & Automate
We run it, and workflows move up
After the build our engineers stay on call. They run and support what was built, and each workflow moves up the autonomy ladder only when a promotion review says it has earned it.
What the stage covers
Running and monitoring
We watch that work is moving through the queues, that every read and write-back to your ERP succeeded, and what each agent did.
Support
Faults, and the adjustments that keep a workflow working when the documents around it change, such as a customer's new purchase order layout.
Promotion reviews
A review is held as soon as a workflow is ready, remotely if need be. It does not wait for a calendar date or for the on-site week. It moves the workflow up one level and records what would send it back down.
One on-site week per quarter
Our engineers come back to sit with the people who use the software and go through the exceptions that keep repeating. A promotion review that falls near that week is held in person.
New workflows come from the Automation Backlog and are added by scheduling more Embedded Build time. Support response times are agreed in your contract. Your ERP, your network and your devices stay with your IT team and your ERP partner.
Stage 03
Operate & Automate
We run, monitor and support the software and the agents, and move each workflow up the autonomy ladder as it earns it.
From $9,000 per month
- Duration
- Monthly, after the build
- Team
- Your engineers stay on call, with one on-site week per quarter
You get
- Monitoring and support for the software and agents
- Promotion reviews that move workflows up the autonomy ladder
- One on-site week per quarter
05 What you provide
What each stage asks of you
An engagement depends on a sponsor, workflow owners, access and decisions within a week. It does not need a requirements document or a full-time project team.
| Stage | People | Access and decisions |
|---|---|---|
| Discovery Sprint | A sponsor on day 1, day 7 and day 10. Named people to shadow at the order desk, in purchasing, in accounts payable, in scheduling and in customer service. | The floor and the offices, a desk near the front office, a safety orientation on the first morning and read access to your ERP data. Before day one, a written agreement with your IT manager on which AI model provider the Working Prototype may use and where it runs. |
| Embedded Build | A workflow owner for each workflow, who plans on Monday and signs off each release. A sponsor who reads the weekly update and sets the order of the backlog. | Decisions within a week. Write access one workflow at a time, when that workflow is ready to write back, through your change control. |
| Operate & Automate | The same workflow owners, who sign off promotion reviews. The sponsor, for the backlog review when our engineers are back on site: one on-site week per quarter. | Notice before an ERP upgrade, or before anyone changes a field, a price list structure or an EDI map that a workflow reads. |
06 If you stop
You can stop after any stage
Nothing ties one stage to the next, and what was built for you is yours.
| If you stop after | You keep | What happens |
|---|---|---|
| Discovery Sprint | The Operations Map, the Systems and Data Audit, the Automation Backlog and the Working Prototype. | Our read access is removed. The deliverables are yours to use with your own team or with anyone else. |
| Embedded Build | All of that, plus the custom code, its data, the documentation and the runbooks. | In the final weeks of the build, an in-house team or another vendor shadows our engineers, then runs a release themselves. |
| Operate & Automate | The same, as it stands on the day we stop. | The same takeover happens before we stop running and monitoring. Then our access is removed. |
Ownership
You own the custom code and the data built for you. We keep our reusable tooling, and you keep the right to run and change the copy inside your software.
After exit we keep none of your data.
Next step
Start with a call with an engineer.
Tell us which ERP you run and the three workflows that hurt most. That is the whole first conversation.