Demo Blocks
What's a block
The demo is not one continuous script, but three self-contained blocks — Developer / Team pain, Enterprise pain, Organizational pain. Each stands on its own and can be presented alone. Read together, in order, they tell one escalating story: the same design-layer principle, shown first for one developer, then for every service in the organisation, then for the requirements that feed into all of it.
Decide beforehand which block(s) fit the expected audience — they can be combined, but don't have to be.
The script parts serve as guidelines to make sure key features and messages are covered. You don't need to follow them word for word — make them your own and be personable — but read them beforehand so you're familiar with the main points.
How a demo session is structured
No matter which block is presented, always start with the presenter's introduction to the product and the demo scenario.
| Segment | Time |
|---|---|
| Introduction (presenter, product) | 3 min |
| Developer / Team pain | 15 min |
| Enterprise pain | 10 min |
| Organizational pain | 10 min |
| Wrap-up | 1 min |
| Q&A | flexible |
Before running any block, check Preparation and Clean-up — settings, branches, and clean-up steps differ per block.
The blocks
Developer / Team Pain
A coding assistant follows an architectural decision the developer never saw. PAYMNT service.
Enterprise Pain
Standards defined once by experts, inherited automatically by every new service. GIFTCARD service.
Organizational Pain
Business intent decomposed into implementable units before any code is written. ROBOFLOWAP project.