The Sales Engineer's discovery contribution in UK SaaS in 2026

The Sales Engineer's discovery contribution has changed materially in UK SaaS in 2026. The 2022-vintage SE was a 'demo specialist': they joined the second meeting, demonstrated the product against the buyer's brief, and exited. The 2026 SE owns half of the discovery from the first meeting.

This piece is on what good SE discovery looks like and where most SE programmes under-invest.

Why SE moved upstream

Three structural reasons:

The buyer's first call is increasingly technical. UK SaaS buyers in 2026 routinely have technical leads in the first meeting (data engineers, security, IT architecture). An AE running discovery alone in front of a technical audience produces a less useful conversation than an AE-SE pair where the SE handles the technical thread in real time.

Demos are decreasingly product walkthroughs. Strong SE work in 2026 is bespoke demo construction against the buyer's actual data context. Bespoke demo construction requires understanding the buyer's situation specifically, which is impossible without first-meeting discovery presence.

Information security is a discovery topic, not a procurement topic. UK enterprise buyers routinely surface security questions in the first conversation. The SE is the right person to answer them; deferring to a 'security review later' communicates the vendor isn't ready for enterprise.

What good SE discovery looks like

The SE discovery contribution sits across three threads:

Thread 1: technical context. What's the buyer's existing stack? What's the data architecture? Where does the team sit in the broader engineering organisation? The SE asks these questions in parallel with the AE's commercial discovery, surfacing constraints and opportunities the AE wouldn't surface alone.

Thread 2: demo design. As the conversation progresses, the SE forms a hypothesis about what to demo and why. Not 'show the product'; 'show the part of the product that maps to the buyer's actual data and problem'. The hypothesis is shared with the buyer in the call: 'based on what you've described, the most useful demo would be X scenario - does that match what you'd want to see?'

Thread 3: technical viability. The SE forms a view on whether the buyer's situation can actually be solved by the product. Some can't be; flagging that early is more honest than running a 6-week sales motion towards a technically-unsuitable deal.

The handoff problem

The traditional SE handoff (AE runs first meeting alone, SE joins second meeting) breaks the discovery model. By the time the SE joins, the AE has formed a positioning hypothesis and the SE inherits that hypothesis. The SE's technical perspective comes too late to shape the conversation.

Strong UK SaaS SE programmes in 2026 have moved to AE-SE pair from first meeting on any deal above a defined size threshold. The threshold varies by team; 30k pounds ARR is a common pattern.

Where SE programmes under-invest

Three habits hold SE programmes back:

SE time is rationed too tightly. A 1:6 or 1:8 SE-to-AE ratio means the SE can join only highest-priority calls; most discovery happens without them. The fix is structural: hire more SEs (and pair them with smaller AE sub-teams) rather than trying to scale a thin SE layer.

SEs don't have discovery training. Most SEs were hired for technical depth; few were trained in SPIN, MEDDPICC, or DPM. The SE who can run technical discovery but not commercial-relevant discovery brings less value than they could. Cross-training between SE and AE on discovery frameworks is the cheapest investment most teams haven't made.

SE post-call coaching is minimal. AEs get manager call-review time. SEs less so. The SE skill ceiling is reached more slowly without structured feedback.

What to operationalise

Three changes:

1. AE-SE pair from first meeting on deals above the threshold.
2. SEs trained on commercial discovery frameworks alongside technical depth.
3. SE call review weekly, same cadence as AE review.

Teams that make these three changes consistently report higher win rates on technical deals and lower no-decision losses on enterprise.