2 min lesson
Close the loop with the field
Talk this through in your own words: "A rep asks for a battlecard against GitHub Copilot. What principle governs how you build it and why?" Finish with the next move.
Step 1 of 2
Close the loop with the fieldmessaging is a hypothesis until the field tests it
The first version of a battlecard is a guess. The field tells you which lines actually land in a deal and which objections you didn't anticipate. Sit in on calls, read win/loss and revise - your enablement gets sharper with every deal it survives.
- Join real sales calls so you hear objections in the wild, not as you imagined them.
- Run win/loss reviews and trace losses back to a messaging or positioning gap you can fix.
- Track which battlecard lines reps actually use and quietly retire the ones they don't.
- Feed recurring objections back to product - sometimes the fix is a feature, not a talking point.
Dishonest battlecards backfire twice. A rep who repeats an inflated claim about a competitor gets corrected by a technical buyer mid-call and loses the room and they stop trusting your enablement after that. Be precise about where Cursor genuinely wins and candid about where a competitor is strong. Credible enablement earns reps who actually use it; spin earns a deck nobody opens.
If the panel raises enterprise, show you understand Cursor serves two motions and that enablement is the enterprise-side bridge. Name the specific assets, stress that battlecards must be honest to be used and say you'd close the loop by joining calls and running win/loss. That demonstrates you can extend PMM beyond launch-day broadcasting into the sales motion the company is now building.