Every Project Starts With a Question, Not a Quote
A website quote without a discovery conversation first is a guess, not a price — and the data on project failure backs that up.
If someone gives you a fixed price for your website or app before asking you a single question about your business, that number is a guess dressed up as a quote. The only way to get an honest price is to first figure out what you're actually building, who it's for, and what it needs to do — and that conversation, not the invoice, is where every real project should start.
The numbers behind why this matters
The most cited dataset on software project outcomes is the Standish Group's CHAOS Report. In its original 1994 study, only 16.2% of projects were delivered on time and on budget, 31.1% were cancelled before completion, and more than half of the ones that did get finished ran 189% over their original cost estimate source. By the 2020 edition, things had improved but not by much: about 31% of projects succeeded, 50% were "challenged" (late, over budget, or cut down in scope), and 19% failed outright source.
The same research found that project size and clarity of scope are the strongest predictors of outcome. Only 6% of large, loosely defined "grand" projects succeed, compared to 61% of small, well-defined ones source. That is not a small difference — it's a ten-times swing based almost entirely on how well the work was scoped before it started.
Standish Group's own surveys asked executives why projects succeeded, and the top three answers were user involvement, executive management support, and a clear statement of requirements source. A later breakdown of failed and challenged projects found 12.3% cited incomplete requirements and 12.8% cited lack of user involvement as root causes source.
Other research points the same direction:
- IAG Consulting studied over 100 organisations and found that companies with poor requirements practices spend an average of $2.24 million more per strategic project than those with strong practices, and see three failed projects for every one success source.
- PMI's Pulse of the Profession (2018) reported that 35% of organisations named inaccurate requirements gathering as the primary cause of project failure source.
- Industry summaries citing McKinsey research found that projects with no defined success measures overran budgets by 75% on average and delivered 39% less value than expected source.
None of these numbers are directly comparable to each other — they come from different studies, different years, and different definitions of "failure" versus "challenged." Figures floating around online that claim 66% or 69% of projects fail are loosely derived from the same Standish data pool but shouldn't be read as one precise statistic source source. The direction, though, is consistent across every source: skipping requirements gathering is one of the most reliable ways to blow a budget or lose a project entirely.
What "discovery" actually means in web development
In the web and app development industry, the step that replaces guessing with facts is usually called a discovery phase — structured questions and research before any design or code work begins. One agency puts it bluntly: "without discovery, any price quote is just a wild guess," and discovery is what prevents scope creep later and makes accurate pricing possible in the first place source. Another notes that starting development without a clear vision makes it impossible to quote realistically, and that features added mid-project — because nobody asked about them upfront — are what actually drive costs up and delivery times out source.
One UK agency reported that after it formalised its discovery process, it achieved a 95% client sign-off rate in 2022, compared to the longer, more inefficient design cycles it had before making the change source. The purpose of discovery, as one source defines it, is to "replace assumptions with validated decisions about scope, cost, and technical feasibility" before anyone commits time or money source.
In practice, a proper discovery conversation for a website or app project should cover:
- What problem is this solving — for the business and for the end user, specifically
- Who uses it — internal staff, customers, both, and what devices they're on
- What it must do on day one versus what can wait for version two
- What it connects to — payment gateways, CRMs, inventory systems, existing databases
- Who owns content and updates after launch, and how often things will change
- What "done" looks like — a measurable definition of success, not just "it works"
Skip any of these and you're not getting a quote, you're getting a placeholder number that will move once the real requirements surface.
Why India's pricing guides prove the point
If you've shopped for website quotes in India, you've probably noticed the ranges are absurd. That's not a coincidence — it's the direct result of vendors pricing without discovery.
| Source | Quoted range for a business website |
|---|---|
| RG Infotech | ₹5,000 to ₹2,50,000+ depending on type source |
| Pink Lemonade | ₹20,000–₹50,000 basic, ₹50,000–₹2,00,000 e-commerce source |
| Akoode | As low as ₹12,000 basic, ₹5 lakh+ for custom portals source |
| Webzyro | ₹25,000–₹1,00,000 basic, ₹2,00,000–₹6,00,000 custom-built source |
| Aalpha | $800–$1,200 baseline, with add-ons like search ranging $500–$30,000 and e-commerce extensions $10,000–$100,000+ source |
| Secuodsoft | Developer hourly rates ₹500–₹5,000; backend for complex apps ₹50,000–₹10,00,000+ source |
That's a 5-to-10x spread for what's nominally "a business website" across different guides. The gap isn't dishonesty — it's undisclosed scope. A ₹20,000 site and a ₹2,00,000 site are answering completely different underlying questions about functionality, integrations, and content volume. One vendor guide is explicit about this, warning buyers that "unrealistically low prices" and "vague timelines" are red flags of a project that was never actually scoped source.
If a studio hands you a number without asking what you need the site or app to do, you have no way of knowing which end of that range you'll actually land in — and neither do they.
The broader industry context
None of this happens in a vacuum. India's technology sector, the ecosystem web and app development sits inside, was projected by NASSCOM to cross $250 billion in FY24, growing 3.8% and remaining the world's largest IT sourcing hub, adding roughly 1% to GDP through digital public infrastructure source. The industry added 60,000 net jobs in FY24 — a sharp slowdown from 290,000 in FY23 — bringing the total employee base to 5.43 million source. In a market this large and this competitive, price alone is a poor way to choose a vendor, precisely because price without scope tells you almost nothing.
What this means if you're commissioning a project
Before you ask "how much will this cost," ask yourself if anyone has asked you these questions yet:
- What business outcome is this website or app supposed to produce
- Who are the actual users, and what do they need to be able to do
- What existing systems does it need to talk to
- What's the minimum version that's actually useful, versus the wishlist
- Who will maintain and update it after launch
If a vendor is willing to quote you a firm number without asking these, treat that as a warning sign, not a convenience. A studio that asks questions before it names a price isn't slowing you down — it's the only way the number they eventually give you will hold up once the work actually starts.
Questions people also ask
How long should a discovery phase take for a small business website?
The research reviewed here doesn't specify a fixed duration, since it varies with project complexity. The consistent point across sources is that discovery should happen before any design or development work is quoted or started, regardless of how long it takes source.
Why do website quotes in India vary so much for what looks like the same project?
Because published guides describe wildly different scopes under the same label. Ranges span from ₹5,000 to ₹2,50,000+ for "business websites" and from $800 baseline to over $100,000 with e-commerce add-ons, depending entirely on functionality, integrations, and content that often isn't disclosed upfront source source.
What's the single biggest reason software projects fail or run over budget?
Across multiple independent studies, unclear or incomplete requirements is the most frequently cited root cause — whether measured as 35% of organisations in PMI's Pulse of the Profession source or as a top-three success factor in Standish Group's CHAOS research source. Sources differ on exact percentages, but all point to the same underlying cause: work started before scope was clear.