OPERATING SYSTEM — ROOFING CONTRACTORS
The Roofing OS
The operating layer for residential roofers running retail and storm claims. An operating layer that runs on top of the tools you already pay for.
An operating layer,
not another CRM.
A Notion workspace, working automations, Claude Skills, and a community channel — engineered for the operator-side work your CRM leaves on your desk.
Triage inbound lead
Inbound web form, phone, canvass capture, or storm-lead intake → deduped against existing customers → source-attributed → urgency-scored (active leak / storm damage / retail) → routed to an inspector → first-touch SMS in under five minutes
Build supplement packet
Adjuster scope uploaded → diff against inspection findings and code requirements → identify likely missing line items → draft a supplement narrative with photo references → assemble a packet for property-owner sign-off. The packet is NEVER
Run storm-canvass brief
NOAA storm event detected in a member service area (or owner manually triggers a ZIP) → pull weather + hail-report data → overlay onto recent install map + service-area polygons → build a prioritized canvass list → generate door-hanger and
Track production schedule
Daily 6am cron syncs job status, checks material delivery dates and the 72-hour weather forecast, flags installs at risk of weather delay, proposes reschedules, and notifies affected crews and customers. Generates the daily production brief
Run after-service follow-up
Job marked complete → wait 24 hours → send NPS-gated review-ask SMS + email. Promoters get a Google review link, passives get a quiet thank-you, detractors route to the owner immediately and never see an automated reply.
Generate weekly owner report
Sunday 6pm cron rolls up the week's leads, jobs, revenue, supplement recovery $, AR aging, callback flags, and crew-by-crew leaderboard. Sends an email digest, posts the headline to the owner Telegram channel, and pins a Notion-block summar
Built for a specific operator.
You'll run this if…
You lead a small team that has outgrown spreadsheets and broker-memory. You treat AI as an instrument, not a magic trick. You'd rather buy sharp software than maintain dull software.
Skip this if…
You want a one-click "AI grows my business" button. You won't spend an hour on setup. You expect outcome guarantees — this product does not sell those.
Memory + inbox
Not a CRM. It sits on top of yours and absorbs the operator-side process work that currently lives in your head and your sent folder.
One price list.
No sales call.
Answers, before you ask.
Q.01Will this replace JobNimbus / AccuLynx / Rooflink?
No — the Roofing OS sits on top of your existing CRM. It handles the owner-side operations your CRM doesn't: supplement-packet drafting with owner sign-off, state-compliant canvass copy generation, weather-aware production scheduling, callback-pattern analysis, and the storm-event broadcast SLA.
Q.02Is the supplement workflow a public adjuster service?
No. The /draft-supplement-narrative skill produces contractor-side documentation — observed damage, code references with section citations, photo callouts. The property owner reviews and signs the cover sheet's authorization page; the contractor submits to the carrier on the owner's behalf. The skill never submits autonomously, never frames the contractor as a public adjuster, and surfaces state-by-state caveats. Some states restrict contractor activity in claims processing — the cover sheet calls this out explicitly.
Q.03What about "guaranteed approval" language?
We don't use it. The supplement narrative skill is hard-coded to block "guaranteed approval", "we'll get this paid", "your carrier owes you", and any prediction of carrier behavior. Every packet describes observed conditions and code requirements — period.
Get the operations audit.
A one-page diagnostic that surfaces the three biggest leaks in your operating week. Emailed once. No nurture sequence.
SENT ONCE · UNSUBSCRIBE IN ONE CLICK · NO CARD