Relationship

The Email Playbook

What this build is for

Email reaches people who already know you, with the one thing they need next, in words they can forward.

It's the oldest channel in this playbook and the most misused. Most firms run it as a broadcast: a newsletter on a schedule, a promotion when sales are slow, a sequence for every download. That reaches everyone and answers no one. This playbook runs it the other way: a message exists only because someone, at a known moment, has a question it answers.

Email belongs to the Relationship category: your system, talking to people you already know. That gives it two jobs. Inside a relationship, it keeps the people around a deal or a review informed at the moments they'd otherwise wonder: is it on track, are the savings real, what happens next. Around the relationship, it keeps Kestrel's thinking in front of people who aren't buying yet, through a newsletter worth reading, cut from Content's core pieces.

Email writes every message other builds send. Automation decides when a message goes; the pitch decides what goes in the proposal; Customers decides when to ask for a referral. The words come from here, written once, in the brand's voice, checked against Credentials.

The footprint, and what it reads from the chain

In Kestrel's map, email leads 3 cells and 3 moments, all during and after the review, where a busy executive needs to know without asking:

It supports 14 more cells, among the widest support of any build: the business case moments for the COO, owner and finance director (7 of them), the investor's trigger, week zero and the plant manager's weekly tasks, the follow-on for the COO, owner, plant manager and investor, and the improvement lead's delivery and next review. In almost all of them, another build decides the moment and email carries the words.

What it reads, and never rewrites:

Its slice of the Score, and its own audit

Email's part of the Selectability Score is Answered and Believed at the moments after the signature: does the COO know how it's going, and does the finance director believe the savings?

The pattern is clear: Kestrel keeps the COO informed and leaves the finance director to guess. The COO hears from the engineers on site; nobody writes to the finance director until the invoice. Yet the finance director decides the next review, and their "are the savings real?" is the question every future proposal has to answer.

The audit.

The newsletter is the same mistake as the old blog: it exists because a calendar said so.

Step 1: the shape, the lifecycle programme

Email's shape is the lifecycle programme: the streams of messages a relationship goes through, from first contact to the next piece of work. Every category has the same skeleton; what changes is how long each stream lasts and who reads it.

Canon is just the welcome and the newsletter: everyone does them, so their absence would be noticed. The opening is in the streams almost nobody runs: delivery, results and renewal. That's where Kestrel's moments are, and where its competitors leave the finance director guessing.

Step 2: coverage, one message per question at each step

The coverage unit is a message per question per step. For each of the 17 cells email leads or supports, take the chooser's question and ask: is this answered best by a message arriving on its own, at the right moment? If yes, it gets a message.

That's 14 messages written once, three weekly templates, and a monthly newsletter. Every message has a moment; none is there because a sequence needed a fourth email.

Step 3: gaps, biases and jobs

The biggest gap is one person. The finance director is written to at none of the moments where they decide what Kestrel is worth.

Step 4: reconcile, the email plan

Every moment email leads or supports has a message; every message has a sender. The two P1 streams are the ones no competitor runs.

Rejected, with reasons:

• A five-email sequence after every download. Nobody downloading a cost article is waiting for five emails. One acknowledgement, then the newsletter if they ask for it.
• Promotional emails. Kestrel has nothing to discount, and no moment asks for an offer.
• The firm-news newsletter. Replaced. News survives as two lines at the foot of the monthly issue.
• Personalisation by first name only. It answers nothing. Personalise by role and moment, or not at all.

The anatomy library

Five rules hold for every message:

• It comes from a person, by name, who will read the reply.
• The subject line answers or names the question. Never "Update" or "News".
• One thing to do, or nothing. An update with three asks gets none of them done.
• Every figure is signed or theirs.
• It can be forwarded as it is. The COO forwards the Friday update to the board; write it for the board.

Briefs: the programme brief, then a brief for every message

STREAM Delivery
RUNS Each week of a review, weeks 1 to 6
MESSAGES Monday tasks (plant manager); Friday update (COO, copied to
the
               finance director from week 3); savings tally (finance
director,
               from week 3)
MOMENTS COO, finance director, plant manager · delivery
FROM The lead engineer, by name
SENT BY Automation: review rhythm, from the delivery tracker
VOICE Plant language; findings in the plant manager's words
OWNER Head of delivery
MEASURE Replies that confirm or correct a finding; the COO forwarding

MESSAGE The savings tally
JOB Believed · finance director · delivery · we follow others
THEIR QUESTION "Are the savings real, and are they being counted properly?"
ANSWER FIRST The running total, with a low and a high, and how it's counted
PROOF Each finding agreed by a named person at the client
THE ONE THING Tell us if any line doesn't match your view
GUARD No finding counted until the client's own person has agreed it

The finished example: Hartwell's week four, and the 90-day check, written in full

Three messages from Kestrel's review at Hartwell Plastics, the account from the Pitch Playbook. Hartwell, its people and its figures are invented.

1. The Friday update, week four. To the COO, Lena Marsh; copied to the finance director, Tom Avery.

• Subject: Week 4 at Hartwell: warm-up scrap after changeovers is the biggest loss so far
• Lena, four weeks in, here's where we are.
• What we found. After each mould change on lines 2 and 4, the first 40 minutes of parts are mostly scrap while the tool comes up to temperature. That's nine changes a week, and the largest single source of the 5.8% scrap rate. What changed on the floor. Dave's crew on line 2 trialled pre-heating the next mould during the last hour of the run. Warm-up scrap fell by about two-thirds on the four changes we measured. What's next. The same trial on line 4 next week, and a look at regrind ratios, which drift on night shift. What we need from you. Nothing this week.
• Priya Raman, lead engineer, Kestrel Advisory

2. The savings tally, week four. To the finance director, Tom Avery.

• Subject: Savings found so far at Hartwell: A$185,000 a year (range A$150,000 to A$210,000)
• Tom, this is the running tally, and how each line is counted. A finding only appears here once someone at Hartwell has agreed it.

• Not counted yet: the line 4 trial, until it's measured next week. If any line doesn't match your view, reply and I'll walk you through it.
• Priya Raman

3. The 90-day check. To Tom Avery, 90 days after the review closed with A$214,000 agreed.

• Subject: Hartwell, 90 days on: are the A$214,000 of savings showing?
• Tom, when the review closed in December, we agreed savings of A$214,000 a year, mostly scrap and resin. Three months on, does that match what you see in the accounts?
• A one-line reply is plenty: "yes", "about A$x", or "not yet". If it's not showing, I'd like to understand why, and we'll come back on site to find out.
• Priya Raman

What to notice. Each subject line is the answer. The update is written for the board as much as the COO, because it will be forwarded. The tally counts nothing the client hasn't agreed, which is why the finance director believes it, and why, at 90 days, a "yes" becomes a signed case for the next proposal. And none of the three asks for anything the reader can't do in a minute. Three messages, for one week and one check, at one client.

Templates

The message inventory (one row per message; the build's single list)

The stream brief

STREAM [name] RUNS [when, how long]
MESSAGES [each one, to whom]
MOMENTS [chooser · step]
FROM [a named person] SENT BY [person or flow]
VOICE [from Identity: words to use and avoid]
OWNER [who reads the replies]
MEASURE [the stage it serves]

The message brief

MESSAGE [name]
JOB [stage · chooser · step · bias]
THEIR QUESTION [in their words]
SUBJECT [the answer, or the question]
ANSWER FIRST [the first line]
PROOF [signed claims, or their own figures]
THE ONE THING [what they do, or nothing]
GUARD [passes only if it can be forwarded as it is]

The newsletter plan (one row per issue)

In the campaign plan

Every campaign has an email moment, usually more than one. The rule: a campaign's emails are written from its core piece and sent to people for whom its question is live, never to the whole list.

Running it

Who owns what. At Kestrel, the marketing lead owns the message inventory, the voice and the newsletter. Every message in a deal or a review is sent in the name of the person who'll read the reply: the deal owner, or the lead engineer. The head of delivery signs the delivery templates; the managing partner signs anything that states the way out.

Permission. Messages in a deal or a review go to the people in it, about it. The newsletter goes only to people who asked for it. Keep the two lists apart, so nobody joins the newsletter because they once signed a contract.

Common mistakes

The bias to watch in the team: the curse of knowledge again, in its email form. The engineer knows what "OEE up 6 points" means; the finance director needs the money.

The business check and the measures

• Revenue: the delivery and results streams protect the next review at every client and make the proof for every new one. If only one stream can be built, build the savings tally and the 90-day check.
• One truth: every figure in every message matches Credentials and the client's own records.
• The offer: the 90-day check asks a question the firm must be ready to hear "no" to. Decide in advance what Kestrel does when savings aren't showing.
• Capacity: the Friday update takes the lead engineer 20 minutes with the template, an hour without it.

The Loop for this build

Each quarter the Loop (step 11) reads replies and decisions beside the Score's delivery and extend moments, and asks: did the people we wrote to believe the results, and act on them?

What Kestrel's first year would look for. Finance directors replying to the tally during the review, which nobody did last year. Then the 90-day checks: if most say "yes", Kestrel has more confirmed cases in a year than it has in its history, and the finance director's "consultants overstate savings" has an answer in every proposal.

Shapes by business type

Feeling a bit overwhelmed?

You should be, a little. One firm: seven streams, 14 messages written once, three weekly templates for every review, a monthly newsletter cut from the content plan, every figure agreed by a named person at the client, and two lists that must never mix. Most firms send a quarterly newsletter of their own news and wonder why the finance director never believes the savings.

RocMode does part of the heavy lifting:

• Emails and sequences, drafted on brand. RocMode's Email Studio drafts your messages and sequences in your voice, from your strategy.
• The moments behind every message. Your choosers, their steps and their questions, mapped from what's known about your brand, so each message starts from a question someone actually has.

Join the RocMode beta