A business owner came to us last year with a number that made him wince every time he said it out loud: $34,000, to rebuild an internal ordering tool that had cost him $18,000 eighteen months earlier. Same features, roughly. Different developer. He hadn't been ripped off the first time, exactly. He'd just bought the cheapest version of something that needed to work for years, from someone who was competing on price, not on whether it would.
Price is a strategy, not a fact
A quote isn't a neutral measurement of how much work something takes. It's a number someone chose, based on what they think will win them the job and what they think they can get away with after. Two developers can look at the same scope and land $12,000 apart, and the gap usually isn't effort — it's what's quietly excluded. Error handling for the cases that "probably won't happen." A way to change the thing after launch without rewriting it. Someone answering the phone in month four.
None of that shows up in a line-item quote, because none of it is a line item. It shows up later, as a second invoice, or as a system nobody can touch without breaking something else.
I've watched this play out from both sides — bidding against quotes that made no sense until I realized they just weren't planning to do the parts that don't show up in a demo.
What the lowest bid is actually telling you
A quote that's dramatically lower than the others isn't a gift. It's information about how that vendor plans to hit that number, and there are only a few ways to do it: less senior people, less time spent on anything that isn't visible in the first demo, or a plan to come back later with change orders once you're already committed. Sometimes it's a vendor who genuinely works faster. That happens. It's rare enough that you shouldn't assume it by default, and you can usually tell the difference by what they ask you in the sales call — a cheap quote tends to come from someone who didn't ask many questions, because the questions are where the real scope lives.
The expensive lesson isn't "pay more." It's that price without context tells you nothing, and the context is almost never in the PDF.
What actually separates a good vendor from a cheap one
The honest signal isn't the number. It's what happens when you ask what's not included — a vendor worth hiring will tell you plainly, because they've thought about it. Ask who maintains the thing after launch, and listen for whether the answer is a person or a shrug. Ask what happens if requirements change halfway through, because they always do, and a fixed-bid quote with no plan for that is a promise that's already slightly false.
We quote projects the way we'd want to be quoted if we were the ones signing the check — which sometimes means losing the bid to someone cheaper, and a few months later, rebuilding what they built.
The takeaway
A quote is a guess about the future dressed up as a number. The question worth asking isn't "what's the price," it's "what did this number have to leave out to get this low." That question costs nothing to ask and it's the one that would have saved our client $18,000 and eight months of an ordering tool that worked right up until it didn't.