01

Three ways to build a website

Freelancer: design and front-end development against your specification. The specification strongly shapes the result; analytics, copy and marketing are often outside scope.

In-house team: full control and detailed product knowledge. However, several specialists are needed, and hiring for a one-off project may not be economical.

Agency: a process from research to launch and support. Costs are higher; agree scope and approval points at the outset.

The key difference is who defines the problem, not just price. A freelancer commonly follows your specification; an agency helps frame it by studying your business, audience and competitors. If your team can prepare a sound specification, the first option may be more economical.

02

What development includes beyond design and coding

Work often omitted from low-cost proposals and later charged as extras.

Research: competitors, audience and website objectives. Without it, design follows taste rather than the task.

Structure and journeys: which pages are needed, how visitors move between them and where they decide.

Copywriting is a separate task. Placeholder text intended for later replacement often remains for years.

Search readiness: URLs, metadata, structured data, loading speed and functioning without JavaScript. Planning these during development is cheaper than rebuilding later.

Analytics: tracking and goals for forms, calls and enquiries. Without them, performance is difficult to judge.

Testing: screens, browsers, forms and speed.

Post-launch support: the first weeks typically reveal adjustments.

03

Why a cheap website can cost more

A common sequence: a website is built quickly and cheaply; six months later it produces no enquiries. Review reveals that its structure misses demand, copy does not answer customer questions, analytics is absent and URLs need changing.

The options are then to improve the existing website or rebuild it. Both can cost more than sound initial planning, because lost time adds to the expense.

Changing URLs is a separate risk. A redesign without a URL preservation plan can lose rankings and organic traffic. This is manageable, but should be planned before launch rather than discovered afterwards.

04

How the process works

Work progresses from the business challenge to a tested result.

Approve from the top down: structure, screens, then individual elements. Changes are possible at every stage, but later changes cost more.

  • Brief and research: objectives, audience, competitors and constraints.
  • Structure: sitemap and journeys, approved before design because diagrams are cheaper to change than layouts.
  • Prototype: block placement without visual styling, focusing discussion on logic rather than colour.
  • Design: visual development based on the approved prototype.
  • Copy: written for page structure and objectives.
  • Development: front-end coding, programming and integrations.
  • Testing and launch: checks, analytics setup and publication.
05

Questions to ask before starting

Before starting, record the scope, responsibilities and handover arrangements.

  • What is included in the price and what costs extra?
  • Who writes the copy?
  • Will the website be search-ready, and what exactly does that include?
  • How will analytics be arranged?
  • What happens after launch: support, improvements and response times?
  • Who owns the source files and access credentials?
  • How will existing URLs be preserved if this replaces a website?