Plays and messaging
Generic messaging is the most common failure of this whole skill. A finished plan can have perfect scoring and still be worthless if the copy could be sent to any vertical at any event. What follows is the structure that stops that.
One play per track
Five tracks cover almost every event. Write one play for each that has accounts in it, and skip the ones that do not.
| Track | Who it is for | The wedge |
|---|---|---|
| Migrate | Accounts on a defunct or end-of-life competitor | Their deadline, not yours — a forced migration with a date attached |
| Displace | Accounts on a live competitor | The specific gap, not a feature list |
| New logo | High-fit accounts with no competitor tag | The problem, before the category |
| Expand | Existing customers | A division, team, or workflow not yet covered |
| Booth demo | Anyone who walks up | What can be shown in four minutes |
Play anatomy
Every play carries five parts. A play missing any of them will not survive contact with a rep on a show floor.
- Title — how the team refers to it out loud, all week.
- Who it is for — the track, plus the persona inside it. "IT operations leads at accounts running an end-of-life competitor", not "Tier 1".
- The body — three or four sentences a rep can internalize, naming the specific thing that vertical cares about: the compliance regime, the network zone, the audit cycle, the ticket queue, the certification deadline.
- A verbatim opening question — one sentence, in quotes, that a rep can say out loud at a booth without adapting it. This is the part teams actually use and the part most plans omit. It should be answerable by a stranger in one breath and should reveal whether the person has the problem.
- The proof point — the customer, the number, or the reference that makes the claim survive a follow-up question.
The persona-mix check
Before finalizing any of it, count buyer-persona titles among the named attendees.
If most attendees do not own the budget for what is being sold — extremely common when a security product is marketed at an infrastructure or operations event — say so plainly in the deliverable and change the aim of the copy. Do not quietly write persona-perfect messaging for people who will not be in the room.
The re-aim is always the same move: lead on operational cost rather than on the product category. Cycle time, ticket volume, audit hours, on-call load, manual steps per change. An operations lead who cannot sign a security purchase can absolutely describe the pain to someone who can — but only if the opening question was about their day rather than about your category.
Anti-patterns
- The category pitch. Opening with what the product is rather than what the person is dealing with. Fails hardest at a booth, where the listener has eight seconds and forty other booths.
- The feature list as displacement play. "We do X, Y, and Z better" loses to a single named gap the person has already felt.
- One play for all verticals. If the body reads the same for a hospital system and a regional bank, neither will recognize themselves in it.
- The unaskable opener. A question that takes twenty words of setup is not an opener. If a rep would rephrase it, it is not verbatim.
- Treating the migrate track like the displace track. An account whose vendor has gone end-of-life is not being sold to — they are shopping, on a clock, and the play is to be the easiest option, not the best one.
- Aggression on the competitor. Naming a competitor's failure works when the buyer already knows it. Telling them it happened reads as a sales tactic, even when it is true.
What the plays are for
The plays are the part of the deliverable a human reads before walking onto the floor, and the only part that gets quoted back. Every line should survive being read on a phone, standing up, thirty seconds before a conversation.
Write them last, after scoring — but write them for the accounts, not for the tiers. A play that names something real about eleven migrate-track accounts is worth more than five plays covering the whole list evenly.