Skip to content

Pricing

Three stages, priced in the open

Every stage has one price line, and all three are on this page. What you pay for is our engineers' time on your floor and at your desks, and you can stop after any stage.

01 The three stages

One price line per stage

These three lines are what we charge for our work. Travel and AI model usage are billed at cost, on top. Hosting, and any extra ERP licenses your vendor requires for the accounts our engineers and agents use, are not in our prices: your contract covers them.

  1. 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
  2. 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
  3. 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

02 Fixed and variable

What is fixed and what varies

The first two rates are fixed. The third is a starting price: the fee depends on how many workflows we run and support, and the proposal states it before you commit. What else varies is how many engineers, for how long, and the two costs billed at cost.

What is fixed and what varies in each stage
Stage Fixed Varies
Discovery Sprint The fee, the length (2 weeks on site), the team (2 forward-deployed 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 one on-site week per quarter. The monthly fee: this page shows where it starts, and the proposal states yours before you commit. Travel and AI model usage.

03 Other terms

The terms beside the prices

Three terms apply in every stage. The rest is agreed in each contract.

  1. Travel is billed at cost. That covers our engineers' trips to your site in every stage, the Discovery Sprint included. The on-site schedule is agreed before a build starts, so you can see the travel it implies in advance.
  2. AI model usage is billed at cost. The Working Prototype in the Discovery Sprint calls an AI model, and so does every agent after it. We pass on what the provider charges for that usage, as it is. 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).
  3. 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. What you own includes the four deliverables, the software built around your workflows in the operations layer, what was built for each agent and the data they hold. The reusable tooling supplies the common parts: the work queue, the approval screens, the audit trail and the stop switch.

Agreed in each contract

Support response times, hosting location and security terms, among others. This page states no specifics for them, because they are set with you.

What your contract records, in the docs

Who this is priced for

US manufacturers and wholesale distributors with $30M to $500M in annual revenue, typically 100 to 1,500 employees.

Signs that it fits, and signs that it does not

04 An example

What one engagement adds up to

The fee for an Embedded Build is the monthly rate multiplied by the number of engineers and the number of months. Here is one engagement worked through.

Illustrative example

A typical shape for a first engagement. It is not a quote and not a specific client.

Discovery Sprint
$25,000
Embedded Build, 2 engineers, 4 months
$256,000
Both stages
$281,000
Discovery Sprint
$25,000 fixed fee. 2 forward-deployed engineers, 2 weeks on site.
Embedded Build
2 engineers for 4 months at $32,000 per engineer per month: $256,000.
Both stages
$281,000, before travel and AI model usage.
After the build
Operate & Automate, if you choose it: from $9,000 per month.

Travel is billed at cost. AI model usage is billed at cost. Neither is in this total.

The proposal at the readout names the workflows your build will cover and the level each is planned to reach, with the number of engineers and months. All of it is agreed before the build starts.

05 Questions

Questions about price

What does the Discovery Sprint fee cover?

The fee covers 2 forward-deployed engineers for 2 weeks on site, and the four deliverables: the Operations Map, the Systems and Data Audit, the Automation Backlog and the Working Prototype of your top workflow on your real data.

You keep all four whether or not you continue. Travel is billed at cost. AI model usage is billed at cost. In this stage the usage is only the Working Prototype's.

Is travel included?

No. Travel is billed at cost. That holds in every stage, including the fixed-fee Discovery Sprint.

Engineers are on site by default in the Discovery Sprint and the Embedded Build, and for one on-site week per quarter in Operate & Automate. The on-site schedule for a build is agreed before it starts, so you can see the travel it implies in advance.

How many engineers and months does a build take?

Typically 2 forward-deployed engineers. Typically 3 to 6 months, with a 3-month minimum.

The number for your build is proposed at the readout, from the top of your Automation Backlog, and agreed before the build starts. A build ends on the date agreed, not when the backlog is empty.

Why does Operate & Automate start "from" a price?

Because the fee depends on how many workflows we run and support. The price line shows where it starts, and the proposal states your fee before you commit.

The fee covers what the stage lists: monitoring and support for the software and the agents, promotion reviews, and one on-site week per quarter. New workflows are added by scheduling more Embedded Build time, at the Embedded Build rate.

Is there a license fee?

No. There is no product to license and install. You pay for the stages above.

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.

Your contract puts it in writing: where the software built for you includes parts of our reusable tooling, you have the right to keep running and changing that copy after we leave, with no license fee.

Data ownership and portability

What if we stop after a stage?

You can stop after any stage. After the Discovery Sprint you keep its four deliverables. After a build you also keep the custom code, its data, the documentation and the runbooks.

Handover and exit

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.