7. What's Missing: The Gap Between Built and Paid, Renewed, Referred
Assumption: nothing is built yet. These are the gaps between the plan and a business, for the recommended wedge.
7.1 Gaps to pay
| Gap | Why it blocks payment | Fix |
|---|---|---|
| No defined buyer | "Food businesses" can't be priced or sold to | Produce distributors with 5–50 staff on QuickBooks Online, not on a produce ERP, in two or three US metro areas first. |
| No pricing | Undefined | Starter $149/mo (1 warehouse, ~300 listed-food invoice lines a month). Standard $249/mo (~1,500 lines, 2 warehouses, customer portal). Pro $449/mo (multi-warehouse, broken-case tools, consultant access). Annual = 10 months' price. Readiness sprint ~$1,000 one-off, credited against the first year if they sign annual. No free plan. |
| Price vs cheaper tools | FoodReady from ~$99, ReposiTrak from $59 | Don't compete on price. Compete on "the FDA spreadsheet comes out right from your QuickBooks, and your customers get lot codes on every invoice". Prove it in the sprint. |
| No quantified promise | "Traceability" doesn't justify a card on file | "Answer an FDA request the same afternoon. Mock recall under an hour. Lot codes on every invoice." Measure each one per customer. |
| Trust | Owners fear a tool that changes their books | Read-only QuickBooks access (plus a memo field), US hosting, full audit log, export everything at any time, delete on cancellation. |
| Liability fear | "If the trace fails, who's responsible?" | Clear terms: the customer owns the records and the plan. You provide the system. E&O insurance bound before the first paid account. |
7.2 Gaps to renew
| Gap | Fix |
|---|---|
| One-time compliance purchase | Anchor on weekly use: lot codes on every invoice and customer data sends. Add a monthly mock recall report. |
| Post-deadline drop-off | Annual billing tied to the calendar. Founding price locked through July 2028. A "customer requests answered" count in every monthly report. |
| A second federal delay | Sell on customer demand, not only the FDA date. The chains' requirements don't depend on Congress (F4). |
| Messy data erodes trust | Show gaps loudly (missing lots, unmatched lines). A weekly "data health" score. Never hide an incomplete record. |
| Rule changes | Ship FDA flexibilities within 2 weeks of guidance, and tell customers in plain English. |
7.3 Gaps to refer
| Gap | Fix |
|---|---|
| Nothing visibly shared | Every invoice PDF and customer data link carries a small "traceability records by [product]" footer. Customers of customers are other distributors' customers too. |
| No free hook | Free public tools: "Is my product on the Food Traceability List?" checker, the FDA sortable-spreadsheet template, and a traceability plan template. |
| No partner economics | Consultants get 20% revenue share for 12 months per referred account, or a discounted console for their clients. |
| No proof | A one-page case study per pilot: mock recall time before and after, and customer requests answered. |
7.4 Non-product gaps
Distribution
- Channels that fit: food-safety consultants who serve distributors; state produce associations and their newsletters; the Blue Book directory for prospect lists; founder-written guides answering the FDA's exact requirements; a booth at one regional produce event in 2027.
- Channels that burn cash: paid search against dozens of vendors bidding on "FSMA 204", and cold email to owners who live on the dock.
Positioning
- As described: "digital HACCP logs". Weak, generic, crowded.
- Better: "FSMA 204 records for produce distributors on QuickBooks: lot codes on every invoice, and the FDA spreadsheet in minutes."
- One sentence, one buyer, one outcome.
Sales motion
- Founder-led for the first 25 accounts: a call, a sprint, a done-for-you setup.
- Consultant-led after that: consultants run sprints and onboard clients, you support them.
- Self-serve only for Starter, from month 9.
Compliance and legal
| Area | Requirement |
|---|---|
| The rule itself | 21 CFR Part 1, Subpart S. Compliance date 20 July 2028. Keep the product aligned with FDA guidance as it lands (F1–F3). |
| Marketing claims | Never "compliant", "FDA-approved" or "recall-proof". Say "records organized and exportable". |
| Records integrity | Audit log of every change; records kept at least as long as the rule requires (two years, per the rule; re-check). |
| Data and privacy | US hosting, business records (little personal data), clear export and deletion. State privacy laws apply lightly. |
| QuickBooks | Intuit developer terms and App Partner Program. Fees for heavy API use are unverified. |
| Insurance | Technology E&O, and check that outbreak-related claims aren't excluded (unverified). |
Team
- Not provided. Minimum: one full-stack developer comfortable with the QuickBooks API and phone camera capture, and one person from the food-distribution trade (condition 1).
Metrics and instrumentation
- Activation: QuickBooks connected and first 20 received lines captured with lot codes within 7 days.
- Weekly: share of listed-food invoice lines carrying lot codes; customer data sends.
- Monthly: mock recall time; data health score.
- Business: M1/M3 retention, share on annual, accounts per consultant, CAC by channel.