Startup Weekend • 54-hour MVP blueprint

Blight2Build DET

Detroit

Policy + Climate + Civic Tech

Vacant lots to community assets—tracked, permitted, and funded.

A map + workflow that helps groups propose reuse projects (gardens, solar, tiny parks), track approvals, and source reclaimed materials.

Local fit: Housing and infrastructure repair, affordability, neighborhood-led redevelopment, and connectivity gaps—good for navigators, cooperative mobility, and blight-to-asset workflows.

← Back to finalist list

Core user stories

As a neighborhood group, I propose a lot reuse project with a simple intake form and map pin.
As a reviewer, I see required approvals and can request changes.
As a builder, I source reclaimed materials through a linked listing feed.

Clickable demo scope (what you build)

Map → propose project → status timeline.
Approval checklist page with ‘next step’ guidance (mock).
Materials tab showing sample reclaimed inventory (seeded).

Team of four roles

Product & Policy Lead: Map the approval steps and define the minimal ‘project intake’ schema; set anti-displacement guardrails.
UX / Frontend: Build map-based project proposal and status timeline UI; design the “next step” guidance.
Backend / Data: Store proposals and checklist steps; seed sample reclaimed materials feed.
Partnerships / Story / Ops: Validate with neighborhood org; craft ‘vacant to value’ story; 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 Detroit).

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