Most website quotes are guesses dressed in confidence. The neat PDF, the line items, the bottom-line number that arrives within a day of you asking — they look like analysis. They aren't. They're an agency's best guess based on a 30-minute conversation where the most important questions weren't asked.
Eight years of running website projects has shown me that the actual final cost of a website is typically 30 to 50 percent different from the original quote. Sometimes the agency absorbs the difference quietly. Sometimes the client gets surprise invoices for "out of scope" work. Sometimes the project just doesn't finish properly, and both sides walk away frustrated.
This isn't because designers are dishonest. It's because website scoping is genuinely hard, and most quoting processes don't allow time to do it properly. Below are the four real reasons quotes go wrong, what they cost you when they do, and the six questions to ask before signing anything.
The discovery conversation is too short
Most agencies scope a website in 30 to 60 minutes of conversation. That's barely enough time to understand what the homepage should say, let alone how the underlying business actually works. By the time the call ends, the agency has a vague picture of the brand, a list of pages, and a handful of features mentioned in passing.
What hasn't been understood: how leads currently flow through the business, what the website's job actually is, who specifically it needs to convert, what existing tools it has to integrate with, and what edge cases will quietly become 30 percent of the build. None of these come out in a single short call. They come out in a real working session — sometimes two.
The agencies that scope in 30 minutes are the ones that send the surprise invoices in week eight. The math doesn't work any other way.
The "small thing" rule
Every project has a "small thing" mentioned casually mid-discussion. The booking calendar that integrates with the studio's existing scheduling tool. The currency switcher that needs live exchange rates. The export to the accountant's specific software. The member login that has to sync with the existing CRM.
These never get scoped properly because they don't sound expensive. The owner mentions them as afterthoughts. The agency nods and moves on. The quote treats them as standard features and budgets a few hours each.
The truth is that these integrations are often the actual hardest part of the build — sometimes accounting for 30 to 40 percent of total development time. When the project is six weeks in and the integration isn't working, somebody pays for the extra weeks. Usually that conversation gets uncomfortable.
Design hours are estimated by designers, not project managers
A designer asked "how long will this design take?" will give you the time it takes to do the design once, well. What they almost never include is the four rounds of client feedback, the two pivots when the brand direction shifts mid-project, and the inevitable "can we try one more option" that arrives in week three.
Real design hours are typically 50 percent creation, 50 percent iteration. Most quotes account for the creation but treat the iteration as a small buffer. When the iteration runs longer than planned (and it usually does), the timeline slips, the cost overruns, and someone has to absorb the gap.
Good project management would price this honestly. Most quotes don't.
The handoff to development is treated as free
Most quotes assume design and development are clean, sequential phases — finish the design, hand it to the developer, build the site. In reality, this handoff is messy. The developer finds layouts that work beautifully in Figma but break on mobile. The designer realises a component needs a state nobody discussed. Decisions made in design get questioned in development, and questions raised in development require design adjustments.
This back-and-forth typically eats 10 to 15 percent of total project time. It's never on the quote. It's the invisible cost that explains why projects that "should have taken eight weeks" took twelve.
The six questions that protect you
If you're about to sign a website quote, ask these six questions before you do. The answers will tell you more about the project than the price ever will.
- "Walk me through what 'unlimited revisions' actually means." If there's no revision cap defined anywhere, the project will drag. Real revision policies define rounds, scope, and what triggers a change order.
- "What happens when scope changes mid-project?" The answer should be a written change-order process with defined approval steps — not a verbal "we'll figure it out." Verbal arrangements always become disputes later.
- "Show me the project plan with timeline breakdown." Vague timelines like "8-12 weeks" mean delivery is also vague. Good agencies break the build into phases with dates, deliverables, and dependencies.
- "Who owns the source code, hosting setup, and accounts when it's done?" If the answer is "we do," that's a hostage situation waiting to happen. You should own everything by the end of the project, with documented handover.
- "What's not included that I might assume is?" Common gaps: hosting, domain, content writing, image licensing, premium plugin licenses, ongoing maintenance, training. Get the full list.
- "Have you built something like this before? Can I see it live?" Generic portfolios mean generic processes. Specific past work tells you whether they actually understand your kind of project.
These six questions will not all get clear answers from every agency. That's information too. Anyone who can't answer them confidently doesn't have a process — they have a sales pitch.
The honest summary
The quote is the easiest thing to get. The truthful quote is the hardest. Most agencies optimise for getting you to "yes" on the document; you need to optimise for "yes" on the project that actually arrives twelve weeks later.
The agencies worth working with will spend more time scoping than quoting. They'll push back on assumptions. They'll ask uncomfortable questions about your business. They'll quote you a range, not a single number, because the range is honest and the single number isn't.
If a quote arrives in your inbox within 24 hours of your first conversation — be careful. It's not a sign of efficiency. It's a sign that nobody thought about your project hard enough to be slow.
If you're trying to scope a website project right now, the website cost calculator gives you an honest tier-based estimate before any quote arrives. It can't replace a proper conversation, but it can prevent you from being misled by your first quote — and gives you a sense of where your project genuinely sits before the sales calls start.
