Skip to content
The GrowthCred field guide

What drives the cost of AI automation?

What will AI automation cost you? It depends on the workflow and everything around it. A drafting assistant and a connected operational system are different projects. I quote after scoping. So I'm not going to invent a standard price here.

By Phila Ngwenya · Reviewed

Separate setup from running costs

Setup might cover process mapping, configuration, integrations and testing. Running costs might cover subscriptions, usage charges and support. Ask for them separately. Otherwise a cheap first quote can hide an expensive monthly bill from you.

Third-party prices change. Check the current price of every tool in your scope. Not an old screenshot. Not a generic monthly figure.

The main scope drivers

A good quote needs enough detail to understand the work. The number of tools is only part of it. Exceptions, review and maintenance often cost you just as much. Answer these before you ask anyone for a price.

  • Process: how many steps, roles and approval points?
  • Data: is it complete, consistent and accessible?
  • Integrations: are supported APIs and permissions available?
  • Volume: how often will it run and how much information is processed?
  • Quality: what must be checked and what happens on failure?
  • Support: who monitors, updates and resolves problems?

Prepare a useful brief

Describe the task. How often it happens. The systems you use. The result you expect. Bring one redacted input and one good final output. List what must stay with a person, and the exceptions you hit most.

An internal report once a week is a different job from answering your customers all day across channels. So don't use one project's price to guess the other's.

Work out the return, carefully

Estimate the time saved after review and corrections. Then compare it with setup and running costs. Keep what you expect apart from what you've measured. And remember, time isn't automatically revenue.

Here's the maths. Four hours saved a week, across 48 working weeks, is 192 hours a year. Is that worth it? It depends what your team does with those hours. My calculator shows its assumptions, so you can test your own numbers.

Agree acceptance before building

Before anything's built, agree the example tasks it must handle. What a good output looks like. What happens when it fails. Who signs off. Write down what's excluded and how changes work. Now you can compare quotes. And you can judge the delivery.

Send me a short description of your workflow. We'll talk about whether a build or training is the better start. Keep confidential records out of that first message.