Most design handoffs are a picture of a product. This one is the product's front end.

In one week you go from "we're not sure what this should be" to a working, coded prototype your developers can build on — hosted, clickable, and ready to put in front of real users.

How the week runs Monday — Alignment. What's the outcome, who is it actually for, what does success look like, and what's already been decided that I shouldn't re-open. Tuesday — Direction. I come back with the shape of it: the flow, the key screens, and the decisions I'm making and why. You course-correct here, cheaply, before anything is built. Wednesday–Thursday — Build. I design directly in code. You watch it evolve in a live link rather than getting a reveal at the end. Friday — Handoff. Working prototype, walkthrough call, and everything documented so your engineers can start Monday.

What you get • A working coded prototype (HTML/CSS/JS) — hosted and clickable, not a mockup • The design decisions written down — the why, not just the what • A dev-ready handoff your engineers build on rather than reinterpret • A recorded walkthrough for anyone who wasn't in the room

Why coded instead of Figma Your developers don't translate a picture — they build on real front-end code. And because it's real, you can test it with actual customers on Friday instead of three weeks after the handoff meeting. If a layout doesn't hold up, you find out on Wednesday, not in your next sprint.

Best for A new feature or flow where the team isn't aligned yet. An idea you need to see before committing engineering budget. Agencies who need senior design at the front of a project.

Not for Full end-to-end product builds, or polish on something already working — I run a separate sprint for that.

A larger version exists Extended: $8,500, two weeks. Everything above, plus a research round with real users and a second iteration pass on what you learn — across two connected flows rather than one. Message me if that's the better fit for what you're deciding