B2Shift · Published · Updated
Automation quotes vary by an order of magnitude for what sounds like the same request, which makes comparison hard. The variance is not arbitrary — it tracks a small number of cost drivers that you can assess before you talk to anyone.
What actually drives the price?
Five things move the number more than anything else. Process complexity: how many branches, exceptions and edge cases the workflow contains. Data quality: whether the inputs are clean and machine-readable or need extraction, cleaning and reconciliation first. Integration count: each additional system means its own API, permissions, rate limits and failure modes. Security requirements: data residency, access control and audit obligations add real engineering. And the cost of being wrong: a workflow that drafts an internal summary needs far less safety engineering than one that issues refunds.
A narrow, single-workflow MVP is usually less costly than a multi-department platform. The gap depends on integrations, exception handling, data readiness and operating controls.
What do the stages cost?
Budget the three stages separately, because they behave differently. Discovery and audit is a fixed, bounded piece of work: at B2Shift it starts at €750 and produces a process map, a risk map, ROI assumptions and a recommended architecture. Implementation is where the variance lives: a focused automation MVP covering one working workflow with one or two integrations starts at €2,500 and takes two to four weeks. Ongoing operations is a recurring line item: monitoring, rule tuning and improvement start at €650 per month.
There is also a free tier that costs you nothing but thirty minutes: an opportunity call that establishes whether automation is the right answer at all. Complex or regulated environments — private deployment, security review, custom SLA — are quoted individually, because the honest answer depends on the review.
How does model usage fit into the wider cost?
Teams new to this often anchor on token prices. For a particular workflow, however, model usage is only one line alongside integration work, testing, monitoring and the internal effort needed to adopt it. Measure provider charges at the expected volume: document processing, long prompts or high case volume can change the balance.
Third-party platform fees deserve their own line. Orchestration tools such as n8n, Make or Zapier have their own pricing, as do the CRM, helpdesk and document systems being connected. Ask whether the quote includes them and who pays each supplier directly; pricing and billing arrangements vary.
How do you compare two quotes fairly?
Ask each supplier for the same three things: a measurable scope, the explicit assumptions behind it, and an operating plan for after launch. A quote without assumptions is not cheaper — it has simply moved the risk to you. A quote without an operating plan is a project, not a system, and unmaintained automations quietly degrade as the surrounding tools change.
One more question separates serious proposals from optimistic ones: what happens when the automation is wrong, and who finds out? A supplier who has thought about that has usually thought about the rest.
Worked 12-month AI automation TCO example
This illustration combines B2Shift's published starting prices with clearly stated assumptions for third-party and internal costs. The €120 monthly platform allowance and two hours of internal ownership at €35 per hour are examples, not vendor quotes or a forecast. Replace them with your actual plan, expected usage and loaded staff cost; confirm the scope and VAT treatment in a written quote.
The first-year TCO is €750 + €2,500 + 12 × (€650 + €120 + 2 × €35) = €13,330. It estimates cost only; it makes no claim about savings or return. Variable model, OCR, storage or overage charges are excluded and should be added when relevant.
| Cost line | Period and assumption | 12-month total |
|---|---|---|
| Bounded audit | One-time published starting price | €750 |
| Focused MVP | One-time published starting price | €2,500 |
| Ongoing operations | 12 × €650/month starting price | €7,800 |
| Third-party platform | 12 × €120/month illustrative allowance | €1,440 |
| Internal ownership | 12 × 2 hours/month × €35/hour illustrative loaded cost | €840 |
| First-year TCO | One-time + recurring lines above | €13,330 |
How to estimate the total cost of ownership
A useful AI automation budget separates one-time delivery from recurring operation. The implementation quote is only one part of total cost of ownership (TCO). Add the platform subscription, model or document-processing usage, monitoring, support, and the internal time needed to own exceptions. If a workflow replaces an existing tool or contractor, record that saving separately rather than subtracting it before the replacement is proven.
The table is a scoping checklist, not a price list. Some lines may be zero for a particular workflow; others can dominate the build. Ask each supplier to state what is included, what is billed directly by third parties, and what happens when volumes exceed the estimate.
| Cost line | What to count | Question to ask |
|---|---|---|
| Discovery | Process mapping, data review, security and acceptance criteria | Is discovery fixed-scope, and what deliverable will we keep? |
| Implementation | Workflow design, integrations, testing, deployment and handover | Which systems, exceptions and environments are in the quote? |
| Platform | Automation platform, hosting, database, backups and monitoring tools | Is this a monthly subscription, usage charge or infrastructure bill? |
| AI and data | Model tokens, OCR, transcription, storage and external APIs | What volume and model assumptions drive the estimate? |
| Operations | Alerts, incident response, tuning, dependency updates and support | Who investigates a failed run, and within what response window? |
| Internal ownership | Staff time for approvals, exception review and process changes | Who owns the workflow after launch, and how much time is reserved? |
| Change and exit | New requirements, migration, data export and decommissioning | Can we export workflows, credentials, logs and business data? |
A transparent way to compare implementation quotes
Do not compare two totals until the scope is made comparable. A proposal that covers one trigger, one happy path and a manual fallback is not equivalent to one that includes duplicate detection, retries, audit logs, permissions, monitoring and a tested rollback. Those differences are often more important than the choice of language model.
Ask each provider to describe the same workflow in the same format: input systems, expected monthly volume, normal path, exceptions, human decisions, security boundary, acceptance tests, owner after handover and excluded work. Request a low, expected and high usage scenario. If a provider cannot explain why its estimate changes across those scenarios, the uncertainty has not been resolved; it has simply been hidden in a single number.
B2Shift's published starting points are €750 for a bounded audit, €2,500 for a focused MVP and €650 per month for ongoing operations. These are starting prices for defined scopes, not a quote for every business. A useful proposal should connect its price to the systems, risk controls, test cases and operational responsibility it includes.
Where low-cost prototypes become expensive
A prototype can look inexpensive because it excludes work that production needs. Common omissions are handling expired credentials, rate limits, incomplete records, duplicate events, vendor outages and changes to source-system fields. If those cases are not tested, a team may discover the real cost only after a person has to repair data by hand.
Before accepting a low estimate, ask for a short failure walkthrough. What happens if the CRM accepts a record but the next system times out? Can the workflow retry without creating a duplicate? Does a human receive enough context to resolve the exception? Are logs available for the period the business needs? A clear answer may increase the initial quote while reducing the unplanned support bill.
Make the estimate specific enough to manage
A budget range is useful only when its boundaries are visible. Ask for the assumptions behind the low and high ends: number of systems, cases per month, model choice, review percentage, retention period and support hours. If one assumption changes, you should be able to see which cost line moves. Keep a small contingency for unknown integration behavior, but do not use contingency to conceal an unbounded scope.
For variable usage, estimate cost per completed business case as well as the monthly total. Include failed and retried runs when the platform bills for them, plus the work spent resolving exceptions. A low platform fee can coexist with a high operating cost if a person must frequently repair records or maintain a brittle workflow. Conversely, a higher plan can be cheaper overall if it includes a needed control or lowers support effort.
Use a pilot to replace assumptions with evidence
A pilot should have a capped duration, a named process owner and a baseline captured before the build. Record the number of eligible cases, time spent per case, exception rate, rework and the percentage that can safely be automated. Then agree what would justify rollout, what would trigger a redesign, and what would make the team stop.
Keep the pilot narrow enough that every result can be inspected. For example, automate intake and classification while leaving the final customer-facing decision with a person. This can measure data quality and routing accuracy without granting the system permission to commit the business to an outcome. Expand the scope only after the error path and owner are working in practice.
Questions to settle before signing
Confirm the source of every recurring fee, the expected volume behind it, and how you will be notified before an allowance is exhausted. Establish who owns credentials, where logs and backups live, how long records are retained, and what access a supplier needs. Agree who can approve production changes and how those changes are documented.
Finally, define a practical exit: exportable workflow definitions, documentation, data ownership, credential revocation and a person who can operate the process without the original builder. These are not edge cases reserved for enterprise procurement. They are part of the cost of choosing any system that becomes important to day-to-day work.
- Usage unit, forecast volume, overage behavior and notice thresholds.
- Named owners for credentials, monitoring, exception review and production changes.
- Log retention, backup location, supplier access and data deletion terms.
- Export format for workflow definitions and business data, plus a named exit owner.