Cooperative Development Toolkit
Practical references for communities that want to launch or formalize a cooperative around urban agriculture and local food distribution.
Who this is for
Resident associations, mutual-aid kitchens, community gardens, and small producer groups that are ready to write down how decisions get made before money or equipment shows up. If you are only shopping for a robot and do not yet have a circle of people who can maintain it, start with the Budgets page—then return here when you need shared ownership language.
Quick start checklist
- Map the network. Document growers, buyers, mutual-aid groups, and distribution partners before inventing new structure.
- Define participation tiers. Clarify how worker-owners, supporters, and institutional allies contribute labor, capital, and decision rights.
- Run the first member survey. Capture goals, risk tolerance, governance preferences, and scheduling realities before drafting bylaws.
- Pilot a single service. Start with one shared function and expand only after it is documented and cash-flow positive.
Templates and references
| Resource | Why it matters |
|---|---|
| Cooperative bylaws outline | Provides a starting point for decision rights, quorum rules, and dispute resolution. |
| Member equity worksheet | Helps model how sweat equity, dues, and grants convert into ownership units. |
| Meeting facilitation guide | Keeps early meetings focused when roles are still fluid. |
| Exit and succession checklist | Clarifies how capital is returned when members leave or new stewards join. |
Automation, telemetry, and trust
Shared farms that add sensors or CNC beds introduce new questions: who can see yield data, who is on-call when a sequence fails, and how vendors fit into member equity. Address these before install day.
- Data custody — Name the steward for logs (soil moisture, water use, camera stills) and whether aggregates may leave the co-op.
- Maintenance rotations — Tie physical upkeep to documented shifts so “the tech person” does not become an unpaid single point of failure.
- Vendor boundaries — Spell out which repairs stay in-house, which require OEM support, and how those costs flow through the cap table.
Pair governance with numbers
Co-ops still have to pass a spreadsheet test. Use the Modular pilot budget template alongside these bylaws conversations, and read the full Track 01–03 budget narrative when you pitch neighbors or funders. The Engine page is a lightweight storyboard for sequencing automation if you need a visual anchor in a meeting.
External reading
- USDA Cooperative Research — case studies on food co-ops and producer-controlled distribution.
- UW Center for Cooperatives — governance and capitalization primers.
- ICA Principles — shared language for cooperative identity.
How to use this toolkit
- Copy the templates into your own planning docs or shared drives.
- Document every experiment, even failed ones, next to the template you borrowed.
- When you discover a better pattern, share the learning so future teams can build on it.
Johnny Autoseed treats every resource as living documentation. If you remix this toolkit, attribute the source and keep useful derivatives open where you can.