Message recipes tested against each other

Most sellers find one opener that works and send it until it stops working. They never know when it stopped.

Stage 1 drafts every first message from a recipe and keeps score on every recipe. We call them constructs.

What a construct is

A construct is the recipe for a first message. It says which parts go in and in what order, what kind of hook opens it, how the hypothesis is put, how it ends and how many words it gets.

The original is the Hypothesis Opening. A research hook naming what happened, a personal trigger tied to the buyer's seat, a plain guess at the hard problem behind it and a yes or no question that invites correction. Seventy words at most.

The others change one or two things. One quotes what the buyer said in public and asks one question about it. One states a strong guess and asks to be corrected. One names the signal and asks a single question in under 30 words. One asks who owns the problem, for when the seat might be wrong. One names what a similar client did after the same event, and only runs when your Brain has real proof to cite.

Here's the shape of the under-30-words opener.

Saw the Head of Data Platform role go up. Is the role there to run the current stack or replace it?

How a message gets its construct

Before anything is written, Stage 1 picks the door for each person. Cold doors use research. Warm doors use a relationship. Each door has its own constructs and its own champion, so a note to a former colleague never competes with a cold note to a stranger.

Inside a door, most first messages go to the champion. About 15 percent go to the constructs in testing. And 5 percent of cold first messages go to the original Hypothesis Opening, always. That fixed baseline is how a fading champion shows up. If the champion is slipping and the baseline isn't, you see it.

Every message is tagged with its construct, signal, seat and path, then followed to the outcome.

What counts as winning

A construct is scored on first messages, by person. Success is a positive reply or a booked meeting. An out-of-office doesn't count as a reply. Opt-outs are tracked on their own, and a construct that draws too many gets paused.

Results are split by signal and seat too. A construct that beats the champion on leadership changes sent to the economic buyer, with 95 percent confidence after 100 sends, becomes the default for that kind of send. The champion keeps everything else.

The daily testing pipeline does the promoting and retiring.

The checklist on every draft

Under each draft on the Desk, an orange note flags a sentence that opens with I or We, a chase like "just checking in", a placeholder left in brackets, or a message running past its construct's word limit.

Email steps get a subject of two or three words drawn from the signal, like "Inherited backlog" for a new executive or "Margin squeeze" for margin pressure.

Where you find it

Open Insights, then Constructs. Each door has a board with its champion, the constructs in testing, the queue and the retired ones. The owner can turn testing off and run the champion only, or pin one construct as the firm's default for cold first messages.

Why it matters for a services sale

A services firm working a focused list of accounts can't run a fair test of two openers before the quarter is over. Pooled across firms, the platform constructs can.

And the measure is the right one. The opener that gets corrected earns the conversation that leads to a meeting, which is what the scoring rewards. For why replies alone mislead, see reply rate is the wrong north star.

With review on, which is the default, every first message waits for you before it goes. The construct drafts it. You own it.