a working prototype, before you fund the build.

prototype

a clickable prototype of the core flows — a real interface in the browser, not wireframes.

deployed

live on a private or public url you can share the day it ships.

design

interface design included — a sketch, notes, or a conversation is enough to start. existing designs welcome but not required.

data

realistic stubbed data and states, so demos feel like the product.

handoff

the code, the deploy, and a written note on what it would take to make it production-real.

not production code — and priced accordingly. the prototype optimizes for speed of learning: some of it can carry into the real build, but plan for the production version to be built properly. when the idea is validated, that's a sprint.

kickoff

30-minute call. the idea, the audience, the one thing the prototype must prove.

build

daily async progress. flows take shape in the browser within the first few days.

end

walkthrough, deployed url, code handoff, and a scope sketch for the production build.

$6,000 for one focused week, $10,000 for two. fixed and agreed before work starts.

two decades designing and building for the web. work for modern treasury, vice, amazon, condé nast. a prototype only convinces if it feels real — that's the part i've spent a career on.

• do i need designs first?+
• can it become the real product?+
• can users log in? does it store data?+
• who owns it?+
• what stack?+
• do you sign ndas?+