AI for roofing companies: inspections, proposals and claim files.

Roofing work splits early. After the inspection, a job either becomes a retail proposal the homeowner pays for directly, or an insurance job in which the homeowner's claim, the adjuster's visit and the insurer's scope shape what happens next. Both paths run through the same estimate, built by the owner or estimator in whatever estimating and measurement tools the company already uses.

Supervised AI assistants fit around that estimate, not inside it. They index inspection photos, check measurement reports, assemble proposal drafts, keep insurance-job files complete and draft weather-hold notices. The estimator sets scope and price, the owner decides what the company tells a homeowner, and no assistant contacts an insurer.

On the retail path the homeowner is the buyer and the only decision-maker, and the paperwork exists to make the agreement clear: what will be done, with which materials, when, and how payment works.

On the insurance path the homeowner is a policyholder with a claim. The Texas Department of Insurance's claim tips, checked on 13 October 2026, tell homeowners to photograph the damage, hold off permanent repairs until the insurer's adjuster has inspected, and set their own repair estimates against the settlement offer; a homeowner may also have their contractor and the adjuster discuss repair costs. Some states limit what a contractor may do beyond documenting; Texas is covered below.

A roof is priced on what a person saw on it: the layers, the decking, the penetrations and flashing, the pitch and the access. That judgment is the estimator's work product, and it stays in the tool it was built in.

What an assistant can carry is the coordination on either side. Before the estimate, it confirms that the photos cover every roof plane, checks that the aerial or drone measurement report has arrived and that its address and roof outline match the job, and lists what the estimator marked as unknown. After it, the assistant carries the line items into a proposal draft or an insurance-job file and tracks which version the homeowner has seen.

Measurement-report providers and estimating platforms connect through a custom integration built against the vendor's API or exports where the vendor offers them, or through supervised browser use where the vendor permits it, subject to testing. A person completes any login, two-factor check or payment the site asks for.

The National Roofing Contractors Association's guidance to homeowners on selecting a contractor, as checked on 13 October 2026, works as a specification for a proposal draft, because it describes what a careful buyer will check. It tells homeowners to insist on a written proposal with complete descriptions of the work and specifications, start and completion dates and payment procedures; to ask for copies of liability insurance and workers' compensation certificates that stay in effect for the whole job; to read the warranty and understand what would void it; and to ask who will oversee the project.

An assistant can assemble each section from the company's approved material, so the owner reviews a complete draft rather than a blank page, confirms the price and sends it. The assistant then tracks the date sent, any reply and when a follow-up draft is due.

The sections of a retail proposal draft (an Aevrion pattern):

• SCOPE AND SPECIFICATIONS

  Carried from the estimator's line items and notes: tear-off or overlay as decided, underlayment, flashing, ventilation and the roofing product line, in the company's standard wording.

• DATES

  A proposed start window and an expected completion, taken from the schedule and marked as weather-dependent in the company's own terms.

• PAYMENT PROCEDURES

  The company's payment terms inserted from the approved template. The assistant does not invent terms or alter amounts.

• CERTIFICATES

  Current liability and workers' compensation certificates attached, with their expiry dates checked against the planned job dates and a flag if either lapses first.

• WARRANTY

  The manufacturer and workmanship warranty wording the owner approved, including what would void it, so the homeowner reads those conditions before signing.

• SUPERVISION

  The name of the person who will oversee the job and how its quality will be checked, taken from the crew plan.

For an insurance job, the assistant's most useful product is a complete, indexed job file that supports the owner's work and the homeowner's own dealings with their insurer, and replaces neither; the storm-claim documentation article in this series sets out what that file holds.

What a contractor may do beyond documenting depends on the state, and this article states one state's rules only. Texas, as checked on 13 October 2026, draws the line explicitly. Its Department of Insurance tells roofers that they cannot act as public adjusters on claims for homes they are working on, or advertise that service. Section 4102.163 of the Insurance Code applies the same bar to any contractor, licensed adjuster or not, and even with the homeowner's power of attorney. Among the department's examples of crossing the line: offering to negotiate or file the claim, or telling an insurer that the company speaks for the homeowner.

The same department says it is illegal in Texas for a contractor to offer to waive, rebate or absorb a policyholder's deductible, and that a contract of one thousand dollars or more involving an insurance settlement must include a notice that the policyholder must pay the deductible. Other states set their own rules, which this article does not describe; a roofing company outside Texas should confirm its own state's position with an adviser.

Those rules write the assistant's job description: it indexes, checks and drafts for the owner, never contacts an insurer or adjuster, drafts nothing that offers to negotiate or promises a recovery, and leaves the deductible alone.

OSHA's fall protection page, checked on 13 October 2026, sets the construction-industry threshold at six feet. How a roof is accessed and whether a crew goes up are decisions for the owner and the crew lead. The assistant only checks that each job file holds the access notes and safety plan the owner requires before scheduling, and flags any job without them.

Weather affects both paths at once. A morning routine can read a public forecast through the browser, compare it with the week's installs, and list the jobs at risk with a draft notice for each affected homeowner. The owner makes the weather call and sends the notices. The re-roof season article in this series follows one of those mornings, including the supplier delivery that has to move with it.

For roofers in England, the Planning Portal, checked on the same date, says repairs or re-covering do not normally need a building control application where less than a quarter of the building envelope and less than half of the roof is affected, but do need approval for structural alterations, a significantly different fire performance, or a covering fifteen percent or more heavier. An assistant can check that each job records the owner's judgment on those lines; it does not make it.

Grok Bot is an agent product, documented at docs.x.ai. Its documentation describes Bots as durable, named AI teammates, each with a job and its own working context, on a persistent cloud computer that carries a browser, files and a terminal. A roofing company's standing rules, such as never contacting an insurer and never sending a homeowner anything the owner has not seen, are given to each Bot in chat to remember, and the documentation says boundaries like these should be backed by approvals rather than rest on memory alone. A skill writes a procedure down once, such as how an inspection photo set is labeled; a routine runs one on a schedule, never closer than five minutes apart.

Where a connector exists a Bot uses it, and for many other web tools it uses the browser, but a measurement provider's or supplier's site may block automation or ask for a login, a two-factor code or a CAPTCHA, and a person handles those steps. The documentation names no connector for roofing, estimating, measurement or field-service products. Proposal emails a Bot prepares sit as editable drafts the owner sends or discards, and where an action is set to pause, the owner sees Allow once, Always allow or Deny; which actions pause depends on the tool, the risk and the owner's own rules.

One documented habit suits insurance-job files. When the stakes are high, the documentation suggests the Bot sort its report into what its sources show, what it took as an assumption, what it has completed, what is waiting on approval and what is still open, with links and timestamps kept as evidence.

Based on the Grok Bot documentation at docs.x.ai as checked on 13 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Aevrion's One-Man Army model has one owner supervising a small roster of named assistants that prepare, draft and check while the owner decides. The documentation advises keeping the roster as small as the work allows and splitting off a Bot only for genuinely distinct work; the pillar article explains the model in full.

For most roofing companies that means two Bots at first, both Aevrion's illustration rather than documented roles: a retail Bot that keeps the inspection-to-proposal pipeline moving, and a claim-file Bot that keeps insurance-job files complete. A third, for scheduling and weather, earns its place once the first two are stable. The documentation advises read-and-prepare work first, approved actions and routines later.

1. 01

   Inquiry recorded

   Owner

   Owner or office

   Advances when

   The retail Bot drafts an acknowledgment for the owner to send

2. 02

   Inspection booked

   Owner

   Owner

   Advances when

   The owner confirms; the Bot opens the job folder

3. 03

   Inspected

   Owner

   Inspector on the roof

   Advances when

   The Bot indexes photos by roof plane and lists gaps

4. 04

   Estimated

   Owner

   Estimator

   Advances when

   Scope and price are set in the estimating tool

   Ends when

   The path splits: a retail proposal or an insurance-job file

5. 05

   Proposal or file in progress

   Owner

   Retail Bot or claim-file Bot

   Advances when

   A proposal draft or file index is checked against its list

6. 06

   Awaiting the owner

   Owner

   Owner

   Advances when

   The owner prices, approves and sends; any insurer contact is the owner's own

7. 07

   Scheduled

   Owner

   Owner and crew lead

   Advances when

   Materials ordered; the owner decides weather holds

8. 08

   Installed and closed

   Owner

   Crew lead, then owner

   Advances when

   Final photos checked; warranty reminder and invoice drafted for the owner

Three documented limits matter most in a roofing office. The full list, sorted into documented capability, Aevrion pattern and not possible, is in the What Grok Bot can actually do for a business article.

• STORM-WEEK WEB FORMS WAIT FOR A RUN

  There is no telephony, and routines run on schedules at least five minutes apart, so a storm-week web form reaches a Bot only through a custom integration or supervised browser use of the form tool: on the next scheduled run, or sooner if the form's system is built to call a routine's webhook, a trigger Cursor's help pages document. A homeowner with water coming through the ceiling needs a person.

• ONE LOGIN, EVERY BOT

  The company's Bots all work on one computer, so a measurement-provider login used to pull a report is open to the claim-file Bot as well; separate Bots are not a security boundary, and a login that only one workflow should use goes under a separate user account.

• NIGHT-TIME PACKETS END AS DRAFTS

  A proposal packet assembled overnight cannot wait on the owner's approval: an unanswered request expires after about ten minutes (Cursor's help pages say thirty) and the action does not run, and approving never reverses work already done.

The first step is a written map: where inquiries arrive, where photos and measurement reports land, which tool holds the estimate, who sends proposals, and where insurance-job files go missing. The readiness assessment linked below works through those questions. Aevrion Ops can then design the roster, write the procedures and approval rules, and build the custom integrations a company's tools need, as far as each vendor's API or terms allow and after testing. Aevrion does not sell or resell Grok Bot access.

1. Roofing runs a retail path and an insurance path through one estimate. Assistants coordinate around the estimate; they do not produce it.
2. A retail proposal draft can follow the NRCA's homeowner guidance: scope and specifications, dates, payment procedures, certificates and warranty terms.
3. Texas, as checked on 13 October 2026, bars contractors from adjusting their own customers' claims and from absorbing deductibles; this page states no other state's rule.
4. Roof access, safety plans and weather calls stay with the owner and crew; OSHA requires fall protection at six feet in construction.
5. Measurement and estimating tools connect through custom integration or supervised browser use.
6. Start with two assistants, read-and-prepare work first, and drafts the owner sends.