$10M in Pre-Orders

The setup.

Industry events are one of the highest-leverage moments in a product's go-to-market timeline. The right conference puts you in the same room as your ideal buyers, your competitors, and the people who shape opinion in your market — all at once. Missing that window doesn't just cost you visibility. It hands the stage to someone else.

But showing up with an incomplete product is a risk most teams aren't willing to take. The instinct is to wait until everything is ready. The problem is that 'ready' is a moving target, and the market doesn't pause while you polish. Companies that figure out how to demonstrate value before the full product exists — through a focused, well-designed demo that speaks directly to what buyers care about — consistently outmaneuver competitors who are still waiting for launch day.

What had to be true.

This was a B2B2B engagement, and a textbook example of the end-user / buyer split. Universarium's client was RUSATOMSERVICE. RUSATOMSERVICE's clients were nuclear power plant operators and their parent organizations. The people who would pay for the LMS and the people who would use it were two completely separate groups, with different concerns, different success criteria, and no shared seat at the table when the contract was signed.

That structure created a specific problem: RUSATOMSERVICE was buying an LMS on behalf of buyers who hadn't been consulted yet. The commercial decision was made at one level of the chain. The acceptance decision would happen at another.

RUSATOMSERVICE, a division of Rosatom, was Universarium's largest client. The engagement: build an LMS that would replace live on-site trainers in the training of nuclear power plant operators. When a buyer purchased a nuclear power unit, they also purchased operator training. The LMS was designed to become that training, digitally, at scale, without a human trainer in the room.

The LMS was mid-development in June 2016 when we learned that ATOMEXPO, Russia's largest nuclear industry forum, was taking place in 16 days. The event would bring together the exact people whose acceptance of the LMS would determine whether the product succeeded: nuclear power plant operators and their managers, the future end users of what we were building.

The core concern, shared by RUSATOMSERVICE and their buyers alike, was whether operators would actually absorb technical information from a screen. The live trainer model had been standard for decades. The assumption was that digital training meant lower retention, less engagement, and operators who would click through without learning anything. Nobody had tested that assumption yet against real users.

There was a real risk in going. If the audience at ATOMEXPO rejected the LMS concept, it would put the entire RUSATOMSERVICE contract in question, a client whose 2016 revenue was $12.91B by IFRS. That conversation with our CEO was direct: we were mid-contract, with time remaining to course-correct if the feedback was negative. The risk of showing an unfinished product was lower than the risk of delivering a finished one that users had never validated. We decided to build a demo and go.

How it moved.

What I actually did.

In a B2B2B structure, the demo had two audiences at once: RUSATOMSERVICE, who needed to believe the product would satisfy their buyers, and the operators themselves, who needed to experience it directly. The demo had to work for both: commercial confidence for one, felt learning for the other.

The first decision was scope, and I made a specific call: design the demo around the one objection we knew the audience would bring. The fear, from both RUSATOMSERVICE and their buyers, was that operators wouldn't absorb information from a screen. They would zone out, click through, retain nothing. The demo had to answer that directly, and it had to do it in under 10 minutes on a noisy conference floor.

The structure I chose: entrance test, then lecture, then final test. Four questions before the lecture, the same four questions after. The delta between the two scores was the proof: not a promise about what the platform could do, but a demonstration of what it just did. That learning delta was the centrepiece of every conversation at the conference.

The lecture itself was built to keep attention in a chaotic environment. Segments of 2-3 minutes. Random-interval knowledge checks inside the video. And a feature that stood out even by today's standards: the ability to leave comments tied to specific timecodes, so a question about something at 10:01 stayed anchored to 10:01, not buried in a general thread. This was 2016. It worked on the conference floor because it turned passive watching into active engagement.

Final test results were emailed automatically to the participant. That detail closed the loop for managers standing nearby: they could see that their operators would receive a documented record of what they had learned.

A team was assembled: a programmer, a designer, a front-end developer, and a QA tester. Sprint planning was done with risk awareness built in from the start. Every task was sequenced around the demo narrative, so the build always served the story we needed to tell on the conference floor.

The demo delivered. Conversations moved quickly from product questions to commercial ones. The pre-order volume reflected both the quality of the demo and the strength of the underlying market demand.

Measurable outcomes.

• Secured $10M in pre-orders at ATOMEXPO 2016: conversations moved from product questions to commercial ones on the conference floor
• Demo built and delivered in 16 days with a team of 4: programmer, designer, front-end developer, QA tester
• Core user objection (retention without a live trainer) addressed directly in the demo structure and resolved in real time
• Product entered market with live user validation before full delivery: feedback confirmed the build direction

The stack behind it.