Problem
Who needs help, and what hurts?
Answer eight guided questions about the user, problem, desired result, solution, and evidence. LaunchBox turns your choices into a focused first-build plan.
✓ Choice-first flow • Writing is optional • Saved in your browser
LaunchBox uses transparent rules—not heavy AI—to narrow the options, recommend the next test, and keep the first build focused.
Start with clear choices. Add optional details only when they make your idea more specific.
Your audience and persona change the problem, outcome, and solution options shown next.
LaunchBox considers your evidence and access to users before recommending what to do.
Receive a first experiment, Build First scope, score, decision, and shareable PDF report.
Your plan connects the user and problem to a success threshold, first-build scope, action plan, and readiness decision.
Clarify the target user, problem hypothesis, current alternative, and expected value.
Get a recommended test, participants, steps, and a measurable success threshold.
Separate Build First, Add Later, and Not Yet, then receive a readiness decision.
The options, recommendation, score, and decision respond to the user, problem, desired result, evidence, and participant access you choose.
Show schedule changes, highlight the announcement that needs action, and keep the next deadline visible.
Why REVISE? The direction is useful, but personal observation should be confirmed with direct student evidence before development.
Review the score and comments, hand the developer-ready brief to a collaborator, or save the full one-to-two-page report as a PDF.
Clarify one user and one problem, check the evidence, and choose the smallest useful version to test first.
✓ No sign-up · Progress stays in this browser.A rule-based first-test recommendation created from guided answers.
Volunteer teams miss important updates spread across group chats and email.
Test five realistic updates with five volunteers using a clickable phone prototype.
Priority update feed, deadline highlight, and simple progress confirmation.
BUILD the focused test version—not the full product.