Marketing Sites
High-converting pages that tell your story. SEO-ready, sub-two-second loads, flawless on every screen.
Web development — fast, fluid marketing sites, SaaS platforms and dashboards, built on React and Next.js.
web development
Sub-second loads. 60fps everywhere. Speed is the first design decision.
Interfaces that respond like native apps — because the web can, when it’s built properly.
Beautiful is table stakes. We design for the moment a visitor becomes a customer.
scroll
Project anatomy
Capabilities
SaaS Platforms
Accounts, billing, dashboards, real-time sync. The unglamorous plumbing done properly.
E-commerce
Storefronts built for revenue. Inventory, checkout, shipping, and the analytics to tune it.
Data & Dashboards
Visualization tools that make complicated information feel obvious at a glance.
Website Redesign & Migration
Replace an outdated site without losing the URLs, content, and search equity already earning their keep.
Connected systems
Stack
None of this is chosen to look impressive on a slide — every piece here is what we'd pick building our own product, and each one earns its place by removing a way your site could break or slow down later. TypeScript catches the bugs a looser language would ship to production. Next.js and Vercel mean your pages load fast without you thinking about servers. Boring, proven tools age well; trendy ones become the reason a rebuild costs more than the original build did.
Frontend
What your visitors actually touch, so it's held to the highest bar. React and Next.js render pages fast and rank well on Google; TypeScript means the interface behaves the same for every visitor, not just the ones who clicked in the right order during testing.
- React & Next.js
- TypeScript
- Tailwind CSS
- Framer Motion
Backend
The part nobody sees but everything depends on — accounts, data, files. Postgres and Supabase are the same database technology banks and Fortune 500s run on, not a trendy database that might not exist in three years when you need to change something.
- Node.js / API Routes
- PostgreSQL & Supabase
- Auth & sessions
- S3 file storage
Infrastructure
How it stays up, gets paid, and tells you what's working. Vercel means no server for you to maintain or renew; Stripe means payments that just work; analytics means you're not guessing which marketing dollar is actually earning its keep.
- Vercel edge hosting
- GitHub Actions CI/CD
- Stripe payments
- Analytics & monitoring
Delivery pipeline
How a project runs
Every project runs the same way, whatever it is being built on. The scope and the price are agreed before anything starts, and the schedule below is the one written into the agreement — not a description of how things usually go.
Scope and price, fixed
Before anything is built
You get a written scope and a number that does not move. Changes after that are handled as a change order — priced, signed, and added to the schedule — rather than absorbed quietly and argued about at the end. Nothing is billed by the hour, so a slow week is our problem rather than your invoice.
Payment 1 — 50%
On signing, before work begins
The deposit starts the work. The remaining two payments are tied to things you can see happening rather than to dates in a calendar, so a schedule that slips does not become an invoice that arrives anyway.
Design, then your decision
5 business days to review
Designs are presented for review, and you get 5 business days to approve them or come back with changes. We send a reminder before that window closes. If it passes without an answer the design counts as approved and the next payment falls due — and we tell you the day that happens rather than letting you find out from an invoice.
Payment 2 — 25%
On design approval
Build starts once the design is settled, so the thing being built is the thing you signed off. Approving the design is what releases this payment, which is why the review window above matters more than it looks.
Payment 3 — 25%
When the project is ready to launch
The final payment falls due when the build is finished and tested, not when it goes live. Invoices are payable within 14 days and count as late 7 days after that; you are reminded on the day each one is due rather than chased out of nowhere a month later.
Launch and handover
30-day warranty from launch
Going live transfers everything: source code, accounts, credentials, domains. You own it outright — there is no licence to keep paying. Anything that breaks within 30 days of launch is fixed at no cost, because it is a defect rather than a new request.
Before we begin
Questions
Websites start at £3,500 and web applications at £9,500. The configurator on the pricing page adds the specific pieces you need and shows the number update as you go, so you can see the figure before speaking to anyone.
A website presents — pages, content, a contact form, a checkout. A web application does work: accounts, permissions, dashboards, data that changes per user. The build is different from the first day, which is why they are priced separately rather than as add-ons.
Both are build decisions rather than things bolted on afterwards. Pages are server-rendered with Next.js, images and fonts are handled properly, and the metadata, sitemap and structured data are part of the build rather than a plugin. Speed and crawlability are the two things hardest to retrofit into a site that was not built for them.
Usually. Rebuilding a front end against an existing database, adding a checkout to a site that has none, or moving off a page builder without losing rankings are all normal starting points. What matters is whether the existing data can be reached, which is the first thing we look at.
Fixed scope, fixed price, agreed in writing before anything starts. You pay 50% on signing and the rest against two milestones you can see reached — design approval, then ready to launch. Nothing is billed by the hour, and the number does not move unless the scope does, in which case it is a signed change order rather than a surprise.
You do, outright. Source code, accounts, credentials and domains all transfer at launch, and there is no licence to keep paying for. If you want to take the code to another studio afterwards, nothing here stops you.
Anything that stops working within 30 days of going live is fixed at no cost — that is a defect, not a new request. After that, ongoing cover is a monthly care plan you can start or stop whenever; it is optional and is not needed for the work to be yours.
Designs are presented for review and you get 5 business days to approve or send changes, with a reminder before the window closes. If it passes with no answer the design counts as approved and the next payment falls due — you are told the day that happens.
Open a channel
Let’s build your web presence.
From first sketch to production deploy — and the monitoring that comes after.