Startup Weekend • 54-hour MVP blueprint

MeetingMint SEA

Seattle

Policy + Climate + Civic Tech

From meetings to commitments—track what government promised.

A tool that converts agendas/minutes into trackable commitments with owners, deadlines, and a public follow-up page.

Local fit: Utility + grid modernization needs, stormwater resilience, and a mix of dense neighborhoods and underserved areas—good for community networks and accountability tooling.

← Back to finalist list

Core user stories

As a resident, I see what commitments were made, by whom, and the promised timeline.
As staff, I assign an owner and update status (in progress / done) with notes.
As a journalist/advocate, I filter commitments by topic and export a weekly digest.

Clickable demo scope (what you build)

Paste minutes text → extracted commitments list (seeded sample).
Commitment detail page with owner, due date, status timeline.
Public dashboard with filters + export (CSV stub).

Team of four roles

Product & Policy Lead: Define ‘commitment’ schema and what counts as completion; pick 1–2 local meeting sources to seed.
UX / Frontend: Build commitment list + detail page + filterable dashboard; optimize for shareability.
Backend / Data: Implement minutes ingestion (seeded) + extraction rules; store commitments; enable exports.
Partnerships / Story / Ops: Validate with a journalist/advocate; craft accountability narrative; 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 Seattle).

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