Startup Weekend • 54-hour MVP blueprint
RepairRoster GR
Grand Rapids
Policy + Climate + Civic Tech
A repair economy you can see and support.
A directory + booking request flow for local repair, with a public “saved from landfill” impact counter and partnership hooks.
Local fit: Mid-sized city constraints, river/watershed stewardship, and limited grant-writing capacity—good for grant tooling and pragmatic circular economy pilots.
Core user stories
- As a resident, I describe a broken item and get matched to 2–3 local repair options with price ranges.
- As a repair pro, I claim my profile, set service categories, and receive booking requests.
- As a city/nonprofit, I view aggregate “repair saved” stats to justify support for repair incentives.
Clickable demo scope (what you build)
- Resident flow: request → recommendations → contact/booking request.
- Provider onboarding flow (simple form) + admin approval toggle.
- Public impact page counting repairs, cost savings, and waste avoided (mock).
Team of four roles
- Product & Policy Lead: Define repair categories, intake questions, and impact metrics (waste avoided, cost saved); write non-extractive marketplace rules.
- UX / Frontend: Build request → matched providers → booking request flow; create provider profile pages optimized for trust.
- Backend / Data: Implement provider directory + matching rules + booking requests; seed sample providers and FAQs.
- Partnerships / Story / Ops: Talk to 2 local repair pros and 3 residents; validate pricing model; deploy and pitch.
54-hour build plan
- Hours 0–6: Pick one user segment; do 5–8 quick interviews; lock the “one workflow” MVP.
- Hours 6–24: Build the clickable flow end-to-end with stubbed data; draft the policy narrative.
- Hours 24–40: Add one policy-ready output (brief/dashboard/export); tighten UX; seed data for 2–3 neighborhoods.
- Hours 40–54: Polish demo script; add analytics mock; finalize pitch + one-page handout.
What to show in the final demo
- The “happy path” (one user completes the core task in under 2 minutes).
- One policy-ready output (a brief, dashboard view, or export).
- One local proof point (seeded neighborhoods / agencies / partner types relevant to Grand Rapids).
How it can earn revenue without becoming extractive
Revenue fit (values-aligned): small transaction fee or membership dues that fund local operators (repair pros, reuse centers), plus optional B2G sponsorship for impact reporting.
Guardrails: publish scoring criteria, minimize data collection, and default to community ownership where possible (co-op/commons patterns).
