How it works
One paragraph, no jargon, no structure. If you can explain it to a friend you can start here.
~30 seconds · free
"A tool where local gyms can sell class packs and members book from their phone."
Product type, primary user, money model, key action, and what we assumed. You correct anything wrong before it hardens.
instant · free
Two-sided marketplace · members on mobile · 8% platform fee · assumed no native app — change it?
Only the questions your project actually needs, each with a recommended answer already selected and a one-line reason. "Not sure" is always an option.
4–8 minutes
Roles: member, gym owner, instructor, admin — pre-selected because marketplaces with schedules always need all four.
Features, roles, permissions, pages, data entities, integrations, monetisation, edge cases. Conflicts flagged before anything is generated.
12 sections · editable
Conflict: guest checkout and class history cannot coexist without a lightweight account. Recommendation applied?
Grouped into four stages, sized for your builder, with dependencies. Later prompts stay locked until their prerequisites are done — so you cannot build in the wrong order.
5–19 prompts
Stage 1 Foundations → Stage 2 Surface → Stage 3 Systems → Stage 4 Ship.
Copy a prompt, paste it, then run the short verification list before moving on. Change a decision later and we tell you exactly which prompts went stale.
as long as it takes
Verify: all five routes load · filters survive refresh · Book button visible at 390px · focus rings present.