The short answer
What this means for you
Normalise first, compare totals last. Send every supplier the same brief, put each quote into one worksheet with the same lines, add back what each quote leaves out, split effort from rate from external fees, and compare risk and ownership terms. Ask a very low bidder to explain the price before you accept or reject it, and use an independent estimate to see which line to question first.
- Two quotes are comparable only after scope, assumptions, exclusions, rates, and ownership terms match.
- Split each total into effort, rate, external fees, and any buffer, and convert fixed price and time and materials into a likely range.
- Silence in a quote is a finding: testing, security, accounts, and warranty that are not stated should be priced or asked about.
- A quote far below the others should prompt questions, not rejection or acceptance.
- A free estimate of your own gives you a baseline range before you read the quotes.
How do you compare software development quotes fairly?
Normalise first, compare totals last. Give every supplier the same brief, put each quote into one worksheet with the same lines, add back anything a quote leaves out, and only then compare prices and risk. Two totals are rarely comparable until scope, assumptions, rates, exclusions, and ownership terms match.
A quick way to start: run your scope through the free software project estimator to get an effort range of your own, then check each quote against it. A quote far outside the range is not wrong by definition, but it tells you which line to question first.
Why do quotes for the same project differ so much?
Our view: Software quotes differ because suppliers read the brief differently, not only because they charge differently. One supplier may price a clickable prototype and another a production system with testing, security, and deployment. Rates, team seniority, location, and how much risk each supplier builds in also move the total.
Professional buyers treat this as a method problem. US federal procurement rules separate price analysis, which evaluates a proposed price without examining its separate cost elements, from cost analysis, which reviews the separate cost elements and profit or fee. They also list comparison of the proposed prices received in response to the solicitation as a price analysis technique. A private buyer can do a light version of both: compare totals, then break each total into elements.[3]
The wage data you can find does not explain the gap on its own. The US Bureau of Labor Statistics reports a median annual wage of $135,980 for software developers in May 2025, based on the page as checked on 2026-11-18. That is an employee wage in one country, not an agency rate, because an agency rate also covers overhead, management, tools, and profit. Use it only to sense-check that an hourly rate is not impossibly low.[7]
Step 1: give every supplier the same brief and estimate
Send one written brief to every supplier: users, the tasks they must complete, integrations, platforms, must-pass checks, budget range, and deadline. If suppliers write their own scope, you end up comparing scopes, not prices.
Add your own baseline. The project brief builder (/tools/project-brief-builder) helps you write the brief, and the software project estimator gives an effort range for the same scope. Keep the range, not a single number: the US Government Accountability Office's Cost Estimating and Assessment Guide lists ground rules and assumptions and sensitivity and risk analysis among the elements of a cost estimating process, which supports keeping a documented range rather than one figure.[6]
Step 2: put each quote into the same worksheet
Copy the lines below into a spreadsheet with one column per supplier. For each line, record what the quote says, normalise it so the suppliers match, and write down the question you will send. If a quote is silent on a line, write "not stated" rather than leaving it blank, because silence is the most common source of surprise.
| Worksheet line | What to record | Normalise by | Ask the supplier |
|---|---|---|---|
| Scope | User tasks, platforms, integrations, content, and design included. | Mapping each supplier's list onto your brief's task list. | Which of my tasks are not in this quote? |
| Assumptions | Conditions that would change price or timeline. | Listing each as a risk with an owner. | Which assumptions are most likely to be wrong? |
| Exclusions | Anything stated as out of scope or optional. | Adding the cost of each exclusion you need. | What would you charge for each excluded item? |
| Testing | Automated tests, manual testing, accessibility, and security checks. | Adding testing effort if missing. | How is testing shown in the hours or milestones? |
| Effort | Hours or days by role, if given. | Converting to the same unit for every quote. | Can you show effort per feature or milestone? |
| Rates | Hourly or daily rate by role and seniority. | Computing a blended rate across the team mix. | What is the rate for changes and extra work? |
| Pricing model | Fixed price, time and materials, capped, or fixed capacity. | Estimating a likely total range for each model. | What happens at the cap or when the estimate is exceeded? |
| External fees | Hosting, paid APIs, licences, and store fees. | Listing who pays, at cost or with margin. | Which third-party costs are pass-through? |
| Contingency | Any buffer inside the price or a separate contingency line. | Showing it as a visible percentage where possible. | Is there a buffer, and who keeps unused budget? |
| Ownership and IP | When and how code and design ownership transfers. | Checking each for a signed written assignment. | What do I own on day one, and what only on final payment? |
| Accounts | Domains, hosting, repositories, and app store accounts. | Confirming they are in your business name. | Who registers each account? |
| Warranty | Length, coverage, and response times. | Comparing in days and severity levels. | What defects are excluded from warranty? |
| Payment milestones | Deposit, milestone triggers, and final payment share. | Mapping payments to accepted working deliverables. | What do I have in hand at each payment? |
| Support after launch | Maintenance, patches, and hosting care. | Pricing an annual cost for each supplier. | What is included after the warranty ends? |
Step 3: separate effort, rate, and external fees
Our view: A total is effort multiplied by rate, plus external fees, plus any buffer. Split each quote into those parts. A low total can come from low effort, which usually means thin scope or missing testing, or from a low rate, which may mean less senior people. Either may be fine, but you should know which one you are buying.
Compare a fixed price with a time and materials quote by converting both into a likely range. For fixed price, the total is the quote plus the priced changes you expect. For time and materials, use the estimated hours at the stated rates and add a margin for overruns, then check what the cap does. Our guide to fixed price vs time and materials software contracts explains how risk moves between buyer and supplier under each.
US federal rules describe the same split. Under FAR 16.202-2 a firm fixed price suits work where performance uncertainties can be identified and their cost impact reasonably estimated. Under FAR 16.601 a time-and-materials contract must carry a ceiling price that the contractor exceeds at its own risk, and is for work whose extent or duration cannot be estimated accurately in advance. These are US federal definitions, not private-contract law.[4][5]
Step 4: add back what each quote leaves out
Add the cost of every excluded item you actually need so the quotes cover the same ground. Common gaps are testing, accessibility, security review, deployment and monitoring, data migration, content entry, app store submission, and project management time.
Ask directly: "How do I know whether testing is included?" Look for it as a line in the hours, a named milestone, or a stated test approach. If testing appears only as the word "QA" with no hours, treat it as unconfirmed. Ask what is tested, by whom, and on which devices and browsers.
The UK Digital, Data and Technology Playbook advises selecting payment milestones so that delivery of non-functional requirements is included. That is a useful test for any quote: if performance, accessibility, and security are not tied to a milestone, they are easy to drop.[8]
What does "assumptions" mean in a quote? Assumptions are the conditions the price depends on, such as "client provides final content by week two", "one payment provider", or "no more than five design rounds". Each assumption is a place where the price can rise. Good quotes list them; ask which are most likely to be wrong in your case.
Step 5: compare risk: the pricing model, change rules, and what happens at a cap
Our view: Two quotes with the same total can carry different risk. Compare who pays when the work takes longer, how changes are priced, who can approve them, and what happens at a cap: does the supplier finish at its own cost, or does work simply stop until you approve more budget?
The US Digital Services Playbook recommends contracts that call for frequent deliverables rather than multi-month milestones, that specify a warranty period in which the vendor fixes defects at no extra cost, and that include a transition-out plan. Those are risk controls you can ask any private supplier for.[9]
How do I compare a local agency with an offshore one? Normalise to the same worksheet, then add the costs that differ: working-hours overlap, meeting time, travel, tax and invoicing, and legal enforceability of the contract. Do not assume the lower rate gives the lower total, because rate and effort move in different directions across teams.
What should you do about a quote far below the others?
Is the cheapest quote a red flag? Not automatically, and not never. Ask the supplier to explain it. GOV.UK guidance for UK public buyers says a low tender should not automatically be disregarded as abnormally low, and that the supplier must be given a reasonable opportunity to demonstrate that it can perform the contract at the price offered.[1]
The GOV.UK Sourcing Playbook sets a firm trigger for central government: departments must refer any abnormally low bid more than 10% lower than the average of all bids, or than the should-cost estimate, for review. It also describes a should-cost model as helping to protect government from low cost bid bias. For a private buyer, your own estimator range plays the role of a should-cost model.[2]
Ask the low bidder what they left out, which assumptions they made, who does the work, and how they price changes. If the answers are specific and the missing items are small, the quote may be sound. If the answers are vague, treat the low price as a deferred cost.
- Scope that omits testing, security, deployment, or content work.
- Rates for changes far above the rate used to price the original scope.
- No written assumptions, or a very short quote for a long, vague brief.
- A large payment before any working software exists.
- Reluctance to explain how the number was built.
Ownership, accounts, warranty, and support: the lines buyers forget
These lines rarely change the headline price and often change what happens when something goes wrong. Check that ownership of code and design transfers by a signed written agreement, say when it transfers, and that domains, hosting, repositories, and store accounts are registered to your business. Our contract guide covers the default ownership rules in the US, UK, Canada, and Australia and cites the official sources for each.
Compare warranty by length, coverage, and response times, and price support after the warranty separately. A quote with a long warranty but no support price can still leave you with an open-ended maintenance bill.
Questions to send every supplier before you decide
Send the same list to every supplier and compare the written answers. The wording of the answers is as informative as the content.
What should a software quote include? At minimum: scope as user tasks, assumptions, exclusions, effort or team and rates, the pricing model and cap rules, external fees, change process, milestones and payments, ownership and accounts, warranty, and support after launch.
- Which of the tasks in my brief are not in this quote, and what would each cost?
- Which assumptions are most likely to change the price?
- How is testing, accessibility, and security covered, and where does it appear in the hours or milestones?
- Who exactly will work on this, at what seniority, and what happens if they leave?
- What is the rate and process for a change, and who approves it?
- What happens at the cap or when the estimate is exceeded?
- When does ownership of the code and design transfer, and who registers each account?
- What does the warranty cover, for how long, and what is the support price afterwards?
- What is passed through at cost, and what carries a margin?
- Can I talk to the team that will build this, and see the handover materials you normally provide?
Sources and further reading
- The Procurement Act 2023: abnormally low tenders (short guide)GOV.UK · Checked 18 November 2026
- The Sourcing PlaybookGOV.UK · Checked 18 November 2026
- FAR 15.404-1: Proposal analysis techniquesU.S. General Services Administration, acquisition.gov · Checked 18 November 2026
- FAR 16.202-2: Firm-fixed-price contracts, applicationU.S. General Services Administration, acquisition.gov · Checked 18 November 2026
- FAR 16.601: Time-and-materials contractsU.S. General Services Administration, acquisition.gov · Checked 18 November 2026
- Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Program Costs (GAO-20-195G)U.S. Government Accountability Office · Checked 18 November 2026
- Software Developers, Quality Assurance Analysts, and Testers: Occupational Outlook HandbookU.S. Bureau of Labor Statistics · Checked 18 November 2026
- The Digital, Data and Technology PlaybookGOV.UK · Checked 18 November 2026
- The Digital Services PlaybookU.S. DOGE Service · Checked 18 November 2026
