Blog · June 1, 2026 · ~9 min read
How to price your first retainer: hours, rate, reset rules
Pricing a retainer agreement is three separate decisions disguised as one. Most freelancers treat it like a rate question — should I charge $100/hr or $125/hr? — and stop there. The rate is actually the easiest part. The hard decisions are how many hours to sell, what happens when those hours roll over, and what the reset date does to your cash flow. Get those wrong and no rate will save you.
Why retainer pricing fails (and it’s not the rate)
The most common retainer pricing mistake isn’t charging too little per hour. It’s selling too few hours. A freelancer who signs a 10-hour monthly retainer at $150/hr has $1,500/month guaranteed — but 10 hours disappears fast, the client always wants just one more task, and within two months the relationship is a slow-drip argument about what counts as “in scope.”
The second mistake is no rollover policy. A client who ends February with 4 unused hours expects to carry them into March. If your agreement doesn’t say otherwise, you have an informal obligation to 4 hours of free carry-forward every month, and that compounds. By month four, they’re effectively paying for a 12-hour retainer while expecting 20+ hours of access.
The third mistake is the wrong reset date. If your retainer resets on the 1st of each month and your client’s budget cycle runs on the 15th, you’ll spend the first two weeks of every month fielding “how many hours do I have left?” questions from a client who can’t correlate their spend to your billing cycle. The hours question is a billing design problem, not a client communication problem. A misaligned reset date makes it structural.
These three decisions — hours scope, rollover policy, reset date — are the real retainer agreement. The rate is almost secondary. Here’s how to make each one.
Decision 1: How many hours to sell
Start from the client’s actual usage history, not your best-case estimate. Look at the last three invoices for this client. What did they actually request, including things you talked about but didn’t bill for? Add those. Now add 10%. That’s your floor.
If you’re proposing a retainer to a new client with no history, look at their stated needs and scope them conservatively — then present two options: a smaller block at your standard rate, and a larger block at a 5–8% discount. The larger block is usually the one they pick, which is the outcome you want. You get more predictable revenue; they get more capacity at a lower effective rate.
The under-pricing hours problem is more dangerous than under-pricing the rate because of how scope creep compounds. If you sell 15 hours and the client actually needs 22, one of two things happens: either you work 7 hours for free each month (scope creep that kills your margins), or you invoice for overages and spend every month defending why something wasn’t included in the retainer. Neither outcome is good. Selling the right number of hours prevents both.
A practical test: if the retainer at full consumption doesn’t leave you any capacity buffer in the week it falls, it’s too small. A retainer that genuinely fits the client’s needs shouldn’t require you to spend the last week of the month scrambling. If it does, either the hours were priced too low or the scope was undefined.
For reference: the most common retainer shapes for solo freelance consultants are 10–15 hours/month (light advisory), 20–25 hours/month (primary execution support), and 40+ hours/month (effectively fractional hire). If you’re consistently billing a client 18–22 hours across three months, you’re in the 20-hour retainer zone — round up slightly rather than splitting the difference.
Decision 2: The rate (and when a retainer discount makes sense)
Your retainer rate should be at or slightly below your project rate. Not dramatically below. The standard is a 5–10% discount in exchange for the client’s commitment — they get slightly better economics, you get revenue predictability. That’s the trade. A 20% or 30% retainer discount isn’t strategic generosity; it’s under-pricing in a way that signals you were padding your project rate.
The case for zero discount: if you’re billing at a rate where demand for your time genuinely exceeds your available hours, a retainer at your full rate is fair. The client is purchasing priority access — guaranteed capacity when they need it — and that has real value even at full rate. Some freelancers charge a premium on retainer over project rate for exactly this reason: priority access is worth more than project-by-project scheduling.
On billing mechanics: most retainers are billed monthly in advance. The client pays on the 1st, and the hours are available for that month. This is the cleanest model — you have cash before you do work, and the client’s usage depletes against their pre-paid balance. Billing in arrears (pay at the end of the month for what you used) effectively converts the retainer back to hourly billing with a commitment wrapper. It defeats most of the cash flow benefit and introduces the same end-of-month invoice scrutiny you were trying to escape.
The predictability benefit of retainers over hourly billing comes primarily from advance billing. If you want that benefit, your retainer agreement needs to specify payment in advance, on a defined date, regardless of usage. This is the sentence most first-time retainer agreements leave out — and its absence is what creates the “they paid late, my revenue was volatile” complaint you hear from freelancers who thought retainers would fix their cash flow.
Decision 3: The rollover policy
Rollover is the most politically charged part of retainer pricing and the one most agreements fail to address explicitly. Here is the spectrum of options:
No rollover (use-it-or-lose-it). Hours expire at the end of each billing cycle. The retainer resets to full capacity on the agreed date. This is the simplest model and the best for cash flow. The client has a strong incentive to use their hours, which means they engage you regularly, which means the relationship stays active. The downside is that clients who don’t use all their hours occasionally feel like they’re leaving money on the table — which creates churn pressure at renewal.
Partial rollover (carry forward up to N hours). Unused hours roll into the next month up to a cap. For example: unused hours carry forward, but the total available in any month is capped at 130% of the base retainer. A 20-hour retainer can carry up to 26 hours into the next cycle. This is a reasonable middle ground. It gives the client some safety if a month is slow, without creating an unbounded liability for you. Document the cap explicitly in the agreement.
Full rollover. All unused hours carry forward indefinitely. This is almost never the right structure for a freelancer. It turns your time into an options contract with no expiry — the client can call on any accumulated hours at any future date. At scale, that’s a liability you can’t plan around. The client may never exercise the rollover, but the obligation affects how you schedule other work. Avoid this unless the client is large enough that the relationship justifies the asymmetric risk.
The rollover conversation is easier when you lead with the client’s benefit. Frame it as: “The retainer resets each month because it’s designed to reflect ongoing work, not banked time. But if a month is unusually light, you can carry up to [N] hours into the next cycle.” This acknowledges their interest while keeping the structure clean.
The reset date conversation
The reset date determines when your billing cycle starts and when unused hours expire or carry forward. It sounds administrative, but it affects when you get paid, when clients ask “how many hours do I have left?,” and how you schedule your own work.
The default is the 1st of the month. This works if your clients are aligned to calendar-month budgets (most are). It makes tracking straightforward: hours used this month resets to zero on the 1st.
The problem is calendar-month resets create a predictable end-of-month surge. Clients who notice their hours running low in the last week scramble to assign work. That’s not inherently bad — you want clients to use their hours — but it creates scheduling pressure you may not want if you have multiple retainers.
Two alternatives worth considering: a mid-month reset (15th or 16th) staggers your billing cycles and smooths your cash flow if you have more than two retainer clients. A rolling 30-day window (hours expire exactly 30 days after billing date) is more complex to track but eliminates the calendar-month clustering effect entirely.
Whatever you choose, put it in the agreement and wire it to your tracking system. A retainer usage tracker that understands billing cycles resets the counter on the configured date automatically, so neither you nor the client has to calculate where they are in the cycle manually. The reset date being visible to the client — as a live counter they can bookmark — eliminates the “wait, did the cycle reset yet?” question that otherwise eats two emails per month.
What belongs in the retainer agreement
A retainer agreement doesn’t need to be long. The core elements that prevent every foreseeable dispute are:
Hours per cycle. The number. Not a range. A specific number.
Rate per hour for retainer hours. What you charge for hours within the retainer.
Rate for overage hours. What you charge if the client requests work beyond the retainer cap. Typically your project rate or your retainer rate plus a 15–20% premium. The premium on overages creates the right incentive: buy more retainer hours upfront rather than running over. Documenting overage rates in the agreement prevents the conversation where a client is surprised that additional work costs additional money.
Payment terms. In advance, on a specific date, via a specific method. Include late payment terms (most freelancers use “hours pause after N days past due” rather than a financial penalty, which is cleaner to enforce and creates a natural incentive for the client to pay on time).
Rollover policy. As discussed: none, partial, or full, with the cap if partial. One sentence.
Reset date. The specific day of the month when the cycle resets.
Termination. How much notice either party needs to give. 30 days is standard. Some freelancers require 30 days’ notice plus payment for the notice period, which gives you one paid month to replace the revenue. This is worth including — the scenario you’re protecting against is a client who cancels on the last day of the month, leaving you with no revenue and no notice to pipeline alternatives.
Scope. What category of work is covered. Not a task list — a category description. “Ongoing marketing strategy and content support” or “technical consulting and implementation support for the client’s web infrastructure” is enough. Specific task lists are a trap: the client will eventually ask for something not on the list, and you’ll spend more time arguing about scope than doing the work.
How to handle the client who pushes back on scope
The scope pushback usually sounds like: “But I thought the retainer covered [task they want], why would that be extra?”
The answer depends on whether the task is inside the retainer’s hours budget or outside the category of work described in the agreement. These are two different problems.
If the task is inside the category but exceeds the hours budget: “This absolutely falls within the scope of what we work on together. We’re at [N] hours this month and this task would take approximately [X] hours, which would take us to [total] against our [retainer total] cap. I can either start next month when the retainer resets, bill the overage at [$rate], or we can adjust the retainer size at renewal to cover this level of work.” Give them three options; let them choose.
If the task is outside the category entirely: “This is a bit outside what the retainer was set up to cover. Happy to take it on as a project at [$rate]. Want me to send a quick estimate?” Keep it short. Don’t re-explain the retainer. Just acknowledge the gap and offer a path.
The most important thing to avoid is doing the out-of-scope work anyway and not billing it. Once you do it once, the client’s internal model updates: this is included. Every subsequent request for similar work will feel free to them, and you’ll be resetting the expectation from inside a worse negotiating position each time.
The hours-visibility problem that shows up at month three
Here’s a timing pattern most freelancers don’t anticipate: the first two months of a new retainer are usually fine. The client is new to the arrangement, they’re being deliberate, the relationship is fresh. By month three, the novelty has worn off and they start treating the retainer like a subscription — they stop thinking about how many hours they’ve used and start asking more frequently.
“How many hours do I have left?” starts as one email per month. By month four it’s two or three. By month six, if you don’t have a system, it’s a recurring thread in every Slack channel you share with the client. A freelance consultant retainer tracker that gives clients a live URL to check their own balance eliminates this entirely — not because clients stop caring about their hours, but because they no longer have to ask. They check the URL. They see 8 of 20 hours used. They plan accordingly.
This matters for pricing because the status overhead is a real cost that doesn’t show up on your invoice. If you have five retainer clients each asking twice a month, that’s 10 status emails — probably 20–30 minutes of context-switching time that you’re not billing. At scale, this is the hidden tax on retainer relationships that no one factors into their pricing math. The tool cost of eliminating it is trivial compared to what you recover.
Putting it together: pricing your first retainer
A practical starting point for a first retainer with an existing client:
Average the last three months of actual hours worked. Propose that number rounded up to the nearest 5 as the retainer size. Price it at your standard hourly rate with a 5% discount. Specify no rollover (or partial with a 20% carry cap). Reset on the 1st of the month (or the 15th if you want to stagger multiple clients). Payment in advance, 30 days’ notice to cancel.
That structure covers 90% of first retainer situations. The edge cases — unusual rollover needs, non-standard scope categories, multi-seat teams — are worth addressing, but they’re not first-draft problems. Get the core structure right, get the retainer signed, and adjust terms at the first renewal if something isn’t working.
Once the retainer is live, the tracking system matters as much as the agreement. HourTab gives each retainer its own public URL showing hours used, hours remaining, and the work log for the current cycle. The client bookmarks it once; the status question stops. The hours reset automatically on your configured date. It handles the tracking side so the agreement can stay focused on the terms. The free plan covers your first retainer with no card required — a natural starting point for a freelancer setting up their first formal retainer arrangement.