Notes

Pricing a website project without the guesswork.

What actually shapes the cost of a business website, and how to budget for one without surprises halfway through.

Atanas Kyurkchiev
14 Oct 2026 · 5 min read

Photo by Kindel Media on Pexels

Most small businesses ask 'how much does a website cost?' and get answers that range from £500 to £50,000. That spread exists because the question is like asking what a vehicle costs. A van, a car and a lorry all get you from A to B, but the price depends entirely on what you need to carry and how far you are going.

Here is what actually shapes the cost of a business website, and how to budget for one without discovering halfway through that you are paying for things you did not know you needed.

What you are really paying for

A website price breaks down into a few parts: design, build, content, any integrations or custom features, and then hosting and maintenance once it is live.

Design means the look, layout and user journey. A template theme costs less because someone else made those decisions. A bespoke design costs more because every screen is drawn for your business, your customers and your goals.

Build is the code that makes the design work. A brochure site with five pages and a contact form takes less time than a shop with hundreds of products, discount codes, stock tracking and courier integrations.

Content is often forgotten in early quotes. If you are writing your own copy and supplying photography, the developer's job is faster. If they are writing, editing, shooting or sourcing images, that time gets billed.

Get a quote that lists design, build, content and integrations separately, so you can see where the cost sits and make trade-offs that suit your budget.

Features that move the price

Some features sound small but add days of work. Others sound complicated but are solved problems that take an hour to wire up.

Taking payments online can be quick if you use Stripe's hosted checkout, where the customer is sent to Stripe's own page to pay. It takes longer if you want the payment form embedded in your site, and longer still if the price depends on options the customer picks, or if you need to split payments between suppliers.

When we built the shop for Surplush, a Norwich buyers club selling wholesale supplies, card checkout was moved to an AWS Lambda so that payment was not held up while invoices and supplier emails were sent in the background. That kind of behind-the-scenes work does not show on the page, but it stops customers waiting and stops you losing sales.

User accounts add cost because you are now storing personal data, handling password resets, and probably building a dashboard where customers can see their past orders or bookings. If those accounts also need different permission levels (a customer, an admin, a team member who can only see some things), the build time grows again.

Integrations with other tools (your CRM, your booking system, your accounting software) can be straightforward if the other service has a well-documented API. They can also be a mess if the API is flaky, rate-limited or missing the one thing you need, and the developer has to build a workaround.

Ongoing costs after launch

The build cost is not the only cost. Once the site is live, you are paying for hosting, a domain name, SSL certificate, and any third-party services the site depends on (email sending, payment processing, analytics).

Hosting for a simple brochure site might cost £10 a month. A site with a lot of traffic, a database, background jobs and image processing might cost £100 or more. The difference is not about hosting companies overcharging, it is about what the site is doing and how much server resource that needs.

Maintenance means keeping software up to date, fixing things that break when a browser or a payment provider changes something, and making small edits when your prices or services change. Some businesses handle that themselves if the site has a simple admin. Others put a developer on a retainer for a few hours a month.

A fixed monthly retainer is easier to budget for than a surprise bill every time something needs changing.

Care plans and retainers

We offer ongoing care for clients who want someone else to handle updates, backups, security patches and small changes. It is a fixed monthly cost, and it means the site does not go stale or unpatched for months until something breaks. For NR Surveyors, a RICS regulated firm in Norwich, we have handled price changes and page updates since the site launched, so the firm does not need to brief a developer every time their fees go up.

How to budget without regret

Start by listing what the site absolutely must do on day one, and what can wait. A shop needs a checkout, but it does not need gift cards, loyalty points and a trade account system in version one. You can launch with the core and add features later as the business grows and you know what customers actually ask for.

Key takeaways

  • List must-have features separately from nice-to-haves, so you can launch sooner and add later
  • Ask for a quote broken down by design, build, content and features, not one lump sum
  • Budget for hosting, maintenance and small changes after launch, not just the build cost

If a quote comes in higher than you expected, ask which features are pushing the cost up. You might find that one thing you mentioned in passing (customer accounts, or a booking system, or a product configurator) is responsible for half the price, and you can defer it or simplify it.

Fixed price or time and materials

Some agencies quote a fixed price for the whole project. Others charge by the hour or day. Fixed pricing feels safer, but it only works if the scope is nailed down in detail before the contract is signed. If you keep adding features or changing your mind about how something should work, a fixed-price project either blows the budget or the agency starts saying no to changes.

Time and materials gives you more flexibility to adjust as you go, but you need to trust that the developer is not padding hours. A middle ground is a fixed price for the agreed scope, with a clear hourly rate for anything added later.

The worst outcome is a project that costs more than you expected and still does not do what you need. That happens when the brief is vague, the quote does not list what is included, and both sides assume the other will handle the gap. A detailed quote and a proper kick-off meeting fix that before any code is written.

More notes