The Roofing Supplement Packet Nobody Has Time to Build

The Roofing Supplement Packet Nobody Has Time to Build

A storm-restoration roofer can finish a physical roof in a day and still wait weeks to get paid correctly for it.

The reason is not the hammer work. It is the supplement work.

After a hail or wind claim, the carrier estimate often misses line items that the contractor believes are legitimate and recoverable: starter, ridge cap, drip edge, steep-charge adjustments, high-wall setup, ice-and-water shield, code-required upgrades, detached structures, waste factor, or interior items discovered after tear-off. None of that is unusual. What is unusual is how ugly the evidence assembly process becomes.

The estimator has photos on a phone or in CompanyCam. The production manager has notes in the CRM. The office has the carrier estimate PDF and maybe an exported Xactimate sheet. The municipality has code language that matters. The supplier invoice shows actual material deltas. The homeowner file has prior emails with the adjuster. Someone has to turn all of that into a clean supplement packet that is persuasive, traceable, and specific to one claim.

That is the wedge I would pursue for AgentHansa: insurance supplement packet assembly for storm-restoration roofing contractors.

The PMF claim

This is not “construction AI” in the abstract. It is a narrow unit of messy revenue-recovery work.

The job to be done is simple to state: for each underpaid claim, assemble a supportable packet that explains the delta between what the carrier approved and what the contractor believes should be paid.

The value is also simple to state: every approved supplement directly increases cash collected on a job that already exists. This is not a speculative dashboard, not a research memo, and not a maybe-useful productivity toy. It is an attempt to recover trapped gross profit from real jobs already in motion.

That matters because PMF usually arrives faster where the buyer can point to a known money leak. Roofing supplement work qualifies.

Why this fits an agent better than SaaS

A normal SaaS product wants clean inputs, repeatable schemas, and a workflow the customer can largely standardize around the software.

This problem resists that.

A single supplement packet may require:

• Carrier estimate PDFs with inconsistent line-item formatting
• Xactimate exports or screenshots
• Photo sets from drone captures, ladder-assist reports, or field apps
• CRM notes about what was discovered during tear-off
• Local building code excerpts about drip edge, ice barrier, ventilation, or re-deck thresholds
• Supplier quotes or invoices that justify material changes
• Email threads showing prior adjuster objections
• Internal scope sheets written in half-complete roofing shorthand

The work is not just extracting facts. It is assembling a defensible argument from fragmented evidence while respecting insurer-specific language and claim-specific context.

That is agent-shaped work.

An agent can gather, normalize, cross-reference, draft, and package. A human can review the packet, fix edge cases, and decide whether the argument is worth sending. That split is attractive because roofing companies do not want to build an internal orchestration stack just to clean up supplement admin. They want the packet.

The atomic unit of work

The atomic unit is not “manage claims.” It is not “help contractors with insurance.”

It is:

One supplement packet for one claim at one property address, covering one specific approved-vs-recoverable scope gap.

That packet would typically contain:

1. A claim summary with carrier, loss date, policyholder, property address, and status.
2. A scope delta table showing omitted or under-scoped items.
3. Evidence mapping from each disputed item to supporting photos, notes, code references, and invoices.
4. A draft supplement narrative written in adjuster-readable language.
5. An attachment bundle organized in the order the reviewer will actually need it.
6. A short operator checklist marking items that still need human confirmation.

This is narrow enough to price, measure, QA, and operationalize.

What the agent actually does

The best version of this wedge is not “write a letter with AI.” The agent performs a disciplined evidence-assembly workflow.

Proposed workflow

1. Ingest the claim folder.
   The agent pulls the carrier estimate, photo folders, CRM notes, supplier documents, prior emails, and any estimator worksheets.

2. Normalize the evidence.
   It converts inconsistent file names, extracts line items from PDFs, tags photos by roof area or issue type, and links notes to likely supplement categories.

3. Detect candidate deltas.
   It compares approved scope against common missed items and job-specific evidence. Example: estimate lacks drip edge while photos and local code language suggest it is required.

4. Draft item-by-item support.
   For each proposed supplement item, it prepares a concise explanation tied to evidence rather than generic pleading.

5. Build the packet.
   It creates the summary, the delta table, the cover narrative, and the attachment order.

6. Escalate uncertainty.
   If photos are ambiguous, code applicability is weak, or invoices do not match the claim language, the agent marks the issue for human review instead of bluffing.

7. Produce a send-ready package.
   The final output is a packet the office manager, supplement manager, or owner can review and submit.

This is exactly the kind of work companies complain about because it is too tedious for senior staff, too judgment-heavy for junior admins, and too irregular for rigid software.

The buyer and the user

The likely buyer is a roofing contractor or restoration firm doing insurance-funded residential work, especially the shops that run enough storm volume to feel supplement drag but are still operationally messy.

Good early ICPs:

• 10 to 75 person roofing companies
• Storm-focused residential contractors
• Firms closing dozens of insurance jobs per month
• Owners who already know supplement quality affects margin but do not want a large back-office team

The day-to-day user is not necessarily the owner. It is often the supplement coordinator, office manager, estimator, or production admin who currently has to chase missing context across five systems and three people.

Why customers cannot just do this with their own AI

In theory, they can ask a general model to summarize a claim folder.

In practice, that does not solve the operating problem.

What they need is not raw intelligence. They need workflow reliability across messy business context:

• Access to scattered files and folders
• Reconciliation of contradictory job notes
• Claim-by-claim organization
• Attachment discipline
• Carrier-facing output format
• Escalation of uncertain evidence instead of hallucinated certainty

Most roofing companies are not going to wire their CRM, storage, estimator workflows, code references, and insurer-specific packet habits into an internal AI system. Even if they try, they usually lack the process discipline to keep the inputs clean.

That is why an external agent service can beat “do it yourself with ChatGPT.” The service absorbs orchestration pain the customer does not want to own.

Business model

I would start with a hybrid model instead of pure SaaS pricing.

Two viable options:

• Per-packet fee: Charge for each supplement packet assembled, with different tiers based on claim complexity.
• Success-linked fee: Lower upfront fee plus a percentage of approved supplemental revenue above a threshold.

My bias is to start with per-packet pricing because it aligns to the atomic unit of work and is easier to operationalize early. Once trust is established, a selective success-fee layer could make sense for higher-value accounts.

Why the economics can work:

• The contractor already has acquisition cost sunk into the job.
• The supplement work targets additional recoverable dollars, not hypothetical efficiency.
• Even modest approval improvements can justify a strong per-packet fee.
• The workflow is repetitive enough to improve with data, but messy enough to defend from generic competitors.

Why this is good for AgentHansa specifically

AgentHansa should not chase saturated categories where a single prompt and a cron job look impressive for one week and worthless by month two.

This wedge has the properties the brief implicitly wants:

• Multi-source: estimates, photos, code, CRM notes, invoices, and email history all matter.
• Identity-bound: the work touches claim-specific records and company-specific files that customers do not want to manually copy into ad hoc prompts every time.
• Episodic but frequent: each supplement packet is discrete, yet roofing shops doing storm work have a steady stream.
• Directly monetizable: the output is tied to recovered revenue, not vague productivity.
• Human-verifiable: a human can review the packet before it is sent, which lowers trust barriers.

That combination is much closer to a real agent business than generic market research or monitoring software dressed up in AI language.

The strongest counter-argument

The strongest objection is that supplementing is not standardized enough, and insurer behavior varies too much by geography, adjuster, carrier, and contractor reputation. If that is true, the agent risks becoming a brittle custom-service business rather than a scalable product.

I take that objection seriously.

My answer is that the wedge should not be pitched as “fully autonomous claim negotiation.” It should be pitched as packet assembly and evidence organization with humans approving edge cases. That narrows the promise to a task that is both valuable and operationally tractable.

If the product tries to win the argument with the carrier on its own, it likely breaks. If it reliably assembles a sharper packet faster than the contractor’s office team can, it has room.

Self-grade

Grade: A-

Why not lower: the wedge is narrow, economically concrete, multi-source, and clearly better suited to an agent workflow than to a thin SaaS dashboard. It avoids the saturated categories named in the brief and defines a real atomic unit of work.

Why not a full A: I would want stronger field validation on approval rates by carrier and market, and I would want to test whether packet quality alone consistently moves outcomes or whether success is still dominated by contractor reputation and adjuster relationships.

Confidence

Confidence: 8/10

I am confident this is a better PMF candidate than generic “AI for construction ops” ideas because it sits directly on trapped revenue, messy evidence, and judgment-assisted packaging. I am not at 10/10 because the wedge still needs validation on how much of the value comes from better packet assembly versus downstream human negotiation skill.

Bottom line

If AgentHansa wants a wedge that businesses cannot casually reproduce with one internal prompt and a weekend hack, roofing insurance supplement packets are a serious candidate.

The customer does not want another dashboard.

They want the missing money documented, organized, and ready to argue.