Planning a UK business website: costs beyond the build

In short

A photographer compares more than the build price: content, domain, email, hosting, care and her own time all matter. She starts with a focused portfolio and a clear enquiry route. The comparison then shows which costs recur and who owns each task.

What does a website cost when you include the ongoing work?

Imagine seeing a low figure for a new website, then discovering that the domain, content, care and your own time all need separate decisions. The useful question is not only what the build costs, but what the site asks of you in year one and afterwards.

Imagine a photographer who needs only a portfolio and an enquiry form. Preparation, image selection and a working mail route matter more than a long list of extra features.

The photographer starts with the working day the website must support, not a package list. A commercial buyer needs to recognise her type of work, view a relevant set of images and send an enquiry. That calls for a disciplined edit, short explanations, a dependable form and a good phone layout. A client portal, booking engine or vast image archive may sound useful, but none solves a confirmed need in this first version.

Put every cost on the same page

Use seven lines in a comparison: preparation, design and build, copy and images, domain and email, hosting, care, and changes. Put an owner beside each line. That prevents a starting price from being compared with a working site that includes more.

Put a technical owner beside domain and email, not just a price. A domain move or DNS change can interrupt email when MX records are changed by mistake.

She then separates one-off work from ongoing work. Structure, design, development and loading the first pages belong to the initial project. Domain registration, hosting and technical care continue after launch. Selecting new shoots, updating captions and answering enquiries also take her own time. These are not universal hidden prices; they are distinct responsibilities that should be visible when she compares proposals.

Compare what will actually be delivered

A defined build price can suit a project with named pages, features and feedback stages. A recurring plan can suit a predictable base. Check the pricing page for current published figures; do not treat an old article as a quote.

Before agreeing, establish who supplies content, how many review rounds fit, and what a later change means. That turns a proposal into a work list rather than a loose promise.

This is where two headline totals stop being comparable. One studio expects final copy and images before work starts; another includes limited editing. One proposal names a review round, while another never says when a request becomes extra work. She asks what will be delivered, who supplies each item, how feedback is gathered, what triggers a new charge and which accounts or files she controls after handover.

Keep domain and email separate

Ask what happens when you need to edit a page, add a page, or move to another provider. A low start is not automatically a problem. An unclear boundary is, because it makes an honest comparison impossible.

For a UK project, compare the scope and ongoing responsibilities before treating a quoted figure as a complete total.

Email gets its own line because her domain also carries the business mailbox. A website launch does not require that mailbox to move. Anyone changing DNS needs to distinguish the records that point to the website from the MX records that deliver mail. Before work begins, she records who controls the domain, where email is hosted, and who will send a test message and submit the form after a change.

Choose the first release

Choose a small first version that explains what you do and gives someone a clear way to contact you. Add complexity only when it answers a real need. That is sensible planning, not a promise of growth.

Only then does she choose the first release: portfolio, approach, a concise about page and contact. The proposal says who prepares image sizes, adds alternative text and publishes a later project. A second language and online scheduling remain outside this round. They are not rejected forever; they are deferred until the photographer knows the core site is accurate, manageable and useful to the people she wants to reach.

What the comparison reveals

The conclusion is not a universal price for a website. It is a comparison in which build work, content, online operation and later changes are no longer mixed together. The photographer can read a low starting figure without calling it cheap, and a broader proposal without calling it expensive. She knows which costs may recur, which questions remain open and which part of the workload remains hers.

Before agreeing, she places each proposal beside her own list one last time. A missing item is not assumed to be included. An unclear phrase gets an ordinary example: who publishes the next photo series, what happens if the form email never arrives, and what information is available if the site later moves? Those answers show whether the arrangement fits her business more clearly than the length of its feature list.