Development Agency
Contact Sign in Get a project quote

Service

Website Development

For businesses of any sector whose website has to do a job, taking enquiries, bookings or orders and telling the right story to the right visitor, and who want it built properly rather than assembled from a theme and a stack of plugins.

Get a project quote

The problem

What goes wrong today

Where it usually starts

Most businesses that come to us already have a website.

  • It was built a few years ago on a theme somebody liked, and since then every new need has been met with another plugin: a form builder here, a slider there, a cookie banner, a booking widget that opens in a frame and looks nothing like the rest of the site.
  • The page that matters most, the one that should turn a visitor into an enquiry, loads slowly on a phone, the contact form sends enquiries to an inbox that two people check, and nobody can say how many enquiries arrived last month or where they came from.

Where it gets harder

Editing content means waiting for whoever has the login, and even then a change to one page breaks the layout of another.

  • Accessibility was never checked, so a visitor using a screen reader cannot complete the form, and the colour contrast fails on the buttons that matter.
  • The agency that built it has moved on, the hosting renews every year without anyone knowing what it includes, and a redesign is put off because the last one took nine months and the content was rewritten three times.
  • Meanwhile competitors with plainer sites that simply work are getting the enquiries.

Scope of the service

What the build covers

A website build normally covers the pages, the content model, the forms and whatever the site has to hand off to: an enquiry inbox, a diary, a payment provider or a system you already run. We start by asking what the site is for in operational terms. For a professional firm that is usually enquiries routed to the right person with a record of each one; for a restaurant or clinic it is bookings with availability; for a manufacturer it is product and specification pages that sales can send to a buyer. The content model is designed around those jobs, so editors add a service, a team member, a case or an opening time in structured fields rather than pasting into a page.

The build is server-rendered HTML with a small first-party stylesheet and minimal JavaScript, checked at phone, tablet and desktop widths and against WCAG 2.2 AA. Forms validate on the server, protect against spam without a puzzle and record every submission so nothing depends on an inbox. Metadata, structured data, sitemaps and redirects from the old site are part of the build, not an add-on.

When the scope grows

Scoping scenario

A regional law firm with four offices wants a site where each practice area has its own enquiry route, each office its own page and opening hours, and solicitors maintain their own profiles. The content model, the routing rules and the per-office data make this a build rather than a template, and the scope document says which pages and fields are included.

Deliberately out of scope

  • Writing your copy from nothing, although we structure and edit what you provide
  • Ongoing marketing and advertising
  • Any business system behind the site, such as practice management or stock, which we connect to rather than replace and which the related service pages cover

Deliverables

What you receive

  • Discovery notes recording what the site must do for each type of visitor and who handles what arrives
  • A written scope document naming every page type, content field, form and hand-off, and what is left out
  • Designs of the key pages and forms at phone, tablet and desktop widths, with contrast and focus states checked
  • The build, deployed to your hosting or ours, with metadata, structured data, sitemap and redirect map in place
  • Migration of existing pages, media and documents from the current site with URLs mapped
  • Training for your editors with a short written guide to the content model
  • Handover material and full ownership of the source code, content and domain configuration

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to the current site, analytics, domain and hosting; an inventory of pages, forms and the systems they hand off to.

    Project stage: Onboarding

  2. Planning

    Discovery with the people who answer enquiries and edit content; the content model, page types and form routes are written into the scope document.

    Project stage: Planning

  3. Design

    Key page and form designs at phone width first, then larger screens, using your brand or a light system we agree together.

    Project stage: Design

  4. Development

    Content model and templates first, then forms and hand-offs, then metadata, redirects and performance work.

    Project stage: Development

  5. Client review

    Your team adds real content, submits test enquiries and checks each page on their own phones against the scope document.

    Project stage: Client review

  6. Revisions

    Changes from the review are made and re-checked, including accessibility and page weight.

    Project stage: Revisions

  7. Ready for launch

    Redirects verified against the old URL list, forms tested to the live inbox or system, DNS change planned for a quiet hour.

    Project stage: Ready for launch

  8. Delivered

    The site is live and measured; hosting and maintenance continue under their own agreement if taken.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Email and shared inbox providers for enquiry notifications and routing
  • Diary and booking systems where bookings are taken on the site
  • Payment providers for deposits and online payments through the provider-independent payment layer
  • Customer relationship and practice management systems you already run
  • Newsletter and marketing email platforms for sign-ups
  • Map, review and social platforms where their embeds are needed
  • Analytics with first-party, consent-aware measurement

How we would approach it

Worked example

Concept demo

A regional law firm with four offices and nine practice areas

The situation

A law firm wants enquiries from each practice area to reach the right team, each office to show its own address, hours and people, and solicitors to keep their own profiles current without touching page layouts.

Why it is a custom build

The custom route is needed because the routing rules, the per-office data and the relationship between people, offices and practice areas go beyond what a theme with a contact form can express.

The scope we would propose

  • Structured content types for practice areas, offices, people and insights
  • An enquiry form per practice area that records the submission, notifies the named team and offers a call-back slot
  • Office pages generated from the office records with structured data for each location
  • A redirect map covering every URL of the current site
  • A performance budget checked on every deployment

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of distinct page types and the depth of the content model behind them
  • Forms, enquiry routes and what each hands off to
  • Bookings, payments or accounts taken on the site
  • Systems to connect, such as a diary, a CRM or practice software
  • Volume of existing pages, media and documents to migrate and redirect
  • Design work: a full visual identity or a light system applied to your brand
  • Accessibility and multilingual requirements beyond the standard build
  • Hosting choice: your own hosting or ours

Start from a package

  • Software package

    Corporate website package

    A packaged corporate website with structured service pages, leadership profiles, careers applications, news, office pages, a document library and enquiry routing by department.

    Custom build

  • Software package

    Law firm website package

    Practice-area pages, solicitor profiles, per-area enquiry routing, secure upload and a managed regulatory block for small and mid-sized firms.

    Custom build

  • Software package

    Restaurant booking package

    Table booking with a real table plan, service periods and turn times, large-party deposits, waiting list, menus with allergen tags and private dining enquiries for independent restaurants.

    Custom build

FAQ

Frequently asked questions

Do you build on a content management system or from scratch?

On our own server-rendered platform with a structured content editor for your team. It avoids the plugin stack and theme lock-in that usually cause the problems described above, and you own the result. Where a packaged starting point fits, for example the corporate website package, we say so in the proposal.

How is this different from the sector-specific website services?

The sector pages describe the particular workflows of one kind of business, such as a law firm website with practice areas and solicitor profiles or a restaurant site with table bookings. This page covers the capability itself: the content model, forms, performance and accessibility work that every build shares. If your business matches a sector page, start there; if not, start here.

Will the site be fast and accessible?

The build is server-rendered with a small stylesheet and minimal JavaScript, and it is checked at phone, tablet and desktop widths and against WCAG 2.2 AA before launch. We measure page weight and the Core Web Vitals on the pages that matter and report what we measured, not a score from a lab tool presented as real-world data.

What happens to our existing pages and search listings?

Every URL on the current site is listed, and each one is either kept, redirected to its new equivalent or deliberately retired, with the map agreed before launch. Content and media are migrated into the new content model. We describe the measurement we put in place; we do not promise search outcomes.

Who owns the website afterwards?

You do. Source code, content, media and the domain configuration are handed over at delivery. Hosting and maintenance are optional and agreed separately, and the site can be moved to another host.

Get a project quote for website development software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences