Website Development
A website that works for your business, not just your portfolio.
There are two ways a website fails: it can be slow, or it can not rank. A slow site loses visitors before they read a word. A site that doesn't rank doesn't get visitors at all. Everything else — the design, the copy, the features — only matters once you've solved those two things.
What this involves
Next.js and React
For anything that needs to be fast, scale, or have any interactivity, Next.js is what we reach for. Server-side rendering, static generation, edge caching — we know how to use each correctly and when to mix them. Not every page needs to be dynamic and not every page should be static.
E-commerce that converts
Shopify for most things. Custom WooCommerce or Next.js storefronts when Shopify gets in the way. The goal is a checkout flow that doesn't make people abandon their cart because something loaded slowly or asked for information at the wrong moment.
Content management your team can actually use
Headless CMS setups where editors can update content without filing a developer request every time. Sanity, Contentful, or Notion-as-CMS depending on how technical your team is and how often you publish. The best CMS is the one people actually log into.
Performance that holds up over time
Page speed doesn't degrade overnight — it creeps. Each new feature, third-party script, and image that never got optimised adds a bit more weight. We build with Core Web Vitals in mind from the start and set up monitoring so you know when something slips before Google does.
This is a good fit if…
- You have an existing site that's slow and you've been told it needs to be rebuilt
- You're launching a new product and need a site that won't embarrass you when people start looking
- Your content team is constantly asking developers to make small copy changes
- You're losing organic traffic and suspect it's a technical SEO issue, not a content issue
- Your current site can't handle the traffic or functionality you now need
Technologies we use
We work in the stack you already have. Here's what we typically reach for in this area.
Common questions
Next.js or something else?
Next.js for almost everything — the App Router is mature, the performance characteristics are good, and the deployment story is excellent. We'll suggest alternatives when there's a genuine reason, not just to use something different.
Do you handle SEO as part of web development?
Technical SEO yes — Core Web Vitals, semantic HTML, meta tags, structured data, sitemap. Content strategy and keyword research is a different discipline and we'll tell you where we end and where you need an SEO specialist.
Can you work with an existing design, or do you do design too?
Both. We can implement an existing Figma file or design from scratch. Most projects are somewhere in between — a direction exists and we refine it as we build.
How do you handle content updates after launch?
We set up a headless CMS so your team can update content without filing a ticket every time. The right CMS depends on how technical your team is and how often you publish — we'll recommend based on that.