Choosing a web development partner is a decision you make once, but you live with the consequences of it for years: the codebase, the hosting contract, the search rankings, the integrations. Learning how to vet a website development company before you sign is what keeps a shortlist from turning into a liability. The cheapest shortlist candidate is rarely the lowest total cost once revisions, re-platforming and support gaps are counted.
This checklist walks through the seven evaluation areas that separate a dependable delivery team from a liability. Work through each one before the final decision, not after the proposal is signed.
1. Audit the portfolio past the screenshots
A polished landing page tells you little about engineering quality. Ask for two case studies that resemble your business and request:
- A live site from each project, not just the designed pages. Open it, load it on a phone, check the console for errors, and run it through a performance check.
- The scope and the outcome. What was the business objective, what changed after launch, and which numbers moved? Vague “increased conversions” claims with no baseline are not evidence.
- Their role. If you are buying back-end work, ask which parts of the featured sites they actually built rather than styled.
Then run one check that reveals process discipline: pick a recent project and test its mobile forms, its load speed, and whether the search engine results page description is current. Teams that treat accessibility, performance and technical SEO as deliverables rather than afterthoughts show it here.
2. Question the platform recommendation
Ask what platform they would build your site on and *why this one for your situation*. A credible answer references your content volume, who will edit it, and how long you expect to keep it.
Red flags:
- One platform for every client regardless of need.
- Proprietary or closed systems you cannot export content from.
- Recommendations driven by what they sell most, with no discussion of total cost of ownership.
Ask for their honest weaknesses of the chosen stack. A vendor who cannot name the platform’s downside is not thinking about your project; they are reading a sales script.
3. Walk the delivery process end to end
Request a step-by-step account of a recent engagement: discovery, design, build, testing, launch, and the first month after. You are looking for three things:
- Structure. Phases with named deliverables, not an undifferentiated “we’ll start working.”
- Your involvement. How many review rounds, what they expect from you, and how quickly decisions block their work. Ambiguity here usually means slow projects later.
- Quality gates. When performance testing, accessibility checks and cross-browser testing happen. If testing is “before launch,” ask what happens to fixes that surface in week two.
The average agency development process for a mid-market site runs six to ten weeks. Quotes that compress this dramatically usually cut the discovery or testing phases, and both failures surface as your cost later. Asking to see one engagement end to end is one of the most reliable tests inside how to vet a website development company, and most vendors underestimate how much it reveals.
4. Verify code ownership and portability
This is the clause most buyers skip and regret. Confirm in writing that at final payment you own:
- The design source files, not just exported images.
- The source code repository and read access to it.
- The database, including your content in an exportable form.
- All domain, hosting and third-party accounts registered in *your* name from day one.
Ask what it would cost to take the site to another provider in two years. A vendor confident in its quality will answer this question; a vendor planning lock-in will find it awkward.
5. Stress-test the support model
Post-launch support is where projects quietly die. Ask:
- What is covered by the warranty period after launch, and how long is it?
- What the support retainer includes: security patches, uptime, content edits, or only one of these?
- Response times in writing, with the SLA applied to different severities, not just “we respond quickly.”
- What happens to the price after the warranty. Support contracts routinely renew at higher rates than the project itself; get the figures now.
If you run campaigns on the site, also ask how they connect to measurement. An agency that plans data analytics and CRM integration during the build, rather than bolt-on later, is easier to work with when a lead fails to route correctly.
6. Read the proposal, not the price
Total figures hide the terms. Read each proposal for:
- Fixed scope definition. Which pages, integrations and rounds of revisions are included, and what is the rate for everything else?
- Change request handling. How changes are logged, priced and approved mid-project.
- Payment schedule. Large upfront percentages are a risk; release tied to named milestones is healthier for you.
- Intellectual property and confidentiality terms. Who owns content you supply, and what may the agency reuse from your project?
A clear proposal is short and readable. If you need a lawyer to find what is actually included, that is the first answer you got. Terms are also where knowing how to vet a website development company pays off most, because the contract decides who absorbs a delay, a failed integration or a scope change.
7. Check the human details
The final filter is often the easiest, and it is the part of how to vet a website development company that no portfolio can substitute for. During the discovery call:
- Do they ask about your business goal before talking about deliverables?
- Can they explain a technical decision in plain language when asked why?
- Does the person presenting the proposal join your project, or is your work handed to a different, junior team?
- Are they direct about budget fit, or do they stretch a scope they know does not fit?
A shortlist of four to five agencies is workable: it gives you a real comparison without a process so long that decisions stall.
How to vet a website development company, step by step
Vetting takes hours of work, and most buyers skip steps two, four and five because the process feels complete after a good demo. It is not: those three areas are where long-term cost and control are decided. Anyone can publish a checklist; the harder skill is knowing how to vet a website development company when the evidence sits in a demo rather than in a document.
For a second perspective on the same steps, Clutch publishes a guide to choosing a web development company that overlaps with this checklist on portfolio review, platform fit and cost comparison.
If you want a second pair of eyes on your requirements, or an independent review of a proposal you have already received, start with a discovery conversation. For the cost side of the decision, read our website development cost guide, and if you are at the stage of shortlisting agencies, the full hiring framework covers the evaluation from first contact to signed contract.
