You describe the same app to four people and get back $500, $6,000, $18,000 and $50,000. Nobody is lying to you. The spread is real, and it is the single most useful piece of information you will get, once you know how to read it.
Key Takeaways
- A quote is not a price. It is a guess about a description you have not finished making.
- The spread measures how differently four people imagined the same sentence.
- Cheap quotes are usually correct about a smaller app than the one in your head.
- You cannot compare quotes until every quoter is pricing the same written scope.
The Quote Is a Guess About Your Description
When you say "an app where customers book appointments," a developer has to fill in about forty details you did not mention. Do two kinds of people log in, customers and staff? Does it take payment? Does it text a reminder? Does it need to know that Tuesday is half day? Does it talk to the calendar you already use?
Each person fills those gaps differently, and each one prices what they imagined. The $500 quote imagined a form. The $50,000 quote imagined a system that runs your business. Both quoted honestly. They were not quoting the same thing, because the thing did not exist in writing.
What Each End of the Range Usually Means
| Quote | What they probably pictured | Where it goes wrong |
|---|---|---|
| Under $1,000 | A single screen, a form, a template | It does not do the part you actually needed |
| A few thousand | One developer, a few weeks, no second pair of eyes | Fine until they vanish or you need a change |
| Mid five figures | A team, a written plan, milestones | Slow to start, because the plan comes first |
| "Custom, let's talk" | Nothing yet | The number arrives after you are invested |
The Fix Is Cheaper Than Any of the Quotes
Write down four things before you ask anyone for a number.
What happens after someone taps the main button on the first screen. Who is on the other side of that, a customer or you. What it has to talk to that already exists, your calendar, your card processor, your spreadsheet. And what you would cut if it cost twice as much.
That last question does more work than the other three. It separates the app from the wish list, and it is the one thing no quoter can answer for you.
Send that page to every person you ask. The quotes will land within about twenty percent of each other, and the ones that do not will now be obviously wrong rather than mysteriously different.
A Concrete Version
A dental practice owner asked four people for a patient reminder app. She got $800, $9,000 and two firms who would not quote without a call. After she wrote one page describing what happened when a patient replied "reschedule" to a reminder text, three of the four requoted. The $800 became $4,500, because the original quote had not included replies at all. The $9,000 stayed within a few hundred dollars. She had turned an unusable spread into a real comparison in an afternoon, and she found out the cheap option had been pricing a different product.
The Honest Counterpoint
Sometimes a wide spread is not your fault. Some firms quote high because they are busy and would rather not take the work, and some quote low to get in the door and make it back on changes later. Writing the scope down does not stop either behaviour. What it does is make it visible, because a change-order strategy is hard to run against a written plan that both of you signed.
Frequently Asked Questions
Should I just take the cheapest quote?
Only if it is priced against the same written scope as the others. A cheap quote against no scope is not cheap, it is a different and smaller project that you will discover halfway through.
Is it normal for a developer to refuse to quote without a call?
Yes, and it is often a good sign. A quote that arrives with no questions is from someone who will find out later, and you pay for what they find. What is not normal is refusing to put a number in writing after that call.
How much detail do I actually need before asking?
One page. Not a specification document, not wireframes. The four questions above, answered in plain sentences.
Should I tell them my budget?
Yes, and give a range rather than a number. Hiding it does not get you a lower price, it gets you a quote for a project nobody sized against what you can spend. A range lets a good firm tell you what fits inside it, which is the useful conversation.
The Bottom Line
The spread in your quotes is a measurement of how vague the request was, not of how honest the quoters are. Spend an afternoon writing one page, send the same page to everyone, and the numbers will converge. If you want that page written for you, the honest read asks you a few questions and produces it, along with the cost range, at no charge. See also what a good software quote looks like and how to write a spec for a developer.
Roberto Espinoza is CEO of Ruzora, which builds custom software for business owners at a fixed price and places pre-vetted senior LATAM engineers with US teams. Get a free honest read on your idea.
