60-Min Sales Training: Technical Demos + SE Partnership

Direct Answer

This is a 60-minute Monday-morning training that fixes the single most expensive failure pattern in 2027 SaaS selling: AEs running technical demos solo, then burning Sales Engineer hours on dead deals. By the end of the hour, every rep on your team will know the three-gate rule for bringing in an SE, the AE-SE pre-demo handoff brief, the TDD (Technical Deep Dive) structure, and a POC scoping contract that prevents the 60-day pilot purgatory.

Outcome: SE attach rate drops to 40-50% of qualified opps while win rate on those opps climbs 15-25 points.

1. Setup (5 min)

Agenda on the board before reps walk in. Six numbered blocks, time-boxed, no slides past slide 3. The point is muscle memory, not theory.

Opening line, verbatim: "We are not here today to debate whether SEs matter. We are here so you stop wasting them on deals that will never close, and start using them as the technical closer on deals that will. Pull up a deal you ran a demo on in the last 30 days where the SE came in cold. We will rebuild that opening together."

Warm-up question, round-robin, 30 seconds each: "Name one deal in the last quarter where you wished you had brought the SE in earlier — and one where you wish you had run the first call yourself."

Materials checklist: Gong recording of one strong technical demo, one weak one. The current AE-SE handoff doc (or a blank one — most teams have nothing). A printed POC scoping template (Section 3 has the verbatim text). One whiteboard or shared Miro.

Why this matters in 2027: SE headcount has been the #1 cost-cut target across SaaS go-to-market orgs for six straight quarters (Pavilion 2027 GTM Benchmark, Gartner SaaS Spend Review Q1 2027). Most orgs are running 1 SE per 4-6 AEs, down from 1:3 in 2024. AI-generated demos (Consensus, Demostack, Saleo) are pulling 30% of "show me the product" requests off the SE queue — but only if the AE knows when to use them.

If your reps treat SEs as on-demand demo monkeys, you are losing the political war for SE hours inside your own company.

2. Framework Teach (15 min)

Teach one framework. Drill it. Do not introduce a second. Reps cannot operationalize two new things in 60 minutes.

The Framework: GATE-3-1

Three gates an opp must pass before an SE is engaged. One artifact (the pre-brief) that the SE receives before the meeting. Named at Demostack's 2027 Presales Summit, popularized by Presales Collective.

Gate 1 — Confirmed Pain (the AE owns this). The buyer has stated, in their own words, a business problem with a dollar number attached. Not "we're evaluating tools." Not "looking at our stack." A sentence like: "Our forecast accuracy is off by 22% and our CFO is asking why we missed Q1 by $4M."

Gate 2 — Confirmed Authority Path (the AE owns this). You know the economic buyer's name, the technical evaluator's name, and the procurement gate. Not "we'll loop them in later." Specific humans, specific dates.

Gate 3 — Confirmed Technical Question (the SE pre-qualifies this). There is a specific technical concern the AE cannot answer credibly. Not "show them the product." A sentence like: "They use Snowflake + dbt + Hightouch in reverse-ETL mode and want to know if our event ingestion supports schema drift without manual mapping."

If all three gates pass, the AE sends a One-Page Pre-Brief (template below) at least 24 hours before the meeting. The SE confirms within 4 business hours. If the SE has a clarifying question and the AE cannot answer it, that is a signal Gate 1 or 2 is weak — push the meeting.

The Pre-Brief contains exactly seven fields: Company + ARR band, Confirmed pain (one sentence with dollar number), Decision committee (named humans + roles), Current stack (named tools), Specific technical question, Competitor in flight (named), Desired outcome from this meeting (one sentence).

The 2027 wrinkle: When Gate 3 fails — meaning the buyer wants to "see the product" but has no specific technical question — the AE should send an async interactive demo (Consensus, Navattic, Reprise, Demostack) instead of pulling the SE. Track who watches what for how long. That data earns the SE meeting later.

3. Verbatim Scripts (15 min)

Hand these out printed. Reps highlight, mark up, and read aloud in pairs.

Script A — AE explaining the three-gate rule to a buyer who asked for a technical demo on call one.

AE: "I want to make sure the next meeting is worth your time and ours. Right now I have a strong sense of where you are headed, but before I bring our principal sales engineer in, I want to confirm three things — that is a 60-minute session with him and I do not want to waste your team's time on a generic overview when he could be answering the specific question that closes this for you.

Can I ask three quick questions before we put time on the calendar?"

Buyer: "Sure."

AE: "First, when you imagine making this decision, what is the dollar number or the metric your CFO is going to ask you about 90 days after we go live?"

Buyer: "We are missing $4M a quarter on forecast accuracy."

AE: "Got it — that becomes the headline of the next session. Second, beyond you and me, who else will be in the room when the buy decision actually happens?"

Buyer: "Me, our CFO, and our head of RevOps. Procurement runs the paper."

AE: "Perfect. Last one — what is the single technical question that, if our SE answers it well next week, would move you from 'evaluating' to 'champions us internally'?"

Buyer: "Whether you can ingest our event stream from Snowflake without us rewriting our dbt models."

AE: "Done. I will send a written brief by EOD tomorrow so you can review what we will cover. If anything is off, you tell me and we fix it before the meeting."

Script B — AE handing off to the SE at the start of the joint call.

AE: "Sarah, thanks for the time. Before I turn it to Marcus, our principal sales engineer, let me reset the room. You shared three things with me last Tuesday: your forecast is off by 22%, which is costing you $4M per quarter; your CFO Linda and your head of RevOps Tom are in the buy decision; and the specific technical question on the table is whether we ingest Snowflake event streams without breaking your dbt models.

Marcus has spent the last two days inside our integration docs with that exact question in mind. Marcus, over to you."

Marcus (SE): "Thanks, Jake. I am going to spend the first ten minutes answering Sarah's question directly with three architecture diagrams, not a product tour. If at any point I am too deep in the weeds or not deep enough, interrupt me — we have 45 minutes and the goal is to leave with you knowing the answer, not with a list of features."

Script C — SE scoping a POC at the end of the technical deep dive.

SE: "Sarah, you have asked twice about how this would behave on your production data. That tells me a POC is the right next step. Before we put one together, I want to write down exactly what 'success' looks like, because I have seen too many POCs run 90 days with no decision. Can we agree on five things right now?"

SE: "One — duration. Fourteen days, kickoff to readout. Not 30, not 60. Fourteen."

SE: "Two — success criteria. One business metric, one technical metric. The business metric is forecast accuracy improvement of at least 8 points on a held-out dataset. The technical metric is ingestion latency under 90 seconds at your peak event volume. If we hit both, we have a deal. If we miss either, you have a clean reason to pass."

SE: "Three — scope. Three use cases. Forecast roll-up, pipeline hygiene, and one custom report. Anything else is out of scope and gets parked."

SE: "Four — your team. I need named owners on your side: one data engineer for the ingestion piece and one RevOps analyst for the metric validation. Without those two people I cannot guarantee a 14-day timeline."

SE: "Five — the readout. Day 14, 60 minutes, with Linda your CFO in the room. We present the numbers, you make a decision in the meeting or within five business days."

SE: "Can we sign that as a one-page document this week before we kick off?"

4. Role-Plays (15 min)

Three role-plays. Pair reps. Rotate every 5 minutes. Observer uses the rubric below.

Role-Play 1 (5 min) — The Premature SE Ask.

Setup: AE is on a first discovery call. Buyer says at minute 12, "Can you bring your engineer to the next call to show us the product?" AE has not confirmed pain, authority, or a specific technical question. The AE's job: do not say yes. Reschedule to get the three gates instead, without losing the deal.

Coach the AE to use Script A verbatim. Observer scores: did the AE resist the premature demo? Did they extract a dollar number? Did they name the decision committee?

Role-Play 2 (5 min) — The Handoff Reset.

Setup: AE and SE are walking into a technical deep dive. The buyer is the head of data engineering. The AE opens. SE takes over. Buyer's first question is hostile: "Last vendor we evaluated promised us schema drift handling and it broke in production. Why should we trust you?"

Coach: the AE does not jump in to defend. The SE answers the question with a specific architectural detail, not marketing language. Observer scores: did the AE stay quiet? Did the SE answer technically and credibly? Did either of them say the word "robust"?

Role-Play 3 (5 min) — The POC Scope Contract.

Setup: SE has just wrapped a 45-minute deep dive. Buyer says, "We are interested. Can we run a 30-day POC?" SE's job: negotiate down to 14 days, lock in two success metrics, and get named owners on the buyer's team.

Coach the SE to use Script C verbatim. Observer scores: did the SE shrink the timeline? Did they get a business metric AND a technical metric? Did they name humans on the buyer's side?

Observer rubric (one page, 5 checkboxes per role-play):

• Did the AE/SE follow the script structure?
• Did they extract specific numbers, not vague answers?
• Did they name humans, not roles?
• Did they avoid the banned phrases ("robust," "best-of-breed," "industry-leading," "synergies")?
• Did they end with a clear next step on the calendar?

5. Common Pitfalls (5 min)

Five failure modes, named. If you hear yourself doing any of these on Monday afternoon, stop.

Pitfall 1 — "Just bring the SE to be safe." This is the single most expensive habit on the team. It burns SE hours, signals to the buyer that the AE is not technical enough to own the deal, and trains the SE to think every meeting is junk. **Recovery: cancel the meeting.

Run a 30-min discovery yourself first. Pre-brief the SE only when Gate 3 passes.**

Pitfall 2 — The AE talks over the SE in the technical deep dive. The buyer asked the SE a question. The SE starts to answer. The AE jumps in because the silence is uncomfortable. The buyer now distrusts both of you. Recovery: AE writes "I will not speak during minutes 5-45" on a sticky note. Put it on the laptop bezel.

Pitfall 3 — POC scope creep. Buyer adds use case four, five, six. Your SE says yes because they want to be helpful. Day 45 arrives, the POC is still running, the deal is dying.

Recovery: every new request goes into a "post-purchase roadmap" doc. The SE says, "Yes, that is in scope for after we sign — not for the POC. The POC stays at three use cases."

Pitfall 4 — No business sponsor at the POC readout. Your champion runs the POC. The CFO never shows up. Day 14 readout happens, your champion takes the results to the CFO, gets a "we need more time" reply, and the deal stalls.

Recovery: CFO attendance at the readout is a precondition for starting the POC. Put it in the scope contract. No exceptions.

Pitfall 5 — SE attach rate north of 70%. If your SEs are on more than 60-70% of opportunities, you are using them as a discovery crutch. Forecast it: in 90 days, an SE will quit and you will not be able to backfill. **Recovery: track SE-attached opp win rate vs unattached.

If SE-attached opps do not win 15+ points higher, the attachment threshold is too loose.**

6. Action Items + Drill (5 min)

Send reps out with three things this week.

This week, every rep does this:

1. Monday: write the 7-field Pre-Brief for the next SE-attached meeting on your calendar. Send it to the SE by EOD Monday. If the SE has a clarifying question you cannot answer, the meeting moves.

1. Wednesday: pull every opp in your pipeline that has had an SE attached for more than 30 days with no movement. Send the SE a one-line note: "Should we de-attach this and re-engage later?" Free up SE hours.

1. Friday: send the POC Scoping Contract template (Section 3, Script C) to one buyer where a POC has been discussed but not scoped. Get it signed before you kick off.

Accountability metric for the next 30 days, tracked weekly in pipeline review:

• SE attach rate — target 40-50% of qualified opps (down from typical 70-85%).
• SE-attached opp win rate — target +15 percentage points vs unattached.
• POC duration — target median 14 days, max 21.
• POC-to-close conversion — target 65%+ (industry median is ~50% per Bridge Group 2027 SaaS Sales Benchmark).

Drill exercise — Tuesday 4 PM standup, 15 minutes:

Each rep brings the Pre-Brief they wrote Monday. The team reads them out loud. SE manager scores each one on the 7 fields. Any brief that scores below 6/7 gets rewritten on the spot. By week three, every brief should pass on the first read.

FAQ

Q: My team only has one SE for eight AEs. How does this work with that ratio?

This training works better with a tight ratio because it forces discipline. With 1:8 you cannot afford a 70% attach rate — the math does not work. The three-gate rule mathematically gets you to 40-45% attach, which puts your single SE on the right 16-20 meetings per month instead of 30+ junk meetings.

Track it: in week one, count how many SE meetings your team requested vs how many actually had a Gate 3 pass.

Q: What if the buyer insists on having the SE on the first call?

Two options. First, send an async interactive demo (Navattic, Consensus, Reprise) with a personalized intro from the AE — most buyers will accept this once they see it is tailored. Second, if the buyer absolutely insists and the deal is large enough, run the SE meeting but use the first ten minutes as discovery — the SE asks the Gate 1, 2, and 3 questions on the live call.

If the gates do not pass in those ten minutes, the SE excuses themselves and the AE continues solo.

Q: How do I get my SEs to buy into the Pre-Brief?

Show them the math. Most SEs are doing 25-35 meetings per week, 60% of which they consider junk. The Pre-Brief cuts that to 15-20 high-quality meetings.

They get hours of their life back. Have the SE manager (not the sales manager) introduce the Pre-Brief in the next presales team meeting and frame it as "AEs are no longer allowed to book you without this."

Q: We use AI demo tools — Consensus, Demostack, Saleo. Does this training still apply?

Yes, and the training tightens with AI in the mix. AI demos are perfect for the "Gate 3 fails — buyer just wants a product tour" case. Use them aggressively for tire-kicker meetings.

The 1:1 SE time stays reserved for confirmed-Gate-3 meetings. Pavilion's 2027 GTM Benchmark shows orgs using AI demo tools alongside human SEs have 23% higher SE retention and 18% higher SE-attached win rates because the SE only walks into qualified rooms.

Q: What is the ROI of running this training every Monday for four weeks?

Based on Bridge Group's 2027 sales benchmark and Pavilion's presales-leader cohort data, teams that adopt the three-gate model see: SE attach rate drops from ~75% to ~45% within 8 weeks; SE-attached win rate climbs 12-20 points; POC median duration drops from 32 days to 16 days; POC-to-close conversion climbs from ~50% to ~65%.

On a team running $20M ARR at 25% win rate, the lift is ~$3-4M in incremental ARR per year without adding headcount.

Sources

• Pavilion (joinpavilion.com) — 2027 GTM Benchmark Report, presales-leader cohort data
• Bridge Group — 2027 SaaS Sales Benchmark Report (annual, AE/SE ratios and POC duration data)
• Presales Collective (presalescollective.com) — "Up-level Your Sales with Better SE/AE Relationships"
• Demostack — "Building the SE/AE partnership," 2027 Presales Summit recap
• Force Management — "Improve Technical Sales Execution: Playbook for B2B Leaders," named the Value Framework methodology
• Paolo Tagliaferri — "Sales Engineer Best Practices to Lead Proof of Concept"
• Gartner — "4 Best Practices for Sales Demonstration Success" and Q1 2027 SaaS Spend Review
• Consensus (goconsensus.com) — "Technical Product Demo: The Most Important Demo"
• We The Sales Engineers podcast (Ramzi Marjaba) — qualification and SE engagement episodes
• "Mastering Technical Sales" by John Care and Aron Bohlig (2026 4th edition, foundational SE playbook still cited in Pavilion curriculum)