Introduction
Project work brings high but uneven income; retainers offer smoother cash flow and deeper relationships. Both have risks: sales pressure on projects, scope bloat and dependency on retainers.
This guide covers when to choose which model, how to bound retainer scope, and how to build hybrids. The goal is portfolio balance—not one true way.
Project-Based: Clear Start and End
Projects fit clear deliverables and clear prices: rebrands, MVPs, migrations. Sales cycle and kickoff cost repeat each time—pricing must include that overhead.
Projects diversify learning and portfolio. The downside is roller-coaster cash flow. Weak pipelines make gaps between projects stressful.
- Clear scope + fixed or capped price
- High focus, defined finish
- Ongoing need to sell
- Great for case studies
Retainer: Renting Capacity
A retainer reserves monthly capacity: maintenance, iteration, advisory hours. The value is 'ready teammate access'—not cheap unlimited support.
Define an hour bank (for example 20 hours/month with partial rollover) or an outcome retainer (monthly sprint goals). Unlimited Slack support poisons retainers.
Retainer clause outline:
- Monthly fee and invoice date
- Included hours / sprint scope
- Response SLA (e.g. 1 business day)
- Unused hours: rollover % or expire
- Overage: extra-hour rate
- Minimum term + cancel notice (e.g. 30 days)
- Out of scope: new product / large feature = separate projectWhen to Choose Which
Ongoing fuzzy needs plus trust → retainer. One clear deliverable → project. High uncertainty often starts as a short discovery project, then converts to a retainer.
One client above 50 percent retainer revenue is risky. Two to four retainers plus occasional projects is a balanced mix for many freelancers.
Retainers deepen relationships; poorly designed retainers turn you into cheap staff.
Pricing and Boundaries
Price retainers above your hourly floor with a reservation premium (10–25 percent is a common mindset). Priority and response guarantees are not free.
If demand spikes mid-month, handle extras via overage or change orders. Three months of constant overage means grow the package or split into a project.
- Classify the need as project or retainer
- Write scope and SLA
- Price with a reservation premium
- Review usage after 90 days
- Grow, split, or end the package
Hybrid Models
Common pattern: project for build, then maintenance retainer. Or small iterations inside the retainer, large features as separate SOWs—state the split in the contract.
Do not mix pure advisory retainers with heavy implementation retainers; they need different energy and pricing. Separate them with package names.
- Build (project) + Run (retainer)
- Hour bank + large-work SOW
- Quarterly strategy + monthly execution
Conclusion
Retainers bring stability; projects bring clarity and variety. A deliberate mix smooths cash flow while keeping learning alive.
Write your model with scope, SLA, and overage rules. A well-designed retainer creates freedom; a poorly designed one becomes a hidden full-time job.