Web development

Websites and web apps that stay fast after launch

Next.js and React builds with a performance budget, structured content and metadata generated from one source — so speed and search visibility are maintained, not audited once and forgotten.

Written scope and a fixed estimate within two business days. NDA on request.

Performance budget

The numbers we build to, and check before launch

These are targets for the pages that carry traffic and revenue. We measure them on a deployed build, on a mid-range device — not on a developer laptop.

LCP

under 2.5s

Largest contentful paint on a mid-range phone over 4G.

CLS

under 0.1

No layout jumps from late-loading images or injected banners.

INP

under 200ms

Interaction response, measured on the pages that do real work.

Payload

budgeted

A JS budget per route, checked in CI rather than after launch.

Capabilities

What we build

Marketing pages, product surfaces and content platforms — with the same standard applied to each.

Marketing sites

Fast, indexable pages with structured content, clean metadata and a CMS your team can actually edit.

Web applications

Authenticated product surfaces with real state, permissions and the loading and error states people forget.

E-commerce

Catalogue, cart, checkout and payment flows with the edge cases — refunds, failed payments, tax — handled.

Headless CMS

Sanity, Contentful or a custom admin, wired so content changes do not require a deploy.

Performance work

Auditing and fixing an existing site: bundle size, images, fonts, third-party scripts and rendering strategy.

Migration and rebuild

Moving off an ageing stack without losing rankings, URLs or the content that earns the traffic.

Process

Four steps, content before code

  1. 1

    Content and structure first

    What each page is for, which queries it answers, and how the navigation connects them.

  2. 2

    Design in the browser

    Build the real components early so typography, spacing and responsive behaviour are settled in code, not in a static mock.

  3. 3

    Build for the slowest device

    Server rendering where it helps, code splitting, image discipline and a JS budget per route.

  4. 4

    Audit before launch

    Performance, accessibility, metadata and crawlability checked on the deployed build.

Launch checklist

What we verify before a site goes live

  • Semantic HTML with one H1 and a heading order that makes sense
  • Metadata and canonical URLs generated from one source, not copy-pasted per page
  • Responsive from 320px up, tested on a real device
  • Keyboard navigation, visible focus and labelled form controls
  • Images sized, lazy-loaded below the fold and served in modern formats
  • Sitemap, robots rules and structured data validated before launch

Stack

What we build with

Next.jsReactTypeScriptTailwind CSSDesign tokensSanityContentfulMDXVercelAWSCloudflare

Proof

Web products in production

A video learning platform, a SaaS dashboard and a global product selector — all built and maintained by us.

FAQ

Web development questions

Do you build marketing sites or web apps?

Both, and they are different jobs. A marketing site is judged on speed, clarity and search visibility; a web app is judged on whether the workflow holds up under real use. The scope and the estimate reflect which one you are asking for.

Can you improve an existing site instead of rebuilding it?

Often yes, and it is usually cheaper. We audit performance, accessibility, metadata and structure first, then propose the smallest set of changes that moves the numbers. A rebuild is recommended only when the foundation blocks the fixes.

Will we be able to edit the content ourselves?

Yes. Pages are built against a CMS model, so your team edits copy and images without a developer or a deploy. We include a walkthrough of the editing flow at handover.

How do you handle SEO on a rebuild?

URLs are mapped one-to-one with redirects for anything that changes, metadata is preserved or improved, and the sitemap is regenerated. We check the crawl after launch rather than assuming it carried over.

What about hosting and maintenance?

We deploy to Vercel, AWS or Cloudflare depending on the requirement, and hand over with the pipeline documented. Ongoing maintenance is optional and covers dependency updates, monitoring and small changes.

Request a quote

What should the site do that it does not do now?

Send the current URL, the pages that matter and the problem you are trying to fix. We will come back with a scoped plan and a fixed estimate.

No obligation. We will tell you if we are not the right team for the job.

  1. 1

    Tell us the goal, platforms and must-have features.

  2. 2

    We reply within two business days with scope, approach and a fixed estimate.

  3. 3

    Sign an NDA first if you prefer — nothing about your idea is public.