Retainer Pricing for AI Builders: How to Charge Monthly Without Guessing
- A retainer is not a discounted hourly rate in disguise. It is a standing agreement to provide access, availability, and outcomes - not to bill by the hour. That distinction matters because it changes what you are selling.
- The right retainer rate starts with your monthly output target, not your hourly rate. Decide what a good month looks like in deliverables, price that, and reverse-engineer the hours from there.
- Three types of retainer work for AI builders: the maintenance retainer for keeping a live build running, the growth retainer for shipping new features each month, and the strategy retainer for advisory with access. Each prices differently and attracts a different client.
Why hourly pricing breaks at scale for AI builders
Hourly pricing has a ceiling built into it. There are only so many hours in a month, and every hour you spend on one client is an hour you cannot spend on another. Claude Code builders run into a second version of this ceiling: as you get faster and better at building, hourly pricing punishes you for it. A build that took you ten hours six months ago takes you two hours now. If you are billing hourly, you just cut your revenue by eighty percent for doing the same work.
Retainer pricing solves both problems. You are pricing the outcome and the access, not the hours. A client on a maintenance retainer is paying for the peace of mind that their build keeps running and problems get addressed quickly - not for your time specifically. That value does not shrink when you get faster. It stays constant or grows.
What a retainer is and what you are actually selling
A retainer is a standing monthly agreement. The client pays a fixed amount each month in exchange for a defined set of deliverables, a defined level of access, or both. The key word is defined: a retainer without clear scope is not a business arrangement, it is an open-ended commitment that will make both parties unhappy.
What you are actually selling in a retainer is one of three things, depending on the type: availability (the client knows they can reach you and something will happen), ongoing output (a set number of features or improvements delivered each month), or standing expertise (advisory access to someone who knows their system and can answer questions or make decisions with them). Each of these is a real, defensible value - but they price differently and attract different clients.
The three retainer types that work for AI builders
Most retainer conversations fail because the builder tries to design a custom arrangement from scratch for every client. The cleaner approach is to have three types ready and match the client to the type that fits their situation.
- The maintenance retainer. The client has a live build - an automation, a tool, a dashboard - and they want it to keep working and improving as their needs change. They are not paying for a new feature every month. They are paying to not have to think about whether it still works. Typical scope: monitoring, bug fixes, minor updates, one async check-in per month. Price range: lower than the other two types, because the expected hours are low in a stable month. The value is the insurance, not the active work.
- The growth retainer. The client has a working foundation and wants to keep building on it. Each month delivers a defined set of new features or workflow improvements. Typical scope: a clear monthly deliverable list agreed at the start of each month, with a defined number of revision rounds and a hard cut-off for what is in scope. This is the highest-hours type and prices accordingly. The key protection is the monthly scoping session - you agree on what this month includes before you start building.
- The strategy retainer. The client does not primarily need code written. They need someone who understands AI tools and their business to help them make good decisions - what to build next, how to evaluate a vendor, whether a given automation is worth doing. This is advisory with access. Typical scope: a set number of hours per month, a standing weekly or biweekly call, and async availability for quick questions. This type often has the highest effective hourly rate of the three because it does not scale with hours.
How to set your retainer rate
The most common mistake when setting a retainer rate is starting with an hourly rate and multiplying. That method bakes your inefficiency into the price and leaves value on the table as you get faster. Start from the other direction: decide what outcome the retainer delivers in a month, decide what that outcome is worth to the client, and price from there.
A maintenance retainer on a live automation that handles fifty customer inquiries a day is worth a different amount than one on a reporting dashboard someone checks weekly. The value of continuous availability is proportional to the cost of downtime. If the automation going down for a day costs the client real money or real problems, the retainer that prevents that is priced accordingly.
- For the maintenance retainer: start at a minimum floor that makes the relationship worth running for you - the admin overhead of a client relationship is real. A common floor is several hundred dollars per month; below that the relationship typically is not worth the attention it requires.
- For the growth retainer: estimate the hours honestly for a realistic month, multiply by your target effective hourly rate, and add a buffer for the unknown. The buffer is not padding - it is the cost of not knowing exactly what this month will surface.
- For the strategy retainer: price the access and the standing expertise, not the hours. What would it cost the client to get the same quality of decision-making from a consultant they hired for a single engagement? That is the comparison you want the client making, not your hours.
What belongs in a retainer scope
A retainer scope is the document that makes the retainer defensible. Without it, every month becomes a negotiation about what is included and what is extra. The scope answers three questions before the first month starts: what is included, what is not included, and what happens when the client wants something that falls outside.
- What is included: the specific deliverables, the availability windows, the response time for different types of requests, and the maximum number of revision rounds for growth deliverables.
- What is not included: the categories of work that constitute a new project rather than part of the retainer. A maintenance retainer does not cover building new features. A strategy retainer does not cover writing code. Name these explicitly.
- The out-of-scope process: when the client asks for something outside the scope, the answer is not no - it is a separate engagement. The scope document should state that additional work is scoped and priced as a new project, so the client understands the path forward is addition, not renegotiation.
Start charging monthly inside the Profit Room
Inside the Claude Code Profit Room we go deep on retainer pricing - the exact templates I use for each retainer type, the monthly scoping process that keeps growth retainers clean, and the conversations that convert a one-off client into a standing monthly relationship. Join us at https://www.skool.com/claude-code-profit-room/about and bring the client you want to put on retainer.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
Should I offer a discount for longer retainer commitments?
A modest discount for a three or six month commitment is defensible if it reduces the churn risk for you. The math works if the certainty of a longer engagement is worth more to you than the per-month revenue you are giving up. What you should not do is offer a large discount to make a retainer feel more affordable - that just trains the client to negotiate on price instead of value. If a retainer is not worth the full monthly rate to the client, the problem is the offer, not the price.
How do I handle a month where the client asks for more than the scope covers?
Treat it as a new engagement, not a retainer question. When the request comes in, acknowledge it, confirm it is outside the current scope, and offer to scope it as a separate project with its own estimate and timeline. The script is: 'That is not covered under the current retainer, but it sounds like a useful build. Let me put together a quick scope and estimate and I can send that over.' Do not absorb it silently and do not have a long conversation about whether it is in scope. The scope document is the reference.
What is the minimum retainer amount worth running?
The answer depends on the actual work involved, but a useful floor is the point below which the relationship overhead - the monthly communication, the invoicing, the mental space a client occupies - costs you more than the income is worth. For most builders that floor is somewhere between a few hundred and a few thousand dollars per month depending on the work type. Below it, consider whether a project arrangement might be more appropriate than a standing retainer.
How do I pitch a retainer to a client who only thinks in one-off projects?
Start by identifying what happens after the project ends. Most one-off clients have ongoing needs they have not articulated - they assume the project will be done and then it will just work forever with no attention. The pitch is: 'After we finish the build, do you want someone available to keep it running well and add to it as your needs change? That is what the maintenance retainer covers.' Frame it as the natural continuation of the project, not a separate product.
Last reviewed July 31, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →
