Skip to content
Engagement models

Priced against what it removes, not against hours

Everything here is an indicative range, because the honest answer depends on integration complexity, data quality and how many exception paths the process has — none of which are knowable before an assessment. The range narrows to a fixed price in week two, and we hold it unless you change the scope.

Assessment

$18,000 – $45,000

Fixed fee, 2–4 weeks

Build

$85,000 – $400,000

Milestone-based, 6–20 weeks

Managed

From $2,500 / month

12-month initial term

Assessment

Know which automations will pay before you commit build budget.

$18,000 – $45,000

Fixed fee, scoped to the number of functions in review.

Typical duration: 2–4 weeks

Who it is for

Organisations with an approved automation budget and no agreed target, or with a pilot that produced no measurable return.

Discuss an assessment

What is included

  • Measured baseline for every process in scope — volume, touch count, cycle time, exception rate
  • Fully loaded cost per transaction, reconciled against payroll and finance data
  • Ranked candidate portfolio with a consistent economic model
  • Value-versus-feasibility view across the business
  • Investment, savings, payback and three-year ROI per shortlisted initiative
  • Sensitivity analysis on the assumptions that carry the most risk
  • Sequenced multi-wave roadmap with owners and success measures
  • Executive board pack with the methodology documented

What is not

  • Building or deploying automation — this engagement produces the decision, not the system
  • Vendor selection or procurement negotiation

Outcome

A costed, ranked roadmap you can execute with us or with any other supplier.

Most common

Build

Design, integrate and land automation in production.

$85,000 – $400,000

Milestone-based, priced against measured savings.

Typical duration: 6–20 weeks

Who it is for

Organisations that know which process to automate and need it built against real systems within a defined window.

Scope a build

What is included

  • Process design, exception taxonomy and decision logic documented and tested
  • Integration against ERP, CRM, ITSM and document stores
  • Extraction and classification with confidence thresholds where input is unstructured
  • Human review queue for exceptions with full source context
  • Purpose-built internal application or agent interface where the process needs one
  • Identity integration (SSO/SAML/SCIM) and least-privilege access model
  • Test suite on the critical paths, CI/CD pipeline, environment strategy
  • Architecture documentation and a formal handover walkthrough

What is not

  • Ongoing monitoring and support after the warranty period — see Managed Automation
  • Third-party licence costs for platforms and model providers

Outcome

Working automation in production, documented and ready for your team to own.

Managed automation

We run it, report on it, and grow the coverage quarter by quarter.

From $2,500 / month

Scaled to process coverage, transaction volume and support hours.

Typical duration: 12-month initial term

Who it is for

Organisations that would rather buy an operated capability than staff a platform team, or that want the return protected while it compounds.

Discuss managed delivery

What is included

  • 24/7 monitoring with alerting on failure, drift and volume anomalies
  • Failed-run replay and incident response against agreed response times
  • Named support path with escalation and a quarterly service review
  • Throughput, accuracy and cost-per-transaction reporting
  • Continuous tuning of thresholds, rules and extraction quality
  • Quarterly coverage review identifying the next highest-value process
  • Platform maintenance, dependency patching and model version management
  • Full handover to your team on request, at no additional cost

What is not

  • Building new processes from scratch — those are scoped as Build projects
  • Cloud infrastructure consumption, billed at cost

Outcome

A running capability with a reported, compounding return and a support path you can hold us to.

Commercial terms

How the commercial relationship actually works

These are the things that usually take three procurement cycles to establish. Better to have them on the table before the first call.

Milestone-based, not time-and-materials

You pay on delivery of agreed milestones. If the work takes longer than we estimated, that is our problem, not an invoice.

A performance milestone on build work

The final payment on a build engagement is tied to hitting the coverage and accuracy targets agreed at the end of modelling. Miss them and it is not due until we fix it.

Savings-linked pricing available

On larger engagements, part of the fee can be structured as a share of measured savings, using the same instrumentation the operations dashboards read.

Infrastructure at cost, no markup

Cloud and model consumption is passed through at cost and reported monthly, so you can see exactly what the automation costs to run.

You can stop after any phase

Assessment, build and managed operation are independent. Take the roadmap elsewhere, or take the codebase in-house — there is no licence that expires.

IP is yours, handover included

Custom code, infrastructure definitions and documentation transfer to you. Handover is a deliverable, not an upsell.

Pricing questions

The commercial questions, answered directly

Including the two that determine whether an engagement is worth having at all: what happens if the savings do not materialise, and whether we will price against them.
Why do your prices come as ranges?
Because the honest answer depends on integration complexity, data quality and the number of exception paths — and those are things we only know after the assessment. The range narrows to a fixed price after week two of an engagement, and we hold that figure unless you change the scope.
Can you price against the savings instead of a fixed fee?
On larger Build and Managed engagements, yes. We will structure part of the fee as a share of measured savings, with the baseline agreed up front and measured against the same instrumentation the operations dashboards use. This only works where the baseline is genuinely measurable, which is most of the time.
What if the project does not deliver the modelled savings?
Build engagements carry a performance milestone tied to the coverage and accuracy targets agreed at the end of the modelling phase. If we miss it, the final milestone payment is not due until we fix it. We do not offer this on forecasts we cannot instrument.
Do you work on a retainer for small pieces of work?
Not as a standing arrangement. Small pieces of work are usually symptoms of an unmeasured process, so we would rather scope a short assessment. The exception is existing Managed clients, where adjacent changes are absorbed into the monthly service.
What are the ongoing costs we should expect?
Cloud infrastructure (typically a few hundred to a few thousand dollars a month depending on document and transaction volume), any model API usage, and managed support if you take it. We report infrastructure consumption at cost with no markup, so you can see exactly what the automation costs to run.
How do you handle payment terms?
Assessment is paid 50% on kickoff and 50% on delivery of the roadmap. Build is milestone-based, typically four to six milestones with a final performance milestone. Managed is billed monthly in advance. Standard terms are net 30.
Loading bay and distribution operation

Bring us the process you already know is costing too much

Thirty minutes with an engineer is usually enough to tell whether it is worth automating, roughly what it would save, and whether the payback is inside a window your finance team will accept. If the answer is no, we will say so on the call.

SOC 2 Type IIISO 27001GDPR & UK GDPRHIPAA-aligned deliveryAWS & Azure partnersCyber Essentials Plus