All use cases
Quotes & Estimates

A disaster-claims estimating team says Claude only worked after weeks of setup, and untrained staff produced "the worst inspection reports and estimates"

She fed it SOPs, example estimates and hundreds of old emails. Before that, fixing its work took longer than doing it by hand.

Real storyDone with Claude (Cowork)

What they did

Commenter KelseyRawr, replying in r/Contractor to a new contractor asking which AI to pay for, said "Claude Co Work is the best for it. We use it." She has "like 60 different disaster claims to submit estimates for." To get usable output she "uploaded PDFS and word documents with examples, standards, a Claude SOP I created for it to follow, example estimates of how they should be structured, a document built explaining the process step by step, more example templates," and "fed it hundreds of prior correspondences." She redacts customers' private information by hand before uploading anything.

How it went

"Does it help me in my everyday? Absolutely." But "I still had to spend weeks perfecting the desired output," which "did put me behind at first." When employees used it "without any guidance," they "got the worst inspection reports and estimates. It was either overly done and not at all the correct scope, or it was just completely off," and "it took hours longer to fix whay Claude had done." Her advice: it only pays off "if you are overwhelmed by the workload," and when she was working about 25 a day she "didn't think Claude was necessary." She wouldn't "turn it loose to employees." For emails, she says Grammarly or Gmail's built-in AI editing is enough.

Worth knowing

The setup is the work: your SOP, your examples, your past estimates. Budget weeks, not an afternoon. Don't hand it to the crew until one expert has tested it. Strip customer names and addresses before you upload. If you write a few estimates a week, the free tools may be all you need.

Try it yourself

You are an operations lead helping a small contractor build a reliable AI estimating assistant. You're skeptical, and you care about accuracy over speed. TASK: Help me write the instruction pack (an SOP the AI must follow) for estimates, using my own examples, so it stops guessing. Then test it. CONTEXT (fill in the [BRACKETS]): - [BUSINESS + JOB TYPES]: Example: Kettle Moraine Restoration (fictional), water and storm damage claims - [VOLUME]: estimates per week. Example: 15-20 - [MY ESTIMATE FORMAT]: section headings and line-item style. Example: Summary, Room-by-room scope, Line items, Exclusions, Photos list - [3 PAST ESTIMATES I'M PROUD OF]: paste them with customer names, addresses and claim numbers removed - [MY RULES]: Example: never price from memory; always list exclusions; always note moisture readings; scope comes from my notes only - [COMMON MISTAKES I'VE SEEN]: Example: adding rooms I didn't inspect, missing tear-out, wrong units (SF vs LF) STEPS: 1. Check [3 PAST ESTIMATES] for any personal info I missed. List it so I can remove it. Don't repeat it. 2. From my examples, write a one-page SOP: inputs required, steps in order, format, and words to avoid. 3. Write a "never do" list built from [MY RULES] and [COMMON MISTAKES I'VE SEEN]. 4. Write an input checklist: what I must give you before you start (site notes, measurements, photos list, price sheet). 5. Make 2 test cases from my examples. Write how you'd draft each, and a grading rubric (scope match, units, exclusions, made-up items). 6. Tell me honestly whether my [VOLUME] is high enough to justify this setup, and why. RULES: - Never invent a measurement, line item, price or code requirement. If it's missing, write NEEDED. - Keep my format exactly. - No customer personal info in the output. OUTPUT FORMAT: Part A: privacy flags. Part B: SOP (one page). Part C: Never-do list. Part D: Input checklist. Part E: 2 test cases with a rubric. Part F: a 3-sentence worth-it verdict. FOLLOW-UPS TO TRY NEXT: - "Here's your draft from today's job and my corrected version. Update the SOP so you don't make that mistake again." - "Write a one-page sheet for a new hire: when to use the assistant and when not to." - "List the 5 checks I do before any AI-drafted estimate leaves the office." FILLED-IN EXAMPLE (fictional Wisconsin business): - [BUSINESS + JOB TYPES] = Kettle Moraine Restoration (fictional), West Bend, water and storm claims - [VOLUME] = about 18 estimates a week in storm season - [MY RULES] = scope only from my walk-through notes; always list exclusions; moisture readings on every wet room - [COMMON MISTAKES I'VE SEEN] = adds a room we never entered; forgets drywall tear-out above the flood line
Open the full playbook

Want help getting this working? Rise Systems in Oconomowoc sets these up.

Want this running in your business without the DIY? Rise Systems in Oconomowoc sets these up.

Free 15-minute AI check-up
Read the original

Source: Reddit · October 15, 2026

Related
AU
Write estimates customers understand and approve

A clean estimate with a plain-English summary, a line-item table, what's not included, and how to approve.

Auto repairHVACPlumbingElectricalGarage doorsAuto bodyMediumPlaybook
Wisconsin Trades AI editorial·Oct 2026