Demo Factory
A proof-of-concept tool helping Strategy's sales engineers craft compelling demo narratives. Not the demo itself: the story scaffold around it. A live experiment in how generative tools can shape sales conversations earlier and faster, with a planned v2 to widen the use case.
Sales engineering at Strategy was bottlenecked on demo prep, but not in the way people usually mean. The actual product demo was fine. What was hard was the narrative: framing the product around a specific prospect’s industry, pain points, and language, in time for the call.
Demo Factory is a proof of concept for solving that.
What it is, and what it isn’t
Demo Factory is not a tool that generates the product demo. It’s a tool that helps sales engineers write the story they tell around the demo.
A sales engineer picks a use case, customises industry context and emphasis, and the tool produces a self-contained narrative scaffold: framing, talking points, suggested order, and a deployed reference page on GitHub Pages they can share with the prospect alongside the live demo.
The point is to compress the time between “we have a meeting on Thursday” and “I have a sharp story to tell.” Currently, what used to take a day of prep takes about 15 minutes.
Why it’s a PoC
This is v1 deliberately. I built it as a working experiment to validate the underlying pattern: that the bottleneck in technical sales is narrative shaping, not artefact production, and that generative tools can compress that loop dramatically. The prototype is in active use by a small group of sales engineers, and what I’ve learned from it is feeding into a planned v2 that widens the scope to include more of the demo creation flow itself.
Decisions worth flagging
I built it as a vanilla JS Vite app rather than reaching for a framework. The surface was small enough that React would have been more weight than help. The screenshot display, custom use case flow, and GitHub Pages auto-deploy took three iterations to stabilise but now run unattended.
The pattern of “build the generator, not the artefact” is something I’ve reused since.