Pricing is the part of a proposal most people dread — and the part that quietly decides whether you win profitably or win at a loss. Learning how to price a proposal isn't about finding one magic number; it's about choosing the right pricing model for the situation, anchoring your number to the value you deliver, and presenting it so the client sees a clear return rather than a big cost.
Get it wrong in either direction and it hurts. Price too low and you devalue your expertise and struggle to cover your costs. Price too high with no justification and you lose the deal. This guide walks through the main pricing models, how to choose between them, how to structure your pricing around value, and how to present it in a proposal so the number lands as reasonable — not as sticker shock.

Start With the Client's Value, Not Your Costs
The most common pricing mistake is starting from the inside out — adding up your hours and costs, applying a markup, and calling it a price. That's cost-plus pricing, and while it's simple, it ignores the only number that actually determines what a client will pay: how much the outcome is worth to them.
Harvard Business School's widely cited value stick framework frames this clearly — a customer's willingness to pay is set by their appreciation of the result, not by your production costs. A project that saves a client $500,000 a year is worth far more than the hours it takes you to deliver it. When you price from value, you capture a fair share of the outcome you create; when you price from cost, you leave that difference on the table.
This doesn't mean ignoring your costs — you need them as a floor to stay profitable. It means your costs set the minimum, while the client's value sets the ceiling, and the right price lives between the two.
The Main Proposal Pricing Models
There's no single correct model — the right one depends on the engagement. Here are the four you'll use most:
Hourly / day rate. You bill for time spent. Simple and low-risk for you, but it caps your income at your hours and quietly penalizes efficiency — the faster you work, the less you earn.
Fixed / project pricing. One agreed price for a defined scope. Clients love the predictability, and it rewards your efficiency — but it only works with a tight scope (and clear exclusions) to prevent scope creep from eating your margin.
Value-based pricing. Priced on the outcome's worth to the client rather than your time. The highest-margin model, but it requires you to quantify the value and have the sales conversation to support it.
Retainer. A recurring fee for ongoing access or a set deliverable each period. Great for predictable revenue and long-term relationships.
Most experienced firms move away from hourly and toward fixed or value-based pricing over time — because those models tie your price to results, not to the clock.
How to Choose the Right Pricing Model
Match the model to the engagement rather than defaulting to whatever you're used to:
Use hourly when scope is genuinely unpredictable or the work is open-ended and hard to define upfront.
Use fixed/project pricing when the deliverables are well-defined and you can scope them tightly — this is the sweet spot for most proposals.
Use value-based pricing when you can clearly quantify the client's outcome (revenue gained, cost saved, risk avoided) and you've had the conversation to agree on it.
Use a retainer when the relationship is ongoing and the client needs continuous access or recurring deliverables.
The single most important input is scope clarity. The tighter your scope, the more confidently you can move away from hourly and toward the models that protect your margin. (If scope is your weak point, our guide on how to write a scope of work is worth a read first.)
Pricing Model Comparison
Hourly / Day Rate | Fixed / Project | Value-Based | |
|---|---|---|---|
Based on | Time spent | Defined scope | Client's outcome |
Client sees | Ongoing meter | One predictable price | Return on investment |
Your margin | Capped by your hours | Rewards efficiency | Highest potential |
Main risk | Penalizes speed | Scope creep | Requires quantifying value |
Best for | Undefined scope | Well-defined projects | Measurable, high-value results |
The pattern is clear: the further right you move, the more your price reflects results instead of effort — and the better your margin, provided you can define scope and value.
How to Present Pricing in a Proposal
How you present the number matters almost as much as the number itself:
Tie every price to a deliverable. When pricing maps to specific outcomes, it reads as justified rather than arbitrary.
Offer options, not a single take-it-or-leave-it number. Presenting two or three tiers (e.g., good / better / best) shifts the client's question from "yes or no?" to "which one?" and often lifts the average deal size.
Lead with value before revealing price. Establish the outcome and ROI first, so the number lands against a backdrop of value rather than in a vacuum.
Be specific about what's included — and excluded. Clear boundaries prevent the "I assumed that was included" conversation later.
Make the price easy to say yes to. Clear payment terms and milestones reduce friction at the moment of decision.
Presenting options is one of the highest-leverage moves here — it's the practical application of tiered pricing, and it consistently outperforms single-price proposals.
Common Proposal Pricing Mistakes
Pricing from cost alone. Cost-plus keeps you safe but leaves value-based money on the table on your best engagements.
Competing only on price. Matching a competitor's low number is a race to the bottom. Add value instead of subtracting price.
A single vague number. One lump sum with no breakdown invites doubt. Itemized, deliverable-linked pricing builds trust.
Ignoring scope creep. A great fixed price becomes a loss if unpriced extras pile up. Define exclusions and a change-request process.
Apologizing for your price. How you present the number signals your confidence in it. State it plainly, backed by value.
Frequently Asked Questions
Should I put pricing in the proposal or send it separately?
In most cases, include it in the proposal — but only after you've established the value and outcomes. Pricing presented against a clear backdrop of ROI lands far better than a number sent in isolation.
How do I price when I don't know the exact scope?
If scope is genuinely unclear, either use hourly pricing or scope a smaller, well-defined first phase (like a discovery or audit) that you can price with confidence, then price the larger project once the scope is known.
What's the difference between cost-plus and value-based pricing?
Cost-plus starts with your costs and adds a markup — it's based on what the work costs you. Value-based pricing starts with the client's outcome and prices a fair share of that value — it's based on what the result is worth to them. Value-based typically yields higher margins but requires quantifying the outcome.
How many pricing options should I offer?
Two or three is the sweet spot. A single price forces a binary yes/no; too many options create decision paralysis. Three tiers let the client self-select based on their budget and needs.
How do I justify a higher price than a competitor?
Shift the conversation from price to value. Quantify the outcome you deliver, show relevant proof, and make the return on investment explicit. Clients pay more when the value gap clearly justifies the price gap.