How much to charge for an AI automation
How much to charge for an AI automation comes down to one measurement: how many hours of someone's month does it remove, and what does an hour of that person cost the business? That monthly value is your anchor. Quote a fixed setup fee that sits well below the first year's saving, add a monthly run fee on top because automations do not stay working on their own, and price each connected system as its own line. Never quote build hours. A client who hears the build took a day will price it like a day's work, no matter how much it saves them.
This is the CCC Hours-Removed Method, and it exists because automation is the offer where builders undercharge most. The build looks small, so the price comes out small, and the client quietly pockets thousands in saved labour every month while you collected a one-time fee that did not cover the third support ticket.
Measure the hours before you say a number
You cannot price an automation you have not measured, so the first call is a measurement call, not a pitch. Four questions get you there: who does this task today, how often does it happen, how long does each one take, and what happens when it is done late or wrong? The answers give you hours per month and a cost per hour. Multiply them and you have the monthly value of the automation in the client's own numbers, which is the only kind of number they cannot argue with.
- Ask for a real week, not an estimate. "Walk me through last Tuesday" surfaces the copy-paste steps people forget they do.
- Count the error cost separately. A task that takes twenty minutes but occasionally costs a lost order is worth far more than its minutes.
- Note who is doing it. Two hours a week of the owner's time is priced very differently from two hours of an assistant's.
- Write the number down and say it back to them before you quote. Once the client has agreed on the value, the price is a fraction of a number they already accepted.
If you want the full question set, [client discovery questions before you quote](/blog/client-discovery-questions-before-you-quote) has the version I run on every deal.
The three parts of an automation quote
An automation is not a website. It runs every day, it depends on other people's software, and it fails silently when one of those tools changes. So the quote has to have three parts, and each one has a job.
The CCC Hours-Removed Method: what goes on the quote
| Part | What it covers | How to set it |
|---|---|---|
| Setup fee | Discovery, the build, testing against real data, handover | A fixed price that is a clear fraction of the first year's saving - big enough to feel serious, small enough to be an obvious yes |
| Monthly run fee | Monitoring, fixing breakages when a connected app changes, usage costs, small adjustments | Priced against the monthly value; includes a stated volume so a spike becomes an upgrade conversation |
| Integration lines | Each system the automation reads from or writes to | One line per system with its own price, so the next system is an upsell rather than an argument |
The monthly fee is the part people drop, and it is the part that decides whether the deal makes money. Every connected app will change its login, its export format, or its API eventually. If there is no monthly, that fix is a free favour and the third free favour is where the relationship sours. The recurring logic is the same as [how to price a maintenance retainer](/blog/how-to-price-a-maintenance-retainer), with a harder floor underneath it because the automation really does stop working without you.
What moves an automation quote up or down
- Number of systems connected. This is the biggest driver. Each system is its own scope, its own failure mode, and its own line on the quote.
- Cost of an error. An automation that sends invoices or touches customer records carries a higher price than one that files reports, because being wrong costs the client real money and you will be asked to guarantee it.
- Human-in-the-loop steps. A review step before anything is sent is safer for the client and more work for you - price the approval flow, do not throw it in.
- Volume. Ten runs a day and ten thousand runs a day are different products. Put the covered volume in writing.
- Who owns the accounts. Build on the client's accounts, under the client's billing, so usage costs land where they belong and the automation survives if you part ways.
- Data sensitivity. Anything touching payment or personal data needs a scope document and a longer testing phase, and both belong in the price.
The pricing mistakes that kill automation margin
- Quoting the build, not the outcome. The moment you say "it is a small build" you have priced it as a small build. Talk about hours removed and nothing else.
- Writing "connects to your tools" in the scope. Every tool the client thinks of later is now included. Name each one, with a price.
- No monthly fee. You now own every breakage, every API change, and every "it stopped working" text, for free, forever.
- Letting them see the build speed. Claude Code turning a week of work into an afternoon is your margin story. It is not the client's discount. The client is paying for the hours they get back every month, and that number did not change because you built it fast.
- Skipping the one-page scope. What triggers the automation, what it does, what it does not do, what happens on failure, and who gets told. Use the format in [how to write a statement of work for an AI project](/blog/how-to-write-a-statement-of-work-for-an-ai-project) before you start.
How to present the number so it closes
Lead with the saving you already agreed on, then put the price next to it. "This removes about the hours we counted, every month, and here is the setup fee and the monthly to keep it running" is a sentence the client can approve on the spot. Offer three shapes - the single automation, a bundle of the three tasks they complained about most, and a monthly retainer where you keep adding to it - and most clients pick the middle one. Send it as [a one-page proposal](/blog/one-page-ai-proposal-that-closes), never as a menu of technologies.
When the push-back comes, it is nearly always "we could just do it ourselves" or "that seems like a lot for something small." Both are answered by the number you measured together: the price is a fraction of what the task costs them today. If they push harder, [the "can you do it cheaper" objection](/blog/can-you-do-it-cheaper-objection) has the exact words.
Put the method in front of a real client this week
Pricing only earns money when it is in front of someone with a repetitive task and a budget. Local service businesses, agencies, and small e-commerce shops all have a spreadsheet someone updates by hand every Monday, and nobody has offered them a straight number for making it go away.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for an AI automation?
Price it against the hours it removes from the client's month, not the hours it takes to build. Measure who does the task, how often, how long, and what errors cost, then quote a fixed setup fee that is a clear fraction of the first year's saving, plus a monthly run fee, plus a separate line for each connected system. Never quote build hours.
Should an AI automation have a monthly fee?
Yes, every time. Automations depend on other people's software and stop working when a connected app changes its login, export, or API. The monthly fee covers monitoring, fixing those breakages, usage costs, and small adjustments within a stated volume. Without it, every breakage is a free favour you are obliged to do.
What makes an AI automation more expensive to build?
The number of systems it connects to is the biggest driver, followed by the cost of an error (invoicing and customer records carry more risk than reporting), any human approval steps, run volume, and data sensitivity. Build difficulty is not the driver - what the automation touches is.
Should I tell the client the automation was built with Claude Code?
Be honest about your stack if asked, but keep the pricing conversation on the hours removed. Build speed is your margin story, not the client's discount. The client is paying for the labour they get back every month, and that number is the same whether the build took a week or an afternoon.
How do I price several automations for the same client?
Offer three shapes: a single automation, a bundle of the three tasks they complained about most, and a monthly retainer where you keep adding automations over time. Present all three on a one-page proposal with the saving you measured together at the top. Most clients pick the middle option, and the retainer is the natural upgrade once the first one is running.
Last reviewed by Duncan Rogoff on September 25, 2026
