Start by defining the website's job
This guide is for businesses commissioning a website, especially a first site or a rebuild. Before comparing suppliers, record the primary goal: enquiries, bookings, service information or sales support. The conversation can then focus on an outcome you can evaluate.
Prepare a short audience description, page list, required features and target date. Send the same brief to each supplier. If they receive different information, price differences may reflect different scopes rather than quality or development cost.
Check live projects and the supplier's actual role
Look beyond appearance when reviewing a portfolio. Open several projects on your phone and check the clarity of the offer, navigation and contact details. Ask which work the supplier handled: design, development, content, deployment or maintenance. A screenshot alone does not explain their involvement.
Experience in your industry can help, but experience with a comparable task matters too. A lead-generation website has different requirements from a customer dashboard or a large portal. A useful case study explains the problem, solution and limits without promising the same result for every business.
Compare equivalent scopes rather than the final price alone
Ask for the quote to describe a concrete deliverable. Page count is only the beginning: unique layouts, languages, copy, forms and integrations also matter. Establish whether tax is included and which third-party services are billed separately.
Clarify revision rounds and how changes outside the scope are priced. The proposal should make the cost of launching the agreed version understandable rather than leave most essential elements undecided.
- pages, features and language versions
- responsibility for copy, photography and translation
- mobile design and form testing
- domain, hosting and any paid licences
- revisions, deployment and the support period
Agree what you receive at handover
Before work starts, agree whose accounts will hold the domain, hosting and analytics tools. Ask about administrative access, content editing, source-code handover and the terms for using graphics, fonts and other materials. Record the answers in the proposal or agreement.
Discuss what would be needed to change the developer or hosting provider later. A website's cost includes the ability to maintain and develop it after launch. Ask for a clear list of accounts and files to be handed over, plus a short operating guide.
Ask about specific SEO work and enquiry measurement
“SEO included” needs an explanation. Ask about page titles and descriptions, headings, URLs, internal links, the sitemap and indexability. If an existing website is being replaced, discuss old URLs and any required redirects.
Agree which outcomes will be checked: calls, submitted enquiries or other meaningful actions. Indexing, search visibility and customers are different measures. A practical SEO plan covers useful content and measurement; a promise of first place alone does not explain the work you will receive.
Check communication and whether the timeline is realistic
Ask who manages the project, how often you will see progress and how feedback is collected. A useful schedule includes content, design, development, testing and launch, with someone responsible for approving each stage.
Delivery also depends on your materials and decisions. Agree what happens if copy arrives late or the scope changes. A clear explanation of the impact on price and launch date is more useful than a short deadline without conditions.
Agree acceptance checks and post-launch support
Agree a checklist before launch. Visit the site on desktop and mobile, review the offer, check links, and test the enquiry form through to message delivery. If analytics is included, also check the agreed events and consent settings.
After launch, it should be clear who receives bug reports and what support includes. Maintenance, new features and defect corrections may have different terms. Ask about backups, updates, service renewal costs and further development.
Seven questions to ask before choosing a developer
Collect the answers in one document and compare them against your business priorities. Not every website needs a complex management system or integrations. A supplier should be able to explain what is needed now and what can follow later.
- Which pages and features are included in the quoted price?
- Who prepares the materials, and how many revision rounds are included?
- Which live project best demonstrates experience with my task?
- What does SEO include, and how will meaningful user actions be measured?
- Which accounts, files and instructions will I receive at handover?
- How are the schedule and stage approvals organised?
- Which costs and support arrangements remain after launch?