Partner Review

Please REVIEW the questions, needs, and technical approach that I heard. Are they correct, incorrect? Could we add clarity or nuance? Let us know!

These statements will determine the solutions we focus on, so this review is very important! Thanks for your help!

HIT SUBMIT when you're done.

Name

Feedback

ID	Questions List	Need Statement	Technical Approach Notes
1101	What are the biggest pain points with managing order cycles in OFN?	As a hub manager, I need OFN order cycles to open automatically on a recurring schedule so I can prevent the store from accidentally going dark when I forget to manually create and open a new cycle each week. [D:DIRECT] [P:5] [S:UNMET]	Sara described forgetting to open her order cycle and only discovering it when trying to show a new farmer the store — 'My damn store was closed. I forgot to open it this week.' She currently creates a new order cycle manually each week. Her proposed solution: auto-recurring order cycles that open on a schedule (e.g., every Sunday morning, close Thursday night) without manual action, while still being editable after auto-open. Quote: 'If you could set up a rolling order cycle that would open even if it didn't have the new products that were added... oh my God. Would that be amazing?' This is a distinct need from notifications — it addresses the base operational reliability problem. Low-effort OFN feature addition (scheduled open/close on repeating interval).
1103	How does farmer payment tracking work, and what is the pain point with marking farmers paid?	As a hub manager, I need to mark individual farmers as paid within OFN — including recording a payment reference number — so I can maintain accurate, auditable payout records without relying on external notes or memory. [D:DIRECT] [P:5] [S:UNMET]	Sara identified this as one of her biggest pain points. OFN payout reports don't show whether a farmer has been paid, don't include dates, and don't identify which order cycle they cover. 'It doesn't even have a date on it. It doesn't say this is from October 1 to October 30... I don't know, maybe I've double paid, maybe I've not paid farmers.' She wants a 'mark as paid' checkbox alongside a field for check number or Zelle reference. 'It would be nice if I could mark when I paid my farmer... and also put a [check] number next to it so that I can reference what check did I pay them with.' Miro board lists this explicitly: 'Cannot mark if farmer was paid — loses trust with farmers.' Cross-confirmed with Jane Jewett's interview (order status tracking need). A simple payment status field and reference number on the producer payout record would resolve this.
1106	How do producers manage their inventory on OFN, and what percentage are actively self-managing?	As a hub manager, I need an automated weekly reminder sent to farmers prompting them to update their product inventory so I can reduce the number of stale or zeroed-out listings without manually texting or emailing every farmer before each order cycle. [D:DIRECT] [P:5] [S:UNMET]	Sara described a consistent cycle: farmers don't update their inventory unless she prompts them, and stale listings lead to buyers ordering products that aren't available — 'there's nothing worse than fighting, fighting, fighting for an order, and then finally getting an order and being like, yeah, you just ordered peas. And it's September, that fucking farmer didn't update anything again.' She estimated that most producers don't update inventory unless she emails or texts them. Some have explicitly opted out: 'Zero it all out. Text me if you need something.' Her proposed solution: an automated weekly reminder (text preferred) sent from OFN to farmers before the order cycle opens. This would shift the cognitive burden from the hub manager to an automated system. Cross-confirmed by findings from Jane Jewett (Aitkin, Grand Rapids context) and Allison Rian.
1107	How do producers manage their inventory on OFN, and what percentage are actively self-managing?	As a hub manager, I need to update product inventory on behalf of farmers directly in OFN — quickly and from a mobile device — so I can keep listings current from farmer texts without requiring farmers to log in. [D:DIRECT] [P:5] [S:UNMET]	Sara described managing dummy producer accounts for 10–15% of farmers who won't or can't use OFN at all (Hmong farmers with language barriers, Amish farmer with no internet, large commercial producers). Even among connected farmers, most rely on Sara to translate their text messages ('I have 200 lbs carrots this week') into OFN inventory updates. She estimated roughly half her working time goes to OFN management and spreadsheets rather than relationship-building. Quote: 'I have to translate that text into an OFN inventory update.' The key need is a fast, minimal-click interface for proxy entry — hub manager selects farmer, selects product, enters quantity — preferably mobile-optimized. Paired with the Jane Jewett finding (row 1085) that delegated farmer account management is 'actually a good thing' and should be the promoted workflow, not a buried permission.
1108	How does the market share box (multi-farm CSA) program work, and what makes it difficult to manage?	As a hub manager running a multi-farm CSA (market share box) program, I need a platform-based tool to plan box contents, record farmer commitments, track fulfillment across multiple distribution channels, and confirm pickup — so I can stop managing 4 simultaneous spreadsheet tabs for a single weekly program. [D:DIRECT] [P:5] [S:UNMET]	Sara described managing four simultaneous CSA box distribution channels (LFPA boxes, Pine Island school staff, Wabasha Farmers Market, on-site market boxes), each with different frequencies, pickup mechanisms, and farmer commitments. She shared a spreadsheet showing each channel as a separate tab with line items per farmer, quantities, costs, invoice status, and payment confirmation. The process: she texts each farmer to confirm weekly availability, manually assembles box contents, tracks fulfillment per channel. 'There's got to be an easier way... How can this be easier?' Neither OFN nor any current platform supports this multi-farm, multi-channel CSA coordination workflow. CSA management without spreadsheets is a universal finding across interviewees (Candace, Jane, Sara). Miro board identifies this as a key operations pain point.
1112	Tell me about the Red Wing Farmers Market Food Hub — how does it operate, what do you do, and what is your role?,What is the 'elbow bumper' concept and how does it relate to the hub's biggest operational constraint?	As a hub manager working at 20% FTE, I need administrative tasks (OFN management, spreadsheet maintenance, farmer text follow-up) to be significantly reduced so I can redirect the freed time toward buyer relationship-building ('elbow bumping') that directly drives sales. [D:DIRECT] [P:5] [S:UNMET]	Sara introduced the concept of 'elbow bumpers' — the consistent, relationship-driven buyer outreach that national distributors do through dedicated sales reps, but that food hub managers can't afford to staff. The core constraint: at 20% FTE, the hub manager's time is finite. Platform administration (OFN order cycles, spreadsheets, texting farmers for inventory) crowds out sales-generating relationship work. Sara estimates roughly half her working time goes to admin rather than outreach. Greg's framing confirmed by Sara: 'If you could reduce [admin time] by 10 or 20%, that's 10 or 20% more relationships you can focus on... elbow bumping you can do.' Miro board labels this 'efficiency of hours' as the top strategic need: 'if they get more done in their limited time, they can grow. Relationships and trust-building are critical but get crowded out by admin.' All OFN automation improvements (recurring order cycles, farmer reminders, mark-as-paid, etc.) feed into this meta-need.
1113	What is the 'elbow bumper' concept and how does it relate to the hub's biggest operational constraint?,What do wholesale buyers say are the biggest barriers to buying local, and how does the hub address them?	As a wholesale food hub manager, I need a way to consistently reach wholesale buyers (schools, restaurants, hospitals) with product availability information — through regular, low-friction outreach — so I can build the habitual purchasing relationship that national distributors achieve through dedicated sales reps. [D:DIRECT] [P:5] [S:UNMET]	Sara described wholesale buyer barriers directly from buyer feedback: they can't find farmers, don't know how to place orders, don't understand pricing, and are accustomed to Sysco/Bix workflow (one order, one invoice, one delivery). The solution she describes is consistent relationship-based outreach — 'We are here, we are here, we are here' — combined with a friction-free ordering experience. This is both a communication/marketing need and a platform need. The Miro board lists this as the top finding: 'Biggest need for hub to make sales: consistent buyer outreach / elbow bumping.' Technically: automated buyer email/text with weekly availability list (fresh sheet), a mobile-first ordering experience, and ideally an account manager-style CRM for tracking outreach. Cross-confirmed with Jane Jewett ('electronic elbow bumping') and Arlene Jones (buyer relationship investment).
1114	What are the challenges with institutional and school buyers, including advance ordering and grant compliance?,What do wholesale buyers say are the biggest barriers to buying local, and how does the hub address them?	As a wholesale buyer purchasing from a local food hub, I need a one-stop, one-invoice, one-delivery ordering experience comparable to Sysco or Bix so I can integrate local food purchasing into my existing procurement workflow without new complexity. [D:DIRECT] [P:5] [S:UNMET]	Sara quoted buyers directly: 'They're so used to going online with Bix and Cisco, which is the easy way to place your orders. They can have one order, one invoice, one delivery. We want to make it similar to a Bix and Cisco system.' This is distinct from individual hub operational needs — it is a buyer-side experience requirement that shapes what hub platforms must deliver. Key components: consolidated ordering across multiple farms/products, a single invoice, reliable delivery on a known schedule, and a mobile-friendly interface. One nuance Sara raised: not all wholesale buyers want large bulk quantities — some want small, flexible orders (1 lb spinach vs. mandatory 4-lb case from Sysco). This means the solution must support flexible quantity ordering, not just bulk. Relevant to OFN and LFM platform design priorities.
1143	What are your specific pain points with Open Food Network?,What are the biggest pain points with managing order cycles in OFN?	As a Hub Manager, I need OFN to support automated recurring order cycles that open and close on a defined weekly schedule without requiring manual creation each cycle so my store doesn't accidentally close or require repetitive weekly setup. [D:DIRECT] [P:5] [S:UNMET]	This is the single most consistently requested OFN platform feature across all OFN-using hubs in this study. Allison Rian: 'If I need an order cycle every week, it's open at the same time, closes at the same time every week — just have the system do it.' Sara George: 'My damn store was closed. I forgot to open it this week.' Sara's proposed solution: set a rolling order cycle template (define open/close days and times) that auto-activates without manual action, while still being editable (toggle items on/off after auto-open). Implementation path: a cron-based schedule on the order cycle object in OFN, with an optional notification hook when producer inventory changes. Domain Expert framing (Sara's direct operational pain) used; Technologist perspective adds the auto-open + notify model. This is a known OFN development priority with funding barriers.
1145	How do you spend your time? Where does your 20–25% FTE actually go?,What is the farmer inventory management process, and what are the pain points around it?,How do producers manage their inventory on OFN, and what percentage are actively self-managing?	As a Hub Manager, I need an automated weekly inventory prompt sent to producers (via SMS, email, or simple web form) so I can collect availability for each order cycle without manually contacting each farmer. [D:DIRECT] [P:5] [S:UNMET]	This is one of the most time-consuming manual tasks across all small hubs: hub managers spend 30-50% of their time texting and calling farmers to find out what is available each week. Allison Rian (Technologist): automated SMS or email inventory prompts with a simple reply interface. Sara George: 'If that could automatically go to the farmers, there's nothing worse than fighting, fighting, fighting for an order, and then finally getting an order and being like, yeah, you just ordered peas. And it’s September, that fucking farmer didn’t update anything again.' The solution has two parts: (1) a scheduled automated message to producers on a hub-manager-defined schedule (e.g., every Friday for weekly CSA; every Monday for wholesale); (2) a friction-minimal interface for farmers to respond — ideally SMS-reply with simple keywords, a single-click web form, or even WhatsApp. Jane Jewett confirmed this is universal, not specific to Amish/Mennonite farmers. Allison narrowed to her most reliable farmers as a coping strategy, reducing supply diversity. Iowa Food Hub addresses this by having farms send formatted availability emails, which is a different model that requires training.
1102	What are the biggest pain points with managing order cycles in OFN?	As a hub manager, I need OFN to notify me when a farmer adds a new product to their storefront so I can include it in the current order cycle without manually checking every farmer's listings each week. [D:DIRECT] [P:4] [S:UNMET]	Sara described checking all farmer listings as a manual step every time she opens a new order cycle: 'I have to every single time I open an order cycle, I have to remember, hey, double check. Make sure nobody added anything new.' A notification (email or in-app) triggered when a producer adds or edits a product listing would eliminate this manual scan. Ideally paired with a one-click 'add to current order cycle' action from the notification. This is consistent with findings from other hub managers (Allison, Candace) who also manage producer listings on behalf of farmers or check for updates manually.
1104	How does farmer payment tracking work, and what is the pain point with marking farmers paid?	As a hub manager, I need OFN payout reports to include order cycle date ranges and report generation dates so I can identify which period a report covers without reconstructing this information from external records. [D:DIRECT] [P:4] [S:UNMET]	Sara described a specific frustration: OFN payout report PDFs have no date and no order cycle identifier. If she changes the order cycle view at all, the context is lost. 'It doesn't even have a date on it. It doesn't say this is from October 1 to October 30... if you change your order cycle at all or anything, it doesn't show order cycles.' The Miro board explicitly lists 'Dates on reports: payout reports need order cycle dates and date ranges' as a top OFN need. This is a minimal change — adding report generation date and order cycle name/date range to payout report headers — but high impact for financial reconciliation and audit trails. Pairs with the mark-as-paid feature need.
1105	How does farmer payment tracking work, and what is the pain point with marking farmers paid?	As a hub manager, I need to initiate farmer payments directly from within OFN — selecting which farmers to pay and confirming payment — so I can eliminate the need to reconcile between OFN reports, a separate payment app (Zelle), and an accounting tool (Wave). [D:DIRECT] [P:4] [S:UNMET]	Sara mentioned that OFN started a trial of a farmer payments feature but she hadn't seen it implemented. Her vision: 'If we could pay our farmers direct out [of] OFN and select the items and say, let's pay these farmers now, holy, that'd be amazing.' Currently: OFN generates payout report → Sara manually reconciles in Wave → pays via Zelle or check → no record in OFN that payment occurred. A direct payment integration (ACH, Stripe payouts, or similar) would collapse 3–4 steps into 1. Even a payment workflow that records payment intent and confirmation within OFN (without moving money) would address the tracking gap. This is a higher-effort feature than mark-as-paid but directly addresses the trust and double-payment risk Sara described.
1109	What are the challenges with institutional and school buyers, including advance ordering and grant compliance?	As a hub manager serving institutional buyers, I need a platform mechanism for buyers to place advance orders months ahead of the growing season so I can secure school and hospital purchasing commitments before products are available. [D:DIRECT] [P:4] [S:UNMET]	Sara described schools as planning their food purchasing in February for September–November delivery: 'They meet and make their plans in February. They need orders for August, September, October, November.' Current OFN order cycles only support orders within a current active window — there is no concept of a future-dated or pre-season commitment. She tracks these on separate spreadsheets. A 'pre-order' or 'forward contract' layer would allow institutional buyers to commit to quantities at the beginning of a season, give hub managers visibility for sourcing, and provide farmers with enough lead time for production planning. Cross-confirmed with Anna Richardson (The Good Acre) who uses seasonal contracts with farmers for similar reasons. This is a structural feature gap across OFN and LFM.
1111	What is the hub-to-hub sales challenge, and how is the markup stacking problem being addressed?,What would it look like for all MN hubs to use the same platform, and what would inter-hub product sharing require?	As a hub manager, I need a platform-supported mechanism for hub-to-hub product sharing with automatic percentage-based markup application so I can sell products sourced from other hubs without manually adjusting prices or managing two separate invoicing relationships. [D:DIRECT] [P:4] [S:UNMET]	Sara demonstrated OFN's enterprise permissions system live — showing how one hub could technically add another hub as a supplier and selectively include their products in an order cycle. The key barrier at scale: each individual farmer on Hub A must explicitly grant access to Hub B — impractical for 20+ farm networks. Sara's vision: 'If we were all using the same platform, you can easily add other hubs to the platform on the backside, and you can choose which products from those hubs to put on your platform. And if you can add percentages to the platform, you can apply markup automatically.' Markup stacking is the economic problem: if Hub A and Hub B both need a margin, the final price to a school becomes uncompetitive. A platform-managed inter-hub markup layer — where Hub A sets a markup, Hub B applies their own, and the system tracks both — would make hub-to-hub commerce viable. Iowa Food Hub has pursued this using spreadsheets and physical node infrastructure as a workaround.
1116	How does the node-based pickup and distribution system work for wholesale orders?,What is the hub-to-hub sales challenge, and how is the markup stacking problem being addressed?	As a hub manager, I need a distributed node-based physical pickup infrastructure so I can collect pre-sold wholesale orders from multiple farms on a single driver route without visiting each individual farm. [D:DIRECT] [P:4] [S:UNMET]	Sara described the Red Wing hub's node system for wholesale (Wednesday) distribution: nodes are physical pickup points — either a farm with refrigeration or a standalone walk-in cooler placed at a strategic location with a hidden key. Farmers drop off pre-sold orders by 8–9am Wednesday, then a single driver picks up from the nodes rather than visiting each farm. This reduces route stops and enables efficient product aggregation. The hub is also mapping routes for hub-to-hub transport nodes connecting southern and northern MN hubs, modeled after Iowa Food Hub's node network. Iowa found nodes require $1,500–$2,500 per trailer to be economically viable plus grant support for mileage. Technology role: node inventory tracking, route optimization, drop-off confirmation notifications. Physical infrastructure (refrigerated units) is the primary requirement; software support is secondary. Cross-confirmed with Jane Jewett's distributed cold storage infrastructure need (row 1096).
1141	Why did you switch from Locally Grown to Open Food Network, and what happened as a result?,What is your current bookkeeping and financial administration workflow, and what are the pain points?,How does farmer payment tracking work, and what is the pain point with marking farmers paid?	As a Hub Manager, I need an automated vendor payout calculation and payment system integrated with my sales platform so I can pay producers accurately after each order cycle without manually computing each payment from reports. [D:DIRECT] [P:4] [S:UNMET]	OFN currently lacks a native vendor payout automation feature. The Domain Expert need is to eliminate manual calculation from OFN reports; the Technologist framing points to automated payout calculation and disbursement via Stripe Connect or ACH. An intermediate solution: an n8n workflow triggered on order cycle close that splits revenue by vendor, calculates the hub fee, and pushes a payment summary to the hub manager with optional direct payment integration. A 'mark as paid' feature with payment reference and date (check number, Zelle confirmation) would be a minimal viable solution; full OFN-native payment integration would be the complete solution. Emily Ricks built partial Python automation to address this; Sara George relies on Zelle + manual reconciliation. Confirmed as a universal gap across OFN hubs.
1144	What are your specific pain points with Open Food Network?,What are the biggest pain points with managing order cycles in OFN?	As a Hub Manager, I need the platform to send me a notification when any producer in my hub adds or updates a product in their catalog so I can keep my order cycles current without manually auditing each cycle. [D:DIRECT] [P:4] [S:UNMET]	Sara George (Domain Expert): 'I have to every single time I open an order cycle, I have to remember, hey, double check. Make sure nobody added anything new.' Sara's ideal: a notification (email or in-app) when a farmer adds a new product. Allison Rian also raised the related issue (row 141): if a farmer updates inventory for a product not in the current order cycle, the hub manager never gets notified, and if a product with zero inventory gets restocked it can pop up on the storefront unexpectedly. Implementation: a change-event listener on the product catalog tied to hub relationships in OFN, triggering an email/in-app alert to the hub manager. This is a relatively straightforward backend addition but requires the event listener architecture to be in place.
1148	What else should a hub management platform do to support hub managers in managing product availability and buyer outreach?,Will buyers (restaurants, school food service) ever log into a platform to order? What does it take to get buyer engagement?,What additional insights emerged from the Miro board analysis about Red Wing's hub operation, finances, and network context?	As a Hub Manager, I need an automated fresh sheet generation tool that pulls current producer availability from the platform and formats it as a buyer-facing product list so I can distribute it via email or text without manually compiling it each week. [D:DIRECT] [P:4] [S:UNMET]	Jane Jewett described hub managers spending significant time each week pulling product availability from producers, formatting it, and distributing to buyers. An automated 'fresh sheet' generator could query OFN catalog data at cycle-open time, format a readable product list (PDF or HTML email), and send to a buyer distribution list. Integration points: OFN API for available products per cycle, email/SMS distribution (n8n or MailChimp), configurable template per hub.
1199	How does farmer payment tracking work, and what is the pain point with marking farmers paid?	As a Hub Manager, I need the platform to track producer payment status per order cycle (marking each producer as paid with reference number and date) so I can confirm all payouts are complete, audit payment history, and provide producers with transparent payment records. [D:DIRECT] [P:4] [S:UNMET]	Sara described maintaining a manual payment tracking log outside OFN to record when each producer was paid, by what method (Zelle, check), and what the reference number was. OFN and most hub platforms generate payout calculations but do not track actual payment execution. A payment tracking module in OFN would allow: marking a payout as paid, logging payment method and reference, generating a producer-facing payment confirmation, and providing an audit trail for accounting. Integration: OFN payout reports → payment status tracker → producer notification.

Made with