Sales Engineer Roleplay: Joint Calls

Why do AE and SE joint calls fail?

They fail on choreography. Both people usually know their material. What they lack is an agreed answer to who speaks when, who owns which question, and who lands the next step.

Three patterns are worth naming. The AE and SE answer the same buyer question in sequence, and the second answer softens the first. The buyer asks a business question — how would we justify the spend — and the SE answers it with a feature tour. Then the call ends with a vague commitment to circle back, because each person assumed the other owned the close.

You can learn choreography on live calls. It is the most expensive way to learn it, because the tuition is paid in deals. Rehearsing the same sequence in a scored session costs a half hour and no pipeline. The counterargument is fair: live calls carry pressure a practice session cannot fully reproduce, and some pairs do sort themselves out after enough shared reps. Our objection is to the cost, not the premise — you are running an unscored experiment on a real buyer and getting no transcript-level feedback from it.

Two competent people with no agreed role split will collide on the questions that matter most.

The pre-call role split: pain, proof, and the close

Write the split down before the call. Three sentences in the calendar invite is enough. Anything that lives only in a verbal agreement dissolves the moment the buyer asks something unexpected.

The AE owns pain and the close. That means the opening agreement about purpose, time, and acceptable outcomes — the Sandler up-front contract, including that a no is an acceptable outcome — plus every question about cost of inaction, decision process, and the next step. The SE owns proof and technical qualification: current architecture, constraints, integration surface, what would have to be true for the solution to work in this environment.

Neither person owns everything they are capable of answering. That is the point. An SE who can answer a pricing question should still route it, because routing is what keeps the buyer's mental model of the two roles clean.

The person who owns the close should say the next step out loud while the buyer is still on the call.

Which handoff cues should both sides drill?

Five lines cover most joint calls. Four of them are routine traffic control; the last is a recovery cue the AE uses only when a demo has already run away. Drill them verbatim until they arrive without thought, then let the branches improvise from there. An agreed first response is not a script for the whole conversation; it is the thing that keeps a pair from colliding in the first two seconds after a surprise.

The objection that agreed language sounds canned is worth taking seriously. It is true when reps recite lines they do not understand. It stops being true when the line is short, the rep knows exactly what it is protecting, and everything after it is unscripted.

Handoff lines only work when both people can say them under interruption without pausing to remember them.

What do you do when the SE gets pulled into a demo too early?

The SE names the trade-off, buys back one question, and only then decides whether to share a screen. The recovery is four moves and takes under a minute.

One: acknowledge the request without deferring to it. Two: time-box what you would show. Three: ask the one technical question you need to make the demo relevant — the constraint, the volume, the system it has to sit next to. Four: show narrow, or defer explicitly to a scoped session with a named owner. The AE's job during all four moves is to stay quiet, then re-anchor to pain the moment the SE hands back.

A failing recovery is easy to spot on the transcript. The buyer says something like can you just show us, the SE says sure, and the next long stretch of transcript is all SE. Nobody asked what the buyer wanted to see or why. By the time the AE speaks again, discovery is over and the call has become an unqualified product tour. If your SEs demo before qualification often, the fix is upstream of choreography — see Demo Certification Before Live Demos.

Screen share is a decision, not a reflex, and the SE is the one who has to make it out loud.

A rubric for joint call choreography

Score the pair on one rubric, in one session, with one set of flags. Separate scorecards let each person read the other's failure as their own success.

Keep it to five rows. Every row has to be verifiable from the transcript alone by a manager who was not on the call. Talk/listen is worth logging as a diagnostic — an AE/SE split that swings hard toward the SE is an input to investigate, not a pass bar on its own.

A generic joint-call rubric will not hold up here either. Load your own call stages and your own discovery exit criteria into the rows, or the pair will rationally discount the feedback.

The paired technical discovery drill you can run this week

Run it as a 30-minute block: 5 minutes setup, 15 minutes drill, 10 minutes debrief. Budget about 10 minutes beforehand to pick the scenario from a live deal and choose which rubric row you are scoring. That prep is the part managers skip, and skipping it is why the debrief drifts.

Scenario: a technical evaluator and a business sponsor on the same call. Script the buyer to ask for a demo in the opening minutes, then to ask a cost-justification question directly of the SE partway through. Both requests are traps for the role split. If you are building the persona from a real deal, Buyer Persona Roleplay: Play the Buyer covers the character sheet.

Pass bar. All three must hold. No screen share until the SE has time-boxed the demo and captured the discovery exit criteria named for your stage. The cost-justification question is routed to the AE within one turn. The AE states a next step with a named owner and a date before the call closes.

What a failing attempt sounds like. The SE says happy to show you and shares immediately, with no qualifying question and no time box. The AE fills the silence after the buyer's first pain answer instead of waiting. The cost-justification question gets a feature answer, then a second answer from the AE that contradicts the framing. The call ends with we'll send over some materials.

Re-run rule. A failed pair re-runs the same scenario within the week, before their next live joint call. Change nothing except the one behavior you flagged.

A drill without a stated pass bar is a conversation, and conversations do not certify anyone.

Debriefing a pair without starting an argument

Pick one moment and one behavior. Play the flagged clip, ask the person who owned that moment what they were solving for, and let them self-diagnose before you render a verdict. Ask the partner second, and only about what they would have done differently in their own role.

Comprehensive feedback breaks pairs faster than it breaks individuals, because every observation reads as an assignment of blame. Three flags in one debrief and the pair spends the next call watching each other instead of the buyer. One flag, one re-run scheduled on the calendar, done. The full format is in Sales Roleplay Debrief: One Behavior, Re-Run.

In XL Roleplay, the flags in a scored session link back to the exact transcript moment, which is what keeps the debrief from becoming a memory contest between two people who remember the call differently.

Debrief the pair on one moment, or they will spend the next call managing each other instead of the buyer.