60-Min Sales Training: Technical Demos + SE Partnership

The two ways teams run this hour — and why one loses

Almost every sales leader who schedules a 60-minute session on technical demos picks one of two designs, and the choice determines whether Monday's behavior actually changes.

Option A — the product-knowledge hour. The Sales Engineer presents. Reps watch a polished walkthrough of the integration layer, the admin console, the security architecture. There are slides. There is a recording. Everyone leaves feeling smarter. The implicit theory is that AEs run bad technical demos because they don't know the product deeply enough, so the fix is more product knowledge. This is the default because it's easy to schedule — you ask an SE to present for an hour and the meeting fills itself.

Option B — the engagement-rules hour. Nobody presents the product. The hour teaches a decision rule about *when* an SE is engaged, a written artifact that travels with that decision, verbatim language for the handoff, and a scoping contract for whatever proof-of-concept follows. Reps spend a third of the hour talking, not listening. The theory is different: AEs don't waste SE hours because they lack product knowledge, they waste them because there is no rule about what qualifies an opportunity for SE time, so "bring the engineer" becomes the default answer to every buyer request.

The evidence for Option B is in the failure pattern itself. When an AE brings an SE into a call that has no confirmed pain, no named decision committee, and no specific technical question, the meeting degrades into a generic product tour — and no amount of product knowledge on the AE's part would have prevented that, because the problem was upstream in qualification. Option A trains reps to give the tour themselves. Option B trains them to notice the tour shouldn't happen.

There's a second reason Option A fails on the calendar math. SE capacity has been under sustained pressure across SaaS go-to-market orgs; many teams that once ran roughly one SE per three AEs now run one per four to six. If you have five AEs sharing one SE and every AE brings that SE to 70-80% of their opportunities, you are asking one person to sit in something like 25-35 meetings a month before any prep, POC support, or post-sale handoff work. Teaching those AEs more product features doesn't create a single additional SE hour. Changing the attach rule does.

The practical answer for most teams is Option B for the 60 minutes, with Option A demoted to an optional async library — recorded architecture walkthroughs the SE makes once, that reps watch on their own time. That split respects the constraint: the scarce resource is SE hours, so the live hour should be spent on the thing only a live room can teach, which is behavior under pressure.

One more contrast worth naming before the hour starts. Option A produces a nice recording and no measurable pipeline change. Option B produces four numbers you can put in a weekly pipeline review — attach rate, attached win rate, POC duration, POC-to-close conversion — which means you'll know within 30-60 days whether the training worked. If you cannot name the metric the hour is supposed to move, you're running Option A regardless of what's on the agenda.

How to decide when the SE actually joins

Teach exactly one framework in the hour. Not two. Reps cannot operationalize two new decision rules in 60 minutes, and the second one always cannibalizes the first. The framework is three gates plus one artifact.

Gate 1 — confirmed pain, owned by the AE. The buyer has stated a business problem in their own words with a number attached. "We're evaluating tools" is not pain. "We're looking at our stack" is not pain. Pain sounds like: "Our forecast accuracy is off by 22% and our CFO is asking why we missed last quarter by several million." If the AE cannot repeat the buyer's pain back as a sentence containing a number, Gate 1 is open and the deal stays in discovery.

Gate 2 — confirmed authority path, owned by the AE. The AE knows three things: the economic buyer's name, the technical evaluator's name, and how procurement runs paper at this company. "We'll loop them in later" fails the gate. Specific humans, specific roles, and a rough sense of the approval sequence pass it. This gate matters because SE time spent in front of someone with no path to a signature is the purest form of waste — the meeting can go perfectly and produce nothing.

Gate 3 — confirmed technical question, pre-qualified by the SE. There is a specific technical concern the AE cannot answer credibly. "Show them the product" fails. A question like "they run Snowflake and dbt with reverse ETL, and want to know whether our event ingestion handles schema drift without manual re-mapping" passes. The distinction is whether an expert is needed to *answer something*, versus needed to *perform something*.

Teach the failure branch as hard as the success branch. When Gates 1 and 2 pass but Gate 3 fails — the buyer wants to see the product but has no specific technical question — the AE does not get an SE. The AE runs the demo solo, or sends an interactive/async demo the buyer can click through on their own time. Async demo platforms (Consensus, Navattic, Reprise, Demostack and similar tools) exist precisely for this case, and the viewing data they return is useful: who watched, which sections, how long. That engagement data is often what *earns* the SE meeting two weeks later, because it surfaces the specific question Gate 3 was missing.

The single artifact is a one-page pre-brief with exactly seven fields, sent at least 24 hours before the joint meeting: company and rough ARR band; confirmed pain in one sentence with a number; the decision committee as named humans with roles; current stack as named tools; the specific technical question; the competitor in flight, named; and the desired outcome of this one meeting in a sentence. The SE confirms within four business hours.

Build one enforcement mechanism into that loop and the whole framework becomes self-policing: if the SE asks a clarifying question and the AE cannot answer it, that is evidence Gate 1 or Gate 2 is weaker than the AE claimed, and the meeting moves. The SE is not being obstructive — they're running a free audit of the AE's discovery. Teams that adopt this find the pre-brief starts catching bad meetings before the SE ever opens a calendar invite, which is where the capacity savings actually come from.

The numbers each option produces

Give reps targets, not vibes. Four measurements make the difference between the two training designs visible inside a quarter, and each one has a defensible range you can hold a team to.

SE attach rate. This is the share of qualified opportunities where an SE participates in at least one customer-facing meeting. Many teams sit at 70-85% without ever having chosen that number — it's simply what happens when there's no gate. The target after this training is 40-50%. That is not a cost-cutting number; it's a focus number. Halving attach on a book of 40 qualified opportunities per quarter returns roughly 12-16 SE meetings, plus the prep time behind each one, which is typically 30-90 minutes depending on how technical the account is.

Win rate on SE-attached opportunities versus unattached. This is the diagnostic that tells you whether the gate is calibrated. If SE-attached deals win at roughly the same rate as unattached deals, the SE is not adding decision-changing value on those calls — the attachment threshold is too loose and the SE is functioning as a demo operator. A well-gated program should show attached deals winning meaningfully higher, on the order of 15-25 percentage points, because the gate is deliberately selecting for deals with confirmed pain, a named committee, and a real technical objection. Track this monthly on a rolling 90-day window; quarter-by-quarter samples are too small to read at most team sizes.

POC duration. Measure kickoff to readout, in calendar days, median rather than mean so one runaway pilot doesn't hide the pattern. Target a median of 14 days with a hard ceiling of 21. The reason to be aggressive here is that POC length is a leading indicator of decision failure, not of technical complexity: a pilot that stretches past 30 days almost always did so because success criteria were never written down, not because the integration was hard. If your median is 30-60 days today, the scoping contract in the next section is the highest-leverage change on this list.

POC-to-close conversion. The share of POCs that reach a signed deal. Set the target above the industry midpoint — most teams should be aiming for something in the 60-70% range, and if you're materially below half, your POCs are being used as a substitute for qualification rather than as a technical validation of a deal that's already qualified.

There's a cost side worth teaching explicitly, because reps rarely see it. Sales engineers are among the more expensive individual contributors in a go-to-market org, and their fully-loaded cost per customer-facing hour — once you include prep, environment setup, POC support, and follow-up — is substantially higher than the hourly cost of an AE. When a rep brings an SE "just to be safe" to a first-call product tour, they're spending a scarce, expensive, hard-to-backfill resource on a meeting an async demo would have handled. The training should say that number out loud in your own org's terms, because "be considerate of the SE's time" is a soft appeal and "that meeting cost us X and returned nothing" changes behavior.

Watch one counter-signal so the program doesn't overcorrect. If attach rate falls below roughly 30-35% and win rate on genuinely technical deals starts sagging, the gate has become a barrier rather than a filter — usually because AEs began avoiding the pre-brief work rather than doing it. The fix is not to loosen the gates, it's to shorten the artifact: a pre-brief that takes 25 minutes to write will be dodged, one that takes eight minutes will get written.

Running the hour: sequencing, scripts and drills

Here is the minute-by-minute build. The design principle throughout: reps should be speaking for at least 20 of the 60 minutes, because a technical demo is a performance and performances are not fixed by listening.

Minutes 0-5 — setup. Agenda on the board before anyone walks in. Six time-boxed blocks. No more than three slides all hour. Open with a line that removes the political charge: the point of the hour is not to debate whether SEs matter, it's to stop spending them on deals that will never close so they can be the technical closer on deals that will. Then a 30-second round-robin: name one deal last quarter where you wish you'd brought the SE in earlier, and one where you wish you'd run the first call yourself. Every rep speaks in the first five minutes, which sets the norm for the rest of the hour.

Materials to have ready: two recorded calls — one strong technical deep dive, one weak — pulled from your conversation-intelligence tool; the current AE-SE handoff document, or a blank page if you don't have one, which is common; a printed POC scoping template; and a whiteboard or shared canvas.

Minutes 5-20 — teach the framework. Draw the three gates and the pre-brief. Spend the most time on Gate 3 and on the failure branch, because "buyer asked to see the product" is the most frequent trigger for a wasted SE hour and reps need a rehearsed alternative to saying yes. Have each rep write the seven pre-brief fields for a live deal on their own calendar while you're still in the room.

Minutes 20-35 — verbatim scripts. Print them. Reps highlight and read aloud in pairs; silent reading does not build language.

*Script A — the premature SE ask.* The buyer asks on call one for the engineer to come show the product. The AE's line: "Before I bring our sales engineer in, I want to confirm three things — that's a 60-minute session with him and I don't want to spend 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?" Then: what's the dollar number or metric your CFO will ask about 90 days after go-live? Beyond you and me, who's in the room when the decision actually happens? And what's the single technical question that, answered well, moves you from evaluating to championing this internally? Close by promising a written brief by end of day tomorrow, offered to the buyer for review — which turns the pre-brief from internal paperwork into a customer-facing commitment.

*Script B — the handoff reset at the top of the joint call.* The AE speaks for 90 seconds and no longer: reset the room by repeating the three gates back as facts the buyer supplied. "You told me your forecast is off by 22%, that your CFO and head of RevOps are in the buy decision, and that the specific question is whether we ingest your event streams without breaking your existing transformation models. Our sales engineer has spent two days inside the integration docs with that exact question in mind." Then the SE opens with a boundary: "I'll spend the first ten minutes answering that question directly with architecture diagrams, not a product tour. If I'm too deep in the weeds or not deep enough, interrupt me."

*Script C — scoping the POC.* Five terms, stated as a list the buyer agrees to in the meeting. Duration: 14 days, kickoff to readout — not 30, not 60. Success criteria: exactly one business metric and one technical metric, both numeric, both agreed before kickoff. Scope: three use cases, named; anything else is parked. Buyer resourcing: named owners on their side, typically one engineer for integration and one analyst for metric validation, because without those two humans the 14-day timeline is fiction. Readout: day 14, 60 minutes, with the economic buyer in the room, decision made in the meeting or within five business days.

Minutes 35-50 — role-plays, three rounds of five minutes, rotating pairs. Round one drills Script A: the buyer asks for the engineer at minute 12 of discovery and the AE has to decline without losing the deal. Round two drills the handoff under pressure — the buyer opens hostile ("the last vendor promised us this and it broke in production"), and the coaching point is that the AE stays silent while the SE answers with a specific architectural detail. Round three drills the POC negotiation: buyer asks for 30 days, SE gets it to 14 with two metrics and named owners.

Use a five-checkbox observer rubric per round: did they follow the script structure; did they extract specific numbers rather than vague answers; did they name humans rather than roles; did they avoid the banned words (robust, best-of-breed, industry-leading, synergies); did they end with a concrete next step on a calendar.

Minutes 50-55 — the five pitfalls, named out loud. Bringing the SE "just to be safe," which burns hours and signals the AE can't own the deal. The AE talking over the SE during the deep dive because silence feels uncomfortable — the fix is literally a sticky note on the laptop bezel reading "I don't speak during minutes 5-45." POC scope creep, where use cases four through six get accepted by a helpful SE and day 45 arrives with no decision; the counter is a standing line: "that's in scope for after we sign, not for the POC." No economic buyer at the readout, which turns your champion into an unpaid internal salesperson; make their attendance a precondition of starting the pilot. And attach rate above 70%, which is the leading indicator that an SE is about to quit and you won't be able to backfill quickly.

Minutes 55-60 — assignments with dates. Monday: write the seven-field pre-brief for the next SE-attached meeting on your calendar and send it by end of day. Wednesday: pull every opportunity with an SE attached for more than 30 days with no movement, and ask the SE whether to de-attach and re-engage later. Friday: send the POC scoping contract to one buyer where a pilot has been discussed but never scoped.

Then run a 15-minute drill at the following Tuesday's standup: every rep reads their pre-brief aloud, the SE manager scores it against the seven fields, and anything below six out of seven gets rewritten on the spot. That drill is what converts the hour into a habit — the training itself is necessary but not sufficient, and teams that skip the follow-up drill see attach rate drift back to baseline within about six weeks.

What the SE owes the AE in return

A gate that only constrains the AE will be resented and quietly abandoned, so teach the reciprocal obligations in the same hour. This is a Partnership with symmetric terms, not a permission system.

The SE confirms or declines a pre-brief within four business hours. A pre-brief that sits unanswered for two days teaches the AE that the process is slower than just booking the meeting, and they'll route around it.

The SE prepares to the specific technical question, not to a generic tour. If the brief says schema drift, the deep dive opens on schema drift within the first three minutes. Reps will do the pre-brief work exactly as long as they see it change what happens in the room.

The SE has standing authority to decline a meeting whose brief fails a gate, and to say so in writing without escalation. Removing that authority is the fastest way to return to 80% attach — an SE who cannot say no has no gate, only paperwork.

The SE owns the async demo library. If the AE's alternative to an SE meeting is "make something yourself," the alternative is theoretical. Recording four or five short architecture walkthroughs — integration model, security posture, data flow, admin experience — gives the AE a real thing to send when Gate 3 fails, and each recording pays back its production time within a handful of uses.

Finally, the SE and the AE co-own the POC outcome. If the pilot runs long, that is not an AE failure or an SE failure in isolation; it is a scoping-contract failure, and both names are on that document. Reviewing overrun POCs jointly rather than assigning blame is what keeps the two roles honest with each other over a full year of Sales cycles.

Adapting the hour to your team's shape

The framework holds, but three variables change the emphasis, and a Training that ignores them will feel generic to half the room.

Deal size and complexity. Below roughly $25-30K annual contract value, most technical questions are answerable by a well-prepared AE with an async demo and a documentation link, and attach rates in the 20-30% range are appropriate. In enterprise motions above six figures, technical validation is genuinely part of the buying process and 55-65% attach can be correct — the gates still apply, but Gate 3 passes far more often because the buyer's evaluation genuinely includes architecture review. Teach the gates as the constant and the resulting attach rate as the variable.

SE-to-AE ratio. At 1:3 you have room for judgment calls. At 1:6 or worse you need the gate enforced mechanically, usually by requiring the pre-brief as a field on the opportunity record before an SE can be added to a calendar invite. Some teams put the seven fields directly into the CRM as required text before an "SE requested" stage change; it's blunt, and it works.

Rep tenure. Reps in their first six months over-request SEs because they're protecting themselves from questions they can't answer, which is rational behavior. Don't punish it — pair each new rep with an SE for a fixed number of shadow meetings, make the pre-brief a coaching artifact reviewed with their manager, and let attach rate normalize over their second and third quarters rather than demanding it on day 30.

One adaptation to avoid: do not create exceptions for named strategic accounts. The moment "this one's important, skip the brief" becomes acceptable, every deal becomes important. If a strategic account genuinely needs more SE time, the honest mechanism is a named allocation — this SE spends 30% of their capacity on these three accounts — not an exemption from the qualification rule.

Related questions

How do we handle a buyer who insists on seeing the product on call one?

Offer an async interactive demo the same day and a live technical session the following week, contingent on a short pre-call to define the specific question. Most buyers accept, because what they actually want is proof you're real, not a 60-minute tour.

Should the SE ever run discovery instead of the AE?

Rarely, and only for deeply technical products where the buyer is an engineering leader. Even then the AE owns Gates 1 and 2. If the SE is routinely doing discovery, you have an AE capability problem the attach rule won't solve.

What if we don't have sales engineers at all?

Run the same hour with the "SE" role played by whoever your scarce technical resource is — a founder, a solutions architect, a support lead. The gates matter more when the resource is one person, not less.

How long before attach rate actually moves?

Expect 30-45 days for attach rate, because it reflects new opportunities entering the pipeline under the new rule. Win rate and POC conversion lag a full sales cycle, typically 60-120 days depending on your average deal length.

Does this training work for renewals and expansion?

Partially. Gates 1 and 2 transfer directly. Gate 3 tends to pass more often on expansion because the technical question is usually concrete — scaling, a new integration, a migration — so expect higher attach on expansion deals and don't treat that as failure.

FAQ

What is the single most expensive habit this training corrects?

Bringing an SE to a call that has no confirmed pain, no named decision committee, and no specific technical question. It burns the scarcest resource in the go-to-market org, signals to the buyer that the AE cannot own the deal technically, and conditions the SE to assume every invitation is low-value — which means they under-prepare for the meetings that actually matter.

How is the pre-brief different from just filling out the CRM?

The pre-brief is written for one specific human who will act on it within four hours, and its fields are chosen for what a technical presenter needs: the exact question, the named stack, the competitor, and the desired outcome of this one meeting. CRM fields are written for reporting. Keep the pre-brief to one page and roughly eight minutes of writing, or reps will skip it.

What if the SE declines the meeting and the deal stalls?

That's the system working. A decline means a gate failed, and a deal that stalls because the AE couldn't produce a dollar number or a named economic buyer was going to stall later at higher cost. Track declined briefs for a quarter — if a meaningful share of declined deals later close, the gates are miscalibrated and you should loosen Gate 3, not overrule the SE case by case.

Why 14 days for a POC instead of 30?

Because pilot length correlates with decision failure more than with technical difficulty. Long pilots almost always trace back to success criteria that were never written down, so the buyer never has a moment where they must say yes or no. Fourteen days forces the criteria conversation up front, and it keeps the champion's internal attention on your evaluation rather than the next priority.

How do we measure whether the hour worked?

Four numbers in weekly pipeline review: SE attach rate on qualified opportunities, win rate on attached versus unattached deals, median POC duration in calendar days, and POC-to-close conversion. Read attach rate on a 30-day window and the other three on a rolling 90-day window, because smaller samples will show noise you'll be tempted to react to.

Can we split this into shorter sessions?

Yes, and for distributed teams it often works better: 20 minutes on the gates and pre-brief, 20 on scripts, 20 on role-plays, run across three consecutive weeks. What you cannot skip is the role-play block. Teams that cut it to save time consistently report that reps can recite the gates and still say yes to a premature SE request on Wednesday.

Sources

• https://www.gartner.com/en/sales — Gartner sales research, including guidance on sales demonstration effectiveness and technical buyer engagement
• https://www.forcemanagement.com/blog — Force Management, B2B sales execution and value-framework methodology content
• https://www.goconsensus.com/blog/ — Consensus, research and writing on interactive/async product demos and demo automation
• https://www.navattic.com/blog — Navattic, interactive demo benchmarks and buyer engagement data
• https://www.hubspot.com/sales — HubSpot Sales Blog, discovery-call qualification and demo practices
• https://www.saleshacker.com/ — Sales Hacker (Pavilion), practitioner content on AE/SE collaboration and POC design
• https://hbr.org/topic/subject/sales — Harvard Business Review sales topic hub, buying-committee and complex-sale research
• https://www.wethesalesengineers.com/ — We The Sales Engineers, podcast and articles on presales qualification and POC ownership
• https://www.gong.io/blog/ — Gong Labs, conversation-analysis research on demo and discovery call behavior
• https://www.wiley.com/en-us/Mastering+Technical+Sales-p-9781630816254 — "Mastering Technical Sales" (Care & Bohlig), foundational presales reference

Related on PULSE

• [How do you run a sales training on selling to technical buyers?](/knowledge/st490)
• [Top 10 Sales Pitch Drill Templates for Product Demos](/knowledge/st0722)
• [60-Min Sales Training: Virtual Demos That Convert](/knowledge/st0453)
• [60-Min Sales Training: Customizing Demos Per Buyer](/knowledge/st0452)
• [Prospecting on LinkedIn: Interactive Template for a 20-Minute Sales Session](/knowledge/st0795)
• [Sales Forecasting Accuracy: Template for a Team Meeting Focused on Data Hygiene](/knowledge/st0796)