Who these recommendations are for
The recommendations are addressed to the person running the demo: a vendor representative, but also an internal implementation coordinator on the plant side. The audience is board members and the plant director, people who decide on direction, not on configuration details.
The common thread of all points: the demo should answer the board's question of what will change in safety and work organization on its site. The functions are only a means.
Recommendations 1-4: data, order and narrative
The first four recommendations concern preparation and the start of the demo.
1. Show the plant's own data
An isometric map with the building shapes and locations of this plant builds trust that no mock-up can match. The data is the georeferencing of the hall, the building shapes and locations with transmitter numbers.
2. Start with the map, not the slides
The isometric 2.5D map in the browser shows buildings, vehicles, employees and work locations. Two minutes of orientation are enough for the board to recognize its own hall.
3. Use a separate demonstration instance
A demonstration instance with separated data removes security objections. State it in the first words, before a question is asked.
4. Connect the permit with the risks of the location
Risks and protective measures are assigned to locations, so a permit in a given hall immediately shows the risks of that place. This is a good scene for the plant director, because it shortens issuing a permit.
Sample split of a 30-minute demo
Recommendations 5-7: alarm, framing and closing
The next three recommendations concern the climax and the finish.
5. Keep the alarm for the middle of the demo
The siren and the marker on the map appear within seconds of creating the event, because the work feed is polled every 3 s. This is the strongest scene, so it is worth neither starting with it nor saving it for the end.
6. Say what InnerWeb is not
InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and resource planning. Localization works without GPS. This message removes the fear that the demo is an introduction to replacing systems.
7. Close with a question about the pilot
Spend the last six minutes on the pilot scope: hall, roles, integrations, date. The presenter may mention company indicators: 20 implementations and pilots and a 100% conversion rate from pilot to implementation.
How to tell that the demo worked
A good demo changes the type of questions. The board stops asking whether the system works and starts asking when and in what scope it can be launched. A second signal is naming a person on the plant side responsible for the pilot.
If after the demo only general remarks follow and nothing concrete about a date, it is worth coming back within a week with a short summary of the scenes and a proposal of two variants of scope.
Video
Frequently asked questions
How long should a demo for the board last?
About 30 minutes. Longer demos shift attention to configuration details, while the board decides on direction.
How many functions should be shown?
A few scenes matched to the roles of the participants: map, permit, alarm, visitor. The full tour of 18 modules is kept for the pilot.
What follows the demo if the board wants to know more?
A workshop on the pilot scope is arranged with participation from safety, IT and security, where halls, roles and integrations are agreed.
Let's prepare a demo for your board
We will plan 30 minutes on your plant's data, ending with an agreed pilot scope.
Let's talk