Retainer vs project proposal: which wins more clients
Project proposals win more first-time clients because they ask for less commitment and end on a date. Retainers win when the work is ongoing and the buyer owns a recurring budget. The format that wins most often for a design studio is a scoped project with an optional retainer tier the client can accept in the same document.
The definitions
Define what you are actually pitching: retainer, project or project retainer
A project retainer is a prepaid, scoped block of work with an end date. A retainer is a recurring monthly fee for ongoing access, hours or deliverables. A contract is the legal agreement that holds either one: the pricing model sits inside the contract, it doesn't replace it.
Project or retainer: the edges are different
A project proposal is defined by its edges. It has a start date, an end date, a written scope and a price for the whole engagement, either fixed or estimated. A brand identity, a website redesign or a launch campaign fits this shape: the client has a specific need, and you propose a specific result.
A retainer proposal is defined by continuity. The client pays a recurring fee, usually monthly, and in return gets your time, a set of outputs or simply access to your team. Ongoing design support, content production, social assets and product design for a team that ships every sprint all fit this shape. The work doesn't stop after a single delivery, so the relationship doesn't either.
What a project retainer is, and how it differs from a contract
The phrase project retainer confuses people because it mixes both. In practice it means the client prepays for a defined block of work, often in instalments, and the studio reserves capacity for it. It has a scope and an end date like a project, and a payment rhythm like a retainer. Freelancers often use it to protect a booking: the client pays upfront to hold the dates.
The retainer vs contract question has a simpler answer. A contract is the legal wrapper: parties, terms, payment, ownership, termination. A retainer is a pricing and engagement model that the contract describes. You can have a contract for a fixed project, a contract for a monthly retainer, or a contract that holds both. Asking whether to sign a retainer or a contract is like asking whether to buy a car or a key.
What a retainer means in marketing and design
In marketing, a retainer usually means a monthly fee for an agency or freelancer to stay on call for a brand: campaigns, content, reporting and the small requests in between. Design studios use the word the same way, with the work tilted toward visual output: brand upkeep, new templates, landing pages, social assets and art direction for shoots.
The retainer you write depends on what the client values most. The table below covers the four common types.
Choose the retainer type that matches what the client values
| Retainer type | What the client buys | Fits when | Watch out for |
|---|---|---|---|
| Hours-based | A block of team time each month | Requests are unpredictable and small | Clients count hours instead of outcomes |
| Deliverables-based | A fixed set of outputs each month | The work repeats in a known pattern | Requests that don't fit the list |
| Access-based | Priority access to your thinking and team | The client values judgment and speed | Always-on expectations with no limit |
| Hybrid | Base deliverables plus extra hours | Some work is planned, some isn't | Separate ledgers for base work and extras |
The buyer's side
Match the proposal format to the buyer's signals, not your preferred revenue model
Yes, it is cheaper to retain a customer than to get a new customer: winning a new client means pitching, proposals and unpaid time, while keeping an existing client means doing good work. That is why the format you open with should be the one this buyer is most likely to accept, then grow from there.
Why projects win more first-time clients
Every competitor article on this topic asks which model pays the agency more. That is the wrong question for a proposal. The proposal is the thing being tested, and the buyer decides. A retainer may be better for your cash flow, but if the buyer can't approve it, the proposal loses and the retainer never starts.
Projects win more first-time clients for plain reasons. The commitment is smaller and has an end. The buyer can compare your proposal line by line with others. And the budget usually already exists: someone approved money for a rebrand or a new site, not for an open-ended relationship with a studio they haven't worked with yet.
Who is in the room has changed
Buying is also getting more formal. Procurement teams now sit in on many creative pitches, and procurement prefers a scope, a price and an end date it can compare.
43%
of agencies believe procurement-led pitches have increased
Why retainers win where work is ongoing
Retainers win in different conditions. The work is ongoing by nature. The buyer owns a recurring budget, such as a marketing or product line, rather than a single project fund. And there is trust already: they've worked with you, or with a studio like you, and know the cost of briefing someone new every time.
Pitching is also a coin toss for the studios that do it most. Even agencies that pitch for a living lose often, which is a strong argument for keeping the clients you already have.
50.3%
pitch-win rate in 2021
Read the signals in the discovery call
Read the buyer before you choose the format. The table below is an editorial heuristic, not research: it maps the signals you can pick up in a discovery call to the proposal format most likely to be accepted, and the objection to answer on the page.
Signal-to-format decision table
An editorial heuristic for choosing the proposal format from the buyer's signals.
| Buyer signal | Lean toward | Objection to answer on the page |
|---|---|---|
| Scope is clear and has a launch date | Project | What happens after launch? |
| Scope is fuzzy or keeps growing in the call | Project retainer or paid discovery | Why pay before the scope is final? |
| Budget owner runs a recurring marketing or product budget | Retainer | What do we get each month? |
| Procurement is involved | Project, with an optional retainer tier | How do we compare this with other bids? |
| First project together | Project, with an optional retainer tier | Why commit before seeing your work? |
| Repeat client with steady requests | Retainer | Are we paying for time we don't use? |
| Seasonal or campaign work | Project | Can we book you again for the next season? |
Worked example
See the same engagement written three ways: project, retainer and project with a retainer tier
The same brand-and-site engagement can be written as a fixed project, as a retainer or as a project with an optional retainer tier. Each format puts a different question in the client's head. The illustrative example below shows the price breakdown, the likely objection and how the page answers it.
Illustrative example, with made-up figures. Imagine a fictional studio proposing a brand identity and a marketing site to a fictional skincare brand, worth $24,000 in total. The work is the same in every version: discovery, identity, an 8-page site and launch assets over 12 weeks. Only the proposal format changes.
Version A, the fixed project, prices the whole engagement at $24,000, paid as $9,600 at signature, $7,200 at the identity sign-off and $7,200 at launch. Version B, the retainer, spreads the same work over 6 months at $4,000 a month, with a list of monthly deliverables. Version C, the project with a retainer tier, keeps the $24,000 project and adds an optional care plan at $2,500 a month after launch, with a 3-month minimum and a monthly allowance of design requests.
Example: one $24,000 engagement in three proposal formats
Illustrative example with example prices for a fictional studio and client.
| A: Fixed project | B: Retainer | C: Project with retainer tier | |
|---|---|---|---|
| Headline price | $24,000 | $4,000 a month for 6 months | $24,000, plus $2,500 a month optional |
| Paid at signature | $9,600 | $4,000 | $9,600 |
| Client commits to | 12 weeks, fixed scope | 6 months of fees | 12 weeks, care plan optional |
| Likely objection | What happens after launch? | Why pay for 6 months before any concepts? | Do we have to take the care plan? |
| How the page answers it | A short section on handover and support rates | A review date after month 2 with an exit option | The care plan is an add-on, off by default |
| Studio income after launch | $0 until the next project | Ends after month 6 | $2,500 a month if accepted |
Which version wins, and why
Version A is the easiest to approve and the easiest to compare, which is why it tends to win the first engagement. Its weakness is the cliff after launch: the relationship ends on the day the site goes live.
Version B asks for the most trust. The client is committing to months of fees before seeing a single concept, and nothing on the page can fully remove that worry. It suits a client who already knows you.
Version C, the retainer on-ramp, is usually the strongest for a new client. The decision the client must make is the same as in version A. The retainer is a second, smaller decision they can take now or later, priced next to work they already want. The studio gets a path to recurring income without asking for it up front.
Write the scope boundaries into every version
Name what is included
List each deliverable with its format, so nobody argues later about what a page or a logo suite means.
Name what is not
Write the exclusions down: copywriting, photography, hosting or extra languages, whatever the client might assume.
Set the revision rounds
State how many feedback rounds each stage includes and what an extra round costs.
Define a request
For any retainer tier, say what counts as a single request and how quickly you reply.
Write the change process
New work outside scope gets a short written change order with a price before anyone starts it.
Making it convert
Build the proposal so the client can say yes to the right option
Lead with the project the client asked for, then add the retainer as an optional tier in the same proposal. Give each tier clear deliverables, let the client choose on the page, and read which option they spend time on before you follow up.
Put the retainer on-ramp in the pricing section
Put the project first and price it in full. Then add the retainer as an optional tier directly below, framed around what the client gets after launch: faster turnaround because you already know the brand, priority access, and a fixed monthly scope. A few retainer tiers are enough. Each tier should list its deliverables, its response time and what happens to unused requests.
In Formlio, an interactive pricing block holds both decisions in a single place. The project sits as the main package, and the retainer tiers sit as optional add-ons the client can switch on or off while the total updates. Approval or an e-signature sits right below, so the client can accept the project, the retainer or both in the same document.
Use tracking and the end of the project
Watch what the client reads. Formlio tracks views and the time spent on each section, so you can see whether the client lingered on the retainer tiers or skipped them. Time on the care plan suggests a follow-up about after-launch support. A quick skip suggests leaving it for now and raising it again near launch.
Converting a finished project into a retainer is easier than selling a retainer cold. Near the end of the project, list the requests the client has made that sit outside the scope, and show how a retainer would have covered them. Then send a short proposal with that list, a single recommended tier and a start date the day after launch.
Keep the margin honest
A retainer only stays profitable if you check it. Set a regular review date with every retainer client, and look at the same few things each time: hours delivered against the fee, requests that fell outside the agreed scope, and whether the client still uses what they pay for. Raise prices or adjust the tier when the pattern is clear, not when you're already frustrated.
Guardrails to check on every review date
Overservicing
Compare hours delivered with hours the fee covers, and act on the gap.
Out-of-scope requests
Count them, price them and decide whether they belong in a bigger tier.
Unused capacity
A client who stops using the retainer is about to cancel it; call them first.
Change orders
Check that every project change was written and priced, not absorbed.
Tier fit
Move clients up or down a tier when their real usage no longer matches it.
Questions
Frequently asked questions
Near the end of the project, list the out-of-scope requests the client made and show how a retainer would cover them. Offer a single recommended tier with a start date right after launch, so support continues without a gap.
Price it from the work, not the hours: estimate the monthly deliverables, cost them at your project rates, then offer a small saving for the commitment. Present it in tiers so the client chooses the level rather than judging a single number.
Usually yes, as a project with an optional retainer tier. The client makes the familiar project decision first, and the retainer becomes a smaller second choice they can accept now or later, in the same document.
Start with a short initial term and a review date written into the contract, then roll it over on a notice period. A short first term with an exit option is easier to approve than an open-ended commitment.
Define what counts as a request, list what is included and excluded, cap the monthly allowance and write a change-order process for anything extra. Review hours delivered against the fee on a regular date.
Paying before they've seen results, and paying for time they might not use. Answer both on the page: a review date with an exit option, and a clear rule for unused requests.
Template
Put both options in your next proposal
Build the project and an optional retainer tier in a single document, let the client choose on the page, and see which option they read after you hit send.