# AI for Roofing Contractors: Turn Estimates into Clear Next Steps https://palnau-systems.vercel.app/insights/ai-for-roofing-contractors-estimate-follow-up Published 2026-11-10 by Oliver Palnau and the Palnau Systems team. Prepared with AI assistance. Audience: Roofing company owners, sales managers and estimators. Roofing companies can use AI to organize estimate conversations, identify unanswered homeowner questions, and prepare timely follow-ups from the actual proposal. Start after an estimator has approved the scope. Connect the estimate version, inspection notes, contact preferences and next action so the office can move a decision forward without inventing roof conditions, insurance coverage or a discount. ## Key takeaways - Follow up on the customer’s unresolved question, not a generic reminder schedule. - Keep approved scope, exclusions and estimate versions attached to each conversation. - Measure profitable accepted work and customer response, not messages sent. ## Make the estimate the source of truth A roofing proposal often contains more than a price: material choice, tear-off assumptions, flashing, ventilation, decking allowances, disposal and warranty terms. An assistant needs the approved version and its exclusions before it can help explain the work. Preserve the original document and label every extracted item with its source. If a homeowner asks whether an item is included and the document is silent, the correct next step is an estimator question. Build a small record with proposal date, revision, owner, customer question, promised callback and decision status. Avoid a single “hot lead” label that mixes a missing answer with a customer who simply needs more time. Those situations need different responses. ## Use a question-led follow-up sequence Ask the salesperson to review the first draft and choose the next useful action: clarify a material option, arrange a scope discussion, confirm timing, or close the opportunity politely. Pause automation when the homeowner replies, the quote changes, work is awarded, or the customer requests no further contact. A shared household conversation should not trigger separate messages from several salespeople. A useful internal instruction is: “Using only proposal revision 3 and the customer’s last message, list unanswered questions, cite the proposal section, and draft a short reply. Flag anything requiring the estimator. Do not add prices, availability, financing terms or warranty promises.” ## Worked example: a decking allowance question Hypothetical example: a homeowner asks whether a proposed roof replacement includes all plywood replacement. The estimate includes a specified allowance and a stated process for additional work. The assistant retrieves that language, flags the distinction between an allowance and unlimited replacement, and drafts a plain-language explanation for the estimator to approve. It also creates a task to discuss how additional conditions will be documented. This creates a more useful conversation than an automatic “ready to book?” text. The system should record that the question was answered, not assume the job was won. If the estimate does not state the allowance clearly, route the record back for a revised proposal. ## Pilot one crew’s proposal pipeline Use a recent sample containing accepted, lost and undecided jobs. Have the estimator score whether drafts preserve scope and identify real objections. Start with drafts only, then allow narrowly approved reminders after the response and opt-out logic works. Keep schedules connected to actual crew capacity so an enthusiastic message cannot promise a start date the production team cannot deliver. Compare similar job types and lead sources over the pilot. A higher close rate is not helpful if it comes from unsupported discounts or work that does not fit the crew. Review accepted margin, revision frequency and customer complaints alongside response speed. ## First steps 1. Choose one estimator and one proposal type for the pilot. 2. Label the latest approved estimate and all superseded versions. 3. Write rules for replies, opt-outs and estimate expiration. 4. Review draft answers to exclusions and allowance questions. 5. Assign a person to every unresolved customer question. ## What to measure Unanswered-question age: Median business hours from a customer scope question to a verified answer. Estimate acceptance by cohort: Accepted proposals divided by proposals issued for comparable jobs and lead sources. Correction rate: Drafts requiring substantive scope or pricing correction divided by drafts reviewed. ## Can AI create a final roof price from photos? Use photos to help organize information, not as authority for a binding scope or price. Inspection conditions, measurements and estimator judgment still determine the approved proposal. ## Should every old estimate receive a new campaign? No. Review contact permission, unresolved disputes, quote validity and capacity first. A relevant clarification is more useful than repeatedly contacting people who have declined. ## Sources and further reading - [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) - [Suffolk County Consumer Affairs](https://suffolkcountyny.gov/Consumer-Affairs) ## Work directly with Oliver and his team Work directly with Oliver and his team to connect your estimates, customer conversations and crew handoffs. Bring a sample proposal and the questions your sales team answers repeatedly. Free introductory call: https://calendly.com/oliverpalnau/30min Services and scope: https://palnau-systems.vercel.app/services Current pricing: https://palnau-systems.vercel.app/pricing