A five-page marketing site and a web application with accounts, payments and tools for staff are not the same purchase. Search results still fold both into one question, which is why a figure copied from a round-up rarely survives contact with a real brief. What matters is the job the site has to do, and which parts of that job belong in the first build rather than in the years after it goes live.
The budget moves with the work. Scope, design, functionality, integrations, content, search foundations, technology, hosting, security, maintenance and room to grow later all change the figure. Leave one of them out at the start and it usually returns as a second project, often at a higher cost, because the first build was not shaped to accept it.
How much does a business website cost?
There is no honest single price for a business website in the UK. Surveys that publish an average tend to mix brochure sites, shops and software, then present the blend as if it were a quote. That number cannot tell a firm what to set aside. A better start is the type of project, and the work that usually dominates the cost. Each line below gives the project type, its usual complexity and what drives most of the cost.
- Small business website. Complexity is low. Cost is driven by the number of pages, the design, and a content system the team can edit without calling a developer for every sentence.
- Growth-focused website. Complexity is medium. Search structure, the quality of the experience and a small set of integrations start to matter as much as the page count.
- E-commerce website. Complexity is medium to high. The catalogue, payments, tax and delivery rules, and the other systems the shop must talk to, usually outweigh the visual design.
- Web application. Complexity is high. Accounts, permissions, business rules and APIs are software. The public pages are the front of that work, not the whole of it.
- Bespoke platform. Complexity is very high. The cost sits in the architecture, the automation between systems, and the ability to keep performing as traffic and features increase.
These are ways of thinking about a project, not a menu with fixed prices, and many briefs sit between two of them. A local service firm with a quote form is not an online shop. A shop with a short catalogue is not a platform. A useful proposal names the category, then lists what is included and what is deliberately left out.
What actually determines website development cost?
Two proposals can both say "a business website" and describe different amounts of work. The gap is usually in the items below, not in a day rate written on its own.
Design and user experience
A template starts from a layout that already exists. Someone adapts colour, type and sections, and the saving is real when the business fits that shape. A bespoke experience is designed around how this customer decides: what they need to see first, which proof matters, and where the enquiry or the purchase happens. That takes research, wireframes and more rounds of design. It is worth paying for when a theme would force the business into a layout that fights the sale. It is waste when a clear, well-edited template would have done the job.
UI and UX design is this work, not a coat of paint applied after the pages exist. Decisions made here change how many components and states the build has to support.
Number and complexity of pages
Ten simple pages are not the same project as ten interactive ones. A page of text, a heading and a photograph is mostly content and layout. A page with a filter, a calculator, a map or a form that changes with earlier answers is interface logic, and it has to be tested on a phone as well as a large screen. Counting pages without describing what each page does is how a small quote becomes a dispute halfway through.
Content management
Someone has to change the words after launch. A straightforward editor, with a small set of page types, is cheaper to set up and cheaper to live with. A heavily modelled system, with many content types, roles and approval steps, is a product in its own right. The expensive mistake is the middle ground: a system that looks flexible in the proposal and is awkward for the person who actually publishes the service pages.
Custom functionality
This is where a marketing site becomes software. Typical examples include a booking flow, a customer portal, a dashboard for staff, a pricing calculator, multi-step forms, and automation that files an enquiry without retyping. Each one needs rules for the unhappy paths: a failed payment, a double booking, an empty field, a user who must not see another customer's data. That edge-case work is a large share of the cost, and it is often missing from a line that only says "add bookings".
When those features are the product, the project is closer to software development than to a brochure, and it should be estimated that way.
Integrations
Connecting the site to a system the business already uses is rarely a switch. A CRM, a payment provider, accounting software, a marketing platform or another API each has its own sign-in, data shape and ways of failing. The cost depends on whether that system has a documented interface, whether the data is clean, and who is responsible when a field does not match. A task described as "sync the contacts" can hide a long mapping exercise if the CRM and the website disagree about what a customer is.
Search foundations
Search belongs in the build, not in a tidy-up after the design is signed off. The information architecture decides which services have their own URL. The technical work covers metadata, headings, canonical URLs, a sitemap and pages that can be crawled. Internal links should follow the way a customer moves, not a list of phrases. Performance belongs here too: a page that is slow on a phone is a weaker page for the visitor, and a weaker page for search.
Ongoing SEO and digital marketing is a separate commitment: new pages, measurement, and the work of earning visibility over time. Building without the foundations means paying later to change URLs, templates and the way content is structured. That is slower, and it puts rankings at risk if the site is already being found.
Performance and scalability
A site that is comfortable at a few hundred visits a month can struggle once the catalogue grows, the templates collect third-party scripts, or a campaign sends many people to one landing page. Architecture and hosting are how you avoid rebuilding for that reason alone. Preparing a page on the server or ahead of time, serving images at the size they are displayed, and not shipping unused JavaScript are build decisions. They cost less at the start than as a retrofit. Measuring that properly is a different question from the quote, and it is set out in what UK businesses should measure with Core Web Vitals.
Website development cost versus the cost of ownership
The invoice for the build is the visible part of the investment. After launch the site still has to stay online, stay secure and stay accurate.
- Hosting and the domain. The domain is a small annual fee. Hosting varies with traffic, whether you need a preview environment, and whether someone is managing releases.
- Security. Updates to the framework, the editor and any plugins, plus a sensible approach to accounts and to forms that accept public input.
- Maintenance. Fixes, small content changes, and a person to call when something breaks.
- Backups and monitoring. A backup nobody has ever restored is only a hope. Monitoring is how you hear about downtime before a customer does.
- Content and search. New services, expired offers and copy that is no longer true are a cost of trading, not an optional extra.
- Further development. The feature deliberately left out of the first version, planned as a later phase rather than discovered as an emergency.
Website maintenance is the practical name for most of that list. A proposal that ends at launch, with no view of the following year, is only half a budget. Maintenance and support should be scoped with the same plainness as the build: what is included each month, and what would be quoted on its own.
Cheap website or cost-effective website
The lowest quote can be the right one when the scope really is small and the site will not be asked to do more. It is a poor saving when the low price comes from leaving out work the business will need. The bill then arrives later, and it is larger because the first version is in the way.
That later bill usually takes a familiar shape: technical debt, slow pages, weak security, an editor that staff avoid, a structure that cannot take a new service, thin search foundations, and a replacement project sooner than anyone planned. A redesign or a rebuild is a reasonable project when the business has changed. It is an expensive outcome when the original site was never fit for the job it was sold to do.
This is not an argument against templates, or against a modest budget. A template is a sound choice for a simple marketing site with a clear offer. It becomes costly when the business needs bookings, a catalogue, more than one language, or a layout the theme cannot support, and the conversation has to start again. Cost-effective means the spend matches the job, including the next two or three years. It does not mean the first number on the page is the smallest.
How to choose the right website investment for your business
Start from the work the site has to do, then set the budget. The other way round produces a site that fits a number and misses the brief. These are the questions worth answering before anyone prices the work.
- What is the website supposed to achieve? Enquiries, bookings, online sales, recruitment, or a place for existing customers to sign in, are different products.
- Who will use it? Customers on a phone, staff at a desk, or both, lead to different designs.
- How will leads or sales actually happen? A contact form, a phone number, a checkout and a request for a quote are not interchangeable.
- Which other systems must it connect to, on the first day and later?
- Who will change the content, and how often?
- Which searches should the site be able to support? Name the services, and the places you genuinely cover. Do not publish pages for cities you do not serve.
- What has to be true in two or three years? A second language, a customer area, a larger catalogue or heavier advertising all favour a foundation that can accept them.
If those answers are still vague, the useful first spend is often a short discovery piece that produces a scope, not a discounted build of a site nobody has defined.
How Web Works Rise approaches website development
Web development here is scoped as a business website: pages a customer can find, a design that matches the way they decide, and a codebase the team can keep. Public sites are built with Next.js, React and TypeScript, because a company site has to be readable by people and by search tools, and it has to stay maintainable after launch. The framework does not set the price. The scope does.
Where the brief needs it, that work sits beside interface design, search, custom software, cloud hosting and, only when a specific feature needs it, practical AI. The team is UK-led, with an office in Birmingham and a development hub in Tunisia that adds delivery capacity for UK projects. There is more on how the team works on the about page.
A sensible next step is a conversation about the job the site has to do, not a request for a number with no brief. If you already have a site and are unsure whether to improve it or replace it, that is a different decision. Either way, contact the team with the outcome you need and any systems the site has to join.