How to Choose a Web Development Company: What to Check Before You Hire
Choose a web development company on evidence you can check: live sites you can open on your own phone, the people who would build yours, who owns the code, domain and accounts at the end, and a quote broken into parts you can recognise. Then compare two proposals written against the same brief.
Prabhu SolutionsPublished 8 October 2026Last reviewed 8 October 202613 min read
On this page
- How do you choose a web development company?
- What are website development services?
- Which parts of a website project should a quote cover?
- What should a web development company show you before you hire it?
- Which platform should your website be built on?
- What questions should you ask any web development company?
- Who should own the code, the domain and the hosting?
- Should you use a freelancer, a small agency or a larger company?
- How do you compare web development quotes?
- When is a web development company the wrong choice?
- What should happen after the website launches?
How do you choose a web development company?
Choose a web development company on evidence you can check: live sites you can open on your own phone, the people who would build yours, who owns the code, domain and accounts at the end, and a quote broken into parts you can recognise. Then compare at least two proposals written against the same brief.
A web development company turns an agreed design into a working, editable, tested website. That is a narrower job than most pitches suggest, and it is easy to confuse with design, copywriting and search optimisation. The website development work is the build; this guide is about judging anyone's version of it, ours included.
The order of checks matters. Ownership and handover come first, because they decide whether you can leave. Evidence comes second, because a portfolio is a description and a live site is a test. Platform fit comes third, and price last, because a price only means something once you know what it buys. What a website costs in the UK sets out the drivers behind the figure.
The point
Ownership and handover come first, because they decide whether you can leave.
What are website development services?
Website development services are the build stage of a website: turning an agreed structure and design into working pages, connecting them to a content management system, building the forms and integrations behind them, testing everything and launching. They sit between design, which decides how the site looks and behaves, and maintenance, which keeps it healthy afterwards.
On a small project one person may cover every role; on a larger one they are usually separate, and knowing the roles helps you read a quote. Front-end developers build the pages. CMS developers build the templates and editable blocks your team will use. Back-end developers build the forms, integrations and data flows. Someone tests, someone owns the hosting and deployment, and someone should be answerable for the technical decisions afterwards.
Three neighbouring services are often bundled into the same proposal and are worth separating. Website design decides structure and appearance. Technical SEO checks that the build can be crawled and indexed. Website maintenance keeps the site secure and working after launch. Whether the company does these itself, subcontracts them or leaves them to you is a question to ask rather than assume.
The point
Three neighbouring services are often bundled into the same proposal and are worth separating.
Which parts of a website project should a quote cover?
A website development quote should cover design or its deliberate absence, the front-end build, the content management system, integrations, migration, hosting, testing and handover. If one is missing, someone pays for it later. Use this table as a checklist against any proposal, and ask where an item is excluded on purpose.
| Part of the project | What it covers | What to ask the supplier |
|---|---|---|
| Design | Structure, layout, visual style and how pages behave on a phone. | Is design included, or is someone else supplying it? |
| Front-end build | Turning the designs into pages that load quickly and work across devices and browsers. | How will speed be measured, and on which pages? |
| CMS and content structure | Templates and editable blocks so your staff can add pages without breaking the layout. | Who will edit the site, and have they used the editing screen? |
| Integrations | Forms, CRM, accounting, booking and stock systems connected to the site. | Which systems must connect, and who documents each connection? |
| Migration | Moving content and addresses from an old site without losing visitors. | Where is the URL map, and who signs it off before launch? |
| Hosting and deployment | Where the site runs, and how releases and backups are handled. | In whose name is the hosting account? |
| Testing and launch | Cross-device checks, forms tested with real data, a crawl of the staging site. | What is tested, and can I see the staging site? |
| Handover and support | Code, content, credentials, documentation and the terms for fixes afterwards. | What do I receive in writing on the day I pay? |
What should a web development company show you before you hire it?
It should show live websites you can open yourself, name the people who would build yours, let you see a staging site from a current project and explain how its work is tested. A case study PDF describes a website; a live address lets you check one. Test on your own phone, not on the company's demo.
- Live sites, opened on your own phone and laptop. Notice how quickly they load, and whether anything jumps around while they do.
- The page source. Use your browser's view-source option on a live site. If the visible text is in the source, search engines and AI crawlers can read it directly; if the source is nearly empty, the page depends on the visitor's browser to build it, which can make it harder to read.
- The editing screen of a site in its content management system. Ask to see a non-technical person add a page, because that is the job your own staff will be doing.
- A staging site from a current project, and an explanation of how changes are reviewed before they go live.
- The people. Who writes the code, who will you speak to, and are they the people who presented the proposal?
- A reference you can actually speak to, rather than a quotation printed on the company's own site.
- What happens when something breaks: who you contact, what the support terms cover and where they are written down.
Which platform should your website be built on?
Choose the platform from what the site must do and who will edit it, not from what the company prefers to sell. WordPress suits content-led sites edited by staff, Shopify suits straightforward online shops, headless builds suit sites where performance or complexity justifies the extra work, and custom applications suit business rules a site builder cannot hold.
| Platform | Fits when | Watch for |
|---|---|---|
| WordPress | The site is mostly content and your own staff will edit it. WordPress development done well uses a custom theme and few plugins. | Heavy page builders and long plugin lists, which can slow the site and add maintenance. |
| Shopify | A straightforward online shop where the platform's features cover how you sell. Shopify development covers the theme, apps versus custom code, and search. | Requirements that fight the platform, and app costs that grow as you add features. |
| Headless or framework front end | Performance or complexity genuinely justifies a separate front end and CMS. | Extra build and maintenance work for a benefit a well-built conventional site could deliver. |
| Custom application | Staff log in, data entered on one screen changes what another person sees, or pricing and approval rules apply. Web application development is the honest description. | A quote that calls it a website, so the scope is underestimated. |
| Site-builder subscription | A simple, temporary or low-stakes presence. | Limits on structure, speed and integrations, and a site that may not be movable elsewhere. |
What questions should you ask any web development company?
Twelve questions work on any supplier, ours included. A good company answers each plainly and in writing. The ones to worry about change the subject, point to a portfolio instead of answering, or say it is covered in the contract. Ask them before you compare prices, because the answers change what the prices mean.
- “Who owns the code, the domain, the hosting and every account on the day I pay the final invoice?” A good answer is that you do, with the repository transferred.
- “Whose name is the domain registered in right now?” A good answer is yours, on your email, with access you can use without asking permission.
- “Why this platform for this site, and what would change your recommendation?” A good answer ties the choice to what the site must do. WordPress or a custom build and Shopify, WooCommerce or custom show how that reasoning runs.
- “Who writes the code, and will I speak to them?” A good answer names people. Subcontracting is common and not a scandal, but it belongs in the conversation before you sign.
- “Can I see a staging version with my real content before launch?” A good answer is yes, with a review stage before anything goes live.
- “Is the page content in the source, or built in the visitor's browser?” A good answer is clear and can be verified by you in a minute.
- “How will you measure speed, and which pages will you measure?” A good answer names the method and the page types. It does not promise a perfect score.
- “Which plugins and third-party scripts will you add, and who maintains them?” A good answer is short, justified, and says who keeps them updated.
- “If I am replacing an existing site, how do you plan the address map and redirects?” A good answer describes the map being built and signed off before anything moves.
- “What does the quote leave out?” A good answer lists exclusions without being pushed. A quote with no exclusions has not been thought through.
- “What happens after launch, and who fixes, updates and backs up the site?” A good answer separates fixing defects, applying updates and building something new.
- “What would you tell me not to build?” A good answer is specific and costs the company some work. If every idea is a good idea, you are talking to a sales process.
Who should own the code, the domain and the hosting?
You should, once you have paid: the code, the design files, the content, the domain and every account, registered in your name and to your email, with the repository handed over. Anything less leaves you dependent on the company that built the site, and the dependency usually surfaces years later, at the moment you want to leave.
Some patterns to watch for: a site provided on a subscription with a large buyout fee if you ever want to own it; a content management system built in-house that only one company can maintain; a domain registered to the agency; “hosting included” with credentials you are never given. None of these is automatically wrong, and a subscription can suit some businesses, but you should know which arrangement you are signing up to.
A proper handover is a list. The repository with its history, an export of the content, the third-party credentials, the build and deployment notes, the design files and the accounts. Ask for that list at proposal stage and check it against what you receive. What happens after hand-over is its own cost, and what ongoing website maintenance costs is worth reading before you agree support terms.
The point
The repository with its history, an export of the content, the third-party credentials, the build and deployment notes, the design files and the accounts.
Should you use a freelancer, a small agency or a larger company?
A freelancer fits a small, well-defined site; a small agency fits a project that needs design, build and search planned together; a larger company fits a big or regulated programme; and an in-house developer fits a site that changes constantly. Match the route to how much change the site will see after launch.
| Your situation | Likely route | What to check |
|---|---|---|
| A small, defined brochure site that will change rarely | Freelance developer | Cover for illness or holiday, and written handover notes. |
| A new site needing design, build and search planned together | Small agency | Who actually does the work, and whether the people you meet are the people who build. |
| A large, regulated or multi-team programme | Larger company | Whether yours will be a small account, and who your daily contact is. |
| A site central to daily operations that changes constantly | In-house developer or a retained team | Whether there is enough work between projects to justify the role. Freelancer, agency or in-house covers the trade-offs in full. |
| A temporary or low-stakes presence | Site-builder subscription | Whether you can move the site elsewhere later. |
How do you compare web development quotes?
Compare quotes by asking each company to price the same written brief, itemised into parts you can recognise, with assumptions and exclusions stated. A single total cannot be compared with another, and a low total often reflects a narrower scope rather than a better price. The cost drivers are the pages, the integrations, the content work and who maintains it.
What moves a price is fairly consistent: the number and type of page templates, any e-commerce, the integrations with other systems, a migration from an old site, custom functionality, how much content the company must produce rather than receive, and the depth of design. Website pricing in Birmingham shows how those drivers play out for one market, and the same logic applies elsewhere.
A pattern to watch for is a fixed price on an unclear brief, which tends to produce either a padded figure or a dispute later. Ask what happens when the scope changes. A good answer is a written change note with a cost agreed before the work is done, not a surprise on the final invoice.
The point
A pattern to watch for is a fixed price on an unclear brief, which tends to produce either a padded figure or a dispute later.
When is a web development company the wrong choice?
A web development company is the wrong choice when a site-builder subscription would do, when the real problem is the offer, the content or the search visibility rather than the build, or when what you need is business software with user accounts and rules rather than a website. An honest supplier will tell you which.
The dividing line between a website and software is plain. If staff log in to do their jobs on it, if data entered on one screen changes what another person sees, or if the site needs to calculate, approve or remind, you are commissioning an application. That is scoped and priced differently. Bespoke software development is the right description, and how to choose a software development company is the better guide. For online shops with their own demands, ecommerce development is a different brief again.
The opposite mistake is rebuilding a site that only needs fixing. A slow site can often be made fast without a rebuild, and a site that nobody finds has a visibility problem that search engine optimisation addresses and a new build alone does not. Rebuilding to solve the wrong problem is the most expensive way to learn the difference.
The point
A slow site can often be made fast without a rebuild, and a site that nobody finds has a visibility problem that search engine optimisation addresses and a new build alone does not.
What should happen after the website launches?
After launch, someone should be named for hosting, backups, security updates, content changes and fixes, and the arrangement should be in writing. Launch is the start of the site's working life, not the end of the project. Ask what support covers, what it costs to change it and what you receive if you move.
Three things get quietly bundled and are worth separating: fixing something that is broken, keeping the software up to date, and building something new. Each has a different cost and a different owner. A company that cannot say which of the three you are buying has not defined the support.
If you would like a second opinion on a quote, send it to us; you will get an honest read whether or not you hire us, and some of our live work is there to check.
The point
If you would like a second opinion on a quote, send it to us; you will get an honest read whether or not you hire us, and some of our live work is there to check.
Questions people ask about this
How do I choose a web development company?
Ask who owns the code, domain and accounts at the end, which live sites you can test yourself, who will write the code and what the quote leaves out. Then compare two itemised proposals against the same brief. Plain, written answers beat a polished portfolio every time.
What are website development services?
They are the build stage of a website: front-end pages, a content management system, forms and integrations, testing, launch and handover. They differ from design, which decides how the site looks, and maintenance, which keeps it running. The website development services page explains how we describe them.
What is the difference between web design and web development?
Web design decides structure, layout and how a site looks and behaves. Web development builds it into working pages, connects the content management system and integrations, and tests everything. Some companies do both and some only one, so ask whether design is included before you compare quotes.
Should I choose a freelancer or a web development company?
A freelancer suits a small, well-defined site and offers direct contact, but little cover for absence. A company offers several skills and continuity at a higher cost. The right one depends on scope and how often the site will change, so compare both against the same written brief.
What questions should I ask a web development company?
Ask who owns everything on final payment, why this platform, who writes the code, whether you can see a staging site, what the quote excludes and what happens after launch. The twelve questions above work on any supplier. If you only ask three, ask about ownership, exclusions and handover.
Who should own my website's code and domain?
You should, once you have paid. The code, content, domain, hosting and analytics accounts belong in your name and on your email, with the repository handed over. Be cautious of subscriptions with buyout fees or content management systems only one company can maintain.
Does a web development company need to be local?
Less than most buyers assume. Development runs through video calls, a staging site and shared documents. What matters more is who owns the code, whether the company shows live work, and how handover works. A local postcode is not evidence of quality; an in-person first meeting is a preference rather than a requirement.
What should a web development quote include?
It should itemise design, the front-end build, the content management system, integrations, migration, hosting, testing and handover, and state its assumptions and exclusions. It should also say who owns each piece at the end. A single total with no breakdown cannot be compared with anyone else's.
The work behind this article
Read next
How Much Does a Website Cost in the UK?
Template sites, freelancers, agencies and full custom builds sit at very different points on the same scale. Here is the band for each, the seven factors that move the figure, and the running costs most quotes leave out.
WordPress or a Custom Build? How to Decide
Eight out of ten business websites are better served by a properly built WordPress theme than by a framework rebuild. The comparison table, the two criticisms that are really criticisms of bad builds, and the cases where custom genuinely wins.
Freelancer, Agency or In-House? Choosing a Development Partner
We are an agency, and we still recommend a freelancer in several situations. UK market day rates for all three routes, the hidden costs of hiring, and the six questions worth asking whichever you choose.