ExplainedSaaS/ 20 June 2026/ 3 min read
60-80 percent of SE time goes to demo prep rather than discovery or POC scoping. A demo library has three layers (scenarios, pre-built environments, assets), three build patterns, and pays back 0.4-0.8 of an FTE per SE seat in recovered capacity.
A reusable demo library is a structured set of demo scenarios, recordings, scripts, and pre-built demonstration environments that an SE team can deploy on short notice rather than building from scratch every cycle.
Most UK SaaS SE teams in 2026 don't have one. The demo for tomorrow's meeting was built between 11pm last night and 9am this morning, by an SE who'd built five similar demos in the last three months and built each one from scratch. The cost is invisible until you compute it: SE time is the bottleneck on most growth-stage UK SaaS deal volume, and 60-80 percent of SE time goes to demo prep rather than discovery or POC scoping.
This piece is on building the library.
A demo library has three layers:
Layer 1: scenarios. Documented use cases the product can demonstrate. For each: the buyer profile (sector, size, role), the problem framing, the demo flow, and the expected reaction. The strongest libraries have 8-15 scenarios covering 80 percent of the team's deals.
Layer 2: pre-built environments. Demonstration tenants of the product loaded with realistic-looking data, configured for each scenario. Pre-built environments save the 4-6 hours per demo that goes into 'spin up a fresh tenant and create the demo data'.
Layer 3: assets. Recordings (Loom or Vidyard) of the demo being run by a strong SE for each scenario. Scripts. Talk-tracks. Common-objection responses. Buyer questions to anticipate.
Three patterns work:
Pattern 1: dedicated SE library week. Once or twice a year, the SE team takes a full week off prospect calls to build and refresh library assets. Strongest pattern at established SE teams; hardest to schedule at growth-stage teams that can't afford the AE-pair time loss.
Pattern 2: post-deal contribution. Every closed-won deal produces a contribution to the library. The SE who ran the demo records a 15-minute walkthrough with annotations. Compounds slowly but consistently; the library grows in proportion to deal volume.
Pattern 3: dedicated SE. A senior SE is full-time on library curation, supporting field SEs as needed but not carrying their own deal load. Works at scale; expensive at growth-stage.
Most strong UK SaaS SE programmes in 2026 use a mix.
A library cuts demo prep time from 4-8 hours per demo to 30-60 minutes. At a 1:6 SE-to-AE ratio with 5 demos per week per SE, the saving is 15-30 SE hours per week. That's the equivalent of 0.4-0.8 of an FTE per SE seat in recovered capacity.
The recovered capacity goes one of three places: more demo coverage (the SE can support more deals), better discovery (the SE has time to run pre-meeting research), or POC scoping (the SE can take a deeper post-demo motion).
The library degrades. Product changes; scenarios go stale; recordings reference deprecated UI. A library that isn't refreshed quarterly becomes worse than no library because SEs trust it and discover the staleness mid-call.
The library is too generic. A 'standard demo' that's used for every deal regardless of context degrades into the canned product walkthrough. Bespoke is the strength of strong SE work; generic library content erodes that.
The library isn't trusted. Senior SEs prefer to build from scratch because they don't trust the library quality. Library quality has to be high enough that the senior SEs adopt it; otherwise the library is junior-SE only and the senior SEs continue burning prep time.
Three habits:
The best UK SaaS SE programmes in 2026 are the ones that have made the library a first-class artefact rather than a side-project.
Snapshot
UK B2B outbound channel mix has shifted materially from 2022 to 2026: LinkedIn first, phone returning, cold email lower-volume but more personalised, direct mail seeing a small revival in enterprise. The relative effectiveness ranks have inverted from the 2022 hierarchy.
Explained
Account-based sales (ABS) was promoted heavily across UK SaaS through 2018-2023 as a structural answer to broad-volume outbound. By 2026 the picture is more nuanced: ABS works at specific deal sizes and team scales, fails predictably outside those, and many UK mid-market teams adopted it for the wrong reasons. A practitioner walkthrough.
Explained
UK enterprise buyers in 2026 increasingly run ESG due diligence on vendors as part of procurement: documented sustainability commitments, modern-slavery statement, supply-chain transparency, and (depending on the buyer) climate-disclosure alignment. The UK Sustainability Disclosure Standards regime has tightened the buyer-side disclosure obligations, which cascades down to vendor expectations.