Roundups
Consulting Retainer vs. Project Pricing: How Do Small Firms Actually Decide?
Project-based pricing is still the most common model among consultants — 30% use it, narrowly ahead of hourly billing at 29%, according to a Consulting Success survey of nearly 1,000 consultants. Monthly retainers sit at just 16% of consultants, even though a separate finding in the same research shows 41% of consultants want retainer clients but don't currently have them — a real gap between what consultants want and what they've actually built. The honest answer to "which is better" is that project pricing is the default for building trust and proving value early, while retainers are what most consultants are actually trying to grow into once that trust exists.
Last updated Aug 21 · 17 min read
What the survey data actually shows
Consulting Success's fee survey, covering nearly 1,000 consultants, breaks pricing model adoption down as follows: 30% project-based, 29% hourly, 16% monthly retainer, 15% value-based, and 10% daily/per diem rates (consultingsuccess.com, "How to Set Your Consulting Fees?"). Project-based and hourly together account for roughly six in ten consultants — meaning the majority of the industry is still pricing by scope or by time, not by ongoing value or access.
That's despite retainers being widely discussed as the more desirable model for income stability. A separate Consulting Success survey specifically on retainers found that 41% of consultants want retainer clients but don't have them, while only 17% say most of their income already comes from retainers (consultingsuccess.com, "Consulting Retainer Guide"). That 41%-vs-17% gap is the clearest evidence that retainers aren't rare because consultants don't want them — they're rare because the transition from project to retainer pricing is harder to execute than it sounds, and most consultants haven't cracked it yet.
There's also a real earnings signal favoring value-based pricing specifically: 51% of consultants using value-based fees report an average project value of $10K or more, compared to only 39% of consultants billing hourly who reach that same threshold. That's a meaningful gap, and it points to a broader pattern that shows up across all of this data — pricing models tied to outcomes or ongoing value tend to outperform pricing models tied to time.
Project-based pricing: how to calculate it
The standard project-fee formula from Consulting Success works in four steps: list every deliverable in the project, estimate the hours required for each one, multiply the total hours by your hourly rate, then apply roughly a 1.5x multiplier to the result to account for revisions, communication overhead, and unexpected complexity that almost always shows up during a real engagement. Their worked example: 30 hours at $100/hour comes to $3,000, multiplied by 1.5 lands at a $4,500 project fee.
That multiplier is doing real work in this formula — it's an explicit acknowledgment that a first-pass time estimate is almost always optimistic, and that padding the number protects margin rather than being a dishonest markup. Consultants who skip the multiplier and quote the raw hours-times-rate figure are the ones who most often end up working for less than their stated rate once scope creep and revisions eat into the unpadded estimate.
The retainer decision: when to make the switch
The clearest, most repeated piece of guidance from Consulting Success's retainer research is timing: propose a retainer after completing at least one successful project, not during the first engagement (consultingsuccess.com, "Consulting Retainer Guide"). Trust has to be established first — a retainer asks a client to commit to ongoing access or deliverables before every project's results are in, and that's a much harder sell from a consultant with no track record with that specific client yet.
The research also identifies concrete signals that a client is ready for the conversation: they start asking "what else can we work on together," or they express concern about losing access to your expertise once the current project wraps. Both signals indicate the client has already mentally shifted from "this is a one-time fix" to "this person is part of how we operate" — which is exactly the psychological position a retainer formalizes.
Project-based pricing has real, well-documented downsides that explain why so many consultants want to move away from it despite it being the most common model: it creates a "feast-or-famine" revenue cycle, constant pressure to land the next client, and — because it's still fundamentally trading time for money — limited scalability even for a consultant who's good at winning projects (consultingsuccess.com). Retainers directly address the first two problems by converting revenue from a series of one-off wins into something closer to recurring income, which is why the desire for retainers (41% wanting them) so consistently outpaces actual adoption (17% getting most income from them) — the appeal is obvious, the execution is the hard part.
The 5X Rule for pricing a retainer
Consulting Success's core pricing heuristic for retainers is to aim to deliver five times the value of what you charge, then price the retainer at roughly 20% of the monthly value you're generating for the client. Their worked examples: charge $1,500/month while generating $7,500 in monthly value; charge $10,000/month while generating $50,000; charge $25,000/month while generating $125,000. The ratio stays constant across price points — it's a value-based pricing logic wearing a simple round-number rule, which makes it easy to explain to a client even if the underlying value calculation took real analysis to get to.
The rule only works, of course, if you can actually estimate and communicate the value you're generating — which is a harder skill than the arithmetic suggests. A consultant who can't articulate "this retainer is generating roughly $X per month in value because of Y and Z" is really just guessing at a number, and clients can usually tell the difference between a justified price and an arbitrary one.
Two kinds of retainers: pay-for-work vs. pay-for-access
Not all retainers work the same way, and the distinction matters for pricing them correctly:
Pay-for-work retainers commit the client to specific, defined deliverables each month — structurally, this is closer to an ongoing project than a true retainer, and it's often the easier first step for building the trust described above, since the client can see exactly what they're getting for the money.
Pay-for-access retainers have the client paying for the consultant's availability and expertise, not a guaranteed list of deliverables. This is the more advanced model, and it genuinely decouples income from hours worked in a way pay-for-work retainers don't — but it requires the level of established trust described earlier, because the client is essentially paying for peace of mind and priority access rather than a checklist.
Most consultants transitioning off project pricing start with pay-for-work retainers and migrate toward pay-for-access as the relationship matures — which mirrors the broader "prove it, then formalize it" pattern that runs through all of this guidance.
Practical examples
Consulting Success's own published material names several consultants who've built substantial practices around retainer or value-based models: Sarah Borders built a $1.5M-revenue practice with a nine-person team using the retainer model; Tony Velasquez reported a 4x revenue increase through value-based retainer pricing; Phil Risher built a $1.1M practice largely through retainers; and Sam Schutte reached seven-figure revenue using retainer models (consultingsuccess.com). These are named, published examples from Consulting Success's own case-study material rather than independently verified financial disclosures, so they should be read as the source's own client success stories rather than third-party-audited figures — but they're consistent with the broader pattern the survey data shows: consultants who successfully make the retainer transition report meaningfully different revenue outcomes than those who stay purely project-based.
Data and evidence
– Pricing model distribution (survey of ~1,000 consultants): 30% project-based, 29% hourly, 16% monthly retainer, 15% value-based, 10% daily/per diem (consultingsuccess.com, "How to Set Your Consulting Fees?").
– 51% of value-based consultants report average project value of $10K+, vs. 39% of hourly consultants (consultingsuccess.com).
– 38% of consultants report earning $10K+ per month (consultingsuccess.com).
– Project fee formula: (hours × hourly rate) × ~1.5 multiplier for revisions/complexity (consultingsuccess.com); worked example: 30 hrs × $100/hr = $3,000 × 1.5 = $4,500.
– 41% of consultants want retainer clients but lack them; only 17% say most of their income already comes from retainers (consultingsuccess.com, "Consulting Retainer Guide").
– The 5X Rule: aim to deliver 5x the value charged; price the retainer at roughly 20% of monthly value generated (consultingsuccess.com); examples: $1,500/mo fee for $7,500/mo value, $10,000/mo fee for $50,000/mo value, $25,000/mo fee for $125,000/mo value.
– Named client examples of retainer/value-based success (Sarah Borders, Tony Velasquez, Phil Risher, Sam Schutte) come from Consulting Success's own published case-study material — treat as the source's client success stories, not independently audited figures.
Comparisons
Retainer vs. project-based pricing. Project-based pricing wins on client comfort (a defined scope and price is easier to say yes to) and is the most common model industry-wide. Retainers win on consultant income stability and scalability, but require established trust and clear scope boundaries to avoid the scope-creep risk that comes with an engagement that isn't bounded by a fixed deliverable list.
Hourly vs. value-based pricing. Hourly billing is simple to explain and track but caps earnings to time worked and is associated with lower reported project values (39% reaching $10K+ vs. 51% for value-based). Value-based pricing requires more upfront skill in quantifying client value but is associated with meaningfully higher project values in the same survey data.
Pay-for-work vs. pay-for-access retainers. Pay-for-work retainers are easier to sell early (clear deliverables, easier for the client to justify) but still resemble project work in structure. Pay-for-access retainers fully decouple income from hours but require a level of trust that usually only exists after a successful project history with that specific client.
The 5X Rule vs. the project-fee formula. The project-fee formula (hours × rate × 1.5) is fundamentally a cost-plus calculation. The 5X Rule is a value-based calculation (price as ~20% of value delivered). They're not competing methods for the same pricing decision — they're suited to different engagement types, which is part of why a consultant's pricing approach often needs to change as they shift from project work toward retainers.
Real-world use cases
– A consultant early in a client relationship: project-based pricing with the hours × rate × 1.5 formula is the appropriate starting point, since there's no established trust yet to support a retainer conversation.
– A consultant who's just completed a successful first project and the client is asking "what else can we do together": this is the documented signal to propose moving to a retainer, per Consulting Success's guidance.
– A consultant who wants to escape feast-or-famine income: moving toward retainers directly addresses the two most-cited downsides of project pricing (unpredictable cash flow, constant new-client pressure) — but the 41%-vs-17% gap in the survey data shows this transition is harder in practice than in theory.
– A consultant trying to price a new retainer offer: the 5X Rule (price at ~20% of estimated monthly value delivered) gives a concrete, explainable starting point rather than picking an arbitrary monthly number.
Common mistakes
– Proposing a retainer during the first engagement, before any trust has been established — Consulting Success's guidance is explicit that this should come after a successful project, not during one.
– Quoting a project fee as raw hours × hourly rate without the ~1.5 multiplier, then absorbing the cost of revisions and scope creep out of margin instead of pricing for it upfront.
– Assuming a pay-for-access retainer is the right starting point with a new client, when pay-for-work retainers are the more realistic first step before that level of trust exists.
– Pricing a retainer as an arbitrary round number instead of grounding it in an estimate of the value actually being delivered (the logic behind the 5X Rule).
– Staying purely project-based indefinitely despite wanting the income stability of retainers (a documented gap — 41% want retainer clients but don't have them) without ever proposing the transition to an eligible client.
– Letting a retainer's scope drift without boundaries, since an engagement not bounded by a fixed deliverable list is more exposed to scope creep than a project with a defined end point.
– Treating hourly billing as a "safe default" without recognizing the earnings gap the survey data shows between hourly and value-based/retainer approaches.
Best practices
– Use project-based pricing to build the first relationship with a new client, and treat that project's success as the foundation for a later retainer conversation.
– Apply a realistic multiplier (roughly 1.5x) to your raw hours × rate estimate for any project fee, to protect margin against revisions and scope creep.
– Watch for the two documented signals a client is ready for a retainer: asking what else you can work on together, or expressing concern about losing access to your expertise.
– When pricing a retainer, try to estimate the actual monthly value you're generating for the client, then price at roughly 20% of that figure (the 5X Rule) rather than picking a number that feels reasonable.
– Start new retainer relationships as pay-for-work, and consider migrating to pay-for-access only once the relationship has matured enough to support that level of trust.
– Set clear scope boundaries on any retainer from the start, since the absence of a fixed deliverable list is exactly what makes retainers more vulnerable to scope creep than project work.
– If you're stuck at project/hourly pricing and want retainer income stability, treat the 41%-vs-17% gap as evidence that the barrier is usually execution (how and when you ask), not client willingness.
Key takeaways
– Project-based pricing remains the most common consulting model (30%), narrowly ahead of hourly (29%), while retainers sit at just 16% despite 41% of consultants wanting retainer clients.
– The project-fee formula — hours × rate × ~1.5 — builds in a margin buffer for revisions and complexity that a raw hours-times-rate quote doesn't.
– Propose a retainer after a successful project, not during the first engagement — trust is the prerequisite, not the pitch.
– The 5X Rule (price at ~20% of monthly value delivered) gives retainer pricing an explainable, value-anchored logic instead of an arbitrary number.
– Value-based and retainer models are associated with meaningfully higher reported project values than hourly billing in the same survey data.
Relevant tools.scult.in resources
Whichever pricing model you land on, the invoicing needs to match it — the Invoice Generator works equally well for a one-off project fee calculated with the hours-times-rate formula above, or a consistent recurring invoice for a retainer client, which matters for reinforcing the "ongoing relationship" framing that supports retainer pricing in the first place.
If this is a gap worth closing properly rather than patching once, get in touch about what Scult builds.
For a related, free starting point, try the AI Visibility Checker.
Frequently asked questions
What is a consulting retainer?
An ongoing monthly (or periodic) fee arrangement where a client pays for a consultant's continued deliverables or availability, rather than a one-time project fee.
What is project-based consulting pricing?
A fixed or estimated fee for a defined scope of work with a clear start and end point, calculated from estimated hours and an hourly rate.
Is retainer or project pricing better for consultants?
Neither is universally better — project pricing is easier to sell early and remains the most common model; retainers offer more income stability and scalability but require established trust and clear scope boundaries.
What percentage of consultants use project-based pricing vs. monthly retainers?
30% use project-based pricing, 16% use monthly retainers, per a Consulting Success survey of nearly 1,000 consultants.
What is value-based pricing?
Pricing tied to the value or outcome delivered to the client, rather than to hours worked or a fixed project scope.
Do value-based consultants earn more than hourly consultants?
Survey data shows 51% of value-based consultants report project values of $10K+, compared to 39% of hourly consultants.
How do you calculate a project-based consulting fee?
List deliverables, estimate hours per deliverable, multiply by your hourly rate, then apply roughly a 1.5x multiplier for revisions and unexpected complexity.
What is the most popular consulting pricing model?
Project-based pricing, at 30% of consultants, narrowly ahead of hourly billing at 29%.
When should a consultant move a client from a project fee to a retainer?
After completing at least one successful project, especially once the client starts asking what else they can work on together or worries about losing access to your expertise.
What are the downsides of project-based consulting pricing?
It creates a feast-or-famine revenue cycle, ongoing pressure to find new clients, and limited scalability since it still trades time for money.
What is the "5X Rule" for pricing a consulting retainer?
Aim to deliver five times the value of what you charge, pricing the retainer at roughly 20% of the monthly value generated for the client.
Why do consultants want retainers if project pricing is more common?
Because retainers offer income stability and scalability that project pricing structurally can't — but the survey data shows a real gap between wanting retainer clients (41%) and actually having them (17%), reflecting how hard the transition is to execute.
What risk comes with retainer pricing that doesn't come with project pricing?
Scope creep — retainers aren't bounded by a fixed deliverable list the way projects are, so unclear boundaries can let the workload grow without a matching increase in fee.
What's the difference between a pay-for-work and a pay-for-access retainer?
Pay-for-work retainers commit to specific monthly deliverables, similar in structure to ongoing project work; pay-for-access retainers charge for availability and expertise without a guaranteed deliverable list.
Why does the project-fee formula use a 1.5x multiplier?
To account for revisions, client communication overhead, and unexpected complexity that almost always exceed a first-pass time estimate.
Does hourly billing cap how much a consultant can earn?
Effectively yes — since income is directly tied to hours worked, it structurally limits scalability compared to value-based or retainer models.
Is retainer pricing suitable for a brand-new client relationship?
Generally no — the documented guidance is to establish trust through a successful project first, then propose a retainer.
What signals indicate a client is ready to discuss a retainer?
The client asking what else they can work on with you, or expressing concern about losing access to your expertise once the current project ends.
Does daily/per diem pricing fit into this comparison?
It's a less common model (10% of consultants) that sits closer to hourly billing in structure — priced per day rather than per hour, but still fundamentally time-based.
Is it common for consultants to use more than one pricing model at once?
Yes — many consultants use project pricing for new clients while running retainers with established ones, rather than committing to a single model across their entire practice.
How do I price a consulting retainer using the 5X Rule?
Estimate the monthly value you're generating for the client, then price the retainer at roughly 20% of that figure.
How do I transition a client from project to retainer pricing?
Wait until after a successful project, watch for signals like the client asking about ongoing work, then propose a retainer framed around continued access to your expertise or ongoing deliverables.
How do I calculate a project-based consulting fee step by step?
List all deliverables, estimate hours for each, sum the hours, multiply by your hourly rate, then multiply the result by roughly 1.5 to account for revisions and complexity.
How do I decide between a pay-for-work and pay-for-access retainer structure?
Start with pay-for-work for newer client relationships; consider pay-for-access once the relationship has matured enough that the client trusts your judgment without a defined deliverable list.
How do I set boundaries on a retainer to avoid scope creep?
Define upfront what's included in the retainer fee (hours, deliverable types, response time) and what would trigger an additional charge, and put it in writing before starting.
How do I estimate the monthly value I'm generating for a retainer client?
Look at measurable outcomes tied to your work — revenue influenced, costs saved, time freed up — and translate that into a rough monthly dollar figure to anchor the 5X Rule calculation.
How do I move from hourly billing toward value-based pricing?
Start by tracking outcomes (not just hours) on your current projects, then use that outcome data to price your next proposal around value delivered rather than time spent.
How do I invoice a retainer client consistently each month?
Set a fixed monthly invoice date and amount as part of the retainer agreement, and use a consistent invoice format so the recurring nature of the engagement is clear to the client's accounts team.
How do I know if my project fee was underpriced?
If actual hours consistently exceed your estimate without a corresponding increase in fee, that's a sign your multiplier or hourly rate needs to be higher on future quotes.
How do I explain the 5X Rule to a client who's skeptical of retainer pricing?
Show the value math directly — the estimated monthly value you're generating versus the proposed fee — so the retainer price is anchored to a number they can evaluate, not an arbitrary figure.
Can a consultant run a hybrid model with both project and retainer clients simultaneously?
Yes, and it's common — many consultants keep project pricing for new or one-off clients while running retainers with their most established relationships.
Does the 5X Rule apply the same way across all consulting niches?
The underlying logic (price as a fraction of value delivered) generalizes, but the ability to quantify "value" varies significantly by niche — a revenue-focused consulting engagement is easier to value than a purely advisory one.
How should a consulting firm (not just a solo consultant) think about retainer vs. project pricing differently?
A firm has more capacity to run multiple pricing models simultaneously across different consultants or teams, and can potentially standardize the transition-to-retainer process across client relationships rather than handling it ad hoc.
Does retainer pricing change how a consulting practice is valued if sold?
Consulting Success's guidance notes that predictable retainer income is associated with a higher business valuation for potential sale or acquisition compared to project-based revenue, which is inherently less predictable.
What's the risk of over-committing to pay-for-access retainers across too many clients at once?
Since pay-for-access retainers charge for availability rather than defined deliverables, taking on too many simultaneously risks being unable to actually deliver the responsiveness clients are paying for.
Retainer vs. project-based consulting pricing — which is more common?
Project-based is more common (30% vs. 16% for retainers), even though retainers are the model more consultants say they want.
Hourly vs. value-based consulting fees — which produces higher project values?
Value-based pricing is associated with higher project values (51% reaching $10K+ vs. 39% for hourly).
Value-based pricing vs. hourly rate consulting — which is harder to start with?
Value-based pricing is harder to start with because it requires quantifying client value accurately; hourly billing is simpler to calculate but caps earnings to time worked.
Pay-for-work vs. pay-for-access retainers — which is the better starting point?
Pay-for-work is generally the better starting point for newer client relationships; pay-for-access is a more advanced model suited to established trust.
Project-based fees vs. daily/per diem rates — what's the real difference?
Project fees are calculated from total estimated hours across the whole scope; daily rates are a flat per-day charge regardless of the specific hours worked that day — both are time-anchored, but structured differently.
My consulting income is feast-or-famine — what should I change?
This is the most-cited downside of pure project-based pricing; consider proposing a retainer to your most established clients as a way to build predictable income alongside project work.
A client won't agree to a retainer — what now?
Reassess whether the trust and value signals (a completed successful project, the client asking about ongoing work) are actually present yet — proposing a retainer too early is a common reason clients decline.
My consulting project scope keeps creeping without more pay — how do I fix this on future projects?
Apply the project-fee formula's 1.5x multiplier more aggressively, and define deliverables explicitly enough that added requests are clearly identifiable as out-of-scope add-ons.
I think I'm underpricing my consulting fees — how do I check?
Compare your current pricing model and rates against the survey benchmarks in this article (e.g., the $10K+ project-value thresholds for value-based vs. hourly consultants) to see where you sit.
I proposed a retainer and the client seemed confused about the pricing — what went wrong?
Likely a missing value justification — anchor the retainer price to an explicit estimate of monthly value delivered (the 5X Rule) rather than presenting a number without that context.
Should I switch my whole consulting practice to retainer pricing?
Not necessarily — many successful consultants run a hybrid model, using project pricing for new clients and retainers for established ones, rather than committing fully to one model.
Is it worth using a consulting retainer agreement template instead of drafting one from scratch?
Yes, particularly for defining scope boundaries clearly upfront — a template that explicitly separates included work from billable extras reduces the scope-creep risk retainers carry.
Is it worth using an invoice generator built for recurring billing for retainer clients?
Yes — consistent, professional recurring invoices reinforce the "this is an ongoing relationship" framing that supports the retainer model, compared to ad hoc invoices that look more like one-off project billing.
Should I hire help to manage retainer client relationships as my practice grows?
Once retainer clients require more responsiveness than you alone can consistently deliver (a real risk with pay-for-access models specifically), it's worth considering support staff or a small team rather than over-committing personally.
How do I decide whether to raise my consulting rates or switch pricing models entirely?
If the underlying issue is capped earnings from time-based billing, switching models (toward value-based or retainer) often addresses the root cause more directly than simply raising an hourly rate within the same model.
