# Grok Bot turns a roofing lead into a full report and quote in 10 minutes for human review

Grok · X (Twitter) · Amount undisclosed (workflow-only case; no revenue claim)

## Business summary

Construction/roofing SMB owner uses Grok Bot on inbound leads: when a lead arrives, the Bot produces a roof report and full quote within about 10 minutes; the author does a quick look and sends. Readers can reuse the “lead → report + quote draft → human confirm and send” pattern to shorten the quote cycle.

## Business value

Construction/roofing SMB owner uses Grok Bot on inbound leads: when a lead arrives, the Bot produces a roof report and full quote within about 10 minutes; the author does a quick look and sends. Readers can reuse the “lead → report + quote draft → human confirm and send” pattern to shorten the quote cycle.

## Workflow

Hand lead details to Grok Bot and request roof inspection report + quote

Grok Bot generates roof report and full quote (author reports ~10 minutes)

Author performs quick review then sends to customer (human confirmation)

## Preparation and limitations

Results and numbers are as reported by the original post author (roof report + full quote in about 10 minutes). Lead source, quote template contents, and data pull method are not described in the original post. Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. The original post is a reply; the author describes his own use in the first person.

## Starter prompt

````text
You are a roofing quote assistant. The user will provide lead information (address, contact, damage description, known area or photo links).

Task: From the provided information generate: 1) a short roof inspection report (visible issues, recommended checks, risk notes); 2) a full quote draft (line items: materials, labor, tax, total range).

Output format:
- Report section (Markdown)
- Quote section (table: Item | Qty | Unit Price | Subtotal)
- Missing-information list (if address or area is missing, explicitly list fields the user must supply)

Missing/conflict handling: Do not invent specific prices or areas when data is insufficient; mark as “needs on-site confirmation” and list questions. Prefer the user’s most recent data on conflicts.

Confirmation boundaries: Generate drafts only. Do not send email, access external payment, or modify customer systems. Final send requires user confirmation.

Untested.
````

## Costs and pitfalls

Results and numbers are as reported by the original post author (roof report + full quote in about 10 minutes). Lead source, quote template contents, and data pull method are not described in the original post. Workflow steps, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. The original post is a reply; the author describes his own use in the first person.

## Source and attribution

SteveH V3.0 (@stevehaag81)
https://x.com/stevehaag81/status/2121653280577146885
2026-11-15
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
