Engagement & Pricing

Pay for jobs done, not software seats.

A one-time build fee, then a fee per completed outcome. If the agent isn’t doing the work, you aren’t paying for it.

Book a working sessionFind your top 3 agents (3 min)

How an engagement runs

Six steps, in this order. Each one ends with something you can read and sign off.

  1. Working session

    You bring one process and real examples — anonymised is fine. We tell you plainly whether an agent can do it, and what "done" means.

  2. Scope & price

    We agree the outcome unit, what counts as complete, the approval limits and the build fee — in writing.

  3. Build

    We connect to your systems with scoped access, write your rules down, and test on your past documents.

  4. Shadow mode

    The agent drafts alongside your team until the numbers say it is ready.

  5. Live, per outcome

    You switch it on for the work it has proven on. Billing starts per completed outcome.

  6. Next agent

    Built on the same layer, so it is faster. It already knows your customers, items and rules.

Every agent starts in shadow mode.

For the first stretch it watches the work and drafts what it would do, while your team keeps doing the job. You compare its drafts to what your people actually did.

It only starts acting when you say so — and only on the kinds of work it has proven it gets right. Anything above a limit you set (a dollar amount, a new customer, a price change) still comes to a person.

Two parts: build, then outcomes

One fee to build the agent. Then a fee for each job it finishes, counted in your own system.

1. Build fee

Covers connecting your systems, mapping your items, customers and rules, testing on your history, and shadow mode.

2. Per-outcome fee

After the build, you pay per unit of work the agent actually completes. The unit is agreed up front and it is something you can count.

AgentYou pay per
Order Entry Agentsales order entered
Quote-to-Cash Agentquote drafted and sent
AR & AP Agentpayment applied; vendor bill matched
Supplier Onboarding & Compliance Agentsupplier onboarded; document renewed
Customer Service Agentticket resolved without a person
Inbound Sales Agent (Lead-to-Quote)inquiry qualified
Reactivation Agentaccount reactivated (order placed)
Upsell & Cross-sell Agentadd-on line accepted
Product Catalog & PIM Agentlisting completed
AI Reporting & Dashboardslive view set per month; Monday brief delivered
  • What counts as "done" is written down before we build. If a person had to redo it, it doesn't count.
  • You see the count every day, in the same action log the agent writes.
  • Why no prices here? Volumes and complexity vary too much between businesses for a list price to mean anything. We give you a written price after the working session.

Why we price it this way

Our incentives match yours

We only earn when the agent does real work, so we build for accuracy, not for demos.

No platform licence

You're not buying seats for people who'll never log in. There is nothing to roll out to your team.

Low risk to start

Shadow mode means you see the agent's work on your own data before it acts in your systems.

Compared with the alternatives

A description of what each option changes, not a claim about results.
Hire another personBuy another SaaS toolAgent, per outcome
Cost grows withHeadcountSeats and tiersCompleted jobs
Works inside your current systemsYesUsually adds another systemYes
Handles the messy exceptionsYesRarelyRoutes them to your people with context
Fits your processLearns your way of doing itYou fit its process — the agent comes out of the boxBuilt around your approval points, part numbers and exceptions
Ramp-upHiring and trainingImplementation and adoptionShadow mode on your data

Do the 3-year math yourself →

What we need from you

  • One owner on your side who knows the process end to end.
  • Read access to sample documents and history — POs, invoices, quotes, remittances.
  • A test or sandbox login where your systems have one.
  • An hour a week from the people who do the work today, during shadow mode.

That is the whole list. No project team, no steering committee, no new system for your people to learn.

Works in the systems you already run

  • NetSuite
  • Acumatica
  • Sage
  • Odoo
  • QuickBooks
  • Xero
  • Zoho
  • Shopify
  • Amazon
  • EDI
  • WMS
  • Outlook & Gmail
  • Spreadsheets

Plus bespoke and legacy systems — if your team can log into it, we can usually work with it.

Questions & Answers

FAQs

We agree a minimum monthly volume or term during scoping, so the build fee makes sense for both sides. It is stated in writing before you sign.

You pay for fewer outcomes. That is the point of the model — the cost follows the work, not a seat count.

Your data, your rules and your action log are yours. The terms for the code and the shared layer are set out in the agreement, and we walk you through them before you sign.

Yes — for reporting and integrations, where a per-outcome unit doesn't make sense. We'll say so in the working session rather than force the job into the wrong model.

It's included while you're paying per outcome. Keeping the agent accurate is how we get paid, so there is no separate support contract to negotiate.

Whatever we wrote down before the build — an order entered, a payment applied, a vendor bill matched. If a person had to redo it, it does not count, and you can check the count yourself in the action log.

Bring one process to a working session

We'll tell you whether an agent can do it, what the outcome unit should be, and what it costs to build. In writing.

Book a working sessionFind your top 3 agents (3 min)