Right after a demo wraps, there's almost always a Slack thread. The AE writes first: "Opener ran long. You got stuck on the security question, should've moved past it faster. Once their VP started taking notes, we should've picked up the pace." The SE reads it, gives a thumbs-up, and writes back, "thanks for the feedback, appreciate it."
The SE noticed plenty too: the AE's small talk in the first six minutes ate into the time meant for the close, and the AE answered a pricing question with the wrong tier before the SE could jump in. None of that makes it into the thread. It just gets carried into the next demo, unspoken, and shows up again and again.
A demo debrief that only runs one direction, from the AE to the SE, isn't a feedback problem. It's a role clarity problem. Account teams can only critique work someone was assigned to do, and when the AE has no defined role in the demo, there's no shared standard to hold them to.
Walk into almost any account team's post-demo routine, and you'll likely find the same two-minute ritual. The buyer drops off the call, and the Slack chat starts:
The SE says, "Noted for next time," and the meeting ends.
The other direction never happens, and it isn't because there was nothing to say. Everyone on that call noticed just as much:
Nobody said any of it out loud.
That asymmetry teaches the team something, whether anyone means it to or not. When only one person's performance is up for discussion after a shared meeting, everyone learns who is being evaluated and who is doing the evaluating. It doesn't matter what the org chart says about the AE owning the account. The debrief has already told the team who the real subordinate is in that room, and it did it without a single sentence about job titles.
Run this same two minutes at the end of every significant demo for a year, and before you know it, your team has formed a habit that is costing them more than deals. The SE learns to expect a note. The AE learns there's nothing coming in return, so there's nothing to adjust. Neither person decided this on purpose. The ritual decided it for them.
The easy read on this gap is that the team lacks the nerve to critique the person who owns the relationship. That read is wrong, or at the very least, incomplete. Feedback needs a shared standard to measure against, and the SE has one: everyone watching the demo knows roughly what a good version of the SE's job looks like, because the SE had a job. The opener, the sequencing, the close all belong to a role with a recognizable shape.
The AE walked into the same demo with no real instruction at all, just an unspoken assumption that whatever they normally do would be enough. Take the same AE at two different demos, three weeks apart: at one, they open with a sharp, forty-second scene-setter that gets the buyer leaning in. At the next, they ramble for four minutes about their weekend before getting to the point.
Both times, they get the same feedback. None. Was four minutes of small talk a mistake, or just how the AE runs the demo? There's no scorecard for what the AE was supposed to do in that room, so there's nothing for the debrief to measure against.
Leaders who notice this gap usually diagnose it as a trust or psychological safety problem and reach for training alone to fix it. It won't work here. The issue isn't that the team is afraid to say something; it's that there isn't clarity on the AE's role in the demo, making feedback arbitrary and most often, obsolete.
You can't give someone feedback on a job they were never assigned.
This is close to home for us, because it's the exact pattern our coaches kept running into. Demo2Win! does what it's built to do: SEs who go through it deliver demos that are correctly sequenced, well-paced, and aimed at the right stakeholders. Our coaches watched that happen, over and over, exactly as designed.
What they also kept watching was the other half of the room doing nothing with it. The AE sitting next to that SE wasn't underperforming their role in the demo. They didn't have a clear one. Half the account team walked into the highest-stakes meeting in the sales cycle without a job to do. A demo built by one person, however well it's built, is still only half of what a team sport requires.
The gap wasn't in what the SE built. It was in the seat next to them that had nothing assigned to it.
Some AEs already do this without being taught:
Those AEs aren't rare because the skill is rare. They're rare because nobody made it the standard for the role, so a handful of strong AEs end up covering for a lot of AEs who were never shown what the job should look like. That gap, between what a few people figure out on their own and what the whole team does by default, is what SalesTeam2Win! was built to close.
The Improvement Rhythm behind SalesTeam2Win! runs in three moves: Plan, then Execute, then Debrief. Plan is the one that does the heavy lifting, because a Debrief only has something to say about what a Plan actually assigned. Skip the Plan, and the Debrief is just two people reacting to a meeting with no shared reference point for what either of them was supposed to do in it.
Assigning that role changes what critique feels like on both sides. "Your Statement of Intent ran long" is a note about a job someone agreed to do. "You talked too much" is a note about a person. The first one is easy to hear because it's specific and fixable. The second one just stings.
Once both people carry a defined responsibility into the demo, they can also carry something to be debriefed on afterward. This way, nobody has to be the one who volunteers to go first or work up the nerve to say something risky, because the risk was never really about courage.
It was about whether there was a clear job on the table to talk about. Assign the job, and the debrief stops being an act of bravery.
Most leaders, checking the health of their account teams, listen for tone. Is the debrief pleasant? Does everyone seem to get along? That's the wrong question, because a friendly debrief and a real one sound almost identical from the outside.
There's a VP we've talked with who reviews demo recordings every week for quality: pacing, clarity, whether the SE hit the right stakeholder value. In three years of that habit, she'd never once asked who received feedback afterward. The recordings told her whether the demo was good. They didn't tell her whether the team was getting better at running the next one.
The direction of feedback is the easier thing to check, and it's a question a leader can actually answer this week without reviewing a single recording: after your last demo, who told someone something they didn't already know?
If the answer only ever points one way, the same gaps will show up in next quarter's demos exactly as they did in this quarter's, because half the team never had the chance to learn from what just happened.
A team where feedback only moves in one direction isn't a team. It's a hierarchy that happens to sit in the same meetings.
None of this happens where the buyer can see it. The buyer never sits in on the Win Plan conversation, and they never see how the two of you divided up the roles beforehand.
What they do see is smaller than that: who answers which question without looking at their teammate first, whether the handoff from AE to SE lands cleanly or gets fumbled, whether the two people in the room seem to have actually talked before today.
That read isn't about polish, and it isn't the buyer being generous about presentation style. It's a risk assessment, whether the buyer thinks of it that way or not. A team that can't operate seamlessly before the sale is a fair signal about what the post-sale team will look like once the contract is signed. Buyers who've been burned before know to watch for exactly that.
The coordination a buyer notices in the room didn't happen by accident, and it isn't chemistry between two people who happen to get along. It was built in Plan and kept alive by an honest Debrief the week before. Take that rhythm away, and coordination erodes within a quarter, whether anyone on the account team notices.
Buyers may never see your Win Plan, but they will feel in the first five minutes whether you built one.
The fix is to make sure both people walking into your next demo have an actual job to do, specific enough that you could sit down afterward and talk about how each of them did. Do that, and feedback begins with this question: who had something to be accountable for, and who didn't.