💡 Cottage Food & Year-Round Producer Discovery Channel

[github-actions[bot]]

Summary

Extend Markets beyond market-day-only visibility by letting cottage food producers (home bakers, jam makers, picklers) and farm-stand operators maintain always-on profiles that customers can discover between market days. These producers are the fastest-growing segment of local food but are nearly invisible outside of market hours and Facebook groups.

Market Signal

The cottage food sector is experiencing explosive growth — Butterbase, Cottage CMS, Homegrown, and FindHomegrown have all launched or expanded purpose-built platforms in 2025-2026. State-by-state cottage food laws are expanding rapidly (Butterbase published a 2026 state-by-state legal map). FindHomegrown.com notes that "many outstanding local food producers were difficult, and sometimes impossible to find outside of market days." Yet none of these cottage food platforms provide the multi-actor coordination that Markets offers — they're isolated storefronts, not connected ecosystems. The Cottage Food Platform Comparison (2026) shows a fragmented landscape ripe for consolidation.

User Signal

The PRD's vision section mentions "multi-city and multi-state rollout" and "cross-market comparison" — extending beyond market-day to year-round producer discovery is a natural expansion of the platform's network effects. Rachel (customer persona) doesn't stop wanting local food on non-market days. Several existing ideas touch adjacent territory: Discussion #362 (Seasonal Produce Discovery), #388 (Market-to-Table Recipe Discovery), #468 (Market Visit Memory & Seasonal Re-Buy Reminders) — but none address the year-round producer discovery gap between market days.

Technical Opportunity

The vendor profile (FR11) and product catalog (FR12) data models already support listings independent of market-day context. The key extension is a new producer type (cottage_food / farm_stand) alongside the existing vendor role, with an always_visible: boolean profile flag. The GraphQL schema's domain-split design (vendor domain) makes this a clean extension. Customer discovery (FR21-23) search already supports product-based and location-based queries — cottage food producers would appear in the same results with a distinctive badge.

Assessment

Dimension	Score	Rationale
Feasibility	med	Requires producer type extension, compliance data modeling (cottage food laws vary by state), and discovery UX updates
Impact	med	Expands addressable market; strengthens customer retention between market days; feeds network effects
Urgency	low	Post-MVP growth feature; core market-day coordination must ship first

Adversarial Review

Strongest objection: This is scope creep beyond the core market-day coordination mission. The PRD explicitly positions Markets as a market-day coordination tool, not a general local-food marketplace. Adding cottage food producers dilutes the focused value proposition and competes with purpose-built cottage food platforms.

Rebuttal: The extension is carefully scoped: cottage food producers get profiles and discoverability, not the full market-day coordination workflow (no check-in, no real-time status). They're a new supply-side node that feeds the same demand-side audience. Many cottage food producers ARE farmers market vendors who want year-round customer relationships. This is about retention — keeping Rachel engaged between market days — not about becoming Shopify for jam makers. Explicitly deferred to post-MVP as a Growth Feature.

Suggested Next Step

Research state cottage food law variations to understand what compliance data the platform would need to surface. Design the producer profile type extension and the customer discovery integration points. Validate with 3-5 cottage food producers who also sell at farmers markets.