Webflow locks you in. Squarespace is slow. Templates look like everyone else. We hand-code marketing sites and operational apps in Next.js — edge-deployed, performance-budgeted, owned by you. Not pretty-and-stuck — fast and yours.
Hand-coded Next.js · TypeScript · edge98+ Lighthouse perf score, mobile+34% Typical conversion lift vs old site100% Code & accounts owned by you
What's in the build
Six pieces, one shipped site.
From the discovery brief to the live URL. Each piece exists because cutting it would cost you a customer or a search ranking — usually both.
01 · Foundation
Next.js, TypeScript, edge.
Hand-coded on the same stack we use for ourselves. Server-rendered, edge-deployed, type-safe. The site loads in under a second on a phone on 4G.
Next.js 16 · App Router
TypeScript end-to-end
Vercel edge · 14 regions
Image optimisation built-in
02 · Performance
Performance budget, enforced.
Lighthouse 98+, LCP under half a second, zero render-blocking. We treat performance as a feature, not a Phase 2. The performance score is in the build pipeline.
Lighthouse 98+ enforced
LCP under 0.5s mobile
CLS < 0.05
CI perf-budget gating
03 · SEO
Built to be found.
Schema markup, semantic HTML, canonical tags, sitemap, robots, OG images per page. Indexable from day one, ranking from month one.
Schema.org JSON-LD
Per-page metadata
Sitemap & robots auto-generated
Per-page OG images
04 · Conversion
The CTA that actually converts.
Above-the-fold copy that works, CTAs that fire to the right place, contact forms wired into your inbox or CRM. Not a Calendly link bolted to the footer.
Above-fold copy & design
Forms wired to inbox/CRM
Conversion-event analytics
A/B-test ready
05 · CMS
Edit without breaking.
Optional CMS layer for content you actually update. Sanity, Contentlayer, or markdown-in-repo — whichever fits how you work. Edit safely; the design holds.
Sanity · Contentlayer · MDX
Preview-on-save
Per-role content access
Versioned, with rollback
06 · Operational app
The staff-side software too.
If you need an internal app — booking, CRM, dashboard, ordering — we build it on the same stack. React Native via Expo for mobile, Next.js for web. One stack across surfaces.
React Native · Expo
Per-role views
Offline-capable
Tablet & phone optimised
Method
Read · Find · Write.
Two weeks reading the existing site, the analytics, the search rankings, the customer journey before we write code. The build follows the conversion leak — not the brand brief.
01
Read
Two weeks auditing the existing site: performance, SEO, conversion path, content debt. We share the analytics — every leak gets a number.
02
Find
One leak gets prioritised — usually a slow homepage or a broken contact path. We propose the smallest rebuild that closes the gap. Fixed price, fixed timeline.
03
Write
We hand-code, integrate, deploy. Ninety days of stabilisation, performance monitoring, content edits. Repo, domain, accounts — yours.
Sample engagement
The agency that left Webflow and got 34% more leads.
Twelve people. One Webflow site. Three-second load on mobile, leads dropping.
A professional services agency was stuck on Webflow — slow, expensive, and impossible to integrate cleanly with their CRM. Four-week rebuild on Next.js with direct CRM integration, schema markup for service pages, hand-tuned mobile performance. Six weeks later: Lighthouse 98, LCP under half a second, contact form conversions up 34%. Repo and domain handed over.
How we measure: Lighthouse runs on the live site (mobile, throttled 4G, three-run median); conversion lift compared on equal traffic windows pre/post-launch (n = 2,418 sessions per side, 60-day windows).
0.4sLCP, mobile (was 3.2s)
+34%contact-form conversion
£0monthly Webflow bill, ongoing
Other use cases
Five more builds, same method.
Each one a tightly-scoped fix for a row that's bleeding on the P&L.