Starting point: machine plant, 10 users, no time limit
Imagine a plant manufacturing agricultural machinery, owned by a global group. The plant director has been tasked by headquarters with checking whether the system protecting lone workers and tracking location in the building works on the shop floor before the group approves the budget for a wider rollout. Ten people are assigned to the evaluation: the OHS manager, two shift managers, the dispatcher, the IT department and several team leaders.
The director has two questions. First: does he need a separate PoC, or a pilot straight away? Second: how long will it take and what will it cost, given that headquarters does not want to impose a deadline? The offer behind this scenario does not limit the pilot's duration, so the evaluation is not driven by the vendor's calendar.
PoC and pilot: two different promises
A PoC (proof of concept) is a short test of one technical claim on a bench or on a fragment of the shop floor: whether the transmitter is visible to a phone, whether the app shows the position, whether the alert gets through. Nobody works with it day to day, there are no real procedures, and the result is either yes or no.
A pilot is production work on a limited scope: real users, a real site, real procedures. The InnerWeb pilot offer covers 50 transmitters and 10 licenses. The system runs permanently rather than for show, so after a month it is clear who opens it, who stops, and where the signal is weak.
When a PoC is enough
A PoC is enough when the only doubt is the technology, for example coverage in a hall with a steel structure. If the system has already been seen in operation and the team trusts the location method itself, a PoC only adds another stage without new knowledge.
When a pilot is needed
A pilot is needed when the doubts concern people and processes: whether a team leader wears the watch, whether the dispatcher responds to an inactivity alarm, whether the phone cascade is up to date. No bench test can check that.
Total pilot cost by duration
The decision in the scenario: straight to a pilot with 10 licenses
The director in our scenario already has evidence at the technology level: the location method based on signals from several transmitters works without GPS, and the transmitters have been verified in other deployments. What he lacks is organizational evidence, so he orders a pilot, not a PoC. Changing the scope midway is cheap, because the offer does not limit time and does not force a decision on a fixed day.
It is worth writing success criteria into the order before the start. Example criteria: at least 7 of 10 users log in every day, every inactivity alarm gets a dispatcher response, and the transmitter map covers all team leaders' routes. Without criteria, a pilot dissolves into opinions.
Pilot cost: what fits in PLN 9,400 and PLN 1,350
The one-off pilot deployment of lone worker protection costs PLN 9,400 net, including the installation of 50 transmitters at PLN 2,400 and plant mapping at PLN 1,500. The pilot subscription for inactivity detection is PLN 1,350 net per month: server with 10 licenses PLN 800, maintenance of 50 transmitters PLN 350 and rental of 2 watches PLN 200. These are indicative ranges from 2025-2026 deployments; individual pricing applies.
Because the pilot has no set end date, the cost depends on the number of months the director decides he needs. The example calculation below assumes the deployment is paid once and the subscription stays the same each month.
- 3 months: PLN 9,400 plus 3 x PLN 1,350, total PLN 13,450 net
- 6 months: PLN 9,400 plus 6 x PLN 1,350, total PLN 17,500 net
- 12 months: PLN 9,400 plus 12 x PLN 1,350, total PLN 25,600 net
After the pilot: next steps for the director
After the pilot the director has three possible paths. First: stop, if the criteria were not met. Second: move to deployment at the same plant. Third: extend to other plants in the group. Moving from pilot to deployment has had a 100% success rate in InnerWeb's existing projects, but that is not a reason to order a pilot without criteria.
Deployment is settled by an order based on the offer, independently of the maintenance agreement, so an additional site does not require an amendment to the service contract. For the director of a group of plants this matters: the first pilot does not close the path or burden the framework agreement.
Conclusions for the plant director
Order a PoC when the technology is in question. Order a pilot when people and processes are in question. Write down success criteria, the number of users and review dates, but do not impose a fixed end date if the offer does not require one. With 10 users and 50 transmitters the pilot is small enough to fit one plant budget, and large enough to show how the system really behaves.
Video
Frequently asked questions
Is a PoC required before a pilot?
No. If the team does not question the location technology, a pilot can be ordered straight away. A PoC makes sense only when the technical assessment of coverage is a real unknown.
Does the pilot have a fixed duration?
In the offer behind this scenario the pilot duration is not limited. The purchaser sets the review dates and the completion criteria.
Can the pilot be extended to another plant?
Yes. Deployment is settled by an order based on the offer, independently of the maintenance agreement, so an additional site does not require an amendment to the service contract.
Plan a pilot with no time limit
Tell us about your plant and your 10 users, and we will help set success criteria and the pilot scope. We will propose pricing matched to your site.
Let's talk