We're on the other side of this conversation constantly — a founder has three quotes from three different web development companies, the prices vary by five times, and they genuinely can't tell what's different between them. So here's the checklist we'd hand a friend before they sign anything.
Ask to see real, live client websites — not a portfolio page
Portfolio screenshots can be old, redesigned since, or built by someone who left the company. Ask for three live URLs of sites they built recently, in a similar category to yours, and actually browse them on your phone. Check load speed, check if the contact form works, check if it looks maintained. This ten-minute exercise filters out more bad vendors than any sales conversation will.
Understand exactly what "SEO-friendly" means for that quote
Almost every agency claims their websites are SEO-friendly. Very few define what that actually includes. Ask specifically:
- Will the site be server-rendered or a client-side-only build that search engines struggle to index properly?
- Does the quote include meta titles, descriptions, and canonical tags for every page, or just the homepage?
- Is there a sitemap.xml and robots.txt configured at launch?
- Will page speed (Core Web Vitals) be tested before handover, or is that a separate paid add-on?
If the answers are vague, that's useful information. This is the exact standard we hold our own web development projects to — it's not an upsell, it's table stakes for a site that's actually meant to attract traffic instead of just existing.
Clarify who owns the code and the domain
This sounds obvious until you hear how many businesses discover — years later, wanting to switch vendors — that their "web developer" holds the domain registration in their own account, or built the site on a locked proprietary builder that can't be exported. Before starting, get in writing: you own the domain, you own the code, and you'll receive full access (hosting, DNS, source repository) at project completion, not held hostage for an ongoing retainer.
Pin down what happens after launch
A website is not a one-time deliverable — it needs updates, security patches, and occasional content changes. Ask what's included post-launch: is there a warranty period for bug fixes? What does an hourly rate look like for future changes? Is there a maintenance plan, and what does it actually cover? Vendors who've thought this through will have a clear answer immediately; vendors who haven't will improvise one.
Compare timelines honestly, not just by the number of weeks
A four-week timeline from an agency that starts design only after finalizing your content and sitemap is very different from a "two-week" quote that assumes you'll provide print-ready content and approve everything within 24 hours. Ask what the timeline assumes from your side, and what happens to the schedule if content or feedback is delayed — that's usually the real reason projects run late, not the developer's speed.
Watch how they handle scope questions during the sales conversation
This is a soft signal but a reliable one. A vendor who asks pointed questions about your users, your goals for the site, and what "success" looks like six months after launch is thinking about the actual outcome. A vendor who jumps straight to a fixed price without understanding your business is often selling a template, not a solution — and templates are fine for some businesses, but you should know that's what you're buying.
A short version of the checklist
- Live examples of recent, similar client work — not just screenshots
- A specific, written answer on SEO fundamentals included in the build
- Written confirmation you'll own the domain, hosting access and source code
- A clear post-launch support and maintenance plan
- A realistic timeline that states what it depends on from your side
If you're currently comparing quotes and want a second opinion — even on a proposal from another company — we're happy to look it over and tell you honestly what stands out and what to ask about. It costs nothing to get that clarity before you commit.