How Much to Charge for a Web Development Project in 2026

What a web development quote needs to include

"Website build — £2,500" tells a client almost nothing about what they're getting. Cover these ten things and the quote reads as a scoped project with a price attached, not a number guessed at over a phone call:

1. 1Your business details and, if VAT-registered, your VAT number.
2. 2The client's business name and a one-line description of the deliverable — "5-page brochure site with a contact form and blog for a joinery business", not just "a website".
3. 3Each deliverable listed individually — design, build, CMS setup, and each integration (payments, bookings, email signup) — not one lump "website" figure.
4. 4Page count and site structure stated explicitly, so "can you just add one more page" is visibly a change of scope, not a free extra.
5. 5Number of design revision rounds included, and the hourly rate for anything beyond it.
6. 6Hosting, domain and ongoing care — whether you're setting it up, who pays the renewal, and what a monthly care plan covers versus the one-off build fee.
7. 7Who supplies the content — copy, photos, product data — and what you charge to source or write it if they don't.
8. 8A copyright and IP ownership clause stating plainly that the finished code and design transfer to the client on final payment — UK law doesn't do this automatically (see the FAQ below).
9. 9The accessibility standard you're building to, even a baseline WCAG 2.1 AA pass (alt text, colour contrast, keyboard navigation), so it's not assumed and then missing.
10. 10Payment schedule and the post-launch support window — e.g. 30 days of bug fixes included, then billed hourly after that.

Fixed fee, day rate, hourly or retainer — which to use

Which pricing model fits depends on how well the work can be scoped before you start:

• Fixed project fee — the default for a scoped build with a defined page count and feature list. The client knows the number before you start, and you're not penalised for working efficiently.
• Day rate — best for work that genuinely can't be scoped upfront: an open-ended rebuild, ongoing feature development, or working inside someone else's half-finished codebase.
• Hourly — reserved for small, unpredictable jobs: bug fixes, one-off tweaks, or "can you just also..." requests that land after launch.
• Retainer / care plan — a monthly fee for hosting management, security updates, backups and small content changes once the site is live. It's the recurring-revenue layer most freelance web developers under-price or skip entirely, even though it's the easiest ongoing income a finished build can generate.

2026 UK pricing benchmarks

• Day rate: junior £240–£360, mid-level £350–£450, senior £450–£550+, with specialist senior rates through agencies reaching £700–£900 in London.
• Hourly: roughly £25–£45 junior, £45–£80 mid-level, £80–£130+ senior.
• Basic template-based brochure site (3–5 pages): £500–£1,500.
• Custom-themed multi-page site with a proper CMS: £2,000–£5,000.
• Freelancer-built e-commerce store (WooCommerce or similar): £2,000–£5,000, rising to £12,000–£40,000+ for fully custom agency builds.
• Ongoing care plan: £25–£50/month for basic updates and backups, £100–£500/month for more active management — typically £500–£3,000 a year in total.

The copyright rule most web developers give away for free

Almost every freelance web developer assumes that once a client has paid the final invoice, the client automatically owns everything — the code, the design, all of it. Under UK copyright law, that's not how it works. When you create a work under a "contract for services" (which covers almost all freelance and contractor arrangements), you are the first legal owner of the copyright in what you create, whether or not you've been paid. Gov.uk's own guidance puts it plainly: "the first legal owner of copyright is the person or organisation that created the work and not you the commissioner, unless you otherwise agree it in writing."

In practice this rarely causes a dispute, because most developers hand over the code and walk away without a second thought — but it means the legal basis for the client's ownership is whatever your contract or quote actually says, not an assumption either side is making. Put the transfer in writing, tied explicitly to final payment: "full ownership of the delivered code and design transfers to the client on receipt of the final invoice." Be equally clear about what doesn't transfer — stock photography, premium fonts, licensed plugins and third-party themes are usually licensed to the client for use, not owned outright, and your own reusable code libraries, boilerplate and internal tooling stay yours unless you say otherwise.

Does a small-business website need to be accessible by law?

The Equality Act 2010 places a duty on service providers — a category that includes websites — to make reasonable adjustments so disabled people aren't excluded, and that duty applies to private businesses, not just the public sector. Public sector bodies have the harder legal standard: the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 specifically mandate WCAG 2.1 Level AA. A private small business can point to "disproportionate burden" as a defence against full compliance if resources are genuinely limited, but that's not the same as having no obligation at all — the basics (alt text on images, sufficient colour contrast, a sensible heading structure) are expected regardless of business size.

No UK court case against a small business has succeeded to date, but the risk isn't theoretical: RNIB's action against travel company bmibaby, after a blind customer couldn't book a flight through its website, was settled out of court. For a web developer, the economics are straightforward — building a WCAG 2.1 AA baseline in from the start (alt text as you build, a colour-contrast check before handover, keyboard- navigable forms) costs very little extra time. Retrofitting it after a client gets a complaint, or after you've moved on to the next job, costs a lot more. Naming it as its own line on the quote turns an easy-to-skip detail into a visible part of what the client is paying for.

A worked example

A joinery business needs a 5-page brochure site — home, about, services, a gallery and a contact page — on a proper CMS rather than a locked-down template builder. Priced as separate lines rather than one round "website build" figure:

£2,750 for a five-page custom-themed CMS build with an accessibility baseline and copyright transfer built in — a clearer number for the client to say yes to than "£2,000, plus extra if it needs more work," and a clearer number for you to defend against a £900 template-site quote from a competitor. Ownership of the finished code and design transfers to the client on receipt of final payment; 50% deposit due at booking, balance due on handover, hosting and a monthly care plan quoted separately.

Five details that get web development quotes accepted faster

• State the page count, not just "a website". "5 pages, 1 contact form, 1 blog template" reads as a defined scope a client can say yes to on the spot — an open-ended "website build" invites a client to assume it covers whatever they think of next.
• Put the copyright line in the quote, not just the contract. Seeing "full ownership of the code and design transfers to you on final payment" up front builds more trust than leaving it to a terms-and-conditions document nobody reads until something goes wrong.
• Separate the build fee from the ongoing care plan. A client comparing your £2,750 quote to a £900 template-site quote can see exactly why — and isn't blindsided by a £35/month hosting-and-maintenance line appearing six weeks after launch.
• Name the accessibility basics you're including. "WCAG 2.1 AA baseline pass included" reads as competence most competitors never mention on a quote, for very little extra build time if it's planned in from the start.
• Put a 50% deposit on anything past a single landing page. It protects the design and research time already spent if a client goes quiet mid-build, and it's a normal, expected ask once it's a line on the quote rather than an awkward phone call later.

The fastest way to do all of this

A single landing page is easy enough to quote over email. A multi-page build that mixes design, a CMS, integrations, an accessibility pass and a copyright clause — and needs to look properly itemised so the client trusts the number — is exactly where a vague back-and-forth costs web developers real time, and sometimes the booking itself.

This is what QuoteRocket is for. Describe the job in plain English — "5-page CMS site, contact form, WCAG 2.1 AA baseline, code and design ownership on final payment, 50% deposit" — and it turns that into a branded, itemised PDF quote in under a minute. Your client accepts it with one tap on their phone, and an accepted quote becomes an invoice in one click — with paid and unpaid status tracked automatically, so a care-plan retainer you're invoicing monthly doesn't get lost in your inbox.

Whichever way you produce the quote, the principle holds: price the deliverables individually, name the pricing model you're using, put the copyright transfer in writing rather than assuming it — and remember that, legally, the code is still yours until you say otherwise.

Frequently asked questions

More reading