Startup Weekend • 54-hour MVP blueprint

ShorelineReady East Bay

East Bay (Oakland / Berkeley / Alameda & Contra Costa)

Climate Adaptation + Capital Planning

Sea level rise decisions, prioritized by community benefit.

A shoreline adaptation prioritizer that maps assets and vulnerabilities and produces a short list of near-term projects with who-benefits narratives and funding-ready briefs.

Local fit: A long, multi-jurisdiction shoreline with critical infrastructure and vulnerable housing needs coordinated, transparent prioritization that communities can understand and influence.

← Back to finalist list

Core user stories

As a planner, I can compare two simple scenarios and see which assets and neighborhoods rise to the top.
As a resident, I can view what’s at risk near me and what solutions are being considered in plain language.
As a grant writer, I can export a one-page project brief (problem, beneficiaries, cost range, timeline) for a top-ranked project.

Clickable demo scope (what you build)

Clickable flow: pick shoreline segment → choose scenario slider → view ranked projects → export project brief.
Seed 1–2 shoreline segments with mocked assets (parks, roads, wastewater, housing) and risk scores.
One funding-ready artifact: project brief page with printable styling and placeholder cost ranges.

Team of four roles

Product & Policy Lead: Define scenarios, scoring, and the ‘who benefits’ narrative template.
UX / Frontend: Build map + scenario slider + ranked list + project brief layout.
Backend / Data: Implement ranking logic and data model; seed assets; generate exportable briefs.
Partnerships / Story / Ops: Interview 1 shoreline advocate + 1 agency staffer; craft the pitch around transparency + speed to funding.

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 East Bay (Oakland / Berkeley / Alameda & Contra Costa)).

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