Skip to content

Embedded Build

The Embedded Build is stage two: our forward-deployed engineers work alongside your team and release working software every week, starting from the top of the Automation Backlog. This page covers the weekly rhythm, how work is chosen, how your people are involved, how releases reach the floor, how progress is reported and when the build ends.

Four things are agreed after the readout and before the first week. The proposal our engineers present at the readout names all four:

  1. The workflows the build will cover, taken from the top of the Automation Backlog, and the level each is planned to reach.
  2. A workflow owner for each: a named employee of yours who decides how the workflow should work and signs off changes.
  3. The number of engineers and months. A build typically has two engineers and runs three to six months, with a three-month minimum.
  4. The on-site schedule. Engineers are on site by default.

Every week has the same four steps.

  1. 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.
  2. Build. Our engineers build the change. They sit with the people whose work it touches and show them work in progress on their own documents.
  3. Release to the people who use it. The workflow owner signs off first.
  4. Measure. The engineers count what went through the workflow that week: how many orders or invoices, how long they waited and how many needed a correction. They compare that with the week before and with the baseline from the Discovery Sprint. The result opens next Monday’s plan.

A week on site walks through one such week day by day.

The order comes from the Automation Backlog, which ranks workflows by hours spent, cost of errors and how feasible they are to automate. The build starts at the top. The Working Prototype was built for the top workflow, so the first weeks turn that prototype into software your team can rely on every day.

Within a workflow, each week’s change is the smallest piece people can use on real work. For sales order entry that could be a screen that records every order and every correction, then an agent that drafts the order from the emailed purchase order, then the handling for one kind of exception at a time.

The sponsor can reorder the backlog at any time, and our engineers say what the change costs in weeks. New ideas go into the backlog and get ranked. They do not skip ahead.

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. The autonomy ladder covers the levels.

Who What they do in a build week
Workflow owner Plans on Monday, answers questions during the week, signs off each change before release, decides when an old spreadsheet or inbox is retired
The people who use the software Are shadowed before anything is built, try work in progress on their own orders or invoices, get a walkthrough at their desk on release day, say what is wrong
Sponsor Reads the weekly update, sets the order of the backlog, settles decisions that cross departments
IT manager or ERP administrator Grants access, takes any change that touches the ERP through your change control

What people correct is the most useful input the build gets. When your order desk changes a draft, the software records the correction, and the corrections that repeat become next week’s plan.

Decisions are needed within a week. With a release every week, a question that waits longer holds one up.

  1. The change is tested before it reaches anyone’s desk.
  2. The workflow owner signs off.
  3. It is released on a day and at an hour agreed with the workflow owner, away from the desk’s busy times. Accounts payable does not get a release during month-end close.
  4. Our engineers are at the desk for the first real work that goes through it.
  5. The old way stays available until the workflow owner retires it.

If a release causes trouble, it is rolled back. Releases and change control covers test and production, approval and rollback. A change inside the ERP itself goes through your change control, as described in Working with your IT team and ERP partner.

Progress is reported in writing every week, to the sponsor and the workflow owners. The update has four parts:

  • What was released this week.
  • What the measurements show against the baseline from the Discovery Sprint.
  • What is planned for next week.
  • Which decisions are waiting on you, and since when.

The Automation Backlog is kept current. It always shows which workflows are in use, in build or not started, with the ladder level of each. There are no status slides.

A build ends on the date agreed before it started, not when the backlog is empty. The backlog can be longer than one build. In the final weeks our engineers complete the documentation and runbooks they have written as each workflow went into use. Then you choose:

  • 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.

The rate for the Embedded Build is on the pricing page.