Choosing between a retainer agreement and a project-based service agreement is one of the most important structural decisions in any professional services relationship. The wrong choice can lead to scope disputes, payment conflicts, and misaligned expectations — for both the service provider and the client.
This guide breaks down when each model works best, how to structure the key clauses, and what to watch for when drafting either type of service agreement.
What Each Model Actually Means
Retainer Agreements: Paying for Access and Availability
A retainer agreement creates an ongoing relationship where the client pays a recurring fee — usually monthly — in exchange for a guaranteed allocation of the service provider's time, expertise, or availability.
The client isn't necessarily paying for specific deliverables. They're paying for:
- Priority access to the provider's time and skills
- Continuity — the provider maintains context about the client's business
- Flexibility — the specific tasks may vary month to month
- Guaranteed availability — the provider reserves capacity for the client
Retainers are common in:
- Marketing and content agencies
- Legal counsel (monthly legal advisory retainers)
- Design and brand support
- IT managed services and ongoing technical support
- Management consulting and strategic advisory
- Bookkeeping and accounting services
Project-Based Agreements: Paying for Outcomes
A project-based agreement covers a single, defined engagement with a clear start date, end date, scope, and set of deliverables. The client pays for a specific outcome — a website, an audit report, a brand identity system, a software application.
The provider commits to:
- Defined deliverables with acceptance criteria
- A timeline with milestones and deadlines
- A fixed or capped fee tied to the scope of work
- Completion — the engagement has a natural endpoint
Project agreements are common for:
- Website design and development
- Brand identity and logo design
- Software development (fixed-scope features or MVPs)
- Business consulting engagements (strategy workshops, market analysis)
- Construction and renovation projects
- Tax preparation and annual audits
Side-by-Side Comparison
| Factor | Retainer | Project-Based | |--------|----------|---------------| | Duration | Ongoing (month-to-month or annual) | Fixed (weeks to months) | | Scope | Flexible, varies each period | Fixed, defined upfront | | Billing | Recurring fee (monthly/quarterly) | Milestone-based or fixed fee | | Payment timing | Beginning of each period | Deposit + milestones + final | | Deliverables | Ongoing support and tasks | Specific outputs with criteria | | Risk allocation | Client bears underutilization risk | Provider bears scope-creep risk | | Termination | Notice period (30-90 days typical) | Completion or breach | | Best for | Ongoing, variable-scope needs | One-time, defined outcomes |
When to Use a Retainer
The Work Is Ongoing and Unpredictable
If the client needs regular support but can't predict exactly what they'll need each month, a retainer provides the flexibility to handle varying requests without renegotiating the contract for each task.
Example: A growing startup retains a marketing agency for 40 hours per month. Some months they need social media content, other months they need sales collateral, and occasionally they need a landing page built. The retainer covers all of it without separate scopes for each request.
Continuity and Context Matter
Some work benefits enormously from a provider who deeply understands the client's business, industry, competitors, and internal processes. Switching providers for each project means losing accumulated context and paying the ramp-up cost every time.
Example: An outside general counsel on retainer understands the company's contracts, past disputes, regulatory landscape, and risk tolerance. A project-based lawyer hired for a single contract review won't have that context.
The Client Wants Priority Access
Without a retainer, the provider owes the client nothing between engagements. They might be fully booked when the client needs urgent help. A retainer guarantees capacity.
Example: A SaaS company retains a design agency at 20 hours per month. When a critical product launch requires immediate design support, the agency has reserved capacity to respond — something they couldn't guarantee for non-retainer clients.
When to Use a Project-Based Agreement
The Scope Is Clear and Finite
If you can define exactly what needs to be done, what the deliverables are, and when it should be complete, a project agreement is cleaner and more appropriate than a retainer.
Example: A company needs a new 12-page website with specific sections, branding, and functionality. The scope of work is defined, the deliverables are concrete, and the project has a natural endpoint.
Budget Predictability Is Critical
Project agreements give the client a known total cost. Retainers provide monthly cost predictability but uncertain total spend over time. When the client needs to budget precisely for a specific outcome, project-based is better.
Example: A nonprofit with a $15,000 grant for brand development needs to know that the engagement will cost $15,000, not "$3,500/month for however long it takes."
Accountability for Outcomes Matters More Than Availability
Retainers compensate for availability. Project agreements compensate for delivery. If the client's primary concern is "will this get done, on time, at the agreed quality," a project agreement with milestones and acceptance criteria creates stronger accountability.
Key Clauses That Differ Between the Two
Scope Definition
Retainer: Scope is defined broadly — the types of work covered, the hours allocated per period, and any exclusions.
"Provider will deliver marketing strategy consulting, content creation, and campaign management services up to 40 hours per month. Website development, paid media management, and video production are excluded from the retainer scope and require a separate project agreement."
Project: Scope is defined precisely — the specific deliverables, acceptance criteria, and what's out of scope.
"Provider will deliver: (a) brand strategy document, (b) logo in 5 color variations, (c) brand guidelines PDF, and (d) business card and letterhead templates. Deliverables are subject to the acceptance criteria in Exhibit A."
Payment Structure
Retainer: Flat monthly fee, paid in advance. May include overage rates for hours exceeding the allocation.
"Client will pay Provider $5,000 per month, due on the 1st of each month. Hours exceeding the 40-hour monthly allocation will be billed at $150/hour. Unused hours do not roll over."
Project: Milestone-based payments or a fixed fee with a deposit.
"Total project fee: $18,000. Payment schedule: 30% ($5,400) upon execution; 30% ($5,400) upon design approval; 40% ($7,200) upon final delivery and acceptance."
Termination
Retainer: Either party can terminate with a notice period. The agreement should address what happens to prepaid fees and work in progress.
"Either party may terminate this agreement with 30 days' written notice. If Client terminates, Provider will deliver all work completed as of the termination date. Prepaid fees for the current period are non-refundable."
Project: Termination is typically tied to breach, missed milestones, or mutual agreement. Early termination by the client usually requires a kill fee.
"Client may terminate for convenience with 15 days' written notice. Upon early termination, Client will pay for all completed milestones plus 25% of the remaining project fee as a termination fee."
Intellectual Property
Both types should address IP ownership, but the timing differs.
Retainer: IP typically transfers upon payment for each period's work. Work created during the retainer belongs to the client once the corresponding retainer fee is paid.
Project: IP usually transfers upon full payment of the project fee and final acceptance of deliverables. The provider retains ownership of work product until the client has paid in full.
Scope Creep Protection
Retainer: The hour cap is the built-in scope protection. Anything beyond the allocated hours triggers overage billing or requires a separate project scope.
Project: A change order process is essential. Any work outside the defined scope requires a written change order with revised fees and timeline before work begins.
"Changes to the project scope require a written Change Order signed by both parties. Change Orders will specify the revised deliverables, additional fees, and adjusted timeline. Provider is not obligated to perform out-of-scope work without an approved Change Order."
Hybrid Models: Retainer + Project
Many professional services relationships use both models together:
- Base retainer covers ongoing operational support (20 hours/month for maintenance, minor updates, and advisory calls)
- Project add-ons cover larger initiatives (new feature development, campaigns, audits) scoped and billed separately
This approach gives the client continuous access for day-to-day needs while maintaining clear scope and budget boundaries for bigger efforts.
To structure this, include a clause like:
"Work falling outside the scope of ongoing retainer services — including but not limited to new product launches, platform migrations, and projects requiring more than 15 hours — will be scoped as a separate project engagement under a Project Addendum to this agreement."
Common Mistakes to Avoid
Mistake 1: Using a Retainer Without Hour Tracking
If the provider doesn't track hours, neither party knows whether the allocation is being used, underused, or exceeded. Disputes become impossible to resolve without records. Always require time tracking, even for retainer relationships.
Mistake 2: Using a Project Agreement Without Change Order Process
Without a formal change order mechanism, every client request becomes a negotiation about whether it's "in scope." This creates friction and delays. Define the process upfront.
Mistake 3: Not Defining What Happens to Unused Retainer Hours
"Use it or lose it" and "rollover with cap" are both valid approaches, but the agreement must be explicit. Ambiguity here creates end-of-month conflicts and resentment.
Mistake 4: Vague Acceptance Criteria in Project Agreements
"Client will review and approve deliverables" means nothing without criteria. Define what constitutes acceptance, how many revision rounds are included, and what happens after the final revision.
Mistake 5: No Termination Clause
Both agreement types need clear exit ramps. A retainer without a termination clause locks both parties in indefinitely. A project agreement without one leaves the client stuck if the provider underperforms — and the provider stuck if the client goes silent.
Which Agreement Do You Need?
Choose a retainer when:
- You need ongoing access to specialized skills
- The scope varies month to month
- Continuity and institutional knowledge matter
- You want predictable monthly costs
- The work is support-oriented, not deliverable-oriented
Choose project-based when:
- You have a defined outcome with clear deliverables
- The work has a natural start and end date
- You need total cost predictability for a specific initiative
- Accountability for delivery is more important than ongoing availability
- You're engaging a provider for the first time and want to test the relationship
Choose a hybrid when:
- You need both ongoing support and periodic large initiatives
- The relationship is established and you want flexibility for different work types
Create Your Service Agreement
Whether you need a retainer agreement for ongoing support or a project-based contract for a specific engagement, you can generate a professionally drafted service agreement that covers scope, payment, IP, and termination in minutes.
Create your service agreement →
This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation.