Every screen from the Figma week, built as front-end code in your stack, responsive and pixel for pixel. That's the whole job, and it's a full one. Where the front end ends — data, servers, infrastructure — we end too, on purpose. Here's what that line buys you.
The line
what people see and touch.
Every screen, every state, both sizes — built from the same tokens as the Figma file, so design and code say the same thing. Your stack, your conventions, a repo your developers can open on day 14 and keep going.
“Pixel for pixel” is a promise about the gap between the file and the build. There isn't one. The person who drew the screen is the person who writes it, so nothing gets lost in a handover between the two.
Your stack
we come to your code.
Tell us your stack in the brief and give us repo access if you have one. The front end lands where your team already works, in the shape they already expect — not in a framework you now have to learn.
The reason
one person, one craft, one week.
weekone is one person. Finishing an interface properly in seven days is possible because it's the only thing being done. Put a database and a deploy pipeline into the same week and something gives — usually the details you hired us for.
Your back end is also the part that knows your business best: your data, your rules, your edge cases. Your developers own it already; they shouldn't have to inherit ours.
“we stop where your back end starts.”
Day 8–14
how the code week runs.
- Day 1–7 — the Figma week: system, every screen, states, your notes.
- Day 8 — components in code, from the Figma tokens.
- Day 9–11 — every screen.
- Day 12 — states and motion.
- Day 13 — your notes, our fixes.
- Day 14 — the repo is yours.
Not included
what stays with you.
- Servers and databases.
- APIs and integrations.
- Hosting and deployment.
What you get is a front end ready to be wired up — named, structured and matched to the design — so wiring it is the only job left. Your developers connect it to the real thing; nobody has to rebuild the screens first.
For sites
or skip the code entirely.
If what you need is a site — a launch page, a company site, docs or a help centre — code may be the wrong tool. The Framer output publishes the same screens as a live site with a CMS your team can edit without a developer, on day 14. Launch on Framer is $5,400.
your week could be next.
Pick your week