Skip to content

Engagement models

Start small. Prove it. Then scale.

You will not find a rate card here, because an honest number depends on your process, your systems and your volumes. What you will find is exactly what each stage delivers and what is excluded.

Three models

What each stage delivers,<br />and what it excludes.

Discovery is a fixed fee, the pilot is a fixed price, production is a monthly retainer. Nothing is billed until the scope is written down and you have approved it.

Discovery sprint

Fixed fee · 1–2 weeks

You know something is automatable but not what it is worth

  • Process mapping with the people doing the work
  • Baseline metrics and cost-per-transaction model
  • Automation candidates ranked by value and risk
  • Written blueprint and fixed-scope pilot proposal

Commercial Fixed fee, credited against the pilot if you continue

Pilot

most common

Fixed scope · 2–4 weeks

You want proof on your data before committing a budget

  • Working system on production-shaped data
  • Human review queue and escalation rules
  • Evaluation set with measured accuracy and cost
  • Go / no-go recommendation, including “no” if that is the honest answer

Commercial Fixed price per pilot, agreed before we start

Build & operate

Monthly · from production to steady state

You want the system in production and someone accountable for it

  • Production deployment in your cloud or ours
  • Monitoring, evaluation runs and drift review
  • Incident response with an agreed response time
  • Monthly quality and cost report, quarterly roadmap

Commercial Monthly retainer with a defined scope and exit terms

A desk with a laptop and monitor overlooking a city skyline at dusk

Not sure which one fits?

Bring one process to a 45-minute call. We will tell you what it is worth automating, what we would charge for discovery, and whether the honest answer is “leave it alone”.

What the discovery fee buys

Six artefacts, whether or not you continue.

  • Process map with volumes — How the work actually flows today, with cycle times and error rates per step
  • Baseline metrics — Four weeks of your own data, so “better” has a starting number
  • Automation candidates ranked — Value against effort and risk, including the ones we would not touch
  • Cost model per item — What each automated transaction costs to run, compared with today
  • Architecture and model choice — Why this model, this workflow engine, this review pattern
  • Fixed-scope pilot proposal — Deliverables, dates, price and the go / no-go criteria

What is never included

No hidden margin on your infrastructure.

  • Hosting and third-party model usage — passed through at cost, no markup
  • Licences for software you decide to buy (workflow engine, warehouse, vector store)
  • Change management inside your organisation — we advise, we do not own it
  • Anything outside the agreed scope: new scope gets a written change note and a price

Our principle We charge for engineering judgement, not for reselling tokens or licences. If a cheaper model or a simpler non-AI approach does the job, we will say so.

Straight answers

Budget questions

No “contact us for details”. If the answer is “it depends”, we say what it depends on.

How quickly can we see something working?

Pilot in two to four weeks from kickoff, including discovery and blueprint. That assumes we get read access to a sandbox and a sample of real documents or tickets in the first week — that sample is the usual cause of delay.

What does it cost?

Discovery is a fixed fee, the pilot is a fixed price, and production is a monthly retainer with a defined scope. We quote after discovery because the honest number depends on your process, not on a price list. If a process is not worth automating, we say so and charge only for discovery.

Do we need to replace our systems?

No. We integrate with what you run — ERP, CRM, ticketing, data warehouse, and the legacy application with no API. Replacing your core systems is a different project and usually a worse idea than automating around them.

Which models do you use?

Whatever the task and your constraints justify: frontier APIs where quality matters most, open-weight models you can self-host where data cannot leave your environment, and classical methods where a model is the wrong tool. We benchmark on your data during the pilot and document why we chose what we chose.

Next step

Get a scoped number, not a range.

Send one process with its rough monthly volume. On the call we will give you a discovery price and a realistic pilot budget before you commit to anything.

One business day — and the reply comes from an engineer, not a sales sequence