Owning every send. Why a human approves

Every note that reaches a senior buyer carries your name. So a person should read it before it goes. No exceptions.

That's the rule. It sounds obvious. It gets broken constantly, especially now that drafting a note takes seconds and sending a thousand takes one click.

Why automation tempts people

Writing a good opener used to take real effort. Research, a hypothesis, careful wording. Now tools can draft one in seconds, and the draft is often decent.

So the temptation is to skip the review. If the draft is decent, why not send it? If a tool can send a hundred a day, why limit it to twenty?

The answer is that decent isn't good enough when you're writing to a CIO about a $250K problem. And the cost of a bad note isn't one lost reply. It's a buyer who now associates your firm with careless outreach.

What can go wrong

Automated research gets facts wrong. A job post that closed months ago. A leader who already left. A filing from two years back read as current. A merger that fell through.

Automated drafts get tone wrong. Too familiar with a stranger. Too formal with a former colleague. Congratulating someone on a promotion that was actually a lateral move.

Automated targeting gets people wrong. A note to the wrong department. A note to someone who explicitly asked not to be contacted. Two reps writing to the same buyer the same week.

Any one of these costs trust. And trust is what a services firm is selling, which I wrote about in trust is the product.

What the human checks

Approval isn't a rubber stamp. It's a short, specific read. Four things.

Is the research hook true and current? Check that the fact happened, it's recent, and it's about this company.

Is the personal trigger right for this person? Make sure the role, the timing and the reason it matters to them hold up.

Is the misery hypothesis plausible? It doesn't have to be right. It has to be a reasonable guess a senior buyer wouldn't find insulting.

Is the binary exit easy to answer? One line, easy to confirm, easy to correct.

That review takes a minute or two per note. It's the cheapest quality control in the business.

Saw you took over as CIO in March and the team just posted for a cloud FinOps lead. In a new seat, I'd guess the pressure is getting cloud costs under control before next year's budget is set. Is that accurate, or is the bigger issue somewhere else?

A reviewer reading that checks the start date, confirms the job post is live, and asks whether "cloud costs" is a fair guess for this company. If all three hold, it goes.

Owning it means owning the reply

The person who approves the note owns what happens next. If the buyer replies, that person answers. If the buyer corrects the hypothesis, that person learns from it.

That's how a team gets better at writing openers. Every correction teaches the reviewer something about the market. A note sent by a machine with nobody watching teaches nobody anything.

Fewer sends, better sends

Requiring approval caps volume. That's a feature.

A rep who has to read and approve every note sends fewer of them. The ones that go out are better. And the team stops burning through its market with notes nobody would sign.

For big-ticket services, the math always favors fewer, better notes. You're not trying to book a thousand meetings. You're trying to book the right twenty, with buyers who'll remember your first note as the one that got their problem right.

The leadership standard

If you run a team, make this a rule, not a guideline. Nothing goes to a buyer without a named person approving it.

Use tools for research and drafting. They save real time. But keep a human between the draft and the send. Owning every send is part of the method for a reason. Your name is on it, so your judgment should be too.