The Three Classic Pricing Models — and Their Limits
Pricing digital work is rarely comfortable. Fixed price, time and materials, and value-based pricing are the three approaches most freelancers and agencies cycle between, and each one carries a distinct set of trade-offs.
Fixed price is what most clients ask for first. It transfers risk away from them and makes competing proposals easy to compare. The problem is that it pushes all the uncertainty onto you. Early in a project, requirements are fuzzy and technical complications are invisible. You are guessing, and the guess usually lands on the wrong side of profit. Beyond that, fixed price punishes adaptation. When testing reveals a better approach, you cannot take it without reopening a difficult conversation about cost. The model quietly converts the goal from “build the best thing” to “build exactly what was written down, nothing more.”
Time and materials fixes some of that. The client pays for the hours actually worked, so new insights and unexpected complexity are billable rather than corrosive. Transparency improves, underquoting stops being a chronic risk, and the work is free to evolve. But T&M simply moves the discomfort to the client. The final number is open-ended, which makes budgeting hard and sometimes creates anxiety about an ever-growing bill. It demands disciplined time tracking and regular communication, or the final invoice arrives as a surprise. And some clients will always suspect that slowness is being rewarded.
Value-based pricing is the model everyone likes to name-drop. The idea — price based on what the work is worth to the client — sounds far more strategic than billing by the hour. In practice, it rarely holds up. You can only apply it cleanly when the ROI is direct and measurable, like a redesign of an e-commerce storefront. Most web projects do not have that kind of traceable financial outcome. Even when they do, isolating your contribution from the other factors that drive sales is nearly impossible. Add in clients who are reluctant to share financial data, and value-based pricing collapses into a conversation about hypothetical returns nobody can validate.
Start With Appetite, Not Estimates
All three models fail at the same point: the opening conversation. Everyone jumps straight to deliverables and rates, when the useful question is about budget appetite. This is a concept 37signals describes in Shaping Up — appetite is how much the product owner is willing to invest based on the expected return. Framing it that way moves the discussion from “What will this cost?” to “What is this worth to you?”
Leading with appetite has practical advantages. It focuses on the number the client can actually spend, so you are not drafting a $100,000 proposal for someone with $20,000 to commit.
It keeps expectations realistic and lets you flag misalignment early, before either side has invested time in a detailed spec. It also changes the competitive dynamic: when you talk about maximizing the value of a known budget, you are no longer comparing like-for-like line items with other agencies.
A useful analogy is real estate. You can describe your ideal house down to the number of bedrooms and the neighborhood, but an agent still cannot quote a price until they understand the budget. The condition of the property, the surrounding amenities and the market all feed into the final figure. Web projects behave the same way: requirements alone do not determine cost, so there is no point pretending they do.
Split the Project Into Sub-Projects
Once you know the appetite, the most effective structure is to break the work into a sequence of sub-projects rather than committing to an all-in fixed price:
- Reserve roughly 10% of the total budget for a discovery phase, issued as a separate fixed-price contract. Use it to dig into the client’s needs, constraints and goals, and to map the architecture before anyone commits to a build.
- Define what needs to be prototyped, then quote that as its own fixed-price piece. Wireframes, mockups or a working prototype of key features come out of this phase, each one tested with the client.
- Use the evolved prototype as a functional specification for the build. By now you know what you are actually building, so the final fixed price is based on foreknowledge rather than hope.
This approach borrows from both fixed pricing and flexibility. Every phase is a defined commitment with a known price, but you can still redirect between phases based on what you have learned. Scope creep does not disappear, but its cost is contained: new requirements surface during one phase and are priced into the next.
Why Clients Prefer Phase-by-Phase Commitments
Clients respond well to this structure, usually because of the control it returns to them. They can review results at the end of each phase and decide whether to proceed. That gives them a natural exit point at every stage, which makes you a less risky option than an agency demanding a full-project commitment on day one.
The accuracy of pricing also compounds as you move through the phases. A discovery contract for 10% of the budget is necessarily an estimate; a prototype quote benefits from the discovery findings; a build quote built on an approved prototype is about as close to certainty as digital work gets. The more information you have, the less you need to pad your numbers to survive the unknown.
This way of working stays in sync with agile delivery methods and forces ongoing client communication. Check-ins and approvals are not an add-on — they are structural. Each sub-project is small enough to price well, large enough to make the administration efficient, and tested enough to let you move forward with confidence.
Handling Pushback on Value-Based Pricing
When clients are used to fixed-price bids, they may push back against a phased, value-based approach. Here is how to frame your response to the most common objections without losing the sale.
“We need a fixed price for the entire project.”
Offer a rough estimate based on their initial scope, but make clear it is a ballpark figure. Position the sub-project breakdown as a way to price each stage accurately as work is defined, which most agency quotes cannot do. Warn that a single fixed price often leads to scope disputes later.
“This seems more complicated than other proposals we've received.”
Concede that the process may look more involved at first, but stress that it removes guesswork and aligns expectations at every step. The extra structure reduces risk for both sides and increases the odds of a project that actually works.
“We don't have time for all these phases.”
Point out that more phases do not mean a longer timeline. In practice, this approach cuts down on rework and keeps the client and team on the same page so delivery is often faster overall.
“How do we compare your proposal to others if you’re not giving us a fixed price?”
Explain that two agencies can quote the same number for very different implementations and quality levels. Your model guarantees they pay for what they need, not for what they assumed they wanted during the pitch. Ask them to weigh long-term value and lower risk, rather than the initial bottom line.
“We’re not comfortable discussing our budget upfront.”
Use the real estate analogy. A buyer who will not share a price range cannot be shown suitable homes; a client who conceals their budget cannot be given relevant solutions. Knowing their investment appetite is what lets you tailor the proposal to fit.
Adopting this pricing model shifts the client relationship from transactional to collaborative. It lowers the chance of surprises for both parties and makes it far more likely the final deliverable meets the brief.
Pricing isn’t just about numbers — it’s about setting the foundation for a successful project and a positive client relationship.
By being clear about how you work and committing to deliver value inside the client’s stated budget, you can stand out in a crowded market without resorting to underbidding.
