Website Development

Most web work we inherit was built under someone else’s urgency — the launch deadline, the redesign sprint, the rebrand that had to ship by the quarterly board meeting. The result is a codebase that worked on day one and has been decaying quietly ever since. Our Website Development practice is organised around the opposite: sites that were built once, slowly, and stay built.

Our default stack is Next.js with React and TypeScript, because the hiring pool is deep, the trade-offs are well understood, and the platform story on Vercel is the best in the business. We pair that with Tailwind for styling and a headless CMS — Sanity most often, sometimes Contentful or Payload — so editors can own the site’s content without needing an engineer in the room. For marketing and editorial work, we reach for Motion when an interaction earns it and we stay out of its way when it doesn’t.

The seam we pay the most attention to is the one between design and engineering. A clean Figma file isn’t enough; the gap between the design system as it lives in the file and the components as they live in the code is where most sites start to drift from their launch state. We close that seam deliberately, with component APIs that read like the design vocabulary and tokens that are authored once and consumed everywhere.

We ship with Lighthouse scores we can defend, with accessibility that isn’t a post-launch audit’s problem, and with preview deployments your stakeholders can look at before a change merges to main. None of that is glamorous. All of it compounds.