Web Development

Fast, accessible sites built to rank from the first deploy.

Next.js and React builds — marketing sites, product sites, multilingual sites and web applications — with Core Web Vitals, structured data and internal linking designed in rather than retrofitted by an SEO six months later.

Typical timeline: 3–10 weeks depending on page count and template complexity

When this is the right call

Problems this solves

In the words people actually use when they get in touch, rather than in the words the technology uses.

  • The current site is slow, and the fix keeps being postponed
  • Every content change needs a developer
  • You need multiple languages and the current setup cannot do it properly
  • A template site has hit its limit

Deliverables

What you get

  • A deployed site, with source in your repository
  • Core Web Vitals within target on real devices
  • Structured data, sitemaps and metadata implemented correctly
  • A CMS your team can actually use, where one is needed
  • Handover documentation

Approach

How it is built

  • Next.js and TypeScript, prerendered where prerendering is right
  • Tailwind, with a design system rather than one-off styles
  • Internationalisation done properly — hreflang, canonicals and locale routing that agree with each other
  • Redirect mapping before launch, because that is where migrations lose their rankings

Process

How it runs

  1. 1

    Scope and sitemap

    Pages, templates, and who edits what.

  2. 2

    Design or adapt

    From your brand, or built to it.

  3. 3

    Build

    Component by component, reviewable as it goes.

  4. 4

    Optimise

    Vitals, accessibility, metadata, schema.

  5. 5

    Launch

    Redirect mapping, verification, monitoring.

What it costs

Scope and price agreed on a short call — no obligation, and you get a written figure before anything starts.

Get a figure

What I need from you

  • Brand assets, or agreement to work from a simple system
  • Content, or a decision on who writes it
  • One approver for design decisions
  • Domain and hosting access at launch

Not included

  • Copywriting at volume
  • Logo or brand identity design
  • Ongoing content updates, unless retained
  • Hosting and domain fees

Web Development — questions people ask

Why Next.js rather than WordPress?

Speed, control and Core Web Vitals headroom. But WordPress is the right answer when a non-technical team publishes daily and needs a mature editor, and I will say so rather than sell the stack I prefer.

Can our team edit content?

Yes, with a headless CMS where that is needed. Which one depends on who is editing and how often.

Will we lose rankings when we migrate?

Not if redirects are mapped before launch and verified after. Migrations that lose rankings almost always skipped that step.

Do you do multilingual sites?

Yes. This site runs nine locales with enforced translation parity — a build guard fails if a locale drifts. That problem is more interesting than it sounds.

Who hosts it?

You do, on your accounts. I will recommend and set it up; the credentials stay yours.

What about accessibility?

Semantic markup, keyboard navigation and contrast are part of the build rather than an audit afterwards.

Start here

Tell me what you are trying to do

You get a written figure and a scope before anything begins. If this is not the right service for the problem, I will say which one is — or that none of them are.

Roughly what you have already, what a good outcome looks like, and any budget or deadline you are working to — that is enough for a first reply with a real figure in it.