How do I know if a software quote is fair?

Matt Turley, Continuum. Updated November 5, 2026.

What a good quote contains, the warning signs, and how to compare bids that are not alike.

The short answer

How do I know if a software quote is fair?

A fair quote lists what is included and excluded, ties the price to named deliverables and dates, says who owns the code and accounts, and covers what happens after launch. Compare at least two on the same brief. Price alone tells you little; the gaps between quotes tell you what each one left out.

What a good quote contains

Scope in plain words: what is included and what is not.
Deliverables with dates, so you can see progress and say when something is late.
Price type: fixed, or a capped estimate, with what triggers a change.
Ownership: the code, the repository and the accounts in your name.
After launch: support, hosting, fixes, and what each costs.

Warning signs

A price with no scope attached. If the document does not say what is included, the price will move.
A very low bid. It usually means a thin plan for testing, security and the hard parts like payments.
An hourly rate with no estimate of hours.
Code or accounts held by the builder.
No one to call a year from now.

How to compare bids that are not alike

Give every bidder the same one-page brief, then line the quotes up in a grid: scope, price, dates, ownership, after-launch. The cell that is empty in one quote is usually the cost that arrives later. Ask the cheapest bidder what they assumed that the others did not.

For market context, app development cost shows how rates are reported and what moves the price. Our own prices come from the price list: a written read of your code is $299, fixes are $4,000 to $15,000, and a new build starts at from $15,000, each fixed once scoped.

Want a number for your own project?

Describe what you want built or fixed and get a ballpark from the published price list straight away. It is labeled as a ballpark, not a quote, and a real quote comes from me after we talk.

Get a free ballpark. Or book a call and talk it through.

Book a call →See all services and prices →

FAQ

Straight answers

Is fixed price always better than hourly?

Fixed pricing protects you from overruns, provided the scope is written down. Hourly can suit open-ended work if the hours are capped and reported. Either way you want the scope and a ceiling in writing.

Should I always take the middle quote?

No. Take the one whose scope you understand best and whose answers to your questions are clearest. Middle is just a price.

What if all the quotes are far apart?

Then the brief is probably unclear or each bidder assumed something different. Ask each to list their assumptions and rewrite the brief so they price the same job.

Can I ask for a trial before committing?

A small paid first piece, such as a written read or a short fixed task, is a fair way to test working together. It costs less than finding out on a large project.

Keep reading

Get a free ballparkFree ballpark, then a real quote.App development costWhat the market charges, what moves the price, and what we charge.Hire someone to build an appWho to approach and what to ask before you sign.What should I put in a brief for a software developer?The one-page brief that gets comparable quotes.Agency, freelancer or one senior developerWho should build a business app, and why.When your agency delivers bad codeHow to assess the damage and decide what to salvage.Signs you have outgrown your freelancerThe warning signs and the replacement options.

Sources

1. App development cost, Continuum: Used for how market rates are reported and what moves a price. That page cites Clutch, Upwork and the US Bureau of Labor Statistics for the figures.
2. Continuum pricing, Continuum: Used for every Continuum price on the page. The prices are read from the same list that renders /pricing.