The Trigger
Use it when something has just changed at their company: a funding round, a new leader, a hiring push, a new office, a product launch. Step type: Email (you send it), because the trigger is different for every account. The shape- The change, in one line, stated as a fact.
- The problem that change usually creates.
- A question that asks whether it is true for them.
- If you have the trigger in your list, put it in a column and use
{{custom.trigger}}. Then the step can be an automatic Email. - Leave out the trigger if it is more than a few weeks old. Old news reads as a mail merge.
The One Problem
Use it when you have a list of people in the same role and no specific trigger for each one. Step type: Email. The same words fit everyone in a well-built list. The shape- One problem that people in their role have, in their words.
- What it costs them, in plain terms.
- A question: is this you?
- Write one version per role. A VP and a team lead do not have the same problem.
- One problem. If you list three, they remember none.
The Lookalike
Use it when you have a real customer the prospect would recognize as a peer. Step type: Email if one story fits the whole list, otherwise Email (you send it). The shape- A company like theirs, and the situation it was in.
- What changed, in one line.
- A question that hands them the comparison.
- Only name customers who have agreed to be named, and only quote results you can back up.
- Pick the peer for the reader: same industry, same size, or same role.
- For an automatic step, put the peer in a column and use
{{custom.peer}}.
The Short Question
Use it when you want the lowest-effort reply possible, or you are restarting a thread that went quiet. Step type: Email. The shape- One sentence of context.
- One question.
- This is the easiest framework to send lazily. The context sentence still has to be true for the person reading it.
- It pairs well with a call the next day: “I sent you two lines yesterday” is an easy opener.
The Switch
Use it when the account already uses a competitor, and you are asking them to replace it. Step type: Email if the tool each account uses is in a column of your list, otherwise Email (you send it). The shape- Name what they use, plainly and without a dig.
- The one reason teams move from it to you, said about you and not about them.
- A question that lets them say whether they have felt it.
Keep it honest
A rip-and-replace email is the easiest one to get wrong, because it is about someone else’s
product.
- Say only what you can point to. State nothing about the other product unless it is on their own website or in their own docs, and note the date you checked. Pricing and features change.
- Talk about what you do, not what they lack. “We do this” is a fact you own. “They can’t do this” is a claim you have to prove.
- Don’t mock the choice. Someone at that company picked the tool, and it may be the person reading your email.
- Name only customers who agreed to be named, and quote only results you can back up.
- Before you upload your list, put the tool each account uses in a column called
tool. It becomes{{custom.tool}}. Only add people whose tool you know: a blank comes out empty, and Preview as a sample contact marks it Would be blank. - Write a battle card for each competitor before the first call. When a prospect says “we’re happy with what we have”, the rep has the answer, and Live Assist can put it on screen the moment the tool is named.
- For the full sequence, see Rip and replace.
Next steps
Frameworks for before and after a call
The Heads-Up, The Double Tap, The Recap, The Right Person and The Not Now.
Cold email playbooks
Full sequences that chain these frameworks with call steps.