How to Price a Claude Code Retainer (So Clients Sign and Stay)
- A retainer is not a discounted project rate. It sells the outcome of having you on hand every month - the builds that get done, the system that stays maintained, the thing the client does not have to think about. Price it on that value, not on hours.
- The Retainer Scope Stack has three layers: a base that covers maintenance and small requests, a grow layer that includes new builds each month, and a premium layer for clients who want unlimited access. Pick the right layer for each client before you name a number.
- The renewal test is the real price check: if you asked a client to renew right now, would they say yes without needing convincing? If the answer is anything other than immediately yes, your price and your value delivery are out of alignment.
Why Retainer Pricing Is Different From Project Pricing
A retainer is not a project with monthly billing. A project ends with a deliverable and a final invoice. A retainer sells access to your output on an ongoing basis - the builds you ship, the system you maintain, the problems you handle before the client even notices them. The price has to be easy to say yes to every month, not just on the first call. That changes everything about how you set the number.
Project pricing works backwards from the deliverable: here is what you are getting, here is what it costs. Retainer pricing works from the outcome the client is trying to buy: here is what your business looks like with me on retainer, here is what it looks like without. The number you name has to feel like a fraction of the value it unlocks, or you will spend the relationship defending it every renewal cycle.
The Retainer Scope Stack - Three Layers, Three Price Points
The Retainer Scope Stack is the framework I use to define what is inside a retainer before I name a price. Each layer has a clear scope and a natural price range that matches it. The mistake most builders make is selling one vague retainer that includes 'whatever comes up' - that is a recipe for scope creep and an underpriced engagement. Define the layer first, price second.
| Layer | What it covers | Who it is for |
|---|---|---|
| Base | Maintenance, monitoring, small fixes, and email support. The system runs and you keep it running. No new builds. | Clients with a finished system who want it maintained without thinking about it. |
| Grow | Everything in Base plus one to two new builds or meaningful improvements each month. The system grows. | Clients who have a working foundation and want to keep building on it. |
| Premium | Everything in Grow plus priority access, faster turnaround, and scope that flexes to what they need each month. | High-trust clients with ongoing build volume who need to know you are always available. |
The three retainer layers and what each one covers
Setting the Number - What Actually Determines the Price
Three things set a retainer number: the layer (Base, Grow, or Premium), the business size and budget of the client, and the outcome value of having you on hand. The outcome value is the one most builders ignore because it is harder to calculate - but it is the one the client is actually paying for.
A useful frame: what does it cost the client in time, errors, or missed opportunity to not have you? A small business losing two hours a week to manual processes you could automate has a clear number attached to that pain. Price your retainer as a fraction of the problem it solves, not as a multiple of your hours. A Base retainer that saves a client four hours a week should cost less than the value of those four hours, not the same as your hourly rate times the hours you actually work.
The Renewal Test - How to Know if the Price Is Right
The renewal test is simple: imagine asking the client right now, mid-month, whether they want to renew. Would they say yes immediately, or would they need convincing? If they would need convincing, something is misaligned - either the price is too high for the value they see, or the value you are delivering is not visible enough for them to feel it without prompting.
Fix misalignment by doing one of two things: increase the visible output (show the client what you shipped or maintained each month in a short monthly update), or adjust the scope so the deliverable matches the price. Trying to hold a price without addressing the underlying mismatch always ends in a lost client at the next renewal.
Price Your Retainer Inside the Profit Room
The Retainer Scope Stack - Base, Grow, Premium - gives you a scope to sell and a reason for the price before you ever get on a call. Define the layer, name the outcome, set the number as a fraction of that outcome, and run the renewal test every month to keep it honest.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
What is a good starting price for a Claude Code retainer?
It depends on the layer and the client. A Base retainer for a small business client covering maintenance and small fixes typically starts in the low hundreds per month. A Grow retainer that includes new builds each month should be priced significantly higher - enough that the new build value alone justifies the fee. There is no universal number because retainer value varies by what the client's time and problems are worth, not by what you spend working.
How do I move a project client to a retainer?
At the handover conversation, not after. When you deliver the project, name the most obvious thing the client is going to need next: maintenance on what you built, a second build that the first one makes possible, or ongoing support so they do not have to call you at a crisis rate. Frame the retainer as the next step, not as an upsell. The timing is when the value of what you delivered is most visible to them.
What do I include in a monthly retainer?
Exactly what you agreed to in the Retainer Scope Stack layer the client is on - no more, no less. The clarity is the product. A vague retainer that includes 'whatever comes up' leads to unpriced scope creep. Document the scope at the start, send a monthly summary of what was done, and handle anything outside scope with a separate quote.
How do I handle a client who wants to pay less?
Offer a smaller scope, not a lower rate for the same scope. Move them down a layer - from Grow to Base, for example - and be explicit about what is no longer included. A lower rate for the same scope tells the client your original price was arbitrary. A smaller scope for a lower rate keeps the pricing honest and leaves room to move back up when the value is visible.
Last reviewed July 29, 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 →
