OPERATING SYSTEM — ROOFING CONTRACTORS
The Roofing OS
The operating layer for residential roofers running retail and storm claims. Runs on top of the CRM and tools you already pay for — and does the operator-side work they leave on your desk.
See exactly what you get.
No mockups. A silent screen tour of the live workspace, the workflows, and the instant post-purchase delivery. Decide in 90 seconds whether from $49/mo is worth it.
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 → inspector's calendar notified.
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 submitted autonomously; the owner of the property signs the cover sheet and the contractor submits it on their behalf.
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 pitch copy with state-compliant disclaimers → push routes to reps. Storm-week SLA: brief fires within 24 hours of…
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 for the owner.
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 summary on the dashboard.
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.
Storm weeks used to mean chaos and dropped balls. Now the storm brief is waiting when I wake up, canvass plans come out of the actual weather alerts, and supplement packets get drafted in observed-damage language my office just has to review and send. Nothing about the week got easier — it got organized.
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.
Q.04What's the storm-event SLA?
When the National Weather Service issues major severe-weather alerts (large hail, damaging wind), the Discord posts a same-day storm note automatically. You then run the run-storm-canvass-brief workflow against your service area: it pulls the live NWS alerts for your state, builds the canvass brief, and drafts state-compliant door-hanger copy — observed-conditions language only, never carrier predictions.
Q.05Do I need to know Notion or AI?
No. The Notion workspace duplicates with one click. Claude Skills install in two clicks. The workflows import into free n8n; you connect your own accounts and activate, following the step-by-step guide. No coding.
Q.06Annual versus monthly?
Annual at $490 is the anchor — $40.83 per month effective vs $49 monthly. Cancel anytime; unused months pro-rate back.
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