Startup Weekend • 54-hour MVP blueprint

MobilityCoop DET

Detroit

Policy + Climate + Civic Tech

Shared vehicles that keep wealth local.

A cooperative scheduling and utilization dashboard for shared vans/EVs used by nonprofits and neighborhoods, built to support grant justification.

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 co-op member, I request a vehicle for a time window and see availability.
As an admin, I approve requests and track utilization and maintenance.
As a grant writer, I export utilization stats and equity impact notes.

Clickable demo scope (what you build)

Availability calendar + request flow (simple).
Admin approvals + maintenance log stub.
Utilization dashboard + export stub.

Team of four roles

Product & Policy Lead: Define cooperative membership rules, equity priorities, and a grant-ready impact metric set.
UX / Frontend: Build availability calendar + request + confirmation screens; design for mobile.
Backend / Data: Implement scheduling, approvals, and maintenance log stub; compute utilization.
Partnerships / Story / Ops: Validate with a nonprofit fleet manager; craft ‘shared asset’ 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 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).