Services / Web / Company websites

A website your team can change themselves, on a Tuesday afternoon

Most company sites go stale because updating them is somebody else's job. We build a fast, distinctive site on a content system your own people can drive: new pages, new prices, new team members, live in minutes without a developer, a ticket, or an invoice.

Why it matters

The cost is the wait

A company website has one job that everything else hangs off: convince someone who has never met you that you are worth contacting. They arrive from a search result, a LinkedIn post or a business card, give you a few seconds, and decide. A site that loads slowly, looks like it was built a decade ago, or cannot answer the obvious question loses that decision before your sales team ever hears about it.

The second job is quieter, and it is where most sites fail. Twelve months after launch the prices are wrong, the team page shows two people who have left, and the case study everyone is proud of never got published, because publishing it meant emailing an agency and waiting a week. A site your marketing team cannot edit is a site that decays, and the decay costs more than the build ever did.

So we build both halves. The visible half is a design system of your own (typography, colour, spacing and a library of on-brand page blocks), rendered fast enough to feel instant on a phone on mobile data. The invisible half is an editing dashboard your team is actually trained on, with previews, scheduling and one-click undo, so a text change takes ninety seconds and a new campaign page takes an afternoon. You leave with the code, the content and the accounts.

What you actually get

Built to be trusted

What separates a site that still looks current in three years from one that needed replacing in eighteen months.

01

A design system, not a pile of pages

Colours, type, spacing and components live in one place, so a rebrand or a contrast fix is a single edit rather than a hunt through every page. It is also why a new section can be built in days without looking bolted on.

02

Page blocks your marketing team assembles

A library of on-brand building blocks (hero, feature grid, testimonial, pricing table, form), that your team composes into new landing pages. A campaign page ships the same day, and it still looks exactly like your brand.

03

Fast on a phone, on mobile data, in a hurry

Pages are prepared before the visitor asks for them and served from a location near them. We agree target speed numbers up front and enforce them automatically, so a change that would slow the site down simply cannot go live.

04

Built to be found

Clean page structure, sitemaps, canonical addresses, social share previews and the structured labelling that earns rich results. Search visibility is designed in at the start rather than retrofitted by a specialist after launch.

05

Usable by everyone

Keyboard navigation, screen-reader labelling, colour contrast and visible focus, checked automatically on every change and by hand before launch. It widens your audience, and across the EU, UK and North America it is increasingly a procurement requirement.

06

Several languages and regions from one site

One content model serving every language you sell in, including right-to-left scripts with the right currency, contact details and legal text per region. Adding your second market stops being a second website.

Where it earns its keep

Same pattern, different desks

The brief is nearly always the same: look credible, load fast, stop being a bottleneck. What changes is who has to be convinced.

Professional services

01 · Professional services

Credibility earned before the first phone call

The problem
Buyers of legal, accountancy and consulting work research quietly for weeks before making contact. A dated site, partner profiles with no photographs and no way to see relevant work means you are compared unfavourably against firms who are no better: only better presented.
What we build
A restrained, confident site organised around the work rather than the org chart: sector pages, plain-language service explanations, publishable case notes, and profiles your marketing lead updates the day someone joins.
What changes
Enquiries arrive better informed and further along, and the firm can publish a point of view within hours of having one instead of queuing behind a developer.
Manufacturing & industrial

02 · Manufacturing & industrial

A catalogue engineers can actually search

The problem
Specifications live in PDFs, the product list is a scanned brochure, and every distributor enquiry starts with a request for a datasheet. Technical buyers who cannot find a spec in two minutes ask a competitor instead.
What we build
A structured product catalogue with real filters, downloadable datasheets and indexable pages per product, fed from one content source, so the same specification can later feed a distributor portal or a partner's site without being retyped.
What changes
Buyers self-serve the technical detail, sales conversations start at the commercial question, and the catalogue stops being a PDF somebody has to remember to re-export.
Hospitality & venues

03 · Hospitality & venues

Photographs that load before the visitor gives up

The problem
Restaurants, hotels and venues sell on imagery, and imagery is exactly what makes a site crawl on a phone. Menus go out of date within a fortnight, and every seasonal change means asking an agency and waiting.
What we build
Image-heavy pages with automatic format conversion and per-screen resizing, plus menus, opening hours and events managed by the venue's own team, with scheduled publishing for seasonal changes.
What changes
A site that feels as good as the room does, on a phone at a bus stop, and a manager who can change Sunday's menu on Saturday night.

The technology

The tools behind it, named

Nothing exotic. This is the stack chosen so your site is fast by default, editable by non-developers, and still maintainable by an engineer we have never met.

6 layers · 31 technologies

01

The build

The foundation: pages rendered before the visitor asks for them, written in a language that catches mistakes before your customers do.

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Astro

02

Where your team edits

A friendly dashboard with preview, scheduling and undo. We pick the one that fits how your team actually works, and if that turns out to be WordPress, we keep it behind a modern front end rather than retraining everybody.

  • Sanity
  • Storyblok
  • Payload
  • Contentful
  • Strapi
  • WordPress

03

Design & the component library

Where the brand gets defined once and reused everywhere, and where each block is reviewed in isolation before it ever lands on a page.

  • Figma
  • Storybook
  • Radix UI
  • shadcn/ui
  • Chromatic

04

Speed, images & search

The unglamorous engineering that decides whether Google ranks you and whether a visitor on a phone waits.

  • Lighthouse
  • Cloudinary
  • Google Search Console
  • Google Fonts
  • SVGO

05

Where it lives

Served from locations close to your visitors, with every proposed change getting its own private preview link before anything goes live.

  • Cloudflare
  • Vercel
  • Netlify
  • GitHub
  • GitHub Actions

06

Knowing what happens next

Which pages earn enquiries and which quietly lose them. We fit the analytics to your privacy position rather than the other way round.

  • Google Analytics
  • Plausible
  • Umami
  • Matomo
  • Hotjar

Product names and logos are the property of their respective owners and are shown to describe the technologies we work with. Their use does not imply any partnership, sponsorship or endorsement.

How we deliver it

Live behind a human first

Six to ten weeks for a typical company site, and most of the outcome is decided in the first two.

01

We work out who has to be convinced

A short discovery session on your buyers, the objections your sales team hears every week, and what a good enquiry actually looks like. Everything after this is downstream of that conversation, so we would rather spend a day too long here than a month too long later.

02

Structure before decoration

Sitemap, page purposes and wireframes agreed in grey boxes. It is far cheaper to argue about whether a page should exist while it is still a rectangle.

03

The design system

Type, colour, spacing and a set of page blocks, designed as a system rather than as individual pages. You approve the components, which means you have approved every page that will ever be built from them.

04

Build it with real content in it

The site is built against your actual words and photographs, never placeholder text. Lorem ipsum hides exactly the problems that surface on launch day, when it is expensive to fix them.

05

Migration and the redirect map

Existing pages are moved across and every old address is mapped to its new home, so your search rankings survive the move. Verified before launch, watched afterwards.

06

Launch, training, and a handover that is real

A rehearsed switchover, then a training session for your editors and a written guide. You leave with the code, the accounts, and the ability to change your own website.

Before you commit

The questions worth asking

Can we really update it ourselves, or is that just what everyone says?

Everyone does say it, so here is the test: at handover we sit with your team and have them make a live change (a new page, a new person, a new price) while we watch and answer questions. If they cannot do it without us, the job is not finished. What we will not pretend is that everything is self-service. A genuinely new kind of page usually needs a new block built, and that is a small piece of development work rather than an afternoon in the editor.

Do we have to move off WordPress?

No. If your team knows WordPress and retraining would cost more than the rebuild, we keep those editing screens and rebuild only the public site in front of them, which usually makes it dramatically faster and removes the plugin-security worry of a traditional install. We will tell you honestly which route we think suits you and why, including when the answer is to stay where you are.

What will it cost to run?

For most company sites, hosting and the content system together come to a modest monthly figure, frequently less than the managed hosting and paid plugins of the site being replaced. We size it against your real traffic during scoping and put the number in writing before you commit, including what happens on the day a campaign brings a hundred times normal traffic.

Will we rank better on Google?

The technical groundwork will be right (speed, structure, indexability, structured data) and that removes the reasons a search engine has to overlook you. But ranking also depends on your content, your competitors and your authority, none of which a rebuild changes on its own. Anyone promising you a position is guessing. What we will do is record your current baseline in Search Console and watch it daily through launch, so a problem is caught in days rather than in next quarter's numbers.

How much of our time will this take?

More than you would like, and it is worth budgeting for honestly. The heavy weeks are discovery and content: someone on your side has to make decisions and, usually, write or approve words. Expect a few hours a week from one decision-maker throughout, with two heavier weeks around content. Projects that stall almost always stall on content, not on code.

What happens after launch?

A written service agreement rather than a hopeful email address: monitoring, security updates, response times when something breaks, and a monthly allowance for small changes. You can also take everything and never speak to us again. You own the code and the accounts, and the handover is deliberately built around that being a genuine option.

Show us the site you are quietly embarrassed by

Send us the address. We will come back with honest feedback on what is costing you enquiries, what is fine exactly as it is, and what a rebuild would realistically involve.

Start the conversation