For the moment before the real money: someone has to try the idea, not hear about it. A deck can't do that, and a Figma link asks the viewer to imagine too much. A page that opens on their phone answers the question faster than either.

What you get

  • Landing page or up to three core screens, built in code and deployed on a live URL

  • States designed and working, empty, loading, and error included

  • Mock data standing in for the backend

  • Dev-ready Figma files carrying every state, so whoever builds production starts from a system instead of screenshots

  • One revision round

There is no production code behind it, and that's the point: it exists to be tested, then thrown away without regret.

How it works

  1. Half an hour on a call, with the idea in whatever form it lives.

    01
  2. I design the screens and build them the same week, and you watch the URL fill in as it happens.

    02
  3. We close with a walkthrough; one revision round follows it.

    03

Where the scope stops

The fixed price holds because the scope is fixed: one landing, or two or three screens. A full user journey, several user roles, or two account types is a bigger animal; that scope gets a real quote after a short call, typically $5,000–$9,000. And anything that needs to survive contact with production belongs to the design and front-end build.

FAQ

What do you need from me to start?
One conversation: the goal, who the users are, and whatever exists already, be it a deck, a voice note, or a napkin sketch. No PRD needed. If a brand exists, send it; if not, the build ships with clean neutral styling that won't fight your future identity.
Can I put it in front of real users?
That's the job. It opens on any phone from a link, no accounts and no app store between your tester and the idea. Mock data plays the backend, including the slow and empty moments, so the reactions you collect come from something that behaves like software rather than a slideshow.
Can we ship it to production?
No, and by design. Nothing behind the screens has to survive, and that constraint is what keeps the price at $2,500 and the timeline inside a week. When the idea earns a real build, the Figma files and the tested flow carry straight into it.
Why include Figma files if the code already exists?
Because production starts from a system, not from screenshots. By default that system ships as dev-ready Figma files, carrying the tokens and components with every state of every screen. If your team builds agent-first, the same system can ship in an agent-native format like Pencil or Paper instead, so whoever extends the design, developer or agent, works from structure rather than reverse-engineering it.

$2,500, about a week.

Good timing: before committing development money, or before a raise when the deck needs a live link beside it.

Book a validation build