Startup Weekend • 54-hour MVP blueprint

LeadSafe Chicago

Chicago

Policy + Climate + Civic Tech

Transparent progress toward lead-free water.

A public dashboard that tracks lead service line replacement progress and makes it easier for residents to find resources and report barriers.

Local fit: Big-city service reliability, building energy compliance, and environmental health; strong need for transparent dashboards and circular construction reuse.

← Back to finalist list

Core user stories

As a resident, I look up my block and see status, next steps, and health resources.
As a city team, I log progress updates and barriers by area.
As an advocate, I export a neighborhood progress brief for oversight meetings.

Clickable demo scope (what you build)

Lookup → status page with resources + next steps (seeded sample data).
Progress dashboard with filters by neighborhood/ward (mock).
Exportable brief page (print-friendly).

Team of four roles

Product & Policy Lead: Define transparent progress metrics and resident-friendly next steps; write equity guardrails.
UX / Frontend: Build lookup → status → resources screens; design a print-friendly brief.
Backend / Data: Seed sample replacement status dataset; implement filters and export stub.
Partnerships / Story / Ops: Validate with a public health advocate; craft oversight story; deploy.

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 Chicago).

How it can earn revenue without becoming extractive

Revenue fit (values-aligned): sell a low-cost subscription to local governments/nonprofits, or charge implementation/support for pilots—avoid extractive fees on community participation.

Guardrails: publish scoring criteria, minimize data collection, and default to community ownership where possible (co-op/commons patterns).