3. Feature-by-Feature Scrutiny (the Idea's Stated Features)
The idea names four record types plus a promise: jobs, inspection or compliance logs, equipment and rental inventory, crew scheduling, replacing spreadsheets and paper. Each is classified below for the chosen trade (portable fire-extinguisher inspection and service).
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.
Some features sit in two buckets. The primary bucket comes first.
3.1 Classification table
| # | Stated feature | Category | Reasoning |
|---|---|---|---|
| 1 | "A system of record for one trade" (positioning) | D, only once the trade is named | The thesis is right: records that a shop is legally required to keep are sticky, and IDC argues systems of record are harder for AI agents to displace. But "one trade" unnamed is "any trade", which is L: it's Jobber's market. Name it: "the system of record for extinguisher service shops". |
| 2 | Jobs (work orders, visits, status) | TS | Every tool has jobs: Jobber, Housecall Pro, FireInspected, ServiceTrade. Needed, but nobody switches for it. Make the job a view on the asset register, not the core record. |
| 3 | Inspection and compliance logs | D (the core) | This is the product. In this trade a "log" means each extinguisher's history: type, size, manufacture date, location in the building, each annual check, 6-year maintenance, 12-year hydro test, and every deficiency with a photo. Generic checklist apps (SafetyCulture, GoAudits) capture the visit, not the unit's life. Build the unit-level history, with a QR or barcode ID on every unit. |
| 4 | Due-date tracking (implied by "compliance") | D | The money feature. A monthly list of "what's due, by customer and street" turns records into billable work. Missed 6-year and hydro cycles are revenue left on the table and accounts lost to rivals. |
| 5 | Equipment inventory, read as the shop's own stock (van stock, recharge agent, parts, spare units, loaner extinguishers) | TS → weak D | Useful: techs run out of parts on site and loaners go missing. But full stock control is a rabbit hole. v1: van stock counts and a "used on job" deduction. Nothing more. |
| 6 | Rental inventory | X for this trade | It came from the party-rental candidate. Extinguisher shops rarely rent units, beyond loaners during service, which feature #5 covers. Cut it. |
| 7 | Crew scheduling | TS | Needed for shops with 3+ techs: who goes where, which day. Build it as the due list grouped into routes, not a general calendar. Route optimisation is X until a shop with 8+ techs asks. |
| 8 | Replacing spreadsheets and paper | D, if migration is done for them | Switching cost is what keeps shops on paper and on incumbents. Migration done for them (CSV, old exports, photos of paper sheets through capped AI extraction plus a human check) is the single biggest reason a shop switches this month rather than "someday". |
| 9 | Reports (implied by "compliance logs") | D | A clean per-site PDF plus export packs for The Compliance Engine and the main city portals saves the office admin hours a week. Contractors pay $15–37 a report and still re-key. Brycer sells re-keying at $5 a report (10). |
| 10 | Offline use (not stated, but forced by the job) | TS → D | Techs inspect in basements, garages and plant rooms. If the app fails without signal, techs go back to paper. Offline-first is table stakes the incumbents often do badly. |
| 11 | Configurable for any trade (implied by the generic framing) | L | Custom fields and "build your own workflow" make the product vague, the onboarding long and the marketing impossible. Every configurable screen is one the extinguisher tech doesn't need. |
3.2 Scoreboard
| Category | Count | Features |
|---|---|---|
| Table stakes | 3 | Jobs, crew scheduling, offline use (it becomes D if done well) |
| Differentiator | 5 | Unit-level inspection history, due-date engine, migration done for the shop, jurisdiction-ready reports, "one named trade" positioning |
| Distraction | 1 | Rental inventory (plus route optimisation, full stock control) |
| Liability | 2 | "Any trade" configurability, the unnamed-trade positioning |
About half of what was described is a reason to buy, once the trade is named. Unnamed, almost none of it is.
3.3 "Building to avoid selling": explicit call-outs
- A configurable "any trade" engine. It feels like leverage. In practice it's months of abstraction with no customer asking for it.
- Route optimisation and maps. They demo well. Shops with 1–5 techs already know their streets.
- Native iOS and Android apps. An offline PWA covers the tech's job. App-store releases double the work.
- Direct integrations into every city portal. Most have no public API (unverified, but likely). Build exports first, and integrate where an API and many customers exist.
- Full inventory and purchasing. Use van stock counts and nothing more until customers pay for more.
3.4 What a disciplined v1 looks like
- Keep: customer and site records, extinguisher asset register with QR/barcode, due-date engine (annual, 6-year, 12-year hydro), offline inspection app (scan, pass/fail, photo, signature), per-site PDF report, migration service, simple job list grouped by route, invoice via Stripe or QuickBooks sync.
- v1.5: deficiency → quote → repair job; Compliance Engine export pack; customer read-only portal with certificates; van stock.
- Defer: kitchen hood suppression and emergency-lighting modules; route optimisation; native apps.
- Cut: rental inventory, "any trade" configurability, payroll, accounting, a marketing CRM.