-
1
Define a sharp trigger for what earns a win wire
A win wire loses its teaching power the moment it fires on every closed-won deal. Decide up front what makes a deal worth broadcasting and write it down. Common triggers include a deal above a defined ACV band, a logo on your strategic account list, a competitive takeout against a named rival, a first win in a new segment or geo, and a new use case worth repeating. Enablement, not sales leadership, should own the trigger definition so it stays about teaching rather than recognition. Publish the rules in the same place reps go to request a win wire so there is no ambiguity about which deals qualify and which do not.
- Write down 3 to 5 specific triggers that qualify a deal for a win wire.
- Include an ACV floor so the channel does not fire on every SMB close.
- Add a competitive takeout trigger even on smaller deals when the rival is strategic.
- Give enablement final say on whether a deal qualifies, not the deal's rep or manager.
Tip: If you cannot name three deals from last quarter that would have fired a win wire under your rules, your trigger is too narrow. If you can name twenty, it is too broad.
-
2
Build a one-screen template the team can scan in 60 seconds
A win wire is read on a phone between meetings, not studied. Standardize a template that fits on a single screen with a predictable layout so readers know exactly where to look for each fact. The core fields are deal size band (anonymized), buyer profile (industry, segment, size), use case or primary problem, competitive context (who else was in the deal and what they offered), the winning narrative in three to five sentences, and one or two actions the field can repeat. Keep the layout identical every time. Repetition builds pattern recognition, and reps start recognizing the shape of a strategic win after four or five issues.
- Pick a fixed set of 6 to 8 fields and never add more without retiring one.
- Use deal-size bands such as 'mid six figures' rather than exact Strkr dollar figures or the buyer's exact spend.
- Lead with the buyer problem, not the product feature, so the lesson is portable to other deals.
- Close with a one-line call to the field such as which play, battle card, or asset the rep used.
Tip: If the win wire runs longer than one phone screen or three short paragraphs, cut it. The point is pattern transfer, not a case study.
-
3
Capture the facts from the rep and the deal record
A good win wire triangulates between what the rep says and what the CRM records. Pull the structured facts first: close date, product mix, close reason codes, competitor fields, and the opportunity notes. Then run a 15-minute debrief with the rep to get the narrative, the moments that changed direction, and the verbatim buyer language that mattered. Reps tell the deal story one way in a Slack message and another way in a structured debrief, and the second version is almost always more teachable. Capture the debrief in Strkr against the opportunity so the raw intelligence is searchable later, even if only the summary ships in the broadcast.
- Pull the opportunity record and read it before you talk to the rep so you ask sharper questions.
- Ask the rep for the single moment the deal turned, in their words, for example, 'they chose us over X because Y'.
- Capture 2 or 3 verbatim buyer quotes you can anonymize and reuse in the wire.
- Log the debrief notes against the opportunity in Strkr so marketing, product, and future reps can find them.
Tip: If the rep cannot name the turning point in one sentence, you have not debriefed long enough. Keep asking until there is a clear hinge in the story.
-
4
Write the narrative like a short field report, not a press release
The narrative section is where most win wires fail. Three to five tight sentences in plain language will teach more than three paragraphs of marketing copy. Open with the buyer problem in the buyer's own words. Name the competitive set and what each rival offered. Describe the specific move your rep made that changed the trajectory. Close with the business outcome the buyer bought into. Avoid superlatives, feature lists, and internal jargon. If a new rep reading the wire cannot explain the winning narrative to a prospect ten minutes later, the wire has not done its job.
- Start with the buyer problem, not the vendor name.
- Name the competitive set and the shape of each rival offer in one line each.
- Call out the one specific move the rep made that mattered most.
- End with the business outcome the buyer signed up for, not the feature they liked.
Tip: Read the narrative out loud before you publish. If it sounds like a case study pitch, rewrite it as a field report a peer rep would text to a friend.
-
5
Review for anonymization, accuracy, and brand voice
Before any win wire ships, run it through a two-person review for anonymization, factual accuracy, and tone. The named account, exact spend, exact seat count, and anything that could identify a confidential customer stay out unless you have written permission to use them. The deal numbers, competitors, and close reasons get a sanity check against the CRM record so the field trusts the broadcast. The tone gets a brand-voice pass so the wire reads as a confident field report rather than a marketing celebration. Published research from Gartner and Forrester on sales enablement shows that trust in the enablement channel is the single biggest predictor of whether reps change behavior from the content you send them.
- Scrub the account name, exact dollar amounts, and any detail that could identify a confidential buyer.
- Cross-check deal size band, competitor, and close reason against the CRM record of truth.
- Have a second reviewer, usually the enablement lead or RevOps partner, sign off before publish.
- Confirm the rep is quoted accurately and is comfortable with how their role is described.
Tip: If you have to ask whether a detail is safe to share, it is not. Default to the anonymized version and get written permission later if marketing wants to use the full story in a case study.
-
6
Publish on a predictable cadence in one owned channel
Reps learn the channel the same way they learn any other product in their life. If the win wire lands in the same place at a predictable rhythm, they open it. If it moves around or shows up in random all-hands threads, they tune out. Pick one owned channel, a dedicated Slack channel or a weekly enablement digest, and ship every qualifying wire there. Add a lightweight tag convention so reps can filter later: segment, competitor, and use case tags are enough. Pin the trigger definition and template to the top of the channel so the rules of the road are always one click away.
- Pick one channel and stay there. Do not cross-post into the main sales channel.
- Publish within 24 to 48 hours of close while the deal is still fresh in the field.
- Tag each wire with segment, competitor, and use case for later search.
- Pin the trigger rules and the template at the top of the channel.
Tip: A single predictable channel with 2 wires a week beats a sprawl of channels with 10 wires a week. Discipline is what makes the field actually read it.
-
7
Teach the behavior you want reps to repeat
A win wire is a teaching artifact first and a recognition artifact second. Every wire should close with a short list of concrete, portable moves other reps can copy on their own deals this week. Which battle card did the rep use. Which discovery question changed the shape of the deal. Which internal partner from product, security, or exec sponsorship did the rep pull in and when. The lesson is in the specifics. 'The rep ran a strong process' teaches nothing. 'The rep sent the executive one-pager three days before the committee meeting and ran a technical validation session with the champion the night before' is a move another rep can run on their deal next week.
- List 1 to 3 specific moves the field can copy, not general principles.
- Link each move to the asset, play, or template that supports it.
- Name the internal partners the rep used so other reps know who to call.
- If the move is new, add it to the shared play library the same week.
Tip: If you cannot connect every win wire to a repeatable move the field can run, you are writing a victory lap, not a wire. Rewrite until there is a copy-this move in every issue.
-
8
Measure engagement and feed themes into enablement
A win wire program should earn its keep in observable behavior change, not channel vanity. Track three signals every month. First, engagement in the channel such as reads, reactions, and threaded questions, as a leading indicator that the field is paying attention. Second, play adoption, meaning whether the moves called out in wires show up in new deals in call recordings and in CRM activity. Third, win rate movement on the specific competitive matchups the wires cover. Roll a short monthly summary back to sales leadership showing which themes are repeating and which plays are spreading. Over two or three quarters the win wire channel becomes the single most trusted source of real deal intelligence inside the company.
- Capture reads, reactions, and threaded questions on each wire as a leading engagement signal.
- Spot-check call recordings and CRM activity for the moves called out in recent wires.
- Review win rate movement on the named competitors you have covered in the last 90 days.
- Publish a one-page monthly summary with top themes and plays trending in the field.
Tip: If engagement on win wires drops for three issues in a row, the problem is almost always trigger drift or template inflation. Audit both before you blame the audience.
