The calendar invite lands in the SE's inbox on a Tuesday afternoon. Three lines underneath it: show the mobile app, the automated dispatch, and the new analytics dashboard. The AE who sent it isn't being careless. They're covering three deals this week, and forwarding the invite feels like help, a fast way to hand off what the SE needs to build a good demo.
What actually lands in the SE's inbox is a request to build a persuasive meeting with no objective attached, no read on who's in the room, and no point of view about what should change in this buyer's business. The SE does the only thing possible with that brief: they build the most complete version of the three things on the list.
A field service software company gets a walkthrough of the mobile app, the dispatch engine, and the dashboard, delivered well, received politely, and forgotten by Thursday.
SalesTeam2Win has a name for this pattern: Just Do What You Normally Do.
A Win Plan is a collaborative document an account team builds before a demo. Objective, audience, and point of view get worked out together, then capabilities come into play. Capabilities come last on purpose, because what you show only makes sense once you know why the demo exists.
JDWYND isn't the AE being lazy. It's the AE handing off the demo strategy to the one person on the account team who doesn't have the relationship intelligence to set it up: the SE. The AE knows why this deal matters, where it sits in the buyer's evaluation, and which stakeholder in the room is still not sold. None of that fits into three lines in a calendar invite.
A topic list is better than nothing. It's also not what the buyer needs, because the buyer showed up with a business problem to solve, not a feature list to confirm.
Demo2Win spends real time training SEs not to build feature tours. Hand that same SE a list of capabilities and nothing else, and a feature tour is the only demo they can build. That's not a training failure. It's a briefing failure, and the training can't fix a gap that sits upstream of where it operates.
The intelligence that would have changed the demo already exists. It just sits with the AE instead of the SE: a VP's specific concern about implementation timelines, a reference customer who solved this exact dispatch problem eighteen months ago, a clear read on which stakeholder is the real skeptic and which one tends to ask the most questions. None of it reaches the person building the meeting.
You can't build a persuasive event without a clear strategy. A topic list isn't a strategy.
The fix isn't a better topic list. It's a different document, built in a different order, and the order is the part most account teams skip.
A Win Plan objective names the decision or action the team wants from the meeting. Compare these two versions of the same deal: a mid-market manufacturer evaluating a supply chain platform, six weeks from a board deadline to cut deal cycle time.
The weak version is a list of what will happen on screen. The strong version is a statement of what should happen in the buyer's head by the time the screen goes dark, and it gives the team something to test every other decision against.
Every other component in the Win Plan gets measured against the objective once it exists. Without one, there's no basis for cutting anything from the plan, which is exactly why unplanned demos try to cover everything and land nothing.
The objective is also, correctly, the AE's to set. It depends on where the deal actually sits in the buyer's journey, what the board deadline is, and what the champion needs internally to move this forward. That information lives with the person who owns the relationship, not with presales.
Skip the objective, or get it wrong, and the team has nothing to measure the plan against, so everything ends up getting included. Get it right, and they know what to build toward and what to leave out.
An objective names the outcome the team wants. On its own, it doesn't say what to tell the room to get there; that's the job of the audience and point of view: they determine which messages move these specific people toward it.
Take a healthcare scheduling deal with two attendees on the call. The VP of Clinical Operations cares about automated patient reminders because her system-wide initiative to cut no-show rates lives or dies on adoption across a dozen clinics. The clinic manager on the same call cares about the same feature, but for different reasons. To her, it means the front desk will stop making 40 reminder calls a day.
Same capability, same demo, two entirely different reasons it matters, and a Win Plan maps both against two axes:
Personal motivation sits underneath business motivation, and it often decides more. A newly promoted director wants a visible win in her first quarter. Someone eighteen months from retirement wants nothing to break before he leaves. Same demo, same room, two different definitions of a good outcome, and the team needs to know which one they're presenting to.
This is where the AE's real contribution shows up, and it isn't reciting features. It's the claim, "here's what we believe should change about how your business runs," not, "here's what the product does."
That point of view is the thing the demo has to argue for. Capabilities don't exist to be shown. They exist to prove that specific claim to those specific people, which is exactly why the team can't responsibly pick capabilities before this work is done.
With the point of view settled, the fourth component finally has a job. Take five typical capabilities:
Picked first, a team shows all five because all five are real and all five are true. Picked fourth, after objective, audience, and point of view are locked, the same five capabilities get a different job.
Single sign-on stops being a feature and becomes proof that IT's rollout concern is handled. Automated reporting stops being a checkbox and becomes proof that the clinical VP's adoption numbers will actually surface. The capability didn't change, only the reason for showing it did.
By the time the team reaches capabilities, the question has narrowed from "what should we show" to "what proves our point of view to these specific people, for this specific decision." That's a short list. The first version of that question never is.
A clear point of view also gives the team something to cut against, and cutting is usually the hardest part of building a demo without a framework. Nobody wants to leave a real feature off the screen. But a capability that doesn't prove the point of view isn't neutral. It's a detour, and every detour costs the team time they don't have with a buyer who's watching the clock.
These same capabilities become the Tell-Show-Tell topics and shape the Visual Roadmap for the rest of the meeting, so getting this sequencing decision right, or wrong, carries through everything that happens after it.
Starting with capabilities produces a feature tour. Starting with the objective produces a business conversation.
The same logic that governs what gets shown applies to who shows it. Most account teams default to a version of "AE handles the Statement of Intent and Next Steps, SE handles everything in between." That split isn't wrong. It's also not a decision anyone actually made for this deal. It's a habit the team inherited.
Presales capacity is a real constraint on most account teams: the fewer SEs there are relative to the accounts they cover, the more each minute of demo time is worth. That math points one direction. It makes the AE's presence in the room matter more, not less. The AE is with the buyer longer than anyone else on the account team, and every demo moment they sit out is a missed chance to show the buyer they've been heard. Four moments in the 2Win Structure are where that participation earns the most:
Consider a Closing Tell at a fintech deal where the AE had planned this in advance: ask the Controller to describe, in her own words, what forty fewer hours at month-end close would mean for her team. That's a different meeting than the version where the AE jumps in mid-Show with "can you also show them the reconciliation report," because one was planned and the other was an interruption.
Planned participation reads as partnership. The same contribution, unplanned, reads as an interruption.
The buyer is quietly forming an opinion about what post-sale support will feel like based on which version they just watched.
Before your next significant demo, ask the four questions in the order the Win Plan specifies: why are we doing this, who's in the room, what's our point of view, and only then, what proves it.
The fourth question has an obvious answer once the first three are settled. It almost never does when it's asked first. Once those four are answered, decide who on the account team delivers which moment, instead of defaulting to the split you've always used.