ServiceProof

1. One-liner

Captures every hood, suppression and refrigeration service record so the adjuster can’t deny a claim for missing maintenance proof.

2. Trend signal — why now?

Three things collided in 2025–2026 and they all point at the same undefended gap: the independent restaurant that has been serviced properly but cannot prove it.

• Adjusters now open the file with maintenance records. Insurance Canopy’s 2026 restaurant fire-claim guidance is blunt: “When an adjuster reviews a fire claim, one of the first things they examine is hood cleaning records. If documentation is absent or incomplete, the claim can be denied on the grounds of negligence — regardless of how the fire started.” Source: Insurance Canopy — Insurance Claim Series #1: Fire. That last clause is the whole business. You can be a diligent operator and still lose the claim on paperwork.
• The severity spike made insurers mean. Average equipment-breakdown claim cost doubled between 2024 and 2025, and carriers responded by enforcing the “Duty to Maintain” clause that had sat dormant for a decade. Fastcility’s March 2026 write-up on the maintenance clause: “an operator with no maintenance records on a five-year-old refrigeration unit that catastrophically fails has given their insurer a very clean argument for denial.” Source: Fastcility, 17 Mar 2026. The Insurance Alliance’s 2026 denial list names “Missing Preventative Maintenance Records” as denial reason #1 — the most common cause of an equipment-breakdown denial is not a bad failure, it’s a bad file. Source: The Insurance Alliance — 10 Reasons Your Equipment Breakdown Claim Might Be Denied.
• The record itself is now machine-readable for pennies. NFPA 96 §11.4 prescribes exactly what a compliant kitchen-exhaust service record must contain — cleaning company name, date of service, areas cleaned, areas not cleaned and why, technician certification, and a signed certification. Source: Clean Hoods Express — NFPA 96 inspection intervals. That is a fixed, checkable schema. A vision model reading a photographed service tag or a scanned vendor invoice can now verify all six fields at sub-cent cost — which means you can tell an owner “this tag your hood vendor left is not NFPA-compliant, it’s missing the areas-not-cleaned note” on the day it happens rather than eighteen months later in a denial letter.

And the deadline pressure is structural rather than dated: the 2025 NFPA 96 revision expanded monthly cleaning to any operation running more than 16 hours per day regardless of fuel type, pulling a fresh population of late-night and 24-hour operators into the tightest inspection interval (Total Fire Protection, NFPA 96 cleaning frequency 2026).

Provenance:
  - Signal 1 (Demand): Adjusters examine hood-cleaning records first; absent or incomplete documentation = denial on negligence grounds regardless of fire cause — https://www.insurancecanopy.com/blog/insurance-claim-series-1-fire-a-dangerous-peril-for-restaurant-owners — observed 2026-08-28
  - Signal 2 (Economic): Average equipment-breakdown claim cost doubled 2024→2025; carriers now aggressively enforce Duty-to-Maintain clauses; "Missing Preventative Maintenance Records" is denial reason #1 — https://fastcilitycorp.com/2026/03/17/your-insurance-policy-has-a-maintenance-clause-most-operators-dont-know-that-until-a-claim-gets-denied/ and https://www.theinsalliance.com/post/10-reasons-your-equipment-breakdown-claim-might-be-denied-and-how-to-fix-it — observed 2026-08-28
  - Signal 3 (Feasibility): NFPA 96 §11.4 fixes a six-field schema for a compliant service record, making photographed vendor tags and invoices cheaply machine-verifiable — https://cleanhoodsexpress.com/understanding-nfpa-96-kitchen-hood-cleaning-inspection-intervals/ — observed 2026-08-28
  Category: Underserved niche (carrier-enforced duty with no vendor serving the single-location operator) + Tech-unlock (NFPA 96's fixed record schema became cheaply verifiable from a phone photo)

3. The opportunity

Every CMMS on the market sells the operator scheduling the work. Nobody sells them proving the work happened.

MaintainX, Xenia, Limble, UpKeep, Ecotrak — all of them are work-order systems. I checked MaintainX’s public pricing page: it makes no mention of insurance claims, claim defense, adjuster evidence, or insurance documentation anywhere. It’s a CMMS ($20–$65/user/month), and it is priced and shaped for the maintenance manager of a multi-unit operator who wants to dispatch technicians. Ecotrak prices per location and reviewers flag that “the costs don’t always pan out” for smaller companies (SelectHub Ecotrak reviews).

That leaves the actual buyer — the single-location owner-operator — with the wrong tool for the wrong job at the wrong price. She doesn’t have a maintenance department to coordinate. She has three vendors who show up on their own schedule, leave a paper tag or a PDF emailed to an address she doesn’t check, and disappear. Her “system” is a drawer.

The gap is a scoring-vs-proving gap: the whole vendor field sells the workflow, and the party who eats the loss — the owner, at claim time — has nothing. This is also the shape of a carrier-enforced duty: there’s no statute forcing her to keep this file, so no compliance vendor has targeted it. The penalty is a denied claim on a $23,000 average kitchen-fire loss plus 3–8 weeks of closure (Modern Restaurant Management, citing FEMA), and it arrives quietly, once, at the worst possible moment.

What a focused product does 10× better than a CMMS: it doesn’t ask her to run a maintenance program. It sits between her and her vendors, catches the record at the moment of service, checks it against the standard the adjuster will apply, and keeps a claim-ready file she never has to think about until she needs it.

4. Target market

• Primary customer: Owner-operator of a single-location full-service restaurant or bar in the US, $400K–$3M annual revenue, 10–45 staff, with a commercial hood, a wet-chemical suppression system, and at least one walk-in. She signs the insurance renewal herself and she personally knows the hood guy’s first name.
• Why they buy: Two moments. First, at renewal — the broker asks for suppression inspection reports and she spends a Saturday digging through a drawer and an email account. Second, at claim — the adjuster asks for 24 months of hood-cleaning records and she has four of them. Carriers give “meaningful credits for fire suppression systems in good working order — typically 5–10% off property premiums” (Northmarq / industry 2026 commercial property trends), and she can’t reliably capture that credit because she can’t produce the evidence on demand.
• Rough TAM reasoning: There are over a million foodservice establishments in the US, of which 60–70% are single-unit, small regional, or family-run, i.e. roughly 600,000–700,000 single-location operators (Webstaurant restaurant industry statistics 2026). Narrow to those with a full commercial hood + suppression + walk-in and a revenue base that supports $79/mo: call it a serviceable 250,000–350,000. At 1,500 customers this is a $1.4M ARR business. I don’t need a big share of this.
• Why now for them: Premiums rose hard through 2023–2026, many operators deferred maintenance to stay solvent during the surge, and carriers are now underwriting on documented risk controls rather than trust. NFPA’s four-year window recorded 7,640 structure fires in eating and drinking establishments causing $246M+ in property damage, with 61% involving cooking equipment (Koorsen, citing NFPA). The exposure is not theoretical and the underwriting has tightened around it.

5. Product sketch (MVP)

• Vendor-forwarded capture. Give the restaurant one email address. Every hood, suppression, extinguisher, refrigeration and grease-trap vendor invoice or report that lands there is filed to the right asset automatically. Forward the backlog once and the file starts populated.
• Snap-the-tag. Staff photographs the service tag or sticker the technician leaves on the hood. The record is read, dated, and filed from the photo — no typing, no login for the line cook.
• NFPA 96 completeness check. Each kitchen-exhaust record is checked against the six fields §11.4 requires. Missing the areas-not-cleaned note or the technician’s certification? Flagged the same week, while the vendor will still fix the paperwork.
• Interval clock per asset. Knows whether this kitchen is on the monthly, quarterly, semi-annual or annual cycle (including the 2025 >16-hours-per-day rule) and warns before the gap opens, not after.
• Claim file, one button. Produces a dated, indexed PDF pack — every service record for the requested asset and window, with a gap report stating plainly what exists and what doesn’t. This is the artifact you hand the adjuster or the public adjuster.
• Renewal pack. The same thing shaped for the broker at renewal, so the operator can actually claim the 5–10% suppression credit instead of shrugging at it.
• Gap ledger. A standing, honest list of what’s missing per asset — because a file that quietly pretends to be complete is worse than no file.

6. AI angle — what’s load-bearing

Remove the AI and this is a shared Dropbox folder, which is what these operators already fail to maintain.

The load-bearing work is reading heterogeneous vendor paperwork and judging it against a standard. Hood vendors, suppression companies, refrigeration techs and grease haulers each emit their own format — a photographed adhesive tag, a carbon-copy work order, a faxed-then-scanned PDF, a one-line email. Extracting asset, date, scope, technician credential and signature from that mess, mapping it to the right piece of equipment, and then ruling on whether the record satisfies NFPA 96 §11.4 is the product. That’s classification plus judgment against a rubric, per document, at a price point where a $79/mo customer is still profitable. That was not affordable at this price two years ago; it is now.

The second AI-load-bearing piece is the gap narrative — turning “no record between March and September for asset 3” into the sentence an adjuster or broker actually reads, with the operator’s own remediation noted. That’s the difference between a folder of PDFs and a defense.

7. Localization angle (if any)

N/A — this is a US-first play and deliberately so. The wedge is NFPA 96 plus US carrier claim behaviour plus the US independent-restaurant density. NFPA 96 is adopted widely (Canada, parts of the Gulf and LatAm reference it), so there’s a later expansion path, but the claim-denial dynamic and the broker-renewal moment are what make this urgent, and those are sharpest in the hardened US commercial property market. Forcing a localization angle here would weaken the product.

8. Business model — path to $1M–$5M ARR

• Pricing: $79/mo per location (single location, all assets, unlimited records, claim + renewal packs). $149/mo for 2–5 locations. Annual prepay at 10 months.
• ACV: ~$950 blended, allowing for a minority of small-group operators on the higher tier.
• Rough math to $1M ARR: ~1,050 locations at $79/mo. That’s roughly 0.35% of the serviceable 300K single-location operators with hoods.
• Rough math to $5M ARR: ~4,400 locations, or fewer with the vendor-side channel below. Requires the hood-cleaning and fire-protection service companies to be reselling or bundling it — a hood vendor with 300 accounts who white-labels the file becomes a distribution multiplier rather than one customer.
• Expansion path: ACV grows via location count, then via vendor-side seats — sell the same evidence engine to the hood-cleaning company so its tags are compliant on issue (they have their own liability exposure when a client’s claim is denied), then via adjacent regulated assets (grease-trap manifests already carry a 3-year on-site retention requirement in many jurisdictions, e.g. Terre Haute wastewater utility food-service rules).

Gross margin is high — the per-customer inference cost is a few dozen documents a year. There’s no field ops, no hardware, no float.

9. Go-to-market wedge — first 100 customers

The buyer is hard to reach cold as a restaurant owner and easy to reach through the two people who already have her trust and her paperwork.

• Channel 1 — hood cleaning and fire protection companies (primary). These firms service 100–500 restaurants each, already visit every account 1–4× a year, and are the ones physically leaving the record behind. Pitch: co-branded file for your customers, you look like the vendor who protects them, and your own tags get checked for compliance. Target 40 regional kitchen-exhaust and fire-protection companies (there are thousands; NFPA-certified firm directories and state fire-marshal contractor lists are public). Land 5 partners × 20 activated accounts = 100 customers. This is the whole game and I’d spend the first eight weeks here.
• Channel 2 — independent insurance brokers and public adjusters in restaurant-heavy metros. The broker wants the 5–10% suppression credit documented because it makes the renewal easier to place; the public adjuster wants clients who arrive with a file instead of a shoebox. Both are warm, both refer for free, both are findable. Target 60 restaurant-specialist brokers; expect 10–15 to refer at least one client.
• Channel 3 — the denial-aftermath cohort. Public adjusters and restaurant attorneys publish about denied claims constantly. Operators who just lost or nearly lost a claim are the highest-intent buyers alive and they talk about it in r/restaurantowners and in state restaurant association forums. Direct outreach to that cohort converts, but it’s a trickle, not a channel — I’d use it for case studies rather than volume.
• Channel 4 — state restaurant associations. Most run member-benefit programs and insurance-adjacent content. A single association newsletter placement in a large state reaches thousands of independents with an implicit endorsement.

If channel 1 doesn’t produce, this idea is a lot weaker. I’d know inside six weeks.

10. Build complexity — justification

Low. Document ingestion (email + photo), extraction against a fixed six-field NFPA 96 schema, an interval calendar per asset, and PDF pack generation. All off-the-shelf: standard web stack, hosted vision/LLM APIs, no custom models, no hardware, no integrations with restaurant POS or accounting required for v1. The genuinely fiddly parts are vendor-format variety (solved by volume and a fallback to human-confirm-in-one-tap) and getting the staff-facing photo capture frictionless enough that a line cook will do it. A solo builder ships a credible v1 in 6–8 weeks; a pair does it in 5.

The hard part of this business is distribution, not engineering. That’s the right way round.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Document management. No regulated advice — the product reports what records exist and whether they meet a published standard; it doesn’t adjudicate coverage.
Ethical — no harm / dark patterns	✅	The gap ledger is deliberately honest. A tool that let operators fabricate backdated records would be insurance fraud; records are captured at service time with provenance, and gaps are reported as gaps.
Market exists (evidence above)	✅	Denial reason #1 is missing PM records; adjusters open with hood records; 600–700K single-location operators.
1–5 person team can build this	✅	Low complexity, 6–8 weeks to v1 for one builder.
Launchable with <$50K / ₹40L	✅	Sub-$10K. Inference costs are trivial at this document volume; the spend is founder time on vendor partnerships.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Severe but infrequent — that’s the honest ceiling here. A denied claim is existential (43% of restaurants that suffer a fire close permanently), but most operators go years without a claim. The renewal moment is what makes it felt annually rather than once a decade. Not hair-on-fire daily pain.
Demand evidence	15	12/15	Strong industry-side evidence: denial reason #1, adjuster behaviour documented, claim severity doubled, premium credits real. Weaker on direct operator voice — I could not source verbatim operator complaints at the volume I wanted, and I’m not inventing them. That gap is why confidence is Medium.
Build feasibility	15	13/15	Off-the-shelf throughout, fixed extraction schema, no integrations required. 6–8 weeks solo.
Distribution clarity	15	12/15	Channel 1 (service vendors) is specific, enumerable and warm, with clear conversion math. Not yet tested, and the whole plan leans on it heavily.
Revenue mechanics	15	11/15	$79/mo is comfortably within a restaurant’s software wallet and well under CMMS pricing. $1M ARR needs ~1,050 locations, which is credible. Risk: this is a “buy it and forget it” product, so churn from perceived non-use is a live concern — the renewal pack is the annual reminder that it’s working.
Time to first revenue	8	8/10	Sellable pre-build to a hood vendor’s client list; first paying customer plausible within 4–6 weeks of launch. Not instant, because the first sale is really a partnership sale.
Defensibility	4	4/10	Weak, and I won’t dress it up. A CMMS could ship a “claim file” button in a quarter. The moat is the accumulating multi-year record (switching means abandoning your evidence history) plus vendor-channel relationships — real but slow-building. Month 3: none. Month 12: modest.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy · sales-heavy

Technical enough to make photo-to-verified-record work reliably; sales-heavy because the entire GTM is partnership deals with hood-cleaning and fire-protection companies. A builder who won’t get on the phone with 40 service-company owners should skip this one.

Key assumptions to validate (3–5)

1. Assumption: Kitchen-exhaust and fire-protection service companies will co-brand or resell this to their own customer base. How to test: Call 20 regional hood-cleaning company owners. Ask directly whether they’d offer a customer-facing record file under their brand and what they’d want for it. Kill signal: fewer than 5 say yes.
2. Assumption: Operators will pay $79/mo for insurance-defense value they hope never to use. How to test: Landing page + 30 direct conversations with single-location owners, priced, with a real checkout. Measure paid conversion, not “that’s interesting.”
3. Assumption: The 5–10% suppression premium credit is actually claimable with better documentation, at the individual policy level. How to test: Interview 8 restaurant-specialist brokers and ask what evidence unlocks the credit and how often clients fail to produce it. If the credit turns out to be automatic or unrelated to documentation, the annual ROI story collapses and pricing has to fall.
4. Assumption: Vendor paperwork is extractable at high enough accuracy to be trustworthy as evidence. How to test: Collect 100 real service tags/invoices from 5 restaurants and measure field-level extraction accuracy against the NFPA 96 six-field schema. Below ~92% and the human-confirm step has to be prominent, which raises friction.

Risk flags

1. Low-frequency pain / churn risk: The product’s value is realized rarely. Operators may cancel in month 7 having never had a claim. Mitigation is making the renewal pack and the interval clock genuinely useful monthly — but this is the central commercial risk, not a footnote.
2. Weak defensibility: MaintainX or Xenia adding a “claim-ready export” is a one-quarter feature. The only durable asset is the multi-year record and the vendor channel.
3. Channel dependency: GTM leans hard on service-company partnerships. If those firms see it as extra liability exposure (“now my non-compliant tags are documented”) rather than a customer benefit, the primary channel closes and CAC rises sharply.
4. Evidentiary limits: Documentation improves a claim’s odds; it does not guarantee an outcome — one source explicitly cautions that “documentation does not guarantee the outcome of an insurance claim or investigation” (Night Vision Clean). Marketing must not overpromise, or the first denied-anyway customer becomes a public problem.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical solo founder who will personally sell 40 hood-cleaning
                        and fire-protection companies; restaurant or insurance background helps
Time to revenue:        6–10 weeks
Capital to launch:      <$10K (₹8L)
Top 3 assumptions to validate first:
  1. Hood/fire-protection service companies will co-brand — 20 calls, need 5 yes
  2. Operators pay $79/mo for rarely-used insurance defense — real checkout, 30 conversations
  3. The 5–10% suppression premium credit is documentation-gated — 8 broker interviews
Kill criteria:
  - Abandon if fewer than 5 of 20 service companies will co-brand or refer
  - Abandon if paid conversion on a priced landing page is under 2% from 200 targeted operator visits
  - Abandon if broker interviews show the premium credit is automatic and not documentation-gated,
    AND month-6 churn in a 20-customer pilot exceeds 8%/mo

15. Next step — 1-week validation sprint

• Day 1–2: Build the list. 40 regional kitchen-exhaust cleaning and fire-protection companies from state fire-marshal contractor lists and NFPA-certified firm directories, plus 30 restaurant-specialist insurance brokers. No product, no deck — one paragraph and a phone.
• Day 3–4: Call them. Service companies get the co-brand question. Brokers get the premium-credit question: what evidence unlocks the suppression credit, and how often does a client fail to produce it? Log verbatim answers, not impressions.
• Day 5: Put up a priced page ($79/mo, real checkout) and drive 200 targeted visits from restaurant-owner communities and two association newsletters. Simultaneously collect 100 real service tags from 5 friendly restaurants and run extraction accuracy against the NFPA 96 six-field schema.

Falsifiable go/no-go: proceed only if ≥5 of 20 service companies commit to a co-brand pilot and ≥4 paid signups land from 200 targeted visits and field-level extraction accuracy clears 92%. Two out of three is a rework, not a go — the channel result is the one I will not compromise on, because without it this is a cold-outreach business to the hardest-to-reach SMB in America.