The follow-up nudge, the price increase notice, and the we can't do this job email: a prompt for each one you keep putting off.
Some emails are easy. "Here's your invoice" writes itself. Others sit in your drafts folder for a week. You don't know how to say them without sounding pushy or awkward. Or like the bearer of bad news. AI is good at exactly these emails. You just need the right prompt.
The follow-up nudge
You sent an estimate ten days ago. You haven't heard back. You don't want to sound desperate, but you also want the job. Try this prompt:
"Write a short follow-up email checking in on an estimate I sent 10 days ago for a bathroom remodel in Waukesha. Friendly, no pressure, one sentence asking if they have any questions, and a line saying the pricing is good for another two weeks."
You'll get back a two or three sentence email. It reads like a normal check-in, not a sales push. That's the tone most contractors struggle to hit on their own. Most people worry about seeming annoying.
The price increase notice
Material costs went up. You need to tell a customer their estimate is changing before you start the job. Nobody enjoys writing this one. A prompt that helps:
"Write an email telling a customer that their deck estimate is increasing by $400 due to lumber price increases since we quoted them three weeks ago. Be direct, not apologetic, explain briefly why, and confirm the new total."
Notice the instruction "not apologetic." AI left on its own tends to over-apologize. That can make a normal business update feel like you did something wrong. Steer it toward direct and factual instead. It usually reads better.
The "we can't do this job" email
Sometimes a job isn't a fit. Maybe it's outside your specialty. Maybe it's outside your service area. Or the scope is bigger than what you handle. Saying no clearly, without burning a bridge, is its own skill:
"Write a short email declining a roofing job because it involves a type of commercial flat roof we don't install. Be polite, thank them for reaching out, and if possible suggest they search for a contractor who specializes in commercial flat roofing."
This kind of email matters more than people think. A clear, respectful decline means that homeowner might still refer you for jobs that ARE a fit. Even though you turned this one down.
Why these prompts work better than a generic one
The difference between "write me a price increase email" and the fuller prompt above is specificity. Give AI the dollar amount, the reason, and the tone you want. It writes something usable on the first try. Leave those out, and you'll get something generic. That version needs three rounds of editing anyway.
Say you write 5 of these tricky emails a week. Each one used to sit unsent for 2 or 3 days because you kept putting it off. A drafted version in 30 seconds changes that. You can send it same-day instead of stalling. That keeps the job moving. The customer won't wonder if you forgot about them.
Always read it before sending
These are the emails where tone matters most. They carry news the customer might not want to hear. Read every draft out loud before sending. If a line sounds cold or oddly formal, rewrite it in your own words. The goal is a message that sounds like you on a good day. Not a customer service script.
Building a small library of your own
Once you find a prompt structure that gets a good result, save it somewhere you can find again. A notes app, a doc, wherever. Next time you need a price increase email, you're not starting from scratch. You're just swapping in the new numbers. For a broader set of ready-made prompts covering these exact situations and more, take a look at our 30 Claude prompts for contractors.
A shop that handles a lot of remodel work in Waukesha County might build out five or six of these over a season. A delay notice for spring thaw scheduling. A change order email. A warranty question response. Each one takes a few minutes to set up once. It saves you that same awkward blank page every time it comes up again.
Questions people ask
What if the customer responds and I need to keep the conversation going?
Paste their reply into the same AI conversation. Ask for a follow-up response. Keeping the thread in one place gives the AI context on the whole back-and-forth. That makes each reply better than starting fresh each time.
Should I tell customers an AI helped write the email?
There's no requirement to. Most contractors don't mention it, since the words and decisions are still yours. What matters is that the content is accurate. You need to stand behind what it says.
Is it okay to reuse the same declined-job email for different customers?
The structure is fine to reuse. But change the specific reason and any details about their job each time. A copy-pasted email that clearly wasn't written for their situation can come across as careless.