AI prompt: Fence and deck builder price objection response

The prompt

You are a fence and deck builder replying to a homeowner who said the quote is higher than expected. Customer: [client name]. Project: [fence type / deck build / deck repair / gate / railing] at [property address or suburb]. Quote amount: $[amount]. Scope included: [demo, posts/footings, framing, boards/pickets, rails, gates, hardware, disposal, staining/sealing if included]. Material/spec details: [cedar, treated pine, composite, vinyl, aluminium, post depth, board size, railing type, fasteners]. Cost drivers to explain: [site access, slope, old removal, material choice, permit/inspection, haul-away, timeline, crew size]. Optional lower-cost alternatives, if real: [material swap, smaller area, remove staining, homeowner disposal, phase work, none]. Schedule window: [real availability]. Desired next step: [approve quote / choose option / book site call]. Write an email or text under 180 words that: (1) acknowledges the price concern respectfully, (2) explains 2-3 real cost drivers using only my details, (3) offers only the lower-cost options I listed without inventing discounts, (4) protects quality and safety without scare tactics, and (5) ends with one simple decision question. Tone: calm, practical, local, and confident. Do not claim code compliance, structural guarantees, discounts, or material warranties unless they are in my notes.

What you’ll get back

A customer-ready reply that addresses the price objection, clarifies scope and materials, gives realistic option choices, and asks for one next decision without automatically cutting margin.

Tips for this one

• Reply within one business day while the homeowner still remembers the site visit and scope conversation.
• Name real cost drivers such as removal, post depth, slope, access, material grade, gates, rails, and disposal instead of saying 'quality work costs more.'
• Offer scope options only if they are genuinely workable. Do not invent cheaper materials, discounts, or warranty promises to win the reply.
• End with one decision: keep the original spec, choose a listed alternate, or schedule a quick scope call. Too many options create another delay.