The 90-day IoT pilot: what makes the difference between a reference case and a shelved project
Most IoT pilots in pharmaceutical and clinical environments do not fail because the technology fails. They fail because the pilot was designed to prove a product, not to build a deployment.
There is a specific moment in every IoT pilot that determines whether it becomes a signed multi-site agreement or a well-documented experiment that no one acts on. That moment is not the technical go-live. It is the design of the pilot itself — before a single sensor ships.
Having managed IoT deployments across pharmaceutical supply chains and clinical environments, the pattern is consistent: pilots that produce commercial outcomes share a structure that pilots which stall do not. The difference is not the technology. It is the intent and preparation behind the 90 days.
What a pilot is actually for
This sounds obvious, but it needs to be stated: a pilot is not a proof of concept. Proof of concept happens in a lab. A pilot is a commercial instrument — it exists to generate the documented outcome that makes the next buyer say yes.
If the pilot does not end with a named reference contact, a quantified outcome, and a clear path to permanent deployment, it has not succeeded. It has consumed budget and produced a report.
The pharmaceutical and medtech procurement cultures that IoT companies are selling into are fundamentally reference-driven. A procurement committee at a Basel CDMO or a Munich hospital will not move on the basis of a vendor's claims. They will move on the basis of what a peer organisation has already done — and whether that peer is willing to have a conversation about it.
Designing a pilot means designing that reference case from day one.
The four elements that determine pilot outcome
A defined success metric that the buyer owns. The most common pilot design mistake is letting the technology vendor define success. Success metrics that matter to procurement committees are not technical — they are operational and financial. Reduction in deviation rate. Reduction in release decision cycle time. Reduction in manual monitoring hours per site. These metrics must be agreed in writing before the pilot starts, and they must be owned by someone inside the buyer's organisation who has a stake in the outcome.
A cross-functional steering group from week one. IoT deployments in regulated environments touch Quality, IT, Operations, and often Finance. A pilot that only engages Operations — the most common failure mode — will stall the moment it needs IT integration approval or QA sign-off on the data architecture. The right stakeholders must be at the table from the first week, not introduced when their sign-off is needed.
A documented GxP compliance position agreed before go-live. In pharmaceutical environments, audit-readiness is not optional. If the data architecture, edge device configuration, and cloud integration have not been reviewed against the site's quality management system before go-live, the pilot will hit a compliance review at the worst possible moment — mid-deployment, when remediation is expensive and visibility is high. Resolving this in advance is not a bureaucratic formality. It is the single most predictable cause of pilot delay in pharma IoT.
A reference case agreement in the commercial terms. Before the pilot contract is signed, it should include — or be accompanied by — a clear agreement that the buyer will serve as a reference site if the defined success metrics are met. Not a guarantee of a case study. Not a marketing commitment. Simply: if the results meet the agreed threshold, the key contact will be available for a thirty-minute call with qualified prospects at peer organisations. This is a small ask when framed early. It is a large ask when raised after the fact.
What the 90-day structure should look like
Days 1–14: Governance and integration. Steering group established. GxP documentation reviewed. IT integration plan signed off. Success metrics agreed in writing. No hardware deployed until this is complete.
Days 15–45: Controlled deployment and baseline. Hardware deployed at the agreed scope — not expanded. Baseline data collected. No configuration changes without a documented change control entry. The objective is clean, comparable data, not impressive-looking dashboards.
Days 46–75: Measurement against success metrics. Real operational data against the agreed baseline. Deviations documented. Steering group review at day 60. If metrics are not tracking positively, this is the moment to diagnose — not the end-of-pilot review.
Days 76–90: Outcome documentation and expansion design. Final results documented against the agreed metrics. Reference case agreement activated if thresholds are met. Multi-site expansion proposal developed with the steering group — not handed over from outside. The buyer should co-author the expansion business case. That investment means they own it.
The commercial mistake that shelves pilots
The most common reason a successful pilot does not convert to a permanent deployment is that the conversation about permanent deployment happens after the pilot ends.
By that point, the budget cycle may have closed. The internal champion may have moved roles. The steering group may have dissolved. The momentum that existed at week twelve is gone by week sixteen.
The expansion proposal must be prepared during the pilot — ideally presented to the steering group at the day 60 review, when the data is starting to show results and the stakeholders are still engaged. The 90-day review should confirm a decision, not initiate a new procurement process.
This requires the commercial and implementation team to be running in parallel — not sequentially. The people managing the technical deployment and the people managing the commercial expansion must be coordinating from week one. In most IoT company structures, these teams hand off sequentially. That handoff is where pilots go to die.
The reference case is the product
For an IoT company entering a regulated market, the first three reference cases are worth more than the first three hundred sales presentations. Every subsequent commercial cycle moves faster because of them. Every procurement committee that says yes to a peer reference removes weeks from its own review process.
A 90-day pilot, designed correctly, does not just deploy technology. It manufactures a commercial asset that compounds across the entire European market.
Design it for that from day one.
Comments