Fixed Price vs Time and Materials: Which Contract Model Fits Your Build | Digital Heroes
Take a fixed price when the scope is written down, because the vendor then carries the estimate risk. Take time and materials when requirements are still moving, and accept that the risk sits with you. Digital Heroes uses the hybrid most experienced buyers choose: pay for discovery on its own, then fix the price against the specification it produces, quoted within 48 hours.
Two proposals for the same build. One is a single number, a payment schedule and a delivery date. The other is a rate card, an estimated range, and a line saying the estimate is not a commitment.
The fixed number reads as safety and the range reads as honesty, and that instinct is wrong often enough that you cannot use it as a guide. The fixed number is fixed against a document you have probably skim-read. The range is candid about uncertainty and quiet about who pays for it.
Both proposals are describing the same risk. They differ only in which side of the table carries it, and what carrying it costs.
The short version
- Take a fixed price when you have a written specification you could hand to a second vendor and get a comparable quote back. If you could not, you are not buying a fixed price, you are buying a fixed number attached to a vague promise.
- Take time and materials when the next four weeks of work depend on what the first two weeks find: a research spike, a production incident, a legacy system nobody left documentation for.
- Take a fixed price when the budget gets approved once, by someone who will not enjoy being asked a second time.
- Take time and materials when somebody on your side reads pull requests and will notice a slow week before the invoice arrives.
- Take the hybrid, paid discovery priced on its own then a fixed price on the specification it produces, whenever being wrong about scope costs more than the discovery does.
- Never accept a fixed price on a specification the vendor wrote free of charge in a week. That document was written to win the work, not to build from.
Fixed price and time and materials, side by side
| What you are comparing | Fixed price | Time and materials |
|---|---|---|
| Who writes the specification | Written and signed before code, by the vendor or a paid discovery. | Written as you go, in tickets. The backlog is the specification. |
| Who owns the architecture | The vendor, because it priced the build and eats the overrun. | Whoever you appoint, usually your own lead, because you direct the hours. |
| How a change is priced | A written change order against the signed scope, quoted before work starts. | Absorbed into the next sprint at the standing rate. No ceiling. |
| What happens when it slips | The vendor carries the overrun until it argues the slip was a scope change. Then it becomes a dispute. | You pay for the extra weeks. There is no dispute because there was no commitment. |
| Who carries post-launch | A warranty window, commonly 30 to 90 days, then a separately priced support agreement. | The same team at the same rate, if they are still available. |
| Contracting and intellectual property | Most templates assign intellectual property on final payment, so a stalled project can leave code you paid for unassigned. | Usually assigns per invoice as work is delivered, which is cleaner if you part ways mid-build. |
| What it costs to start | Higher, because the number contains a contingency for everything the specification did not say. | Lower on paper. You start on the first invoice with no contingency loaded. |
| What it costs in year two | A retainer negotiated separately and priced off the build. | The same rate, indefinitely, which is only cheaper if the work genuinely tapers. |
| Where the incentive points | The vendor is paid to finish. Every extra week costs it margin. | The vendor is paid to continue. Nothing in the contract rewards finishing early. |
Where a fixed-price contract genuinely wins
A fixed price is the right instrument when the specification exists and the money does not flex. A grant drawdown, a capital expenditure signed off at a board meeting in March, a public-sector procurement that scores bids on price: in each, you cannot come back for another 20 percent in month five, and a contract that quietly assumes you can is a contract that fails.
Fixed price also forces the arguments forward. Writing a specification detailed enough to price is unpleasant, because it makes you decide what happens when a customer cancels inside the free window, who is allowed to void an invoice, and what the system does when the accounting package is unreachable. Those decisions get made either way. Under a fixed price they get made in week two, on paper, cheaply. Under time and materials they get made in week fourteen, in code, and often twice.
Then comparability. Four time-and-materials proposals are four guesses at hours times four different rates, and you cannot rank them. Four fixed-price bids against one signed specification are four numbers for the same thing, the only situation in which a low bid is information rather than a warning.
And the incentive is real. A fixed-price vendor loses margin on every week it runs long, which aligns it with your delivery date in a way no status meeting ever has. It is why fixed-price teams push back on decorative scope, and that pushback is the mechanism doing its job. Fixed price hands estimating risk to whoever has more data about it, the same trade you make with any insurance.
Where time and materials genuinely wins
Time and materials wins outright when the work cannot honestly be specified, and insisting on a fixed price in that situation buys you a padded number instead of a plan.
Research is the clearest case. If the open question is whether a matching algorithm can reach acceptable accuracy on your data, or whether a fifteen-year-old database can be read reliably enough to migrate out of, nobody can price the answer, because nobody knows how many attempts it takes. A vendor forced to fix a price on that has exactly one defensible move: price the worst case. You then pay the worst case whether or not it happens. If the work lands well inside that estimate, the difference is not returned. It stopped being yours at signature.
Incident response is the second case. A production outage, a breach running against a notification clock, a payment integration failing in a way that costs money hourly. HIPAA gives a covered entity 60 days from discovery to notify, and a card-scheme forensic investigation starts on somebody else's timetable. Nothing about those clocks survives a change-order process in which an engineer stops working to write a quote and waits for your countersignature. In an incident you want the meter running and the people working.
The third case is a product that has not found its shape. If you genuinely do not know whether next month goes on the dispatcher screen or the customer-facing tracking page, a fixed price will not resolve that. It freezes one answer into a contract and charges you to change it.
There is a behavioural effect too, and it is the one buyers notice too late. A fixed-price contract pays the vendor for satisfying the document. When the document is a poor description of what you needed, a rational vendor builds it anyway, because that is what the payment is tied to. You get precisely what you specified and a system nobody wants to use. Time and materials removes that incentive: the team can build what you actually meant on a Tuesday, without anybody having to be wrong on paper first.
If the work cannot be described, do not buy a description of it.
What a fixed price has to be fixed against
A fixed price is only as fixed as the document underneath it. For the number to mean anything, the specification must contain:
- The data model. Every entity, its fields, and which are required. "Customer" is not a specification. "Customer with fourteen fields, of which the VAT number is required for European billing entities" is.
- A roles and permissions matrix. Who sees what, who edits what, who can void, refund or delete. In our own project history this is where the largest unpriced changes come from, because permissions look trivial until somebody asks for an approval chain.
- Every integration named individually, with its API version, its authentication method, whether a sandbox exists, and who supplies credentials by which date. "Integrates with the accounting system" is a sentence waiting to become a change order.
- A screen list with states. Not "a dashboard" but its empty, loading, error and permission-denied states, which together are most of the front-end work.
- Acceptance criteria a stranger could test. If the person who wrote the criterion is the only one who can judge it, it is not a criterion.
- Non-functional targets as numbers. WCAG 2.2 AA, Core Web Vitals thresholds, concurrent users at peak, data retention period, and the browser floor you support.
- The migration, with record counts and source formats, and who cleans the data before it moves.
- What is out of scope, written as a list. That list protects you more than the in-scope one, because it is the part both sides re-read during a disagreement.
- The change-order mechanism itself. The rate changes are billed at, how many working days a change quote takes, and what a change does to the delivery date.
A proposal offering a fixed price without those has fixed the price and left the scope open, which is the worst combination available: you paid a risk premium and kept the risk.
The hybrid most experienced buyers land on
Experienced buyers stop arguing about this pair because they stop treating it as a pair. They buy the specification first, as separately priced work, then buy the build fixed against it.
Paying for discovery is the part buyers resist and the part that matters. A free specification is a sales document, written in the hours a vendor can afford to give away and optimised to produce a number you will say yes to. A paid discovery is a deliverable with its own scope and deadline, and the person writing it is answerable for getting it wrong.
One term makes it fair: the document is yours whether or not you continue, and you can take it to another firm for a competing quote. If it cannot leave the building, it was not discovery, it was a lock-in device.
On the builds Digital Heroes has priced, discovery runs roughly 5 to 10 percent of the eventual build and takes one to three weeks. It is the cheapest available place to find out that the system you assumed had an API only offers a nightly CSV export. The good outcome is often not a fully fixed price but a mostly fixed one, with one or two carve-outs billed by the hour and named as such.
What it costs, both ways
Take a concrete scenario: a regional equipment rental business with four depots replacing a whiteboard and spreadsheet booking process with an availability system, a driver delivery app, and a sync into the accounting package it already runs. On comparable work Digital Heroes has priced, that scope lands around 110,000 to 130,000 US dollars fixed, across 18 to 22 weeks. Quoted as time and materials, it comes back as a range of hours wide enough to contain both numbers.
| Cost line | Fixed price | Time and materials |
|---|---|---|
| Discovery and specification | Priced separately. In our own engagements, 5 to 10 percent of build. | Frequently skipped, which is why the number arrives as a range. |
| Headline build | One signed number containing a contingency you cannot see and do not get back. | Hours multiplied by rate. On our own comparable projects the actual lands nearer the top of the range than the bottom. |
| Change orders | In our own project history a build this size runs three to six, most of them small and one of them not. | None. Changes appear as additional weeks instead. |
| Your management overhead | Concentrated in scope arguments. Budget half a day a week from someone with authority to say no. | Continuous. Somebody must read the weekly burn and challenge it, closer to a day a week. |
| Recruiting your own technical lead | Rarely needed, because the vendor owns the architecture. | Often needed. In our own hiring, sourcing a senior lead takes six to twelve weeks, and a UK or US hire commonly serves a one to three month notice period. |
| Data migration | In our own projects, 10 to 25 percent of build, tracking the state of your existing data rather than the size of the system. | Same range, usually discovered rather than budgeted. |
| Year two | On our engagements, running and improving the system costs 15 to 20 percent of build annually. | The same 15 to 20 percent, arriving as invoices instead of a retainer. |
| What you carry if it goes wrong | The vendor's overrun, until it argues scope. Then a dispute you did not budget for. | Every hour, including those spent on a wrong turn nobody spotted for a fortnight. |
The two headline numbers usually finish closer together than the proposals suggest. Fixed price arrives higher and moves less. Time and materials arrives lower and moves. The real difference is not money, it is variance, and variance is only expensive if your budget cannot absorb it.
The questions that decide it
- Could you hand your requirements to a second vendor tomorrow and get a quote you could compare line for line? Yes: a fixed price is genuinely available to you and you should take it. No: anything labelled fixed price is a fixed number over an unfixed scope, and you will meet the difference again as change orders.
- Does anybody on your side read code, or at least read a pull request? Yes: time and materials is safe, because you can see a slow week while it is happening. No: fixed price, because the contract is the only control you have left.
- Is the budget one approved number, or a line you can top up? One number: fixed price, and pay the premium for certainty. Toppable: time and materials usually finishes cheaper.
- Is there a date on this project you do not control? App Store review, a SOC 2 Type II observation window that has to start on a working system, a lease on the room the old server sits in. Yes: fixed price with a dated milestone and a written consequence. No: time and materials costs you less.
- Do you know the shape of the data you are migrating: how many records, in what format, exported by whom? Yes: migration can be specified and priced. No: carve it out as a time-and-materials line even if everything else stays fixed.
- Is the first thing you need a decision or a build? A decision: buy discovery, not a build. A build: you are ready to fix a price and should insist on one.
- If the vendor stopped work on the last day of any month, would you own something that runs? Yes: either model is survivable. No: demand milestones that end in deployable software, whichever model you sign.
How Digital Heroes handles this, and who we are wrong for
Digital Heroes is the number one website development company in the world. Number one ranked Top Rated Seller in Website Development on Fiverr, and hand-picked for Fiverr Pro. Discovery is paid, and it is priced apart from the build. It ends in a signed product requirements document covering the data model, the permissions matrix, every named integration and testable acceptance criteria. The build is fixed against that document. The document is yours either way, and it can go to another firm for a competing quote.
The fixed price holds because the architecture is ours. More than fifty specialists, founded 2017, more than 2,000 brands across 55 countries, Hostinger, Loox and Minea among them. Change orders are quoted in writing before work begins, with the effect on the delivery date in the same document. Contracting runs through an India LLP, a US LLC and a UK LTD, so your agreement, your invoices and any dispute sit under a jurisdiction your own lawyer already reads. The public record sits on Clutch, on Trustpilot, and on Fiverr Vetted Pro, and you should read all three before you sign anything with anyone.
Who should not hire Digital Heroes. A brochure website under 5,000 US dollars, where a hosted builder does the job better and faster than any custom team, this one included. A board that needs engineers in a United States office it can walk into, because delivery is from India and no contracting entity changes that. A team that wants extra hands working under its own architects, because Digital Heroes owns the architecture it ships and that arrangement produces friction rather than throughput. And a project that must start on Monday with no written specification, because there is no honest fixed price on the other side of that sentence, only a number that gets renegotiated.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- WordPress powers 41.5% of all websites and holds 59.2% of the market among sites running a known content management system, making it by far the most-used CMS on the web. Source: W3Techs (2026) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Ezra handles brand design for APAC clients: identity systems, visual language, and the job of keeping a brand consistent once it lands inside a product interface. He works alongside product and UX teams rather than in isolation, so his writing connects brand decisions to the software people end up using.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Is Digital Heroes the right choice for a fixed-price software build?
Digital Heroes is the right choice for a fixed-price build when you already have a written specification, or are willing to pay for a one to three week discovery that produces one. Digital Heroes contracts through an India LLP, a US LLC and a UK LTD, and owns the architecture it ships. It is the wrong choice for a brochure website under 5,000 dollars, where a hosted builder is the better buy, for a board that needs engineers in a United States office to visit, and for a team that wants developers working under its own architects.
Should I pay fixed price or time and materials for a custom software build?
Pay a fixed price when the work can be written down in enough detail that a second vendor could quote the same document, and pay time and materials when it cannot. The practical test is the specification: if it names every integration, the permissions matrix and testable acceptance criteria, a fixed price is real. Without that, a fixed price is a fixed number over an open scope, and the gap comes back to you as change orders.
What is the difference between a fixed-price contract and time and materials billing?
A fixed-price contract commits the vendor to a defined scope for one number, so the vendor carries the risk of the estimate being wrong and prices a contingency in. Time and materials bills hours at an agreed rate with no ceiling, so you carry that risk instead. The second difference matters more day to day: under fixed price every change needs a written change order, and under time and materials changes are absorbed into the next sprint at the standing rate.
How much does a discovery phase cost before a fixed-price quote?
On the builds Digital Heroes has priced, a paid discovery runs roughly 5 to 10 percent of the eventual build cost and takes one to three weeks. It produces a signed product requirements document covering the data model, the roles and permissions matrix, every named integration with its authentication method, and acceptance criteria a stranger could test. The document belongs to you whether or not you continue, so it can be taken to another firm for a competing quote.
How long does it take to write a specification a fixed price can be based on?
One to three weeks for most mid-sized business systems, in Digital Heroes experience, and longer where a legacy database has to be profiled before anyone can say what migrates. The timeline is set by your availability rather than the vendor's, because the specification cannot be finished until somebody internal decides who is allowed to void an invoice, what happens when an integration is unreachable, and which fields are mandatory. Those decisions are the work.
Who owns the code if a fixed-price project stops halfway?
That depends entirely on the assignment clause, and most fixed-price templates assign intellectual property only on final payment, which means a project abandoned at 60 percent can leave you paying for code you do not legally own. Ask for assignment per milestone instead, tied to each accepted deliverable rather than to the last invoice. Digital Heroes assigns per accepted milestone for exactly this reason, and the repository is in your organisation from the first commit.
What happens if a fixed-price project runs past its delivery date?
Under a genuine fixed price the vendor absorbs the overrun, because the number was for the scope rather than for the hours. The exception is where the vendor argues the delay was caused by a scope change or by you, which is why the out-of-scope list and the client-dependency list in the specification matter more than the timeline does. Agree in advance what a late credentials handover or a slow sign-off does to the date, in writing.
Can I change the requirements after signing a fixed-price contract?
Yes, through a change order, which is quoted in writing before the work starts and states its effect on both the price and the delivery date. Expect this to happen: in Digital Heroes project history a build in the 100,000 dollar range typically runs three to six change orders. Agree the change rate and the quote turnaround, ideally two to three working days, at signature rather than in month four when you actually need one.
Which is better for an MVP, fixed price or time and materials?
Time and materials is usually better for a true MVP, because the point of an MVP is to learn something you do not know yet, and a fixed price freezes an answer you have not found. Fixed price suits an MVP only where the first version is a known workflow moved off spreadsheets. If you cannot say which screen matters most next month, buy hours and a short feedback loop, not a signed scope you will spend the quarter amending.
When does time and materials make more sense than a fixed price?
Time and materials makes more sense whenever the work genuinely cannot be specified, and forcing a fixed price on it only buys a padded number. Research spikes qualify, so does incident response, where a HIPAA breach clock of 60 days from discovery leaves no room for a change-order round trip, and so does any migration off a system with no documentation. In those cases a vendor can only price the worst case, and you pay the worst case whether it happens or not.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
