Section 10
3-hour hackathon pacing
A simple time box. If you're behind, cut scope before you cut the demo prep.
Plan
0–30 minRead the challenge, define the user, problem, decision, PRD, V1 scope, and demo path.
- Write the one-paragraph product statement.
- Fill the lightweight PRD.
- Decide what is explicitly out of scope.
Build core
30–90 minBuild the app shell, core pages, forms, and basic data structure.
- Land the spine of the user flow end-to-end.
- Use placeholder copy where it doesn't matter yet.
- Don't style anything beyond defaults yet.
Logic + AI
90–150 minAdd logic, scoring, AI decision support, result page, explanation, and recommended next step.
- Wire the inputs to the logic.
- Show a clear result with reasoning.
- Add the recommended next step on the result page.
Demo prep
150–180 minStop adding features. Test demo path. Fix only critical issues. Prepare final explanation.
- Walk the demo path twice from a fresh load.
- Tighten the demo screen — typography, spacing, empty states.
- Rehearse the 60-second story out loud.
Tip
If the clock says 90 minutes and the spine isn't end-to-end yet — cut a step from the flow.
V1 readiness checklist
Tick each item as your build hits it. If something is unticked at 150 minutes, that's where attention goes.
—
Saved on this device only.