AI Prompts for Contractors: The Five Messages You Send Every Week

Every contractor sends the same five messages every week. The quote follow-up. The change order notice. The payment nudge. The review request. The estimate explanation. Different customers, different jobs, same five messages, written from scratch every time, usually on a phone, usually in a hurry.

AI can draft all five in seconds. The catch is the word "can." A vague prompt produces a vague draft, and a vague draft takes longer to fix than writing the message yourself. The prompts below are structured for the trade: each one was drafted, tightened, and tested until the first answer came back usable, so you skip the rewrites and the wasted tokens. That is the difference between a prompt list and a prompt pack, and it is what you are reading: the structures, free. The finished, tested set of fifty is the product.

What makes a contractor prompt work

Three ingredients, in every prompt:

The role and the reader. "You are writing as a residential remodeling contractor to a homeowner who received a quote three days ago." The AI needs to know who is talking and who is listening, because the same message reads differently to a homeowner, a property manager, and a general contractor you sub for.

The facts as fill-in fields. Names, dates, amounts, job descriptions. The prompt marks exactly where your specifics go, so the draft comes back with the blanks filled by you, not invented by the AI. An AI that invents your prices is worse than no AI at all.

The constraint on tone and length. "Two short paragraphs. Professional, direct, no fluff." Without the constraint, AI writes like a brochure. With it, AI writes like a contractor who respects the customer's time.

Every prompt below follows that structure. Copy the shape, fill in your facts, and the draft that comes back needs a read-through, not a rewrite.

1. The quote follow-up

The message that wins work. Most awarded jobs go to the contractor who followed up, and most contractors do not follow up because writing the message feels awkward. It is not awkward. It is a calendar event with words attached.

The prompt shape: role (your trade, writing to the homeowner), the facts (customer name, job description, quote date, quote amount, expiration date), the ask (a short check-in message offering to answer questions, mentioning the expiration date once, no discount offered), tone (brief, confident, one question at the end).

What comes back is a two-paragraph message you could send as-is: the reminder, the expiration date doing the quiet work, and a question that invites a reply. The follow-up schedule behind it (day 3, day 10, expiration) is a separate system, but the message is the part people avoid, and the prompt removes the avoidance.

2. The change order notice

The message that protects margin. A change order presented clearly gets signed. A change order mumbled about on site gets argued about at invoice time.

The prompt shape: role (contractor writing to the client mid-job), the facts (original scope line, the requested change, the added cost broken into labor and materials, the schedule impact in days, the new contract total), the ask (a clear written notice presenting the change, the price, the schedule effect, and requesting written approval before work proceeds), tone (factual, unapologetic, no hedging).

The draft that comes back states the change, the price, and the approval request in plain language. No throat-clearing, no "sorry for the inconvenience" for work the customer asked for. Change orders are not bad news. They are the job evolving, priced honestly.

3. The payment nudge

The message nobody likes writing. An overdue invoice needs a nudge at day 7, a firmer one at day 14, and a formal one at day 30, and each one has a different job.

The prompt shape: role (contractor's office writing to the client), the facts (invoice number, amount, due date, days overdue, payment link or method, late fee clause if the contract has one), the ask (a message appropriate to the stage: day 7 is a polite check, day 14 restates the amount and the terms, day 30 is formal), tone (professional throughout, warmth decreasing as days increase, never angry).

The key detail: the prompt includes which stage this is. A day-7 nudge and a day-30 letter are different documents, and the prompt treats them that way. The draft comes back matched to the moment, which is what makes it sendable without editing the attitude.

4. The review request

The message that builds the pipeline. Reviews compound: the contractor with forty recent reviews gets the call, and the call becomes the next review. But asking feels awkward, so it does not happen, so the reviews do not compound.

The prompt shape: role (contractor writing to a just-completed customer), the facts (customer name, job description, one specific detail about the work), the ask (a short thank-you with a direct link to the review page and one sentence on what to mention), tone (genuine, brief, no bribe, no script).

The specific detail is the ingredient that matters. "Thanks for trusting us with the kitchen" is forgettable. "The tile backsplash came out great" gives the customer something to write about. The prompt asks for the detail because the detail is what turns a request into a review.

Timing note the prompt should include: send it the day the job finishes or the day the final payment clears, whichever the customer experiences as the end. A review request sent three weeks later is archaeology.

5. The estimate explanation

The message that closes. The estimate goes out as a document, and then the customer has questions, or worse, has silence. A short explanation message, sent with the estimate, answers the questions before they form.

The prompt shape: role (contractor writing to the homeowner with the estimate attached), the facts (the three or four main line items in plain language, the total, the deposit, the valid-until date, the one scope boundary most likely to come up), the ask (a cover message walking through what the number includes, in the customer's language, ending with the next step), tone (clear, unhurried, confident).

This is the message that turns "we will think about it" into a signed estimate, because most customers do not object to the price. They object to the uncertainty, and the explanation removes it. The estimate is the number. The message is the sale.

The weekly habit

Five messages, five prompts, one habit: when the situation arises, open the prompt, fill in the facts, read the draft, send it. The quote follow-up on day 3. The change order notice before the extra work. The payment nudge on schedule. The review request at completion. The estimate explanation with every bid.

The time savings are real but they are not the point. The point is that the messages stop depending on your mood, your memory, and your thumb-typing patience. They go out because the prompt makes them easy, and easy things get done. Follow-ups get sent. Change orders get signed. Invoices get nudged. Reviews get requested. Estimates get explained. That is five revenue habits running on rails.

Why tested prompts beat free ones

The internet is full of free prompt lists. Most of them were written once, never tested, and read like it: vague roles, no fact fields, no tone constraints, drafts that need a rewrite. A prompt you have to rewrite is not a shortcut. It is a chore with extra steps.

Each prompt in the Contractor Prompt Pack was drafted, tightened, and tested until the first answer came back usable: the right role, the fact fields in the right places, the tone constraint that keeps the draft sounding like a contractor. Fifty prompts covering the messages, the documents, and the weekly paperwork of a contracting business. Copy, fill in your facts, send. $29, works with ChatGPT, Claude, and Gemini, and the structures above are the free sample of how they are built.