Development
You already have the design. Now it has to survive the build.
You bring the file. I build it, and I tell you what I found in it first. One person, start to finish.
What you get
One person. Your file. No translation loss.
Handoffs drift. The same heading at two sizes on two pages, body text at three, spacing that never repeats. You get that list first, with what I’d do about it.
01
Built as drawn
Your type scale, spacing and states carried across. Nothing rounded to whatever was convenient to build.
02
A style system underneath
Type, colour and spacing become reusable styles, so the pages you add after I’m gone still match the ones I built.
03
CMS setup
Blog, case studies, careers. Your team publishes without touching the build.
04
Technical SEO, including the machine-readable part
Meta, schema, sitemap, alt and aria labels - plus llms.txt, because a growing share of your buyers ask an AI before they ask you.
05
Forms that say where the enquiry came from
Every enquiry should say which page produced it. Otherwise you know the site gets traffic, and nothing about what the traffic did.
How it works
Five steps, file to launch.
01
File review
I go through the Figma before quoting. You get what’s inconsistent,
what’s missing, and what will behave differently in a browser than it does on the canvas.
02
Scope
We agree in writing what’s in and what’s out. Anything that turns out to need
design rather than implementation gets flagged, not silently absorbed.
03
Build
Styles first, then pages. Interactions, CMS, integrations.
04
Review
You review in the browser, not in screenshots. Two rounds.
05
Launch
QA across breakpoints, technical SEO, go live. Most builds go live in 2–3 weeks from kickoff.
Who this is for
Teams who already did the design work.
B2B SaaS and deep tech teams with a finished design who need it built exactly, and who want someone to say so when the file has a problem. WeAreFuture came with a Figma file and a homepage to implement, roughly one-to-one. It ended as five pages, an English version with its own URLs, a blog and a HubSpot setup - because the build kept surfacing decisions nobody had made yet. The first enquiry landed six hours after launch, from an enterprise prospect, through a subpage that didn’t exist in the original brief.
If that’s not you
Coming without a design, or with one that no longer fits where the company is? That’s a different job and it’s on the other page.