Retainer vs Project-Based: Which Engagement Model Fits?
A retainer reserves ongoing capacity for a client who needs work done continuously. A project-based engagement scopes a fixed deliverable with a start, an end, and a price. Choose by asking whether the client's need is open-ended or finite. Picking the wrong model usually surfaces as billing friction within the first two months.
| Retainer | Project-Based | |
|---|---|---|
| Scope definition | Broad, defined by capacity or hours per period rather than specific deliverables | Specific, defined by deliverables with acceptance criteria |
| Duration | Open-ended, typically with a notice period for cancellation | Fixed, with a defined start and end date |
| Billing structure | Recurring, usually monthly, regardless of actual usage | Tied to milestones, deliverables, or a fixed total |
| Revenue predictability for provider | High, because the payment recurs as long as the engagement continues | Low, because each project must be sold separately |
| Client commitment | Higher, because the client pays whether they use the capacity or not | Lower, because the client commits to one deliverable at a time |
| Scope change handling | Absorbed within the monthly capacity or addressed at renewal | Handled through formal change orders that adjust price and timeline |
What is the difference between a retainer and a project-based engagement?
A retainer is a recurring agreement where the client pays for ongoing access to your time, expertise, or services. The scope is typically defined by capacity, such as a number of hours per month, rather than by a specific deliverable. A project-based engagement is a fixed agreement with a defined scope, timeline, and end point. The client pays for a deliverable, not for access. The difference comes down to whether the work is continuous or finite.
When does a retainer make more sense than a project?
A retainer makes sense when the client's needs are ongoing and difficult to predict in advance. This is common in marketing, design, development support, and advisory work, where the client needs to be able to call on you without scoping a new project each time.
- The work is continuous and the volume varies month to month.
- The client values availability and fast response over detailed scoping.
- Scoping each request as a separate project would cost more in overhead than the work itself.
- The relationship has proven itself through one or more successful projects.
When does a project-based engagement make more sense?
A project-based engagement makes sense when the deliverable is clear, the scope can be defined upfront, and the client wants to pay for a result rather than for time. This is the natural model for work with a defined output, such as a website, a brand identity, or an audit.
- The deliverable is specific and can be described in a statement of work.
- The client wants to compare providers on price for the same output.
- The engagement has a natural end point after which the work is done.
- The client is not ready to commit to an ongoing relationship.
How do you transition from project-based to a retainer?
The transition usually happens after one or two successful projects, when both parties recognize that the client's needs are ongoing. The conversation is easier when you can point to the last few months and show that the client has been buying projects at a pace that a retainer would simplify. Frame it as reducing overhead for both sides rather than as a pricing change. Start the retainer with a trial period and a clear cancellation clause so the client is not locked in before the model has proven itself.
What are the risks of each model?
Each model has a characteristic failure mode. Retainers fail when the client does not use the capacity and starts to see the payment as waste, or when the provider overcommits and cannot serve all retainer clients in the same month. Project-based engagements fail when the scope was underspecified, leading to disputes about what was included, or when the provider underestimates the effort and absorbs the loss. Knowing the failure mode helps you write the agreement to prevent it.
- Retainer risk: unused capacity feels like waste, leading to cancellation.
- Retainer risk: over-subscription, where the provider sells more capacity than they can deliver.
- Project risk: scope creep, where undefined edges of the deliverable expand without additional payment.
- Project risk: underpricing, where the fixed price does not cover the actual effort.
Which one should you use?
Use a Retainer when
- The client's needs are ongoing and vary in volume from month to month.
- You have completed at least one successful project and the relationship is established.
- The overhead of scoping each request as a separate project exceeds the value of the work.
- You want predictable recurring revenue rather than project-by-project sales.
Use a Project-Based when
- The deliverable is specific, finite, and can be described in a statement of work.
- This is a new client relationship and neither side is ready for an ongoing commitment.
- The client wants to pay for a defined result, not for ongoing access.
- The work has a natural end point after which no further engagement is needed.
FAQ
What is the difference between a retainer and a project-based engagement?
A retainer is a recurring agreement where the client pays for ongoing access to your capacity, typically defined by hours per month. A project-based engagement is a fixed agreement with a defined deliverable, timeline, and price. The difference is whether the work is continuous or finite.
Do unused retainer hours roll over?
That depends on the agreement. Some retainers allow unused hours to roll over to the next month, some do not. The rollover policy should be stated explicitly in the retainer agreement because it is one of the most common sources of billing disputes.
Can you combine a retainer with project-based work?
Yes, and many providers do. The retainer covers ongoing maintenance or advisory work, while larger initiatives are scoped and priced as separate projects. This hybrid model gives the client consistent support without forcing large deliverables into the retainer's monthly capacity.
How do you price a retainer?
Most retainers are priced based on the number of hours or the level of capacity reserved per month, informed by the actual usage from previous project work. Pricing a retainer too high relative to usage leads to cancellation; pricing it too low leads to over-delivery and margin erosion. Starting with a three-month trial at a conservative scope is a common approach.