Scale is coordination power.
Economies of scale are usually described as a production advantage: larger farms, buyers, warehouses, routes. That is true but incomplete. Scale also creates an information advantage: a centralized system can see, redirect, and absorb more activity than an isolated producer can.
Supply visibility includes
- Product quantity, location, quality or grade.
- Earliest and latest movement windows.
- Storage and handling requirements; substitutes.
- Expected buyer requirements; shortages and surplus.
Profit is not only the result of producing cheaply. It is the result of controlling optionality, and optionality reduces risk, which lowers financing cost and strengthens bargaining power.
Sources of advantage
Volume aggregation, cost spreading, buyer-facing simplicity, and market legibility are not separate wins. They compound: each tier makes the next cheaper to hold, until the stack itself becomes the moat.
Evidence note. The SBIR proposal frames the structural problem as fragmented farm-side data and buyer requirements remaining across incompatible systems and manual workflows.
Local supply is physically near but operationally fragmented.
A farm can be close to a grocery store, restaurant, school, or institution and still be difficult for that buyer to use. Physical proximity does not automatically become procurement reliability.
A buyer still needs to know
- What is available, when, and how much.
- Whether supply is reliable and meets specifications.
- Whether delivery can happen on schedule.
- Whether substitutions and documentation requirements can be met.
When sell-through is uncertain, farms may limit planting or stay within familiar direct-sales channels. That is not a lack of ambition. It can be a rational response to unsold-perishable downside risk.
Evidence note. The market analysis distinguishes total regional produce demand, localizable demand, feasible local supply, and recapturable friction, and reads the Summit County case as supply- and coordination-constrained rather than demand-constrained.
The visible price hides a delivered-cost stack.
Food prices do not only reflect the crop. They reflect the cost of moving, cooling, storing, packaging, financing, merchandising, documenting, and coordinating the product after it leaves the farm.
Delivered Cost = Production Cost + Delivered Overhead
Centralized agriculture often appears efficient because it is highly optimized around post-farm functions. A system can be efficient in one dimension and loss-heavy in another. The stronger claim is that some of those constraints create avoidable cost when local supply could satisfy demand through shorter channels.
Evidence note. The market-recapture article defines delivered overhead as all non-growing costs required to sell a unit (transport, handling, spoilage, coordination, payments, communications, scheduling), and the SBIR proposal frames post-farm marketing as a major part of the food-cost stack.
Adjacency is an advantage only when it becomes usable.
Local supply has a physical advantage: proximity. But a nearby farm that is invisible, unpredictable, or hard to verify remains operationally distant. Adjacency becomes valuable when supply is:
- Discoverable - buyers can see what exists.
- Schedulable - buyers can see when product can move.
- Aggregatable - multiple farms fill useful order sizes.
- Substitutable, auditable, repeatable.
Market recapture is not replacing the global food system. It is replacing the portion of nonlocal supply used only because nearby supply is too fragmented to order from reliably.
Evidence note. The market-recapture article defines local recapture as replacement of nonlocal supply when local goods become discoverable, schedulable, and competitively delivered, and holds that adjacency compresses delivered overhead rather than guaranteeing lower production cost.
Regional food systems have always needed shared interfaces.
Local food was never only informal. It depended on shared interfaces that made supply and demand visible: food terminals, market houses, auctions, cold storage, trust networks. The coordination function is old.
Modern models each solve a fragment: food hubs solve aggregation but carry high fixed costs; cooperatives solve shared identity but carry governance overhead; CSAs and farmers markets solve direct trust but leave institutional procurement unresolved.
The remaining gap
The unresolved product is buyer-side orchestration: the ability to source from fragmented local farms as if they were a legible, schedulable, auditable regional supply pool.
Evidence note. The competitive analysis identifies buyer-side local procurement orchestration as the strongest starting position, distinct from generic farm ERP, consumer discovery, or a universal data-language pitch.
Coordination requires shared operational meaning.
Data transmission is not interoperability. Two systems can exchange a file while still failing to share meaning: what the product is, what unit is used, what timing window applies, what substitutions are allowed.
Failure modes
- Schema drift and semantic drift.
- Adapter explosion - every pair of systems needs a custom translation.
- Stale availability and context loss.
- Centralized capture - one platform forcing everyone into its rules.
A schema-first, federated data layer can make local produce procurement legible enough to test coordinated sourcing.
Evidence note. The self-describing-grammar material separates transmission agreement from operational interoperability, and names schema drift, semantic drift, adapter explosion, mapping, and provenance as the core concerns.
The proposal reduces to a bounded feasibility question.
The central test is whether an open-source coordination framework can identify a local sourcing scenario where participating farms improve their position and buyers remain non-worse-off on delivered cost and service. The feasibility window is the overlap between the two.
Two implementation tracks
Track 1 · now
Agricultural coordination
Make fragmented farm supply legible enough to test whether stranded local value is recoverable. The scenario ladder:
- 01 Proof lane - narrowest useful supply-demand lane.
- 02 Single-hub routine - repeat purchasing, cadence.
- 03 County network - participation density, substitution.
- 04 Regional multi-hub - replication without a chokepoint.
Track 2 · coming
Food as medicine
The same coordination substrate, tested against a different demand signal. This track first establishes a medical need (a population whose health outcomes and care costs turn on nutrition access), then asks whether a healthcare organization, a food-aid program, and FND together can turn consistent, care-linked demand into reliable local-produce sourcing. The venture ladder:
- 01 Establish the need - a documented population where nutrition access moves health outcomes and care cost.
- 02 Care-linked demand - the healthcare organization and the food-aid program commit steady, prescribed produce volume.
- 03 Reliable local sourcing - FND's legibility layer routes that demand to schedulable, auditable local farms.
- 04 Four-way test - whether it improves nutrition access, program cost, and farm viability at once: a durable model, not a one-season pilot.
◇ conceptual: the parties are named by role, not identity; the venture is drafted, not yet run.
Evidence note. The SBIR proposal defines Phase I as an eight-month feasibility study: schema definition, prototype engine, bounded data collection, scenario simulation, and a feasibility decision. A negative result that identifies the binding constraint still counts as decision-grade evidence.
The good thing and the profitable thing can become the same thing.
Better food, lower cost, easier access, and stronger local economies do not need to remain separate hopes if the obstacle is coordination rather than value itself.
FND is called to the missing layer, making independent local supply legible enough to test whether stranded agricultural value can be recovered, building only where the two-sided window exists, and letting evidence decide whether to proceed, revise, or stop.
Where the software comes in
MiCyte does one narrow thing: it lets a farm keep its own records, structured and content-addressed, and gives the farm an address a registry can resolve. That is the substrate legibility needs.