A bespoke website has no single UK price. Its cost depends on what needs to be understood, created, connected and tested before launch, and what it will take to run afterwards. A useful budget starts with that work. Page count and a desired launch date will not tell an agency enough to price it responsibly.

If the same brief produces three very different quotes, resist the urge to label one cheap and another expensive. “Bespoke website” might describe a custom visual design on a familiar setup, a structured publishing system or an application with substantial integrations. First establish whether you are comparing the same job.

What sits behind the fee

Discovery has a practical purpose: resolving questions that would otherwise surface during design or development. A clear offer and well-documented requirements create a different starting point from a merger with overlapping services and competing stakeholders. Audience interviews, content auditing and technical investigation may all be relevant. Ask what decisions “Strategy” will produce. Deleting the line from a proposal does not delete the questions.

Content is another reason page counts can mislead. Fifty pages using a few established templates may be simpler than ten with different layouts and complex interactions. Allow for writing and asset production, including photography, film, illustration and translation where needed, as well as migration. “Content supplied by client” needs a definition: final approved material is a different starting point from copy that still needs rewriting. Specify who creates, checks, uploads and signs it off. Your team’s time belongs in the budget too.

Design and development then have to make the proposed direction work across real content, mobile layouts, forms, navigation and interaction states. Reusable components can help editors publish consistently, but unlimited layout freedom brings extra design, build and testing work. It may also make inconsistent pages easier to create. Agree which variations the site needs before paying for flexibility nobody has a use for.

A “contact form” can conceal a much bigger task

A form that sends an email is one requirement. A process that checks data, assigns a territory and creates a CRM record is another. Authentication, search, commerce and external data feeds introduce further dependencies. The proposal should identify who supplies access, whether documentation exists and what users see when a connected service fails.
Those details affect investigation, implementation and testing. So do the conditions around delivery: a fixed launch event, a large approval group, limited access to a legacy platform or a specialist review that depends on someone else’s availability. Project management and quality assurance need a realistic allowance. Their absence from a quote is not evidence that the project can do without them.

At Framework, we believe buyers should be able to see where the money goes and which choices would change the fee. A credible proposal makes its assumptions visible and gives responsibilities an owner, including the work that is easy to overlook.

An illustrative £30,000 budget

The following £30,000 example is an invented budget model to show the arithmetic. It is not a market average, Framework price guide or quotation, and excludes VAT and ongoing costs.
Discovery and planning: £4,000. Content preparation: £5,000. UX and visual design: £5,000. Development: £10,000. Migration and testing: £3,000. Delivery management and training: £3,000.
The useful discussion is what each allowance contains. Supplying approved copy may change the content allocation. An integration requiring substantial investigation could make the development allowance inadequate. The figures illustrate a way to examine a budget; they cannot substitute for a real scope.

Match the price to what is known

An early range should explain the assumptions behind its lower and upper ends. A fixed fee becomes easier to assess once deliverables, review rounds, content responsibilities and technical dependencies are defined. It buys agreed work, rather than unlimited change.
Where a major dependency remains untested, a paid definition phase or staged pricing may be more appropriate. Establish what that phase will deliver and whether it gives you enough information to make the next decision. For remaining uncertainties, such as poor legacy data, undocumented integrations or content that may need rewriting, agree how they will be investigated or funded.

Keep contingency separate from agreed scope and name who can authorise its use. It should reflect identifiable risks, rather than conceal an arbitrary margin. Unknown work is not free simply because nobody has priced it yet.

Unknown work is not free simply because nobody has priced it yet.

Compare ownership costs as well as launch costs

Ask for the first-year cost alongside the build fee and a view of recurring expenditure. Hosting, licences, maintenance, support and ongoing content work may be charged separately. Additional development is a further commitment; it is not automatically included in maintenance. Establish the allowance for each service and what happens when demand exceeds it.

The commercial details should be equally clear. Confirm the fee basis, payment milestones, expenses and whether VAT is included or excluded. You should be able to understand the planned cash commitments without decoding the proposal.

When reviewing competing quotes, put their deliverables, team involvement, content assumptions, integrations, testing and support side by side. Ask each agency to explain meaningful differences. A less expensive approach can be sensible if it meets the need with less scope.

Reduce the scope with care

If the budget will not cover the proposed programme, simplify it. Remove unnecessary templates, phase secondary functionality or prepare better source content. Keep the checks the agreed launch requires, including accessibility, migration and testing. A smaller, complete release is a more coherent purchase than a larger site with unfinished essentials.

Sharing a working budget range helps agencies make those choices with you. Say whether it covers the website alone or also brand, content and ongoing services, then ask what would be delivered and what would wait. Before agreeing the fee, describe what must be true on launch day: the journeys that work, the content that is ready, the integrations that connect and the people who can operate the site. That is the basis for judging what the number buys.