ToolLoop MPLS

Minneapolis

Policy + Climate + Civic Tech

Share tools, cut costs, strengthen neighborhoods.

A lending-library platform for community tool sheds with scheduling, deposits, and simple trust scoring.

Local fit: Heat and winter resilience, neighborhood-based organizing, and a strong ecosystem of mutual aid and tool libraries—good for offline-first and community infrastructure tools.

← Back to finalist list

Core user stories

As a member, I reserve a tool and see pickup/return instructions.
As a librarian/volunteer, I check items in/out and flag repairs.
As a coordinator, I view utilization to justify new purchases and grants.

Clickable demo scope (what you build)

Inventory page with categories + reservation flow.
Admin check-in/out page (simple).
Utilization dashboard with top items + waitlists (seeded).

Team of four roles

Product & Policy Lead: Define membership rules, deposits, and repair workflows; write a governance model that supports a commons.
UX / Frontend: Build inventory browsing and reservation flow; design check-in/out screens for volunteers.
Backend / Data: Implement inventory + reservations + utilization stats; seed sample items.
Partnerships / Story / Ops: Validate with a tool library; craft local circular-economy narrative; 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 Minneapolis).

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