Three studios, three quotes, three completely different numbers for what looks like the same project. €18,000. €42,000. €65,000. This happens constantly, and it's not because two of the three are ripping you off. It's because a quote is only as good as what it's actually pricing — and most quotes don't make that visible.
Here's how to read a quote properly, and the red flags that predict a painful project regardless of the number on the front page.
Start with what's actually included
Before comparing prices, compare scope line by line. A €20,000 quote that excludes testing, deployment and a month of post-launch support is not cheaper than a €28,000 quote that includes all three — it's the same project with part of the invoice hidden until later. Ask every studio for a written breakdown of exactly what's in and out of scope. If a studio resists giving you this, that's already a signal.
Five things to check on every quote
1. Is the scope specific or vague?
"Build a client portal" is not a scope. "Client login, order history view, document upload with a 10MB limit, admin panel to manage user access" is. Vague scope means either the studio didn't do the work of understanding your project, or they're deliberately leaving room to interpret it in their favor later through change requests. Compare this against your own brief — if their scope doesn't map cleanly to what you asked for, ask why.
2. What's the contract model, and does it match the risk?
A fixed-price quote for a genuinely uncertain project (undocumented legacy integration, unclear requirements) usually means a large hidden risk buffer, or a studio that will lean hard on change requests once work starts. Check whether the contract model fits the actual uncertainty of the work, not just what sounds safest on paper.
3. Is there a discovery phase, or straight into building?
A studio that quotes a full six-month project after one call, with no separate discovery phase, is pricing on assumptions. That's fine for very small, well-understood projects. For anything non-trivial, the absence of discovery is one of the most reliable predictors of scope creep and rework later.
4. Who owns the code and the credentials?
Check that the contract states you own the source code, the domain, the hosting account and any third-party credentials at the end of the project — not just a license to use what they built. This matters most the day you want to switch studios or bring development in-house; see the build vs. outsource trade-offs for why that flexibility is worth protecting upfront.
5. What happens after launch?
A quote that ends at "go-live" with no mention of bug fixes, hosting or a support arrangement is incomplete. Ask explicitly: what's covered in the first 30 days after launch, and what does ongoing support cost after that. This is often where the real long-term cost of a project lives, not in the build price.
Red flags worth walking away from
- A price with no breakdown — one number, no line items, no assumptions listed.
- No questions asked — a serious quote follows a conversation where the studio pushed back on your brief or asked things you hadn't considered. A quote that arrives unchanged from your first message means nobody dug into it.
- Unwillingness to name a contract model — "we'll figure out billing as we go" is not a plan.
- A price that's dramatically lower than the others — the cheapest quote is sometimes the best deal, and sometimes it's a studio that hasn't understood the complexity yet, or plans to make up the difference through change requests.
- No mention of who you'll actually work with — a quote that doesn't name the person doing the work, especially from larger agencies, can mean your project lands with whoever's free that week.
Comparing quotes apples to apples
Before deciding, normalize the quotes yourself: list scope, contract model, discovery phase (yes/no), ownership terms and post-launch support side by side for each. Once the hidden differences are visible, the numbers usually make a lot more sense — and the cheapest quote on paper isn't always the cheapest project.
Want a second opinion on a quote you've received?
Send it over — I'll tell you honestly what looks reasonable, what's missing, and where the real risk sits. No obligation, and no sales pitch dressed up as advice. Get in touch.