A web development quote is a promise of work for money. Understanding what's actually being promised prevents painful surprises later.
Here's how to read quotes critically and compare them fairly.
What a Good Quote Includes
Project Scope
A clear description of what will be delivered:
- Number of pages - Specific pages or page types (homepage, service pages, contact)
- Features - Contact forms, galleries, blog, e-commerce, specific functionality
- Design work - Custom design, template customisation, or no design
- Content - Who provides content? What about images?
- Integrations - Payment processing, CRM, email marketing, other tools
Watch for: Vague descriptions like "professional website" without specifics. That could mean anything.
Deliverables
What you'll actually receive:
- Live website on your hosting
- Design files (if applicable)
- Admin access and training
- Documentation
- Source code and assets
Watch for: Missing deliverables or ambiguous ownership. "Access to your site" isn't the same as "ownership of all custom code."
Timeline
Realistic schedule for completion:
- Project phases with durations
- Milestones and checkpoints
- Dependencies (what they need from you, when)
- Launch date or range
Watch for: No timeline (suggests unclear planning) or unrealistic timelines (suspiciously fast).
Pricing Breakdown
How the total is calculated:
- Line items for different components
- Clear total
- What's hourly vs fixed
- How additional work is priced
Watch for: Single lump sum with no breakdown. You can't compare or understand a number without context.
What's Included
Explicit list of inclusions:
- Revisions (how many, at what stages)
- Testing across devices/browsers
- SEO basics
- Training
- Post-launch support (how long)
- Content entry
Watch for: Assumptions about what's "obviously" included. If it's not listed, it's not guaranteed.
What's Excluded
Equally important - explicit list of exclusions:
- Hosting and domain
- Content writing
- Photography/videography
- Ongoing maintenance
- Third-party costs (plugins, subscriptions)
- Future changes
Watch for: Missing exclusions section. This leads to "I assumed that was included" disputes.
Terms and Conditions
The legal/business framework:
- Payment schedule
- Cancellation terms
- IP ownership
- Liability limits
- Revision process
- Change request handling
Watch for: Missing terms or one-sided terms that heavily favour the developer.
How to Compare Quotes
Getting three quotes is standard. Comparing them fairly requires more than looking at the bottom line.
Normalise the Scope
Different quotes may describe different projects. Before comparing prices:
- List what each quote includes
- Note what each excludes
- Identify genuine differences in scope
- Consider adding missing items to make fair comparison
A £5,000 quote including e-commerce isn't comparable to a £3,000 quote without it.
Look at Value, Not Just Price
Consider what you're getting for the money:
- Experience level and quality indicators
- Included support and training
- Revision allowances
- Timeline (faster isn't always better, but matters)
- Communication quality already demonstrated
The best value isn't always the lowest price.
Identify Assumptions
Each developer makes assumptions about your project. Find them:
- Ask what they assumed about content, images, and copy
- Clarify expectations about your involvement
- Understand their interpretation of your requirements
Misaligned assumptions become change orders later.
Question Outliers
If one quote is dramatically different from others:
- Very low: What's being cut? What experience level?
- Very high: What's included that others missed? Is this overkill?
Both extremes need explanation. Neither is automatically wrong.
Red Flags in Quotes
Too Vague
"Website development - £2,500"
This tells you nothing. What kind of website? How many pages? What features? What's included?
Ask for: Detailed scope breakdown.
Suspiciously Cheap
If one quote is half the others without clear reason, something's missing:
- Less experienced developer
- Reduced scope
- Offshore work (not inherently bad, but know what you're getting)
- Bait and switch (low initial quote, charges pile up)
Ask: "Why is your quote significantly lower than others?"
Suspiciously High
If one quote is double the others:
- Premium agency overhead
- More comprehensive scope
- Gold-plating features you don't need
- Simple overcharging
Ask: "Can you help me understand why this is priced higher than alternatives?"
Undefined Revision Process
No clarity on how revisions work means:
- Potential for disputes
- Either unlimited (unsustainable) or arbitrarily limited
- Unclear when revisions become change orders
Ask for: Written revision policy with defined rounds per phase.
No Exclusions Listed
Everything has limits. If nothing is excluded:
- The developer hasn't thought it through
- Disputes await over what's "obviously" not included
Ask: "What's NOT included in this quote?"
Unusual Payment Terms
- 100% upfront: High risk, no accountability
- 100% on completion: Developer takes all risk (uncommon)
- Back-weighted with no milestones: Cash flow problems
Normal: 30-50% upfront, milestones throughout, remainder at launch.
Questions to Ask About Quotes
About Scope
"Can you walk me through exactly what's included?" "What happens if we need something not on this list?" "How do you define a 'page' in this context?"
About Pricing
"How did you arrive at this number?" "What would reduce the cost if we needed to?" "How are additional requests priced?"
About Process
"How many revision rounds does this include?" "What happens if revisions exceed the allowance?" "How do you handle changes mid-project?"
About Risks
"What could make this take longer than estimated?" "What could add costs beyond this quote?" "What do you need from me to stay on track?"
Negotiating Wisely
Negotiation is normal, but approach it thoughtfully:
Understand What You're Trading
Reducing price typically means:
- Reducing scope (fewer pages, features)
- Reducing revisions
- Reducing the developer's margin
- Reducing time/quality investment
Ask what they would remove to lower the price. This is more productive than just asking for a discount.
Don't Squeeze Too Hard
A developer with no margin has no buffer for problems. They may:
- Cut corners
- Become resentful
- Deprioritise your project
- Disappear mid-project
Fair pricing for good work serves both parties.
Consider Value Adds
Instead of reducing price, consider what else you could get:
- Extra month of support
- Additional training
- Future work discount
- Content help
Sometimes these are easier to provide than discount.
Before You Sign
Final checks before committing:
Is everything understood? - Don't sign if anything is unclear.
Is it in writing? - Verbal promises need to be in the document.
Do payment terms match cash flow? - Can you actually pay when due?
What about IP? - Do you clearly own the result?
How do you exit? - What if you need to cancel or they fail to deliver?
Who's your contact? - Who handles communication and decisions?
The Bottom Line
A quote is a proposal for a business relationship. It should be clear, complete, and fair to both parties.
Good quotes:
- Detail what you're getting
- Specify what you're not getting
- Explain how the process works
- Set clear expectations
- Feel fair and professional
Be wary of quotes that:
- Are vague or incomplete
- Are dramatically different from others without explanation
- Have unusual or one-sided terms
- Come from developers who seem annoyed by questions
Take time to understand what you're agreeing to. The clarity you gain now prevents the disputes you'd have later.