How to Choose a Web Development Company
The questions that separate suppliers who will serve you from those who will not.
How do I choose a web development company?
Judge a supplier on what they ask rather than what they claim. Good ones ask about your customers, your process and how content will be maintained before quoting. Then check the practical terms: who owns the code and accounts, what happens after launch, how many templates the quote covers, and who specifically does the work.
Most disappointment with web projects traces back to questions that were not asked at the start. These are the ones that matter, with an explanation of why each one does.
What should I ask before hiring?
Who exactly will do the work. How many templates the quote covers. Whether content is included. Who owns the code, domain, hosting and analytics. What happens if something breaks after launch. Whether there is a staging environment. And what the supplier will need from you, and when.
The last question is revealing. A supplier who cannot tell you what they need from you has not thought about how the project will actually run.
Who should own the code and accounts?
You should. The domain, hosting, repository, analytics and any advertising accounts belong with your business, with access granted to the supplier. Agree it in writing before work starts. Recovering accounts held by a former supplier is difficult and sometimes impossible.
This matters most for advertising accounts, where the historical data has real value and cannot be transferred if the account belongs to someone else.
How do I evaluate a portfolio?
Open the sites on a phone and check how they load and behave. Look for depth of content rather than visual polish alone. Ask which parts the supplier actually did — design, build, content, or all three — since portfolios often show collaborative work without saying so.
Also check whether the sites are still live and maintained. A portfolio of sites that have since been replaced tells you something.
What are warning signs?
Guaranteed search rankings, which nobody can honestly promise. Quotes given before any questions are asked. Reluctance to name who does the work. No mention of hosting, maintenance or what happens after launch. Pressure to decide quickly on a discount that expires.
A supplier who explains what could go wrong and what they would not recommend is usually more reliable than one who agrees with everything.
Should I choose local or remote?
For most web work it makes little practical difference — nearly all of it is done remotely with scheduled calls. Local matters when a project genuinely needs on-site sessions, or when you personally work better face to face. Judge on capability and communication first.
What matters more than location is response time, clarity of communication and whether the supplier documents decisions somewhere you can both refer back to.
Services related to this topic
Related solutions
More on web design
Related comparisons
Want help applying this?
Tell us your situation and we will tell you what we would actually do first.