VARS Framework (Validate, Acknowledge, Reframe, Specify)

What it is

A four-step conversational technique for handling a customer's live question about a competitor, presented by Alex McDonnell as part of the Competitive Intelligence Alliance's CI: Masters certification programme. Where the Competitive Battlecard Framework is the content a rep prepares in advance, VARS is the technique for delivering it live, in the room, without the conversation curdling into a defensive feature-by-feature fight. The four steps run in sequence: Validate (before addressing the competitor at all, learn what is actually on the buyer's mind; a rep who launches straight into a rebuttal skips the chance to learn how seriously the buyer is considering the alternative), Acknowledge (name the competitor's genuine strength rather than dismissing it; a rep who won't credit an obvious strength reads as biased, and a buyer who has used the competitor for years will simply stop trusting anything said afterward), Reframe (once the competitor's strength is acknowledged, shift the buyer's attention to a different, more fundamental problem the competitor is not positioned to solve, rather than continuing to argue on the competitor's own chosen ground), and Specify (close with something concrete: a specific proof point, a demo moment, or a named customer outcome that makes the differentiation stick rather than staying an abstract claim). The insight behind the sequence is that a rep who jumps straight to rebuttal turns a competitive question into an argument the buyer did not ask for; validating and acknowledging first defuses the defensiveness that makes a reframe land.

When to use it

• A buyer asks directly how you compare to a named competitor, in a discovery call, a demo, or a procurement Q&A, and the rep's instinct is to launch straight into a feature comparison.
• Reps report that competitive conversations feel like arguments rather than discovery, a sign they are skipping Validate and Acknowledge and going straight to a rebuttal the buyer did not ask for.
• A Competitive Battlecard Framework exists but reps still stumble in live competitive moments. A battlecard supplies the content (the pitch, the counter, the proof points); VARS is the missing delivery structure for using that content without sounding defensive.
• Win/loss interviews show deals are lost to a competitor buyers were actively comparing you against, and the loss reason cites a rep who "got defensive" or "didn't seem to know the competitor well," a delivery problem VARS is built to fix.
• Onboarding a new rep who has strong product knowledge but freezes or over-explains when a competitor comes up mid-call. VARS gives a simple, memorable sequence to practise against, rather than a page of talking points to memorise.

How to run it

1. Train reps on the sequence, not just the acronym. Role-play all four steps together; a rep who skips straight to Reframe without validating and acknowledging first still sounds defensive, even with the right closing proof point.
2. Pair VARS with the relevant Competitive Battlecard Framework entry. VARS is the delivery technique; the battlecard is the source of the specific acknowledgement (what the competitor is genuinely good at), the reframe (the problem they are not positioned to solve), and the Specify step's proof points. Reps should never be improvising the content live, only the conversational sequence.
3. Practise the Validate step as a genuine question, not a formality. "What's drawing you to look at [competitor] as well?" surfaces how seriously the buyer is considering the alternative and what specifically they value about it, information that shapes which acknowledgement and reframe actually land.
4. Write the Acknowledge line for each competitor in advance, sourced from the same battlecard research (a real demo, real customer feedback, an honest read of what the competitor does well), so reps are not put on the spot to invent a fair-sounding concession live.
5. Draft the Reframe as a genuine shift in the problem being discussed, not a disguised feature comparison. A strong reframe moves from "whose feature list is longer" to a different question entirely, the one the acknowledged competitor is structurally not built to answer.
6. End every Specify step with something concrete and, where possible, visual. A live demo moment or a specific customer outcome ("this customer cut implementation from six weeks to three days") sticks; a general claim ("we're more flexible") does not.
7. Review real call recordings for VARS adherence, not just deal outcomes. A rep can win a deal despite skipping the sequence; reviewing the actual conversation is what shows whether VARS is being used correctly and where reps still default to old habits under pressure.

Cadence & ownership

PMM or the CI function owns building the Acknowledge, Reframe, and Specify content for each named competitor, sourced directly from the Competitive Battlecard Framework so the two stay consistent; sales enablement or sales leadership owns training reps on the four-step delivery sequence itself and running the role-play practice that makes it stick under live pressure. Refresh the content on the same cadence as the underlying battlecard, and retrain whenever a new competitor becomes commonly named in deals or an existing competitor's genuine strength changes enough that the Acknowledge line is no longer accurate.