What an AI-Written Outreach Message Should Never Do

Builders and developers get more cold messages than ever, and most of them were written by a machine in under a second. They can tell. The tells are consistent, the deletes are fast, and the sender never knows why. AI can write a first message that earns a reply, but only when it is kept away from seven habits that mark a message as noise. Here they are, with what to do instead.

1. Never invent a detail

This is the cardinal sin. An AI that is short on facts fills the gap with something plausible: a timeline it guessed, a project type it assumed, a compliment about "your recent project downtown" that never happened. The builder knows their own project. One wrong detail and the whole message is a fake, and so is the sender.

Instead: every claim in the message must trace back to a record. The permit says what is being built and where. The stage says how far along it is. The company record says what else the builder has done. If the fact is not in the record, it is not in the message.

2. Never open with the sender

"My name is Sam and I'm reaching out from Sam's Electrical, a leading provider of..." The builder stopped reading at "leading." They did not ask who you are; they want to know why this message is in their inbox.

Instead: open with their project. "You've got the six-storey rental on Dundas at framing." Now they are reading, because it is about them and it is correct.

3. Never sound like a press release

AI defaults to a register no human uses in a message to a builder: "innovative solutions," "seamless experience," "we would be delighted." Trades do not talk like that, builders do not talk like that, and the mismatch is the tell.

Instead: write it the way a foreman would say it on site. Short sentences, plain words, one point. If a line would sound strange said out loud in a site trailer, cut it.

4. Never send the same message to two people

Personalization is not swapping the first name. When the same message goes to the site super and the president with only the greeting changed, it lands wrong on both. The super does not award the work and the president does not care about the crew schedule.

Instead: draft to the role. The person who awards a package wants to hear about capacity, reliability and comparable projects. The person running the site wants to hear that you can be there when the stage opens. Same project, two different messages.

5. Never ask for a meeting in the first line

The AI equivalent of proposing on the first date. "Do you have 15 minutes this week for a quick call?" before the builder knows what you do or why it matters to this project.

Instead: offer something first. A specific claim about being ready for their stage. A relevant job you have done nearby. A quick question about who is handling the mechanical package. The meeting comes after the reply.

6. Never write more than the reader will read

AI likes paragraphs. Builders read messages on a phone, standing up, between two other problems. Anything longer than a few lines gets skimmed or skipped.

Instead: three to five sentences. Project, what you do, why now, one question. If the draft is longer, it is trying to do the second message's job in the first.

7. Never follow up with "just checking in"

The empty follow-up is the most common AI message there is, and it is the least likely to get a reply. It gives the builder nothing to respond to.

Instead: follow up with a new fact. The project moved to the next stage. The builder filed another permit. You finished a comparable job. Every follow-up should be a reason to reply that did not exist last week, and the project record keeps producing those on its own.

Where the good AI messages come from

None of this means AI is the problem. The problem is what the AI is given. Fed a company name and a title, it has nothing to say and says something anyway. Fed a real permit, a real stage, a real builder history and a real decision maker with a real role, it drafts a message that reads like a rep who did their homework, because in effect it did.

That is how Builtie's outreach scripts are built. Each one is drafted from the project record: the permit scope, the current stage, what else the builder has filed, and the role of the person being written to. The rep reads it, changes what they want, and sends it. Every line refers to something that is true and checkable, which is the only kind of message a builder answers. And the same rule holds on Instagram and LinkedIn: Builtie never sends a cold direct message on your behalf and never reads a private profile. The signals it uses are public, and the outreach is a reply or a first message a builder can trace back to a real project.

How Builtie fits

Growth includes the LinkedIn and email outreach built on these scripts; on the done-for-you Custom plan our team writes and runs them for you. Starter covers up to 20 projects a month for $79 per month per seat with a 10-day free trial; Growth raises that to 50 and adds the events dashboard and social media signals. The script is only as good as the record behind it, which is why the record comes first.

Know the projects. Reach the decision makers. See how the scripts read for a live project in your area at builtie.com.