Quick Answer: How do I choose a web development company?
Choosing a web development company means matching a clearly written project brief to a vendor whose proven work, technical process, and contract terms you have actually checked. You can act on this by shortlisting three to five firms, reviewing their live sites and code quality, and interviewing their past clients directly.
Agencies, freelancers, and specialist shops differ mainly in scale, price, and how much of the work they keep in-house. A small studio may suit a brochure site, while a larger agency fits complex platforms and integrations. (Best places study abroad choose country that fits you)
Before signing, compare portfolio evidence, accessibility conformance, security practices, ownership of code and domain, data protection terms, timeline, support model, and total cost.
Why the cheapest quote is usually the most expensive

Ever noticed how the lowest bid always arrives fastest and looks the tidiest? That is not a coincidence. A cheap quote often hides assumptions: content you must write yourself, hosting nobody has priced, or a template stretched until it squeaks.
The real cost of a website is not the invoice. It is the invoice plus the rework, the missed launch, and the migration you pay for eighteen months later when the original team disappears. Buyers who compare only headline prices tend to learn this the hard way.
A better habit is to compare quotes against the same written brief. When every vendor prices the same scope, the differences become visible. When each vendor prices a different imaginary project, the numbers mean nothing.
Start with a brief, not a wish list
Most bad projects begin with a vague request. “We need a new website” gives a vendor nothing to work with, so they guess, and their guess becomes your contract.
Write a short brief that covers what the site must do, who uses it, which systems it must connect to, and what success looks like. Include your deadline and your budget range. Vendors who flinch at a stated budget were never going to fit it anyway.
Practical tip: describe outcomes, not solutions. “Customers must be able to book a repair slot in under two minutes” is testable. “We want a modern, dynamic experience” is not. The UK government’s service manual guidance on working with technology suppliers makes a similar point: over-specifying the solution too early narrows the field and can lock you into the wrong approach.
Check the portfolio like a sceptic
Every agency shows its best three projects. Your job is to look past them.
Open the live sites they built and test them yourself. Load them on a phone over a slow connection. Click the forms. Try the checkout. Run a free audit tool such as Lighthouse, which checks performance, accessibility, SEO and best practices, and see what scores come back. A pretty homepage with a failing performance score tells you plenty.
Then ask the questions that separate builders from decorators:
- Which sites on your list did you build end to end, and which were redesigns of someone else’s code?
- Can you show me the content management system a client actually uses day to day?
- What happened to your last three clients after launch?
- Who maintains those sites now?
Vendors who cannot answer the last two questions cheerfully are worth a second thought.
Ask about accessibility before you have to
Accessibility is not a courtesy feature. In many markets it is a legal requirement. Public-sector bodies across the EU must meet the accessibility requirements set out in the Web Accessibility Directive, adopted in 2016. In the United States, Section 508 of the Rehabilitation Act applies to federal agencies. If you sell to the public sector, or hope to, an inaccessible site is a barrier to the contract itself.
The current benchmark is WCAG 2.2, published as a W3C Recommendation on 5 October 2023. A vendor claiming their work is “accessible” should be able to name the conformance level they target, usually AA, and show you an audit that backs it up.
Common mistake: accepting “we follow best practices” as an answer. Ask for a sample accessibility report from a recent project. If they have never produced one, they are learning on your budget.
Security is a process, not a plugin
A security plugin is not a security strategy. Ask how the team handles the risks catalogued in the OWASP Top Ten, the widely used awareness list of critical web application security risks, currently the 2021 edition. You do not need to understand every category. You do need to hear specific answers about input validation, authentication, dependency updates, and how they handle secrets and credentials.
If your site sits behind protective infrastructure, it helps to know what that layer actually does. This plain explanation of what a web application firewall blocks is a useful primer before conversations get technical, and this guide on how to choose a web application firewall that fits your stack helps you judge whether the vendor’s hosting recommendations are sensible or just familiar.
Red flags worth noting: no staging environment, direct edits on the live site, shared logins for the whole team, and nobody able to explain how security patches get applied.
Data protection belongs in the contract
If the vendor will touch personal data, they are a processor under the EU GDPR, in force since 25 May 2018, and Article 28 requires a written contract with specific terms. That is not legal trivia. It shapes who is liable when something goes wrong and what the vendor must do if there is a breach.
Ask where data is stored, which sub-processors are involved, how long backups are kept, and what happens to your data when the relationship ends. Vague answers here are a warning sign, not a personality quirk.
Own your code, your domain, and your accounts
This is the single most common regret in web projects. A business pays for a site, then discovers the domain is registered in the agency’s name, the hosting account belongs to them, and the code licence is murky.
Insist on the following in writing:
- The domain is registered in your organisation’s name, with you holding the registrar login.
- Hosting and cloud accounts are in your name, with the agency given access, not ownership.
- The contract states clearly that you own the custom code and design on final payment.
- Any third-party or open-source components are listed, with their licences.
That last point matters more than people expect. The Open Source Initiative maintains the Open Source Definition and an approved licence list, and some licences in the GPL family can impose obligations on how you distribute your own code. A vendor who cannot list the licences in your stack has not looked.
Compare the shortlist on the same criteria
Once three to five firms remain, score them side by side. A simple table beats a gut feeling, especially when a senior colleague asks why you picked one over another.
| Criterion | What good looks like | Warning sign |
|---|---|---|
| Relevant work | Live sites similar to your scope | Only mockups or dead links |
| Accessibility | Names WCAG 2.2 level, shows audit | “We follow best practices” |
| Security | Explains OWASP risks, has staging | No patching process |
| Ownership | You hold domain and hosting | Agency holds accounts |
| Data protection | Written processor terms | Verbal assurances |
| Support | Named response times, clear cost | “Just call us” |
| Communication | Direct access to the build team | Only a sales contact |
Score each row honestly. A firm that wins on price but loses on ownership and support is not the cheap option; it is the deferred-cost option.
Interview their past clients, not their sales team
Reference calls are where the truth leaks out. Ask for two clients from the last two years whose projects resemble yours, and speak to them without the vendor on the line.
Useful questions: Did the project finish on the date promised? What changed in scope, and how was it handled? How quickly did problems get fixed after launch? Would you hire them again, and why?
Listen for hesitation as much as words. “They were lovely people” is not a reference. “They shipped two weeks late but told us in week three and absorbed the overrun” is.
Match the vendor type to the job
Not every project needs an agency, and not every project survives a freelancer. Be honest about which one you are buying.
| Vendor type | Best for | Watch out for |
|---|---|---|
| Freelancer | Small sites, tight budgets, clear scope | Single point of failure, limited capacity |
| Small studio | Brochure sites, CMS builds, ongoing care | Fewer specialists, thinner cover |
| Mid-size agency | Custom platforms, integrations, design systems | Higher minimums, more process overhead |
| Enterprise firm | Large regulated programmes, procurement needs | Cost, slower decisions, layered contacts |
If your project touches design tooling and you are weighing a switch mid-project, this comparison of Figma alternatives for beginners choosing a design tool covers the handover implications. Similarly, if your team will manage content and tasks after launch, this roundup of board tools for beginners comparing Trello alternatives helps you pick something the vendor can actually support.
Read the contract for the exit, and for the entry
Everyone reads the scope section. Almost nobody reads the termination clause until they need it.
Check what happens to your code, data, and accounts if you leave. Confirm the notice period. Ask whether there is a handover fee, and get the number in writing. Confirm what happens to unpaid invoices and whether you keep the work already delivered.
A vendor confident in their work will not object to a fair exit clause. Resistance to that conversation is information.
Budget for after launch
Launch day is the start of the relationship, not the end of the project. Plan for hosting, maintenance, security updates, backups, and small changes. Ask each vendor to quote a twelve-month support arrangement alongside the build.
Common mistake: spending the entire budget on the build and leaving nothing for care. A site with no maintenance plan ages badly and quietly becomes a security risk.
Conclusion
Choosing a web development company is really a test of diligence, not charm. Write a clear brief, check live work with your own hands, ask about accessibility, security, data protection, and ownership before anyone signs, and speak to past clients directly. Compare shortlisted firms on identical criteria and read the exit clause as carefully as the scope.
The right partner will welcome those questions. The wrong one will find them inconvenient, and that reaction is the most useful answer you will get.
FAQ
How long should a website project take?
A small marketing site might take four to eight weeks. A custom platform with integrations often runs three to six months. Ask each vendor to break their timeline into phases with dates, and treat any estimate given without a written brief as a guess.
Should I choose an agency or a freelancer?
It depends on scope and risk. Freelancers suit clear, contained projects and tight budgets. Agencies bring cover, specialists, and process, which costs more but reduces the risk of one person vanishing mid-build. Match the choice to how much you can afford to lose if it goes wrong.
What deposit is normal?
Deposits vary widely by market and project size, often somewhere between a quarter and a half of the total, with the rest tied to milestones. Never pay the full amount upfront. Milestone payments tied to delivered, reviewed work protect both sides.
How do I check a vendor’s technical quality?
Open their live sites, test them on a phone, and run a free audit tool such as Lighthouse on performance and accessibility. Ask how they handle staging environments, dependency updates, and code reviews. Then ask a developer you trust, outside the vendor, to look at one sample.
What should the contract include?
Scope, timeline, payment milestones, ownership of code, domain, and hosting accounts, data protection terms, warranty period, support arrangements, and a clear termination clause with a handover process. If any of those are missing, ask for them in writing before signing.
Can I switch companies later?
Usually yes, provided you own the domain, hosting, and code, and the previous vendor hands over documentation and access. That is why ownership clauses matter so much at the start. A clean handover takes days; a contested one can take months and cost a rebuild.


