Web development
A Next.js site on Vercel with every template checked for speed and accessibility, and marked up so search engines and AI assistants can read it.
We build from the approved Figma files: shared components first, then templates assembled from them, so every new page reuses tested parts. You get a staging link in the first week of the build and a demo each week after. Each template has a weight budget for images, fonts and scripts, and motion switches off for visitors who ask their device for reduced motion.
For Marketing leads, founders and in-house product teams at B2B companies replacing a slow, template-based or plugin-heavy site.
You need this when
- 01
Your site is slow on a phone and nobody knows why.
- 02
Every plugin update risks breaking a page.
- 03
Your developers are busy on the product, so the marketing site waits.
What’s included.
Front-end build
Shared components coded once from the Figma library, then assembled into templates.
Performance
Image sizes, font loading and script weight set per template, and measured with Core Web Vitals, Google’s page-speed metrics.
Accessibility
Semantic HTML, keyboard navigation, visible focus and screen-reader labels, tested on each template against WCAG 2.2 AA.
Structured data
Schema.org markup for your organisation, services, articles and FAQs, so search engines and AI assistants can read what each page covers.
Site plumbing
The code side of the CMS, forms and analytics: content previews, form handling and the data layer your tags read, with Supabase where a page needs its own data, such as downloads behind a form.
Preview links
A separate link for every change, so you can check it before it reaches the live site.
How it runs.
Build starts in week 4 of a 6–10 week marketing site, on a staging link you can click through.
- 01 · Set up
Repository, hosting, staging and preview links are in place before the first template is built.
- 02 · Build components
We build the shared components first, then assemble the templates from them.
- 03 · Connect
CMS, forms, CRM and analytics are wired in and tested on staging.
- 04 · Demo weekly
Every week you click through what changed on staging and comment on it there.
- 05 · Hand to launch
We fix what the template checks find, then move to launch setup: redirects, tracking and go-live.
Deliverables
- Production site on your domain
- Staging environment with preview links
- Component library in code
- Structured data on every template
- Setup and deployment documentation
- Core Web Vitals and accessibility results for each template
Works with
What buyers ask.
Why Next.js and not WordPress or Webflow?
Next.js lets us decide exactly what each page loads, and there’s no plugin stack to keep patched. If your team has to stay on WordPress, Webflow or another platform, we tell you in week 1 whether we’re the right people for the job.
Can you build from designs we already have?
Yes, if they cover desktop, phone and the main states. We review them first and list what’s missing in the proposal.
Will animation slow the site down?
We count motion in each template’s weight budget. It loads only on pages that use it, is checked with Core Web Vitals like everything else, and switches off for visitors who set reduced motion.
Pairs well with
Pages, case studies, blog and jobs your team edits without touching code.
Let’s build your pipeline.
Tell us what you sell, who buys it and roughly what a customer is worth to you. We reply with questions, then a written proposal.