Skip to content
Idea AtlasSign in

KitchenLog

As described:StopNarrowed:Narrow

No as described, and No as a UK care-home kitchen log. Go, small and conditional, for FSMA 204 with food-distribution trade access.

food distribution · ~$200 per distributor per month · last reviewed (next review by 29 Dec 2026) · 36 cited sources

Save
Share

← All research

5. Pre-Mortem: It's September 2028 and KitchenLog Is Dead

Three most likely causes of death for the recommended wedge, ranked by probability. They compound: #3 usually makes #1 worse.


Cause #1: Nobody needed a new vendor (probability ~40% of failure cases)

What happened. The founder built a clean receiving-to-invoice flow and a perfect FDA spreadsheet. Then the calls went like this:

  • "We're on Famous. They handle it."
  • "Our suppliers are on ReposiTrak, and it's free for us."
  • "Our consultant set us up with FoodReady for $99."
  • "We'll deal with it in 2028."

The distributors who were left, on QuickBooks with no system, were the smallest and least organised. Many were too small to care until a customer forced them. By month 18 there were 22 accounts, mostly on the Starter plan.

Early warning signs

  • Fewer than 5 paid readiness sprints by day 60.
  • More than half of discovery calls name an existing tool (ERP, ReposiTrak, FoodReady).
  • Prospects ask for inventory, ordering or routing, which means they want an ERP, not a records tool.
  • Trial users never connect QuickBooks.

Fixable? Partly. Move to consultants as the buyer (pivot A), or to another listed-food category with less ERP coverage, such as seafood or shell eggs (pivot B). You can't fix it if the QuickBooks-run segment turns out to be small. Find that out in the first 60 days, not the first 12 months.


Cause #2: The date moved, or the rule softened (probability ~35%)

What happened. In autumn 2027 the FY2028 appropriations bill carried another rider pushing enforcement back, or the FDA's flexibilities for broken cases and inferred lot codes turned out so generous that a spreadsheet kept by hand was "good enough". Buyers who were planning to start in early 2028 stopped. Existing customers on monthly plans cancelled. The pipeline for the pre-deadline rush, which the whole revenue path depended on, emptied.

Early warning signs

  • Trade press or associations lobbying for a further delay in 2027.
  • FDA guidance that allows inferred lots without supporting records.
  • Prospects saying "let's wait and see what Congress does".
  • A rise in monthly-plan cancellations after any FDA announcement.

Fixable? Partly. Annual billing buys a year. Selling on customer demand (chains and grocers asking for lot data, F4) rather than on the FDA date makes the product useful with or without enforcement. You can't fix a market that only buys under a deadline once the deadline goes away. The first delay came through an appropriations rider (F1); that route is still open.


Cause #3: No way in (probability ~25%)

What happened. The founder didn't know anyone in produce distribution. Search results for "FSMA 204" were owned by vendor blogs (Famous, FoodReady, ReposiTrak, TrueCommerce, Nulogy and a dozen others). Cold emails to produce houses went unanswered, because the owners are on the dock at 4am and don't read email. Associations were polite but wanted sponsorship. By month 9, the pipeline was the founder's LinkedIn contacts.

Early warning signs

  • No advisor from the trade signed by day 30.
  • Fewer than 10 distributor calls booked in the first month.
  • Every lead comes from search, and converts below 2%.
  • No consultant refers a client in the first 6 months.

Fixable? Yes, early. Pay for access: an advisor with equity, a consultant partnership with revenue share, an association booth. After 9 months of trying cold, it's usually too late for this deadline.


Honourable mentions (less likely, still real)

  • Outbreak liability. A customer's trace fails during a real outbreak, and the lawyers read your marketing. Never claim compliance; keep E&O insurance; keep an audit log.
  • Data quality. Receiving staff skip the scan, lots are guessed, and the FDA spreadsheet is wrong. The product must refuse to hide gaps, and show them loudly.
  • Platform dependence. Intuit changes QuickBooks API terms or fees (unverified exposure). Keep the data model independent of QuickBooks so a Xero or CSV path exists.
  • An incumbent adds a QuickBooks distributor flow. FoodReady or ReposiTrak ships the same thing at $59–$99. Speed and a trade reputation are the only defence.

For the idea as described (kitchen logs)

The pre-mortem is short: death by price. The product launches at £20–$50 a site, competes with £4.99 apps and free paper, adds sensors to stand out, drowns in hardware support, and churns restaurants that close or switch. That's why it isn't the recommendation.