StackLift
All comparisons

Fixed-Scope vs Hourly Billing

Hourly billing pays for time; fixed-scope pays for outcomes. The model you choose changes who carries the risk of slow or padded work.

Dimension
Fixed-scope (story points)
Hourly / time-and-materials
Budget certainty
Known up front
Open-ended
Risk owner
Delivery partner
You (the client)
Incentive
Ship the agreed scope efficiently
More hours = more revenue
Change handling
Explicit, priced change requests
Absorbed into hours
Best for
Defined builds with clear scope
Pure R&D with unknown direction

The verdict

Fixed-scope protects your budget and aligns incentives for most builds - you know the number and the partner is motivated to deliver efficiently. Hourly only makes sense for genuinely exploratory work where scope can't be defined yet.

Start in 60 seconds

Get the answer for your project.

A scoped estimate replaces the general comparison with real numbers for your case. Free, no login.

Frequently asked questions

What happens when scope changes under fixed-scope?

It becomes an explicit, priced change request against the original baseline - transparent, not hidden in a growing invoice.

How is fixed-scope priced fairly?

Via story points tied to deliverable complexity, set after an AI scope and senior-architect review - so the number reflects real work, not guesswork.

The complete guide

Fixed-Scope vs Hourly Billing: the complete guide

Updated November 18, 2026 · Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

Fixed-scope pricing sets the cost of a defined set of deliverables before work starts, so the delivery partner carries the risk of overruns. Hourly, or time-and-materials, billing charges for the time worked, so you carry that risk but gain flexibility. Choose fixed scope when the work can be defined, and hourly when direction is genuinely unknown.

What is the difference between fixed-scope and hourly billing?

With fixed-scope pricing, you and the delivery partner agree what will be built, and the price for it, before engineering begins. With hourly billing, also called time and materials, you pay for the hours the team works, usually at an agreed rate per role, plus any direct costs.

The core difference is who carries the risk of the unknown. In a fixed-scope deal, an estimate that turns out too low is the partner's problem. In an hourly deal, it is yours. That one fact shapes incentives, budgeting and how the whole relationship feels.

Billing models at a glance
ModelYou pay forBudget certaintyFlexibility
Fixed scopeAgreed deliverablesHighChanges are priced explicitly
Hourly (time and materials)Time spentLow to moderateHigh; direction can change freely
Capped hourlyTime spent, up to a ceilingModerateModerate
Retainer or capacityA team's time over a periodHigh for the periodHigh within the team's capacity
HybridFixed discovery, then fixed or capped deliveryHighModerate to high

How does fixed-scope pricing work?

It starts with scope. A scope document lists the features, the user stories, the technical approach and what is out of scope. The price is attached to that baseline, and the delivery plan is agreed with it.

At StackLift, pricing is by deliverable complexity, measured in story points, not hours. Scope, budget and delivery path are agreed before engineering begins, and every estimate is reviewed by a senior architect before it becomes a commitment. Estimate, proposal, project and client portal share one baseline, so any change is explicit.

  1. Discovery captures goals, users, constraints and risks.
  2. Scope is written feature by feature and reviewed by an architect.
  3. Each deliverable is sized by complexity and priced.
  4. You choose a delivery plan: MVP-first, Standard, Fast Track or Priority.
  5. Work starts against the agreed baseline.
  6. Changes are raised as change requests, priced and approved before they are built.

How does hourly billing work?

The partner assigns people, tracks their time and invoices you on a regular schedule, often monthly. You get a rate card and, typically, an estimate that is not binding. If the work takes longer than expected, the bill grows with it.

Done well, hourly billing suits work that is genuinely open. You can change direction mid-sprint without renegotiating anything. Done badly, it rewards time spent instead of results delivered, and budget control depends entirely on how closely you watch the hours.

What to watch in an hourly arrangement
Watch forWhy it mattersWhat to ask for
Open-ended estimatesNothing stops the total from growingA cap, or a budget checkpoint at each sprint
Vague timesheetsYou cannot tell effort from progressHours tied to named deliverables
Seniority mixSenior rates for junior work inflate the billA clear team plan and who does what
Slow-moving workHours, not outcomes, drive revenueRegular demos of working software
No end stateProjects drift without a finish lineMilestones with acceptance criteria

When should you choose fixed scope, and when hourly?

Match the model to how well the work can be defined. The clearer the scope, the better fixed scope fits. The less you know, the more you need room to learn.

  • Choose fixed scope for an MVP with a clear feature list, a defined integration, a migration, a rebuild of a known system, or any build where you need a number for a budget approval.
  • Choose fixed scope when you want the partner motivated to deliver efficiently, since time saved is not lost revenue.
  • Choose fixed scope when finance, procurement or a board needs a commitment before work starts.
  • Choose hourly for genuine research and development, where you do not know yet what will work.
  • Choose hourly for ongoing support and small, unpredictable fixes that cannot be listed in advance.
  • Choose hourly when you plan to change direction often and accept the budget risk that comes with it.

If you are not sure, you do not have to choose blind. Define scope first through discovery, then decide. The software estimation playbook shows how to test whether your scope is clear enough to price.

How do risks and incentives compare?

Decision matrix: fixed scope vs. hourly
DimensionFixed scopeHourly
Budget certaintyKnown before work startsKnown only as work proceeds
Who carries overrun riskThe delivery partnerYou
Partner incentiveDeliver the agreed scope efficientlyTime spent; more hours means more revenue
Handling changeExplicit, priced change requestsAbsorbed into hours, sometimes unnoticed
Effort before work startsMore upfront scopingLittle; you can start quickly
Flexibility mid-projectLower; changes need approvalHigh
Best forDefined builds with clear scopeExploratory work with unknown direction

Neither model is automatically honest or dishonest. Fixed scope can tempt a partner to cut corners to protect margin. Hourly can tempt a partner to stretch the work. The safeguards are the same in both cases: senior review, automated tests, visible progress and acceptance criteria you control.

Is there a middle path between fixed and hourly?

Yes. The most common is a hybrid: a short, fixed-price discovery, followed by fixed-scope delivery for what is now well understood, and capped or hourly work for the parts that are not. You pay for certainty where you can have it and keep flexibility where you cannot.

StackLift's engagement ladder follows this logic. A free AI Project Snapshot comes first, then a 3-day AI Scope Sprint that produces detailed scope, user stories, tech stack and a cost and timeline range. From there you can go to an MVP Build Sprint or an AI Software Pod for ongoing capacity with sprint planning, QA and DevOps, and a weekly delivery report.

  • Fix the price of discovery so uncertainty is resolved early.
  • Fix the price of the first release once scope is written down.
  • Keep a separate, capped allowance for support and small changes.
  • Review the model again after each release, as certainty grows.

What happens when scope changes under a fixed price?

Scope changes. A fixed price does not forbid that; it makes it visible. A new request is written up, sized and priced against the original baseline, and you decide whether to approve it, swap it for something else or leave it for later.

That transparency is the main advantage over hourly billing, where the same change quietly becomes more hours. Keep every change in writing, as the change request entry describes. Scope creep is rarely one big decision. It is many small additions that nobody priced, and an explicit change process is the cheapest defense against it. If a request feels too small to write up, that is usually the one that gets forgotten and argued about later.

What mistakes do buyers make choosing a billing model?

  • Choosing fixed price for scope that has not been defined, then fighting over every ambiguous line.
  • Choosing the lowest fixed price without asking what is out of scope.
  • Choosing hourly with no cap, no milestones and no demos.
  • Comparing a fixed quote to an hourly estimate as if both were commitments.
  • Skipping acceptance criteria, so nobody agrees when a deliverable is done.
  • Treating the model as the whole decision and ignoring who reviews quality.

How do you get a fixed-scope number you can trust?

A fixed price is only as good as the scope behind it. Start with the free estimate: it scopes a project feature by feature and returns cost, timeline and team in about five minutes, with no signup. A senior architect reviews it before it becomes a commitment. Most first versions take 6–16 weeks depending on scope.

Ask the partner what is included in the price and what is not: testing, deployment, security review, documentation, a warranty period for fixes, and handover. Two fixed quotes that look equal can cover very different work. A written list of exclusions is a good sign, because it shows the scope was thought through.

For drivers by project type, see the web application cost page and the SaaS platform cost page.

Questions people ask

Is fixed-price software development always cheaper?

Not always cheaper, but more predictable. A fixed price can include a margin for the partner's risk. You trade some flexibility for knowing the number up front, and for a partner who profits from efficiency rather than from extra hours.

Can I switch from hourly to fixed scope?

Yes. A common pattern is to work hourly or on a capped basis through discovery, then move to fixed scope once the requirements are written down. It is easier than the reverse because you now have a scope to price.

What is time and materials?

Time and materials means you pay for the time spent by the team and for materials, such as software licenses or cloud costs, used on the project. It is the usual form of hourly billing in software development.

How are change requests priced in a fixed-scope project?

Each change is written up, sized against the original baseline and priced before it is built. You can approve it, swap it for lower-priority work or defer it. Nothing is added silently.

Why price by story points instead of hours?

Story points measure the complexity of a deliverable, not how long one person sits at a desk. Pricing by deliverable ties what you pay to what you get, and it removes the incentive to stretch time.

Which model is better for an MVP?

Fixed scope usually fits an MVP, because the point of an MVP is a narrow, defined first release. If the idea itself is still unclear, scope it first with a short discovery or scope sprint. See the MVP glossary entry.

What if the fixed-scope estimate turns out wrong?

That is the partner's risk inside the agreed scope, which is why careful scoping and architect review happen first. If your own requirements change, that is handled as a priced change request.

Sources

Sources and further reading

The standards, rules, research and official documentation this page draws on.