Back

Design + front-end build

One critical journey, taken from research to production front-end by the same person who designed it. From $15,000, typically 3–4 weeks, a working demo every week on a live preview.

Book a scoping call

This is for a founder who knows where the product is going, often after a teardown or with a prototype in hand, and needs one journey done properly: designed, built, and live. The usual alternatives are a studio at $18,000 and up, with three people and two handoffs between them, or a designer-developer pair whose design file and codebase stop matching somewhere around week two. Here the person who framed the problem is the person who ships the front-end.

What you get

  • Framing: goals, success criteria, and the boundary of the release, written down before any screens exist.

  • Design: UX for one core journey and the IA around it; UI with every state designed (empty, loading, error, edge cases) across breakpoints; a compact component system the product can grow on.

  • Build: a production front-end on the stack we agree, integrated with your existing documented APIs, with written specs where my work meets your backend.

  • Launch and after: accessibility and browser QA, handoff documentation, help with the deploy, and 14 days of defect support.

The writing is part of the work, not an extra line item. If the project needs a PRD, development specs, or QA documentation, I write them; early teams rarely have anyone whose job that is, and it shows later.

How it works

  1. A scoping call first, then a fixed proposal, so the number you agree to is the number you pay, and the timeline is set by what your product actually needs.

    01

  2. Design and build run together, with a demo every week on a preview URL you can open from your phone.

    02

  3. Launch comes with QA and the 14-day support window.

    03

Not included

Backend and data schema, auth architecture, payments, migrations, native apps, infrastructure, long-form copywriting, and a stream of post-release features. This list is what lets the price stay fixed after scoping: you know what you're buying, I know what I'm building.

FAQ

Do you write the production front-end yourself?
Yes. Design and front-end are the same pair of hands here, so nothing gets lost in a handoff. Your team keeps the backend; where my code meets your APIs, written specs replace assumptions.
Can you work with our existing design system?
Yes: an existing design system gets extended, not replaced. I build the missing components and states in the language your product already speaks, so the project ends with one system rather than two. If no system exists yet, the build ships with a compact one.
What do you need from us before the scoping call?
A business goal, access to someone who knows your users, and documentation for any APIs the front-end will touch. Bring a PRD if one exists; if not, the framing stage produces one. The scoping call settles the boundary of the release.
Why is the price fixed instead of hourly?
Because the scope is closed before the work starts. The not-included list draws the edges and the scoping call sets the number; after that the number doesn't move. Hourly billing makes slow work profitable; a fixed price from $15,000 puts the risk of speed on me.

From $15,000, fixed after scoping.

Good timing: once you've tested the idea and the next step is a journey that has to hold up in production. Three to four weeks is about half the usual timeline for that scope; the speed comes from an AI-assisted workflow and from having no handoffs to wait on, not from skipping states or QA. A finished product in ten days is a different offer, and usually a different kind of product.

Book a scoping call