InnerWeb
Skip to main content

Demo instead of a pilot: where purchasing saves time and budget

A demo on plant data does not replace a pilot, but it can narrow it: the fewer functions to test in the field, the shorter and cheaper the pilot. For the purchasing department the order of decisions matters. First a cheap verification of fit, then a paid pilot of narrower scope. Below is a sample calculation with explicit assumptions and a list of risks the demo does not remove.

-2 wk
shorter pilot in the sample calculation
Source: sample calculation
5 days
effort to prepare the demo
Source: sample calculation

Why the order matters for purchasing

A paid pilot assumes it is known what works. When the board has not seen the system on its own data, the pilot scope tends to swell: all modules, all halls, all users. The demo changes the order. The board sees the hall map, permits from templates, SOS, no-movement and the visitor path, and then indicates what interests it.

The demo is a rollout scenario on a demo instance with plant data, not a production deployment. Therefore it does not replace evidence from real movement, but it filters out functions that clearly do not fit the plant before a pilot invoice arrives.

The second argument is transparency for the board. A decision taken after a demo rests on what the board saw on its own data, not on sales materials. Such a decision is less likely to be reopened after the pilot starts.

What the demo filters out and what it does not

The demo filters functional fit well: whether permit templates match plant procedures, whether risks assigned to locations make sense, whether the visitor path fits reception, whether the alarm is readable for the dispatcher. The board also sees where data touches the existing access control, time and attendance, HR and ERP systems.

The demo filters technical field risks poorly: transmitter range, watch behaviour at workstations, signal quality in difficult parts of the hall. This is the pilot's task. InnerWeb is an independent system complementing the client's existing systems, and location works without GPS using signals from several transmitters averaged on the map, so the pilot checks precisely the placement of transmitters in a specific hall.

  • filtered by the demo: template compliance, map readability, visitor scenario, dispatcher alarm
  • left for the pilot: coverage in difficult places, watch operation, transmitter placement
  • left for deployment: full integrations with access control, time and attendance, HR and ERP

Pilot duration without and after the demo

Pilot duration without and after the demoBefore and after chart: pilot without demo 8 weeks, after demo 6 weeks.02468weeksWithout demo: 8 weeks8 weeksWithout demoAfter demo: 6 weeks6 weeksAfter demo
Source: Sample calculation based on the assumptions in the Calculation section

Sample calculation: a narrower pilot

This calculation shows the mechanism, not the result for your plant. We assume a pilot that without a demo covers five functions and lasts eight weeks, and after the demo the board drops two functions and the time falls to six weeks. Preparing the demo takes five workdays.

The result depends on assumptions that each purchasing department can replace with its own. The point is that five days of demo are compared with two weeks of pilot that do not have to be run.

The purchasing department can extend the calculation with the time cost of its own people: the head of health and safety, an IT person and a dispatcher, who in a pilot spend a few hours a week on assessment. Two weeks of a shorter pilot also mean two weeks less load on these people. This component depends on the plant, so we do not give it in the calculation.

Risks and conditions for the saving to be real

The saving is real only if after the demo someone records the conclusions. Without this the board drifts back to a broad scope. That is why after the demo the instance shutdown, marker cleanup and conclusions are written down, so the pilot decision has a basis. The second rule: the demo must run on plant data, because a demo on generic data filters nothing out.

The third risk is confusing the demo with a deployment. The demo uses demo accounts with addresses in a domain reserved for testing. Conclusions about production load must not be drawn from it. The company indicators, 20 deployments and pilots and a 100% conversion from pilot to deployment, relate to other plants and are not a promise of outcome.

Example calculation

Sample calculation: pilot after the demo

Assumptions
ParameterValue
Pilot without demo: number of functions5 functions
Pilot without demo: duration8 weeks
Functions filtered out at the demo2 functions
Pilot after demo: duration6 weeks
Demo preparation5 workdays

Result: Pilot shorter by 2 weeks (from 8 to 6), which at the assumed figures outweighs the 5-day demo effort.

Note: Sample calculation; the numbers of functions and weeks are illustrative assumptions, not data from a deployment. Individual pricing.

Video

Frequently asked questions

Can a demo fully replace the pilot?

No. The demo verifies functional fit on plant data, while the pilot checks system behaviour in a real hall. The demo can narrow it.

Which company indicators may be cited to the board?

20 deployments and pilots and a 100% conversion from pilot to deployment. These are company indicators, not a promise of outcome at a given plant.

Who should attend the demo from purchasing?

The person who will define the pilot scope, together with the head of health and safety and an IT representative. This way the conclusions go straight into the scope.

Does the demo require a contract?

Terms are agreed individually. The demo runs on a separate demo instance and does not touch the plant's production systems.

Narrow the pilot with a demo

Let's discuss which functions to test in the demo and which to leave for the pilot. Individual pricing.

Let's talk