1 min lesson
Keep positioning current
Rebuild the sequence in "Keep positioning current" from memory, ending with the check that proves the outcome.
Step 1 of 2
Keep positioning currenta claim true last quarter can be stale today
- 1Re-check claims on a cadence. Treat competitive copy as perishable; set a recurring review so a feature gap you cited isn't quietly closed.
- 2Watch the channels devs watch. Release notes, X, Hacker News and GitHub threads are where the field shifts before any analyst notices.
- 3Test claims against the live products. Use the competitors enough to speak from experience, not from their landing pages.
- 4Version your battlecards. Date them and note what changed, so sales never pitches a claim that went stale two releases ago.
Overclaiming is the fastest way to lose a developer audience and, in a competitive deal, to lose the deal. One demonstrably false comparison and the engineer discounts everything else you said. When you're unsure whether a claim still holds, soften it to what you can prove or cut it - a smaller true claim beats a bigger false one every time.
In the cross-functional panel, expect a competitive question. Show range and honesty: “Copilot's reach is real and I'd never pretend otherwise; where I'd plant Cursor's flag is editor-native multi-file work over a codebase the model can actually see.” Crediting the rival first is what makes the differentiation land.