Fixed-Scope vs Hourly Billing: What SMEs Actually Pay
Both models build software. They differ in who carries the risk when the work takes longer than expected — and that difference decides your final invoice.
What is the difference between fixed-scope and hourly billing?
Fixed-scope billing sets one price per milestone, agreed in writing before work starts, so the cost cannot drift. Hourly billing charges for time spent, so an estimate is not a cap — the longer the work takes, the more you pay. Fixed scope places delivery risk on the vendor; hourly places it on your budget.
Fixed-scope vs hourly, side by side
| Dimension | Fixed-scope (AnyPlace) | Hourly retainer |
|---|---|---|
| Pricing model | Fixed price per milestone, agreed in writing before work | Hourly rate (time-and-materials) with an initial estimate |
| Incentive | We earn by shipping the agreed scope on time | The longer it takes, the more it costs you |
| Scope changes | New scope is a newly priced stage you approve in writing | Every change becomes a change-order invoice |
| Visibility | Working software demoed every week in your repository | Status reports and a demo near the end |
| Budget risk | Capped at the milestone price; you can stop after any release | Final invoice can exceed the estimate by 2–3x |
| Handover | Code, docs and access lists handed over; IP assigned to you | Code released on final payment, sometimes with dependencies |
| Best for | Defined outcomes with a clear scope and budget | Genuinely unknown, research-heavy exploration |
Example: the same app, two billing models
| Line item | Fixed-scope | Hourly |
|---|---|---|
| Discovery and written scope | $1,200 – $2,800 (credited) | 10–25 hours of meetings and documents |
| First working release | Fixed milestone price | 80–120 hours billed before you see it |
| Scope change | Swapped or newly priced stage | Change-order at the same hourly rate |
| Total for a 3–5 workflow app | from $5,000, capped | $18,000 – $52,000 (typical drift) |
Illustrative figures based on typical engagement ranges, not a quote. See pricing ranges.
Common questions
Is fixed-scope more expensive than hourly?
Not usually. Fixed scope removes the agency incentive to stretch work. You pay for a defined outcome, and the price cannot drift mid-project. Hourly can look cheaper per hour but routinely costs more in total once rework, meetings and change-orders are billed.
What if the scope was wrong?
Changes become a newly priced stage that you approve in writing before any work starts. Finished stages stay fixed, so nothing drifts silently into the invoice — and you can stop after any working release.
Can I see the work as it progresses?
Yes. Every week you get a live demo of working software in your own repository, with tests and documentation. You redirect scope early, before it hardens into cost.
When is hourly actually the right choice?
Hourly suits genuinely open-ended research with no defined outcome. If your goal is a specific working system — a store, app, dashboard or platform — fixed scope protects your budget better.
Content last reviewed October 2026.
More comparisons
Other comparisons worth reading
Each comparison answers a different question — billing model, team model, vendor choice or technology. These are the ones buyers read next.
Team model
Agency vs In-House Team
Time to first release, year-one cost and code ownership compared, so you can choose how to build your product team.
Read the comparison
Make or purchase
Build vs Buy Software
When a SaaS subscription is enough — and when a custom build pays for itself in process cost and lock-in you avoid.
Read the comparison
Team model
Staff Aug vs Dedicated Team
Who plans the work, who owns quality, and which staffing model fits a new product versus a missing skill.
Read the comparison
See all 12 comparisons — billing model, team model, vendor choice, sector economics and technology trade-offs.
Related services
Services Priced This Way
Discovery, fixed-scope builds and fixed-price pilots — what each includes and where the cost actually moves.
- Custom Software DevelopmentScope doc + tested releasesDiscovery typically 1–3 weeks; first usable release in weekly sprints after that
- AI Software EngineeringPilot + evaluation notesPilot typically 2–4 weeks on your sample data, then a go/no-go decision
- Cloud Setup & DevOpsInfra as code + runbookSetup typically 1–2 weeks per environment, then handover walkthrough
- Data Pipelines & DashboardsLive dashboard + data dictionaryFirst dashboard typically 2–4 weeks after data access and scope agreement
TELL US ABOUT YOUR PROJECT
Tell Us What to Build, Fix or Modernize
Send a short brief. We reply within 12 hours with clarifying questions and a discovery quote — no retainers, no spam.
What Happens Next
Request a Discovery Quote
Share your goals and timeline. NDA signed first if needed.
12-hour response