# Project, retainer or hourly: how to price AI automation work | Gareth B. Davies

Source: https://garethbdavies.com/articles/pricing-models/

[← All articles](https://garethbdavies.com/articles/) Sell it · Pricing

# Project, retainer or hourly: how to price AI automation work

 By Gareth B. Davies · Updated July 2026

 Project, retainer, or hourly looks like a formatting choice until you realize each one prices a different thing entirely.

 Most builders treat pricing as a formatting decision. Do I put a dollar figure next to "project," "monthly," or "hour," and move on. That framing misses what is actually being decided, because each of those three words prices a different thing. A project prices an outcome. A retainer prices an ongoing relationship. An hourly rate prices your time, which is the one thing a client cannot verify and does not actually want to buy. The confusion in most pricing calls does not come from not knowing what to charge. It comes from not knowing which of those three things the client is even asking for.

## Why hourly quietly punishes you

 Hourly pricing feels safe because it feels fair. You did the work, you get paid for the hours, nobody argues. But it caps your upside at your own speed, and it puts the client's attention on the wrong number. A prospect who asks "what's your hourly rate" is usually trying to estimate total cost from a number that has nothing to do with the value they will receive. One coach who has delivered close to $300,000 in freelance-platform work still finds himself stuck competing on an hourly basis in a saturated niche, unable to differentiate or scale past it. That is the mechanism: hourly billing trains the market to compare you to the next cheapest hour, not to the outcome you produce. The fix raised again and again in coaching conversations is not a bigger hourly number. It is a different question entirely: what is this actually worth to the client, in dollars they already understand.

## Project pricing forces the value conversation you were avoiding

 A flat project fee does something hourly can never do. It forces you to quantify the problem before you quote the solution. A recurring pattern in coaching calls is a builder who wants to skip straight to a number, and gets redirected toward a specific kind of discovery question first: how many hours does this manual process cost per month, what does an hour of that person's time cost, what is a single qualified lead or booking worth to this business. One case walked through this cleanly. A prospective client, an educator, was spending over 30 hours a year manually producing more than a hundred student reports. At a modest hourly rate for that role, the manual cost of the status quo came out to roughly $800 to $900 a year, a figure the client had never actually calculated before it was put in front of them. Once that number exists, a project quote in the low thousands stops being a big ask and starts being an obvious trade. This is the real function of project pricing: it is not a payment structure, it is a forcing mechanism that makes the client compute their own pain before you name your fee.

 Setup fees observed across dozens of these builds range enormously, from around $1,000 for a simple small-business system up to $13,000 or more for a multi-channel build spanning voice, chat, and email. That spread is not inconsistent pricing. It reflects how much of the client's actual cost structure the system replaces.

## Retainers are where the real money and the real risk both live

 A project fee gets you paid once. A retainer gets you paid for staying responsible for something that keeps running, and that is a fundamentally different commitment than "I built you a thing." The advice that surfaces consistently is to price the retainer against what it protects, not against how much maintenance time it consumes. One useful anchor is to frame the whole annual retainer as roughly equivalent to the cost of one piece of software the client already pays for without blinking. Monthly maintenance figures across various builds land anywhere from $200 to $1,500, and the spread tracks system complexity and how many discrete change requests are bundled in before extra billing kicks in. Whatever the number, define what is included. A retainer with an unlimited scope is not a retainer, it is unpaid hourly work wearing a monthly invoice.

## Naming your own number is the trap inside the trap

 Even once you have decided project versus retainer versus hourly, there is a second, quieter decision buried underneath it: who says the number first. The advice given to a builder who kept freezing on this exact point was simple. Ask the prospect what they think this is worth to them before you name a figure. It feels like a stalling tactic. It is actually a pricing tool, because a client who has just walked through their own missed-call rate or their own manual-hours cost will frequently propose a number close to, or above, what you were about to ask for anyway.

 The single principle underneath all of it: never price the format, price the outcome the format is delivering, and let the client's own numbers set the ceiling before yours sets the floor.

 Want a partner working through this with you?

 The AAA Accelerator is where AI agency builders get coached on exactly these calls, from first client to full pipeline.

 [Join the AAA Accelerator](https://ref.aaaaccelerator.com/apply)