Skip to content

How to Evaluate a Software Quote

A software quote is a confidence signal, not a price tag — and you evaluate it by how the number was reached, not by how big it is. A quote built from someone who clearly understood your problem and broke it into parts is worth trusting even if it’s high. A round number with no working behind it is a guess wearing a suit, and you should treat it as one no matter how reasonable it looks.

That’s the answer. Here’s how to read the quote in front of you, what to ask, and why the cheapest and most expensive quotes are usually the two to walk away from.

The number isn’t the information — the reasoning is

When you can’t write code, you can’t judge a quote on technical grounds, so you reach for the only thing you can compare: the price. That’s exactly the wrong instinct, because the price tells you almost nothing on its own. Two competent firms can quote the same job at numbers that differ by a factor of three, and both can be honest — they’ve made different assumptions about scope, polish, and risk.

What you can actually judge is whether the person quoting understood the problem. A real quote shows its working. It breaks the build into pieces, names what’s included and what isn’t, flags the parts that are uncertain, and makes its assumptions explicit. That structure is the signal. It tells you the person sat with your problem long enough to take it apart, which is the single best predictor that they’ll build the right thing. A quote that’s just a total with a timeline attached tells you they pattern-matched your request to something they’ve done before and slapped a number on it. Sometimes that’s fine. Often it means they’ll discover the real scope halfway through, and you’ll discover it on the change-order invoice.

So before you compare prices, compare reasoning. The quote with the clearest breakdown is usually the one to trust, and price becomes a secondary question once you know which quotes were actually thought about.

The questions that separate an estimate from a guess

You don’t need to be technical to expose a weak quote. You need to ask questions that force the working into the open, and then watch how comfortably they answer.

Ask what’s explicitly not included. A real estimator has boundaries and will name them happily — “this doesn’t include data migration, doesn’t include the admin reporting, assumes you provide the content.” A guess has no edges, because no one mapped them; you’ll get a vague “it covers what we discussed.”

Ask which part of this they’re least sure about. Every honest build has an uncertain part, and someone who’s thought it through can point straight at it. Someone who says it’s all straightforward either doesn’t understand the job or is hoping you won’t.

Ask what happens when something takes longer than expected — whose cost that is. The answer tells you how the risk is split. Fixed price means they carry the overrun, which is why fixed-price quotes are higher and more padded. Time-and-materials means you carry it, which is cheaper on paper and open-ended in practice. Neither is wrong; you just need to know which one you’re signing.

Ask what you own at the end — the code, the data, the accounts, the ability to take it to someone else. If that question makes them uncomfortable, you’ve learned something important before you spent a penny.

How they handle these questions matters more than the answers. Calm, specific, unbothered means they’ve been here. Defensive or vague means they haven’t thought about it, or they have and don’t want you to.

Watch both ends of the price range

The instinct is to fear the high quote and trust the low one. Reverse it. The two quotes most likely to hurt you are the cheapest and the most expensive, for opposite reasons.

The cheapest quote usually wins by understanding the job least. It’s low because it’s missing the parts that are hard — the edge cases, the integration, the testing, the bit where real data behaves nothing like the demo. You’ll pay for those parts eventually; you’ll just pay for them as overruns, in a worse negotiating position, mid-build, when walking away is no longer an option. A genuinely cheap-because-efficient quote is rare. A cheap-because-they-missed-it quote is the norm.

The most expensive quote is often pricing in things you don’t need — enterprise process, layers of project management, gold-plating, or simply a comfortable margin because they don’t really want the work. Big and thorough are not the same thing. A high number with no more reasoning behind it than the low one is just a bigger guess.

The quote worth taking is usually neither extreme: the one in the sensible middle that showed its working, named its assumptions, and made you feel the person understood your problem better than you’d explained it. Pay for understanding, not for size.

The question almost nobody asks before getting quotes

Most people get quotes for the wrong thing. They write up everything they can imagine wanting, send it out, and get back quotes to build all of it — when half of it shouldn’t be in version one at all.

Before you evaluate a single quote, the question to answer is what the smallest version is that solves the actual problem. If you quote the kitchen-sink spec, every quote you get is a quote to overbuild, and you’ll be comparing prices on a thing you shouldn’t be commissioning. Cut the scope to the real core first — that’s what scoping an MVP is for — and then the quotes you get are quotes for something worth buying. A well-scoped small build also gets you a quote you can actually judge, because there’s less surface area for the guess to hide in.

A pattern I see

The classic: three quotes, wildly different, and the buyer instinctively drawn to the cheapest because the others “seem like a lot.” The cheap one had a one-paragraph description and a round number. The middle one had a breakdown by feature, a list of exclusions, and a flagged risk. The buyer almost picks the cheap one to save money.

What actually happens with the cheap one is a build that ships at roughly double the quote once the missing pieces surface, three months late, with a change order for everything the breakdown in the middle quote had already named for free. The middle quote wasn’t more expensive. It was the same total, told to you honestly up front instead of discovered painfully later. The cheap quote didn’t save money; it deferred the bad news.

Who this isn’t for

If you’re choosing a developer purely on lowest price and you’ve decided that up front, none of this helps you — you’ve already optimised for the wrong thing, and you’ll get exactly what the cheapest quote was hiding. This is for people willing to pay a fair price for work that’s understood, not the lowest number on the page.

The call, in one line

Judge the quote by how clearly the work was thought through, not by the size of the number — and be most suspicious of the cheapest and most expensive ones.

This is one of my playbooks. It pairs closely with how to brief a developer — a clear brief is what makes an honest quote possible — and how to scope an MVP, which is what you should be quoting in the first place. If reading the quote tells you the build is bigger than one developer, how to evaluate a developer is the next decision.

If you’ve got quotes on the table and want a second pair of eyes that can read what they’re actually telling you, talk to me — half an hour reading three quotes can save you the cost of picking the wrong one. And if what you’re commissioning is a full system that needs a team to build and run, that’s what my agency, Digital Royalty, is for.