3. Feature-by-Feature Scrutiny (The Catalog Idea's Features)
Categories:
- Table stakes (TS): customers expect it. It earns nothing, but its absence costs you.
- Differentiator (D): a real reason to choose you over the alternatives.
- Distraction (X): built but unlikely to move revenue or retention.
- Liability (L): creates support, compliance, legal or trust risk.
Each feature is judged twice: for the idea as described (kitchens), and for the recommended wedge (FSMA 204 records for small produce distributors).
3.1 Classification table
| # | Catalog feature | As described (kitchens) | For the wedge (distributors) | Reasoning |
|---|---|---|---|---|
| 1 | Auto-generated HACCP plan | TS / L | X (replaced by a traceability plan template: TS) | FoodDocs puts HACCP plan creation in its $199 Standard plan, and the FSA pack is free. A generated plan presented as authoritative is a liability if a hazard is missed. The FSMA rule needs a traceability plan, not a HACCP plan. A template the customer edits and signs is table stakes. |
| 2 | Daily temperature logs | TS | X | Every kitchen app does it, from £4.99 a month. The traceability rule doesn't ask for temperatures. |
| 3 | Cleaning logs | TS | X | Same. Commodity, and irrelevant to lot records. |
| 4 | Cooling logs | TS / weak D | X | Useful for cook-chill kitchens and commissaries, and paper handles it. Not part of the wedge. |
| 5 | Sensor feeds (Bluetooth or LoRa probes) | D for funded players / L for you | X / L | Navitas, Checkit, Jolt and ComplianceMate sell sensors with sales and support teams. For a small team, hardware means stock, pairing, gateways, batteries, returns and site visits. Sensors don't help lot traceability at all. |
| 6 | Inspector-ready reports | TS | D, as the FDA sortable spreadsheet | For kitchens, every app exports a PDF. For distributors, the regulator defines the output: an electronic sortable spreadsheet within 24 hours (F2). Making that one click from QuickBooks data is the product. |
| 7 | Mobile capture (implied) | TS | TS → D at receiving | Kitchens expect it. At a distributor's dock, scanning case labels or photographing a packing slip to capture lot codes is the step nobody makes cheap for a small warehouse. Build it as a web app that works on a phone (PWA), not store apps. |
| 8 | Corrective actions and alerts (implied) | TS | TS | For the wedge: alerts when a received listed-food line has no lot code, or a supplier never sends one. |
| 9 | Multi-site dashboard (implied) | TS for chains | P2 | Most target distributors have one warehouse. |
3.2 Scoreboard
| Category | As described | For the wedge |
|---|---|---|
| Table stakes | HACCP plan, temperature, cleaning and cooling logs, inspector reports, mobile capture, corrective actions, multi-site | Traceability plan template, missing-lot alerts, exports, audit log |
| Differentiator | None a solo founder can win (sensors are a differentiator only for funded players) | Receiving capture tied to QuickBooks bills; lot codes on invoice lines sent to customers; one-click FDA spreadsheet; monthly mock recall |
| Distraction | Cooling logs as a headline, multi-site before chains | Temperature, cleaning and cooling logs; sensors; HACCP plan generation |
| Liability | Generated HACCP plans; hardware | Any "compliant" claim; generated plans presented as authoritative; hardware |
As described, none of the catalog features is a reason to buy from a new vendor. For the wedge, only the inspector-report idea survives, transformed into the FDA spreadsheet.
3.3 Feature bloat and "building to avoid selling": explicit call-outs
- Sensors. They demo beautifully and make the product feel "real". They also turn a software business into a hardware logistics business, against vendors with installers and warehouses.
- The HACCP plan generator. It feels like the clever AI feature. It's where a missed hazard becomes your fault, and FoodDocs already ships it.
- Keeping kitchen logs "for later" in the distributor product. Distributors don't cook. Every hour spent there is an hour not spent on receiving capture.
- Consumer-facing traceability (QR codes on produce, farm stories). Nobody at a 20-person produce house pays for marketing to shoppers.
- EDI to large retailers. SPS Commerce and TrueCommerce own it, and your buyer rarely ships to Walmart directly.
3.4 What a disciplined v1 looks like
Keep: QuickBooks Online connection + phone receiving capture (scan or photo) + lot codes on invoice lines + customer data send (PDF and CSV) + one-click FDA sortable spreadsheet + traceability plan template + monthly mock recall. Defer: ReposiTrak and supplier CSV import (P1), broken-case and inferred-lot tools (P1, when FDA guidance lands), consultant multi-client console (P1), Xero (P2). Cut: temperature, cleaning and cooling logs; sensors; HACCP plan generation; EDI; consumer QR codes; native store apps.