Anyone can write the email

Writing a good cold email is no longer a skill.

Any competent model will produce one in four seconds — correctly structured, appropriately brief, with a plausible reason for the contact and a clean call to action. It will be better written than most of what a sales team sends today.

Which is precisely why outbound stopped working. When the marginal cost of a well-written email goes to nothing, a well-written email stops being evidence of anything. The recipient adjusts. The bar moves from is this written well to does this person know something about me, and that is a much harder bar, because it cannot be cleared by a language model on its own.

That is the whole subject of this piece. The drafting is the easy part and it is the part everybody has automated. The hard part is upstream, and it is the seven articles before this one.

The job, as it exists today

A salesperson has a list of accounts and a number to hit. The list is too long to research properly and too short to ignore anyone on it.

So they do one of two things.

They write genuinely personal notes to the handful of accounts they know already, which works and does not scale. Or they send a template with the utility's name merged into the first line, which scales and does not work — and they know it does not work, and they send it anyway, because the alternative is sending nothing and sending nothing is visibly not trying.

The industry's answer to this has been tooling that makes the second option faster. More sequences, more steps, more variants tested against each other. It raises volume against a falling response rate, which is the same trade the previous decade already made and lost.

Why it is harder here than in most markets

A utility is not a company that ignores you. It is a public body that remembers you.

The buyer here is a small, stable, professional community. The operations manager you emailed badly in March is at the same conference in October, talking to the peers you also emailed badly. There is no infinite supply of fresh prospects to burn through — the market is finite and it talks to itself.

That changes the maths that justifies spray-and-pray. A bad email is not free. It is a small permanent deduction from a reputation you need for years, in a market where the total number of relevant buyers is smaller than most vendors' contact lists suggest.

And the specifics that make an email land are not in any sales tool. Not the job title, not the firmographics, not the funding round — the things that make a utility person read past the first line are the plant, the project, the committee meeting, the thing they said in public and assumed nobody outside the room heard. That is the reading problem again, arriving at the last step of the process rather than the first.

What the workflow does

It drafts from the account record, not from a template. The inputs are the things the earlier workflows produced: the signals, the verified contact, the installed base and its clock, the profile. The draft is downstream of all of it, which is why this article is ninth and not first.

It writes to the person, not to the account. The same development at the same utility is a different message to a plant superintendent, a finance director and a consulting engineer, because they are worried about different things and are measured on different things. One development, several drafts.

It produces the form the motion actually needs. A full email for a cold approach. A three-line version for someone who has met you. A short note for social. A call script for the people who would rather pick up the phone, with the two or three objections this particular account is likely to raise and what is actually true about each.

Every claim in the draft traces to a document. Same rule as everywhere else in this series. If the email says a capital plan carries a line for something, that line exists and you can open the page it is on before you press send. This matters more here than anywhere else in the product, because this is the only workflow whose output leaves the building with your name on it.

And a person approves it. Drafts are written to be edited and are gated on a human before anything is sent. Not as a legal fig leaf — because the rep knows things the record does not, and the edit they make is usually the reason the email works.

What it looks like in practice

An illustrative example — not a customer, and not a real utility.

The generic version of the email writes itself and you have received it a hundred times. I noticed your utility is investing in infrastructure modernization. Our solutions help utilities like yours reduce costs and improve resilience. Do you have fifteen minutes on Thursday?

The grounded version says: your board approved a condition assessment of the north pump station in March, the report went back to the board in August with a rehabilitation recommendation, and the capital plan now carries a line for it in the next fiscal year. We have done this work at utilities of your size. Before the specification is written, here are two things worth deciding early, and here is why one of them is usually decided wrong.

The second one is not better because the writing is better. The writing is about the same. It is better because it is evidence that somebody did the reading — and that is the only thing in the message the recipient cannot get from anyone else that week.

The thing we will not build

We do not send it.

That is the third time in this series that a workflow has stopped at the same kind of line, and by now it is a deliberate position rather than three coincidences. Not the CRM. Not the bid feed. And not the sending infrastructure: the sequencer, the mailbox warm-up, the deliverability management, the unsubscribe handling, the domain reputation.

Those are real disciplines and there are companies that do nothing else and do it well. A vendor with a functioning sales team already owns one. Replacing it would mean a migration, a procurement cycle and an argument with whoever chose it, in exchange for a worse version of a thing that already works.

The context is the part nobody else has. So the context is the part we build, and the draft lands in the tool the team already opens every morning.

There is a commercial argument for doing the opposite — sending is where the recurring revenue and the lock-in are — and it is the same argument that would have had us rebuild the CRM. It is wrong for the same reason. You do not get to own the workflow by owning the last mile of it; you get to own it by being the part that cannot be replaced.

What it cannot do

It cannot manufacture a reason to call.

The draft is built out of what the record supports. Where the record is thin — no project forming, no contract coming up, no committee discussion worth quoting — the workflow says so, and says what it looked at, rather than reaching for the strongest available filler and calling it an angle.

That is a quality control, not a shortage. A system that always produces an email will always produce an email, and some of the time it will be the generic one with better vocabulary. Do that at a volume no human could have managed, in a market this small, and you have automated exactly the thing that stopped working.

So the useful output is sometimes not yet, and here is what to watch for — which is a different instruction from nothing here, and considerably more useful than a paragraph of warm nothing sent under your own name.

And it does not know what happened in the room. The rep who visited in February, the procurement officer who is difficult, the consultant who has a history with your equipment — none of that is in the public record and all of it changes what should be written. The draft is a first draft assembled from what is knowable at a distance. It is not the finished thought, and the person sending it is not a formality.

Next

The thing every article so far has gestured at: writing all of this back into the system the sales team already lives in. It is the least interesting thing to build and the one that decides whether the workflows before it were worth building at all.