Website cost UK searches often lead to a single number, but a useful budget depends on what the website must do, what is already prepared and who owns the work after launch. A focused service site and an ecommerce store may use similar visual components while requiring very different product data, payments, integrations, testing and support.
This guide separates those decisions so you can create a realistic brief, compare like with like and avoid paying twice for omitted work. If you want to see the available approach before preparing the details, start with Alchemist Media’s web design service.
Website cost UK: practical starting routes
There is no responsible fixed price for every business website. A useful first step is to choose the closest scope route, then confirm what is included for your specific business. Alchemist Media currently publishes two clear setup starting points:
- Standard site setup: £250. This is the live starting price shown on the Site & Presence standard setup page. Use it as the initial route for a focused business presence, then confirm pages, content, features and responsibilities before purchase.
- Ecommerce setup: £500. This is the live starting price shown on the Site & Presence ecommerce setup page. A store normally needs additional decisions around products, payments, delivery, tax, transactional messages and order handling.
- Custom or integrated work: scoped separately. Membership areas, booking logic, legacy migrations, multilingual content, complex data flows or unusual third-party systems need a written requirements review before a reliable price can be given.
The starting route is not the whole budget. Ask whether copywriting, photography, product entry, legal review, premium software, domain services, hosting, maintenance and future changes are included or separate. A lower setup price can still create a higher total cost if essential work has been left to the buyer without being made clear.
Why two similar-looking websites can cost differently
Page count is only one part of scope. A five-page brochure site with approved copy and a simple contact route can be straightforward. Another five-page site may need workshops, audience research, custom service journeys, a location finder, CRM handover, multilingual content and migration from an old platform. The second project contains more decisions, dependencies and testing even if both finish with five public pages.
Cost also rises when information is incomplete. If service descriptions, images, prices, policies and calls to action are still being decided during the build, the team may need to revise layouts repeatedly. Content readiness is therefore a commercial issue, not an administrative detail. Agree who supplies each asset, its format, its approval date and what happens when it is late.
Integrations should be named precisely. “Connect the CRM” is not a specification. State which form fields move, where they go, what happens when a duplicate is found, who receives an alert and how the team recovers from a failed connection. The same discipline applies to booking tools, payment providers, email platforms, analytics, stock systems and customer support.
Separate discovery, design and build
A clear proposal distinguishes the thinking from the production. Discovery establishes the audience, business goal, priority journeys, evidence, constraints and measures of success. Design turns those decisions into page structures, visual hierarchy, components and responsive behaviour. Build implements the approved system, connects services and prepares it for testing and launch.
When these stages are compressed into one vague line item, buyers cannot see where decisions happen or how changes affect cost. Ask for the number of page templates rather than only the number of pages. Ten service pages may use one reusable template; a homepage, comparison page, configurator, account dashboard and checkout may each require different behaviour.
Request an approval point after discovery and another after key page designs. Confirm how many revision rounds are included and what counts as a new requirement. This is not about making the relationship rigid. It gives both sides a shared record and prevents late surprises from being treated as if they were always part of the original brief.
Budget for content, migration and SEO foundations
A website cannot communicate clearly without usable content. Decide whether your team will provide finished copy and images or whether the supplier will research, write, edit and optimise them. Product catalogues add further work: titles, descriptions, attributes, prices, variants, image preparation, categories, shipping data and policy pages all need consistent information.
If an existing site is being replaced, migration needs its own checklist. Record every valuable URL, decide which pages will be retained, map changed URLs to appropriate redirects and preserve important metadata. Test links, forms and tracking after launch. Removing or changing established URLs without a migration plan can waste previous search and link-building work.
SEO foundations should cover crawlable navigation, descriptive page titles, one clear main heading, useful internal links, canonical signals, image alternatives and a sitemap. They cannot secure rankings by themselves. They make the site understandable and reduce avoidable technical obstacles. Agree whether keyword research, content planning and ongoing optimisation are part of the project or separate services.
Include performance, accessibility and privacy in scope
Quality requirements affect time and cost because they must be designed, built and tested. Google’s Core Web Vitals guidance describes metrics for loading performance, responsiveness and visual stability. Ask how image sizing, fonts, scripts, caching and third-party tools will be handled, and which pages and devices will be tested.
Accessibility is also a planning requirement. The GOV.UK accessibility introduction explains that services should work for disabled people and with assistive technologies. Your brief can include keyboard use, meaningful labels, visible focus, colour contrast, alternative text, error messages, zoom and responsive layouts. Specialist auditing may be separate, so ask what level of review is included.
Websites that collect enquiries, accounts, orders or analytics data also need privacy decisions. The Information Commissioner’s Office says in its data protection by design guidance that privacy should be considered from the design phase and throughout the lifecycle. Define what personal information is collected, why it is needed, where it goes, who can access it and how long it is kept. Legal advice and policy drafting should be identified separately where required.
Understand ecommerce cost before choosing a package
An ecommerce website is not simply a brochure site with a payment button. The quote should state how products, categories, variants, tax, delivery, discounts, stock, customer emails, refunds and order administration will work. International selling can add currency, customs, shipping and policy requirements. Subscription products, marketplaces and personalised products introduce further rules.
Count the catalogue work. A store with ten simple products differs from one with hundreds of variants, inconsistent supplier images and incomplete weights. Confirm whether product data will be imported, entered manually or supplied in a validated spreadsheet. Decide how errors will be corrected and who checks the final catalogue.
Use the live ecommerce setup route as a starting point, then list every operational requirement before relying on the displayed price. A concise requirements call can be cheaper than discovering after launch that delivery rules or product options were never included.
Plan ongoing website costs after launch
Launch is the start of ownership. Separate one-off setup from recurring and occasional work. Recurring costs may include hosting, premium software licences, domain renewal, backups, security monitoring, updates, uptime checks and support. Occasional costs may include new landing pages, product uploads, photography, copy changes, integration work and larger redesigns.
Ask who is responsible for software updates, backups and recovery. A statement that backups exist is not enough; clarify frequency, retention, storage location and who tests restoration. Confirm response times and what counts as an emergency. If the site generates leads or sales, decide who monitors forms, checkout behaviour, analytics and search visibility.
Create a twelve-month ownership budget rather than comparing launch totals alone. Include internal staff time as well as supplier fees. A site that is simple for the team to update may be more valuable than a cheaper build that requires paid help for every small change.
How to compare website quotes fairly
Send the same brief to every supplier. It should contain the business goal, audiences, required journeys, page templates, content status, integrations, ecommerce rules, accessibility expectations, migration needs, launch date and ongoing support requirements. Then compare each proposal line by line.
- Check exactly what will be delivered and what the client must supply.
- Confirm the platform, licences, hosting, ownership and access arrangements.
- Identify assumptions, exclusions, dependencies and revision limits.
- Ask how mobile layouts, browsers, forms, payments and integrations will be tested.
- Confirm launch, rollback, training, warranty and post-launch support.
- Compare the first-year total, not only the setup fee.
Be cautious with both extremes. A very low quote may omit strategy, content, testing or support. A high quote is not automatically better unless the additional work is visible and relevant. The strongest proposal makes responsibilities, risks and acceptance criteria easy to understand.
Prepare a useful website budget brief
Write one page before requesting a quote. State what the site must help visitors do, the actions that matter to the business and the evidence already available. List your essential launch requirements separately from later improvements. This lets the supplier propose a focused first release without quietly discarding important needs.
Attach current URLs, brand assets, content inventory, product data and integration details. Name the people who approve copy, design and technical decisions. Include a realistic internal review period. If the deadline is tied to an event or campaign, explain that dependency rather than presenting the date without context.
If you want a direct recommendation, use the Alchemist Media contact page and share the brief. The useful next step is not an instant universal price; it is confirmation of the right route, included work and the decisions needed for a reliable scope.
Sources
- Google Search Central: Understanding Core Web Vitals and Google search results
- Information Commissioner’s Office: Data protection by design and by default
- GOV.UK Service Manual: Making your service accessible
Frequently asked questions
How much does a small business website cost in the UK?
The cost depends on scope rather than business size alone. Alchemist Media currently lists a standard setup at £250, but content, custom design, integrations, migration, licences and ongoing support may be separate. Request a written scope and compare the first-year total.
Why does an ecommerce website cost more?
Ecommerce adds product data, payments, delivery, tax, customer messages, order administration and more testing. Variants, international selling, subscriptions and system integrations can add further work. Alchemist Media’s current ecommerce setup route starts at £500, subject to the live scope.
What should a website quote include?
It should identify discovery, page templates, design, build, content responsibilities, integrations, testing, accessibility, privacy, migration, launch, ownership, licences and post-launch support. It should also state assumptions, exclusions, revision limits and recurring costs.
Recent Comments