Running the Office

The Emails You Keep Putting Off Are Costing You Jobs

By Travis Evans, Founder of TradeGOAT · 20+ years in the trades

There is a short list of emails sitting in the back of your head right now. The proposal you sent eleven days ago that never got answered. The customer who needs to hear that the part is late before he finds out from somebody else. The invoice that’s thirty days out and you haven’t said a word about it. The question a general contractor asked you on Friday that you know the answer to and still haven’t written down.

None of those are hard to write. That’s the part that used to bother me. They are not hard, and they still don’t get written.

The emails that slide are always the ones that matter

Look at what the two piles actually contain. The easy emails are confirmations, scheduling, a one-line yes. Those go out fast, because they take no thought and carry no risk. The other pile is different. Every email in it needs you to go look something up, decide how to say it, and take a small amount of heat.

So the second pile waits for the moment when you have time and a clear head. In this business that moment is nine at night, after a ten-hour day, and by then you are done. That is not laziness, that is a long day. The email that would have taken you four minutes at a desk is the one thing you cannot make yourself do, and it rolls to tomorrow, and then to next week.

The cost never shows up as a line item. It shows up as a bid that went quiet and you never followed up on. A customer who got the bad news late and remembers that more than the work. Money sitting out at sixty days because nobody ever sent a polite note at thirty. You didn’t lose those on price or on craftsmanship. You lost them on paperwork you meant to get to.

Why most people won’t hand this to a computer

Everybody in the trades has been pitched some version of AI that answers your email for you. I understand exactly why contractors don’t bite, because I didn’t either.

These messages go out under your name. Your customer does not know or care what wrote it. If something goes out that is wrong about a date, wrong about a number, or just sounds like it came from a call center, that is your reputation, on the one job where it mattered. In this trade your name is about one bad email wide. Nobody sane hands that to software and hopes.

And the fix for that is not a better model or a longer set of instructions. It is not a setting in a menu that somebody can flip on a bad morning. The only version of this I would ever use myself is one where the software physically cannot send.

How it works: it writes, you send

Inside TradeGOAT you have an assistant that can draft any email your business needs to send, customer-facing included. You ask for the follow-up on the Thompson proposal, or the note about the delay, or the polite nudge on the invoice, and it writes it.

What makes the draft actually usable is that it is not writing from nothing. It reads the real job. The actual proposal you sent and what was in it. The real dates, the real numbers, the change order that got signed last week. That is the difference between a draft you can send in thirty seconds and a form letter you have to rewrite from scratch. And because your own documents are what the job was built from, the language in the draft sounds like your business, not like software.

Then it stops. The draft lands on a card in front of you. You read it, change anything you want, and you send it from your own email. That happens every time, with no exceptions. There is no setting anywhere that turns that off, because it was never built as a setting.

One more piece I want to be specific about, because it is where these things usually go wrong. If the email needs a technical answer, a real question about the equipment, the code, or the engineering, the assistant does not invent one. It will not author an expert answer and put it under your name. It carries through the answer from the expert side of the tool, with the source cited so you can check it, or it hands the question back to you. Typing up an answer you provided is paperwork. Making one up is a liability, and I would rather the tool tell you it doesn’t know.

What changes in a week

The list in the back of your head empties out, because the four-minute email is now a thirty-second read. Follow-ups actually go out on the bids that went quiet, which is the cheapest work you will ever do to win a job. Customers hear about the delay from you first. The thirty-day note gets sent at thirty days instead of at sixty when you finally get annoyed.

And you still read every single word that leaves your business. I did not build that as a limitation, I built it that way on purpose.

I will be straight with you about how this works, because it is the part I would want to know if I were you. The no-send fence is structural, not a promise. There is no send path in the email drafting at all, so nothing can go out under your name that you did not send yourself.

It starts with the paperwork you already have

None of this works if the assistant doesn’t know the job. That is the whole reason TradeGOAT starts by taking your documents instead of asking you to rebuild them, so you keep your proposal, your scope language, and your payment terms exactly as they are. Once the job lives in the tool with real numbers on it, everything downstream gets easier: pricing it the same way every time, getting paid when the scope changes, and knowing whether you made money when it’s done. The email is just the last mile of work you already did.

I spent years being the bottleneck on my own correspondence. It turns out I didn’t need somebody to send my emails. I needed somebody to write them and then get out of the way.