How is software work priced?
Fixed price, hourly, milestones, value-based, subscription — every quote you'll ever get uses one of a handful of pricing models. Here's what each one really means, who carries the risk, and why modern agencies mix them across a project.
What a pricing model actually is.
Software pricing model, defined
A pricing model defines how the cost of a software or web project is calculated and paid — one agreed amount for a defined scope, an hourly rate for actual time spent, instalments tied to milestones, a monthly subscription, or a fee based on the business value delivered. Each model really answers one question: who carries the risk when reality differs from the estimate?
The pricing model is one of three choices that shape a project — the other two are the development methodology (how the team works) and the engagement model (how you work together over time). They fit together: plan-first methods pair naturally with fixed prices; iterative methods pair with time-based or subscription pricing, because the scope evolves.
- What it decides
- How the cost is calculated — by scope, by time, by milestone, or by value.
- What it really moves
- Risk. No model makes work cheaper — each decides who pays when estimates are wrong.
- What it pairs with
- The methodology and the engagement model — the three are usually chosen together.
- What to ask first
- “How certain is my scope?” — the honest answer picks the model for you.
The seven models, in plain words.
All figures below are illustrative examples, not quotes — real numbers depend on scope, region and team. What matters is the shape of each deal.
Who carries the risk, in each model.
| Model | Best for | Who carries the risk | Flexibility |
|---|---|---|---|
| Fixed price | Small, clearly defined projects | Agency | Low |
| Time & materials | Agile builds, evolving products | Client | High |
| Milestone-based | Medium projects | Shared | Medium |
| Pay-as-you-go | Occasional fixes & tweaks | Client (small stakes) | High |
| Value-based | Measurable, high-impact outcomes | Shared, on the outcome | Medium |
| Retainer | Ongoing support & marketing | Shared | Medium |
| Subscription | Continuously improved products | Shared | High |
Note: all example figures on this page are illustrative, not quotes. No model is inherently cheapest — each moves risk rather than removing cost. The right model is the one that matches how certain your scope really is.
What most modern agencies actually do.
Real projects rarely use one model end to end, because certainty changes as the product evolves. Early phases are small and definable — they suit fixed prices. The main build has unknowns — it suits time & materials or milestones. After launch, improvement never stops — it suits a subscription. A common lifecycle:
This is also how we price: a fixed-price Discovery Sprint, a fixed-price Prototype Sprint (creditable toward the build), a build scoped from the validated plan, and a monthly Care & Growth phase — because software is improved through small, high-impact iterations, not infrequent rebuilds.
See it applied
Our packages follow this exact lifecycle.
Discovery Sprint → Prototype Sprint → The Build → Care & Growth. Each step de-risks the next, and every sprint's output is yours to keep.
Pricing, answered.
What's the difference between fixed price and time & materials?
Fixed price is one agreed amount for a defined scope — the agency carries the estimating risk. Time & materials pays for actual hours at agreed rates — you carry more risk but can change direction anytime.
Fixed suits small, clearly defined projects; T&M suits evolving products.
What is value-based pricing?
The fee is set from the business impact, not the hours — e.g. an automation that saves $200,000 a year might be priced at $40,000. Common in consulting and AI projects where the outcome is measurable and large relative to the effort.
How do milestone payments usually split?
A typical split: 20% upfront, 30% after design approval, 30% after development, 20% on launch. The exact split varies — the principle is that neither side gets far ahead of the other.
Why do agencies mix models across one project?
Because certainty changes as the product evolves: discovery and prototypes are definable (fixed price), the build has unknowns (T&M or milestones), and post-launch improvement is continuous (subscription or retainer). Mixing models matches the price to the risk at each stage.
Is a pricing model the same as an engagement model?
No. The pricing model is how cost is calculated; the engagement model is how you work together over time — project, retainer, or dedicated team. They usually get chosen together — see our guide to engagement models.