Skip to content

Stratgik — technology strategy and business systems engineering.
Delivery across the USA, UK, UAE and India.

Talk about a problem

Fixed-Price vs Time and Materials for Custom Software 2026

Published 20 November 2026 · 10 min read

A 2026 guide to fixed-price vs time-and-materials software contracts: where each works, the clauses that matter, and who legally owns the code.

Fixed-Price vs Time and Materials for Custom Software 2026

The short answer

Choose fixed price when the scope is genuinely settled and you can write down what "done" looks like before work starts; choose time and materials when you are still discovering what to build and need to change direction without renegotiating. The failure mode is the mismatch, not the model: fixed price over unsettled scope produces padding and change-order fights, while uncapped time and materials with no acceptance criteria produces an open-ended invoice. Most custom software engagements are better served by a third option — a capped, phased structure that fixes price per increment while keeping scope negotiable.

Below: where each model works, the clauses that matter more than the headline price, and the ownership question founders discover too late — who legally owns the code when an outside developer writes it. Stratgik is a technology firm, not a law firm; treat the legal references as pointers to primary sources and have a lawyer in your jurisdiction review any contract before you sign.

What each model actually transfers

Pricing models are risk-allocation devices. A fixed price does not make a project cheaper; it moves the risk of being wrong about effort to the supplier, who charges for carrying it. The US Federal Acquisition Regulation puts it plainly: a firm-fixed-price contract "places upon the contractor maximum risk and full responsibility for all costs" and "provides maximum incentive for the contractor to control costs" (FAR 16.202-1).

The same regulation is candid about what makes a fixed price sensible. FAR 16.202-2 says firm-fixed-price suits work with reasonably definite specifications "when the contracting officer can establish fair and reasonable prices at the outset" — possible where there is price competition, comparable prior purchases, cost data supporting realistic estimates, or uncertainties that can be identified and costed.

Time and materials sits at the other end. FAR 16.601 permits it "only when it is not possible at the time of placing the contract" to estimate the extent or duration of work accurately, and is candid about the consequence: because the model gives no profit incentive for cost control, "appropriate Government surveillance of contractor performance is required." It imposes two hard limits — a written determination that no other contract type is suitable, and a ceiling price "that the contractor exceeds at its own risk."

Those two requirements are the most useful thing a commercial buyer can borrow. A time-and-materials contract with no ceiling and no oversight on your side is not a contract model; it is a standing instruction to bill.

DimensionFixed priceTime and materialsCapped, phased (hybrid)
Who carries estimate riskSupplierBuyerShared per phase
Scope flexibilityLow — changes go through change ordersHighHigh within a fixed budget per phase
Budget certaintyHigh at the total levelLow without a ceilingHigh per phase, moderate overall
Best fitSettled scope, known stack, integration or migration workDiscovery, R&D, ongoing product teamsMVPs and first releases
Main failure modeChange-order disputes; corners cut on quality you cannot seeOpen-ended spend; drifting prioritiesPhase boundaries treated as formalities

Why fixed-price software quotes drift

The honest reason is that software estimates are predictions about work nobody has done yet, and the quality of the prediction depends on how well the thing being built is defined. Evidence from large public-sector programs is sobering on this point. A US Government Accountability Office review of 16 major federal IT programs, covering about $51.5 billion of planned IT spending for fiscal year 2012, found that "all but 1 of the estimates were not fully reliable," with many lacking credibility because they "were not properly adjusted to account for risks and uncertainty" (GAO-12-629).

Those programs had dedicated cost-estimating staff and formal methods. A founder asking three agencies to quote on a weekend brief has far less. That does not make fixed price wrong — it means the quote is a priced opinion whose contingency is invisible to you.

Two consequences follow. A fixed quote on vague scope is either padded or optimistic and you cannot tell which from the number alone; and the supplier's rational response to an under-priced fixed contract is to narrow its reading of scope, which is where change-order friction comes from. The parts you cannot inspect — test coverage, documentation, migration edge cases, accessibility — are where silent trade-offs get made, so write those into the acceptance criteria or expect to lose them.

If you are still sizing the work, our free app cost estimator gives a range to sanity-check quotes against, and the build vs buy tool is worth ten minutes before commissioning anything custom.

When fixed price is the right call

Fixed price works when the uncertainty has already been removed, usually because someone did discovery first. Good candidates:

  • A defined integration. A known API into a known system, with documented endpoints and a test environment you can access before quoting.
  • A migration with a fixed inventory. A counted set of records, screens or reports, with the count agreed in writing.
  • A second phase after paid discovery. The most reliable pattern: run discovery on time and materials, produce a specification and technical baseline, then let suppliers bid fixed price against it.
  • Compliance or audit work. The standard, not the supplier, defines the finish line.

The shared feature is that "done" is checkable by someone other than the supplier. If you cannot write an acceptance test for a deliverable, you cannot meaningfully fix its price.

When time and materials is the right call

Time and materials is correct when learning is part of the work, which covers most early product development: discovery sprints, genuine R&D where feasibility is unknown, ongoing product teams past first launch, and support where volume is unpredictable.

It is only safe with three controls in place, and all three are things the buyer must do:

  • A ceiling. Borrow the FAR discipline: a stated maximum the supplier exceeds at its own risk, reviewed formally before any increase.
  • Named rates by role. FAR 16.601 requires separate fixed hourly rates per labour category for a reason — blended "team rates" hide who is actually on your project. Ask for rates per role, and for the right to approve substitutions.
  • Real oversight. Weekly demos against a prioritised backlog, visible commit history, and a burn report you get without asking. If nobody on your side has time for this, you are not ready to buy time and materials.

If you lack the capacity for that third control, that gap — not the pricing model — is the thing to fix. It is the core of what a fractional CTO does on a supplier-managed build.

The hybrid most first builds should use

For an MVP or a first release, the structure that handles reality best fixes the budget and the timebox while keeping the scope negotiable. In practice:

  1. Paid discovery on time and materials — small and short. One to three weeks, producing a prioritised backlog, a technical approach, named risks and a cost range. You should be free to take it to another supplier.
  2. Phases of fixed duration and fixed price, variable scope. Each phase has a fixed cost and end date; what goes in is drawn from the backlog and re-ordered by you at the start of the phase at no charge.
  3. A swap rule instead of change orders. Adding a feature mid-phase means removing one of equivalent size. This removes most change-order friction while protecting the supplier's margin.
  4. An exit at every phase boundary. You can stop having paid only for completed phases, and leave with working code, deployment access and documentation.

This is close to how we structure engagements ourselves; our engagement models page has the detail. The label matters less than the properties: budget certainty for you, margin certainty for the supplier, and the freedom to change your mind about scope without a contract amendment.

Who owns the code — and why this is not automatic

Paying for software does not by itself make you the owner of the copyright in it. Ownership follows the contract, and without the right written terms it can stay with the people who wrote the code.

Under UK law, the Copyright, Designs and Patents Act 1988 provides that "the author of a work is the first owner of any copyright in it" (s.11(1)), and shifts ownership to the employer only where the work "is made by an employee in the course of his employment." The section says nothing about independent contractors — so a contractor or agency is the first owner by default. Transferring that ownership requires a written assignment: "an assignment of copyright is not effective unless it is in writing signed by or on behalf of the assignor" (s.90(3)).

The US position is sharper still. The US Copyright Office's circular on works made for hire explains that a commissioned work qualifies only if it falls within one of nine statutory categories — a contribution to a collective work, part of a motion picture or audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas (Circular 30). Software is not on that list, so a contractor's code cannot be a work made for hire through the commissioning route, and ownership stays with the contractor unless the contract assigns it in writing.

Several of the markets we work in, India included, also require copyright assignments to be in writing — check the applicable statute with local counsel rather than a summary. Whatever the jurisdiction, the practical rule is the same, and independent of your pricing model:

  • A present, written assignment of all IP in the deliverables to your company, not a promise to assign later.
  • Flow-down obligations binding every subcontractor and freelancer the supplier uses.
  • A disclosed list of third-party and open-source components with their licences, so you know what you cannot freely relicense.
  • Accounts and infrastructure — repositories, cloud, domains, app-store listings — in your company's name from day one, not transferred at the end.
  • Deliverables defined to include source code, build scripts, infrastructure configuration and documentation, not just a running application.

Checklist before you sign either model

  • Acceptance criteria written as checkable tests, not adjectives.
  • A stated ceiling (time and materials) or written change control with pre-agreed rates (fixed price).
  • Rates by named role, plus the right to approve team substitutions.
  • A present written IP assignment with subcontractor flow-down, and accounts in your name from the first commit.
  • Non-functional requirements stated explicitly: test coverage, performance targets, logging, backups, accessibility; plus data protection terms for the market you serve.
  • Exit terms: notice period, handover contents, a paid transition window, no dependency on the supplier's private tooling.
  • A warranty period for defects in delivered scope, and a written rule on who pays for rework caused by a defect versus a change of mind.

Frequently asked questions

Is fixed price always more expensive than time and materials?

Not always, but it usually carries a contingency premium, because the supplier is pricing the risk of being wrong about effort. On well-defined work that premium is small; on vague work it is large and partly invisible. Whether it is worth paying depends on how much budget certainty is worth to you.

What if a supplier will only quote fixed price on a vague brief?

Treat the willingness as a warning, not a reassurance. Ask what assumptions the number rests on and what happens when one proves wrong. Better: pay for a short discovery, then take the specification out to bid.

Can I cap a time-and-materials contract?

Yes, and you should. A ceiling the supplier exceeds at its own risk is standard practice in US federal contracting and works equally well commercially. Pair it with a monthly burn report and a formal review before any increase.

Does paying the invoice mean I own the code?

No. Ownership follows the contract, not the payment. In the UK the author is first owner unless there is a written assignment signed by the assignor; in the US, contractor-written software cannot be a work made for hire through the commissioning route, because software is not one of the nine statutory categories. Get a present written assignment with subcontractor flow-down, and have local counsel review it — we are a technology firm, not a law firm.

How should I structure the contract for a first MVP?

Fixed price and fixed duration per phase, scope drawn from a backlog you control, a swap rule instead of change orders, and an exit at every boundary. That gives budget certainty without locking in a scope you will want to change once real users touch the product. Our MVP development and custom software pages describe how we apply it.

If you are about to sign a software contract, or you are mid-build and uneasy about one, we will read the statement of work and tell you plainly where the risk sits — a free 30-minute session, no obligation. Get in touch and we will come back with the specific clauses we would change.

Written by the Stratgik team. Stratgik is a technology strategy and engineering firm headquartered in Gurugram, India, working with clients in India, the US, the UK, Singapore, the UAE and Saudi Arabia. We are not a law firm and nothing here is legal advice.

Tell us what isn't working.

One process, one system, one decision you are stuck on. We will come back with how we would approach it, what it would take, and whether it needs building at all.

The Stratgik model

Strategy first. Technology that follows through.

Four stages, in order. Most businesses need them one at a time.