Technical
Retainer vs Project Pricing: How I Actually Choose
Every new client conversation eventually lands on pricing. Retainer or project? Hourly or fixed? I have charged all of the above over the years, and I have settled on a framework that lines up the pricing shape with the work shape. The wrong shape costs both of us more than the rate does.
What Project Pricing Is For
Project pricing (a fixed fee for a defined scope) is right when three conditions hold:
- The outcome is well-defined (launch a site, ship a feature, migrate a system)
- The scope is stable (the client knows what they want, unlikely to change)
- The timeline has a natural end (there is a point where we are done)
Typical examples: a new marketing site, a content migration, a specific integration.
What Retainers Are For
Retainers work when the opposite is true:
- The outcome is ongoing (keep the systems running, respond to requests)
- The scope is fluid (priorities shift monthly)
- The timeline is open-ended (this relationship lasts as long as it works)
Typical examples: ongoing maintenance, fractional CTO, content operations.
The Worst Combination
The combination I avoid is project pricing with fluid scope. That is the path to scope creep, unpaid work, and resentment on both sides. If scope is unclear, charge a retainer or start with a small scoping engagement to nail down the real project first.
How I Price Each
Project pricing:
estimate hours, multiply by target rate, add 25% buffer
if client balks at the number, reduce scope, never rate
Retainer pricing:
agree on a block of hours per month at a blended rate
define what is in-scope and what needs a separate SoW
review quarterly, adjust based on actual usageThe 25% buffer on projects is non-negotiable. Every project has surprises. That buffer is what keeps the relationship healthy when they happen.
What Changes at the Edges
Strategic work (fractional CTO, technical advisor) is almost always a retainer. Discovery work (audits, architecture reviews) is almost always fixed-fee, because the outcome is a specific deliverable. Emergency work (incident response) is hourly at a premium rate, because you are trading flexibility for urgency.
The rate matters less than the shape. A good rate on the wrong shape is a bad deal for someone. A fair rate on the right shape is sustainable for both sides, which is what you actually want.
Read High-Output Management for the underlying thinking on leverage.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read