An AI automation budget needs to separate the decision to invest, the work to build, and the cost of operating the workflow afterwards. A low build quote is not necessarily a low total cost; an inclusive monthly bill is not necessarily unlimited support.
This guide explains how to compare those costs. It is not a survey of UK market prices or an Elevate AI rate card. Our current pricing approach is proposal-led: paid consulting produces a roadmap you own, and any implementation is scoped separately.
The four parts of an automation budget
| Cost line | What it buys | What to clarify |
|---|---|---|
| Consulting | Discovery, priorities, solution concepts and a costed roadmap. | Deliverables, investigation depth, ownership and timetable. |
| Implementation | The agreed build, testing, documentation and handover. | Systems, exceptions, acceptance criteria, exclusions and defect-correction terms. |
| Running costs | Hosting, platform subscriptions, AI/API usage and other required services. | Account owner, billing party, usage assumptions, limits and variable charges. |
| Ongoing support | Agreed monitoring, maintenance and defined adjustments to live workflows. | Coverage, response expectations, change allowance, start date and notice terms. |
Include your team's time for supplying examples, testing and training. State the VAT basis consistently when comparing supplier quotes. A forecast should also show any costs that continue if volumes grow or you stop using the original delivery provider.
Why implementation prices differ
The number of steps in a demo is a poor proxy for build effort. A workflow that reads one clean document is different from one that handles varied formats, matches existing records, detects duplicates, routes exceptions and recovers safely from failed updates.
- Inputs: are records consistent, complete and available in an accessible format?
- Integrations: are the necessary operations supported by the systems, permissions and subscription tiers you already have?
- Consequences: does a mistake create a draft for review, alter a financial record or send something externally?
- Exceptions: which failures can be retried safely, and which need a person?
- Handover: who will operate the workflow, and what documentation and training will they need?
Ask for these assumptions in the scope. If an integration has not been tested, the proposal should identify that uncertainty rather than promise a fixed outcome without qualification.
How staged implementation protects the next decision
Our electrical-contractor roadmap case study describes completed consulting that produced phased concepts, indicative costs, dependencies and approval points. The roadmap gave the business a basis for choosing what to implement; it was not a commitment to build every proposed phase.
Apply that principle to your budget: agree the next phase's scope, acceptance criteria and price, then reassess the following phase using what you learn. Distinguish a programme estimate from an approved order. A pilot is useful when it answers a specific uncertainty, not simply because every project is expected to have one.
What is an automation support retainer for?
The build fee pays for the agreed working system and handover. A separately agreed retainer pays for defined care of the live workflows: for example monitoring failures, investigating a changed connection and making permitted small adjustments. It should not be used to charge twice for unfinished original scope.
Consider an illustrative inbox-to-job-record workflow. A supplier changes its order layout, a connection expires or an update fails after a retry. The support agreement should explain how that event is noticed, who investigates, what happens to the affected order and when additional work needs a quote.
- Name the workflows and systems covered.
- Specify monitoring checks and the manual fallback.
- Distinguish response time from a promised resolution time.
- Define the allowance and boundaries for small changes.
- Separate defects, maintenance and new development.
- Agree when billing starts, review points and notice terms.
If you do not take ongoing support, establish who will monitor and maintain the workflow instead. Where an IT company or existing software partner is involved, agree the boundaries so responsibilities are neither duplicated nor left unassigned.
Should AI usage and hosting be included in the retainer?
Either an inclusive fee or separate billing can work. What matters is visibility of the allowance, ownership and consequences of higher usage. A predictable invoice should not conceal an uncapped variable cost.
Ask which accounts belong to the client, which services belong to the provider, who receives each bill and how access is handed over. Bundling costs does not require pooling client data or transferring ownership. Billing options also depend on each platform's arrangements.
For usage-based AI, document expected monthly volume, the allowance and what happens before an overage is incurred. Include retries, larger documents and exception processing when testing the estimate. Do not assume a fixed cost per job until representative usage has been measured.
A transparent first-year budget example
Illustrative arithmetic, not an Elevate quote or a client result: assume consulting of £1,500, a build of £6,000, and combined operating/support costs of £300 a month for twelve months. The first-year total is £11,100 before VAT and internal staff time. Different go-live dates or separately billed software will change the calculation.
Do not add platform charges twice if they are already included in the monthly figure. Do include them if the proposal excludes them. Compare this total with a conservative benefit estimate using our ROI calculation guide.
How Elevate AI separates its offers
AI Consulting produces a client-owned roadmap; subsequent implementation is agreed separately. The Outbound Sales Engine is a different offer: a managed outreach service with configuration and monthly fees, not ownership of our reusable engine. Its proposal and service terms govern the engagement.
Use our quote comparison checklist to compare like-for-like scope. To discuss your own requirements, book a free scoping call. The call establishes fit; the detailed analysis and roadmap are paid work.
