Your first AI agent, with 30 days of post-launch support included.—days—hrs—min—secExplore offer

Implementation & costs

What does AI implementation actually cost?

The useful budget is the cost of a working operation, not just the cost of generating an answer. Start with one workflow and count what it takes to keep that workflow reliable.

The practical answer

There is no meaningful universal price for AI implementation. Budget the initial delivery, recurring software and usage, human review, maintenance and the cost of handling failures. Compare quotes against the same scope and acceptance criteria.

Concept illustration of a structured AI decision workshop.
AI-generated concept illustration; not a client photograph.
Build the budget in three layers
  1. Deliver

    Discovery, data preparation, integrations and acceptance testing.

  2. Operate

    Licences, usage, support and the team’s review time.

  3. Change

    New cases, supplier changes and regression tests.

1. Define the workflow before requesting a price

“Automate onboarding” can mean sending a welcome email or reconciling documents across several systems. Write down the trigger, input, output, users, connected tools and the decision that remains with a person. Include the exceptions that regularly consume time.

Ask each provider to quote the same bounded version. Specify whether migration, historical records, security review, training, documentation and support are included. A cheaper quote that leaves these tasks to your team is a different offer.

2. Use a total-cost model you can challenge

For a chosen period: total cost = initial delivery + software and infrastructure + model usage + human review + support and maintenance + agreed change work. Keep the assumptions beside the calculation so that a change in volume does not become a surprise.

Cost lineWhat to includeWhat to ask
Initial deliveryProcess mapping, data cleanup, implementation, testing, handover.What deliverables and acceptance tests are included?
UsageModel calls, extraction, retries, storage and environments.What is the measured cost per completed case, including failures?
PeopleReview, exception handling, training and process ownership.Who reviews cases and how much time is allocated?
MaintenanceMonitoring, regression checks, supplier and integration changes.What response, repair and change work does support cover?

3. Compare two implementation scopes

Scenario A: draft a structured summary from an incoming enquiry and let a person copy approved information into the CRM. There is one input channel, one output format and no automatic change to customer records. The main work is input handling, summary evaluation and the review screen.

Scenario B: classify enquiries, check duplicates, enrich existing records and synchronise several systems after approval. This adds permissions, conflicting updates, retries and reconciliation. The model may be similar, but the delivery and maintenance scope is larger. Get a scoped quote for each scenario rather than applying an invented price range.

4. Compare value with the full operating cost

Measure the current process before estimating savings. Useful inputs are cases completed, handling time, waiting time, rework and error consequences. Value depends on what the team does with released capacity; minutes saved do not automatically become cash savings.

Model a normal month and a difficult month with more exceptions or review. Keep a manual fallback in the estimate. If the business case only works when every response is correct and no person checks it, the scope is not yet robust enough.

5. Leave the scoping conversation with a decision

A useful quote states assumptions, deliverables, ownership and what happens after launch. Decide which part is fixed, which part varies with usage and which changes require a new agreement. Confirm billing currency and taxes in the proposal rather than assuming that UK and US budgets are directly comparable.

  • An explicit input/output scope and representative test cases.
  • Named responsibilities for access, review, incident handling and maintenance.
  • A handover plan covering accounts, documentation and recovery.
  • A way to stop or reduce usage if cost or quality moves outside agreed limits.

Separate setup from ongoing operation

Record the current manual cost, implementation quote, licences, usage, review time and support separately. Use your own volumes and rates; do not count time saved as cash unless that capacity can actually be redeployed.

Budget worksheet (CSV)

Download the table shown above. Replace illustrative records with authorised examples from your own workflow; this is a working template, not an assessment of your business.

Budget worksheet (CSV)

References and further reading

Khalid Boudrari

Entrepreneur and AI consultant, I help service businesses improve their operations. I turn software choices into practical plans. My team at Klicky builds what we decide.

Khalid Boudrari

Bring a workflow. Leave with a scoped next step.

If the use case is still unclear, start with the decision. If inputs, owners and acceptance criteria are already known, discuss delivery with Klicky.