Build the Card: Landmine Question and Talk Track for a Live Deal
Objective: Given a messy win-loss call transcript, draft the top-of-card elements a rep needs first: a landmine question, the competitor's one-sentence pitch, and one full talk track.
Allbirds keeps losing footwear deals to a fast-fashion sneaker brand undercutting on price. You have one win-loss call transcript and one quarter until the next sales kickoff.
Turn the transcript into the top of a usable battlecard: the landmine question, the competitor's pitch in one sentence, and a talk track for the price objection, then set a last-updated date policy.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, fast commenting and easy to hand off to a designer later
Paid upgrades (optional, faster/deeper)
Templated one-page layouts speed up the design pass once the words are locked
The process
2 steps
Step 01 of 02
The lesson's top-of-card element is one line the rep asks the prospect that surfaces the competitor's known weakness before the competitor can hide it.
The transcript shows the prospect discovered the competitor's shoes wear out within 4 months of daily use, after already signing. What question gets that fact on the table during the call, not after signing?
Procedure
- Read the transcript's loss reason section for the specific, named weakness
- Write one question the rep can ask early in the call that gets the prospect to state that weakness themselves
- Test it out loud: if it takes more than one breath to ask, cut it down
Landmine question: "How many pairs have you gone through with your current pair in the last year?"
Healthy
The rep asks the question in the first two minutes and the prospect volunteers the wear-out timeline unprompted.
Unhealthy
The question is really a feature pitch in disguise ('Did you know our shoes last longer?'), which reads as a sales line instead of genuine curiosity.
What this means
A landmine question sounds like curiosity, not a pitch, and the prospect supplies the damaging fact themselves.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| The question reads like a rehearsed sales line | Rewrite it as a genuine, open question with no product mention | 5 min |
Step 02 of 02
A visible last-updated date signals freshness to reps and creates social pressure on the card owner to keep it current.
This card will ship with a price-comparison table that changes seasonally. Where does the date go, and what triggers an update?
Procedure
- Add a 'Last verified: [date]' line directly above the pricing table, not buried in a footer
- Set a trigger: any confirmed competitor price change updates the date within 48 hours
- Assign one named owner for the update, not 'the team'
Last verified: Aug 2026 · Owner: PMM lead · Trigger: confirmed price change
Healthy
Reps see the date before they see the price and trust the number without double-checking.
Unhealthy
The date sits in a footer nobody scrolls to, so it exists but does not build trust.
What this means
A date only builds trust if it's positioned where the rep's eyes land right before the number it's verifying.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| The date is present but buried at the bottom of the doc | Move it directly above the pricing table | 5 min |
Final deliverable
A top-of-card draft with a landmine question, the competitor's one-sentence pitch, one full price-objection talk track, and a last-updated date policy.
See a reference example
Squarespace vs. Competitor Z, card top section Landmine question: "How long did your last free-tier site actually stay live before you hit a paywall?" Their pitch: "Build a website for free, forever." Talk track: "Free sounds great until you hit the 3-page limit in week two, ours gives you the full builder from day one, no surprise wall." Last verified: Aug 2026 · Owner: PMM lead
Success criteria
You're done when you can:
- Landmine question reads as genuine curiosity, not a disguised pitch
- Talk track is written as sentences a rep would actually say, not fragments
- Last-updated date is positioned directly above the data it verifies