The Questions that Matter When Moving from Successful Pilots
Several themes from our recent From Pilot to Production webinar stayed with us because they show up repeatedly whenever industrial teams move from a successful pilot to a real deployment.
This is the conversation operators, IT teams, security leaders, procurement, finance, and operations managers have once the excitement of the pilot is over, and someone finally asks the harder question:
If this works, are we ready to live with it?
A pilot can work and still leave a plant manager uneasy. A champion can be enthusiastic yet have no budget authority. IT can agree the technology is valuable and still worry about what it will connect to. None of that means the pilot failed. It means the conversation has shifted from proving value to accepting operational responsibility.
The stories that follow are drawn from a pattern we have seen repeatedly across industrial organizations. Different companies, different technologies, different industries; but often the same underlying questions. They tend to emerge only after the pilot succeeds, which is precisely why they catch so many founders by surprise.
The First Red Flags Appear Before the Pilot Starts
During our discussion, Jerry O'Gorman shared an ERP example that captured this pattern. The pilot software was implemented. The operating model was not. The organization adapted the software to fit existing behaviors rather than changing how it worked. As Jerry put it, the result was "digital transfer rather than digital transformation."
Experienced OT and IT leaders notice this long before a pilot fails on paper. They are watching whether the organization is preparing to adopt the technology.
When the Pilot Works, the Real Sale Starts
The KPI moved in the right direction. The champion is pleased. The readout went well. Everyone agrees the technology did what it was supposed to do.
From the startup’s side, the next step feels obvious. The pilot worked. Now the customer should roll it out.
Inside the customer organization, the decision has become more complicated. Security wants to understand the architecture. Procurement wants commercial terms. Finance wants to know whether the ROI survives beyond one line or site. Operations want to know who supports the system when the vendor is no longer standing next to the team. Mobeen Khan described this second sales process.
That second sale is harder. The conversation is no longer about whether value exists. It is about whether the organization is prepared to accept the change required to capture it.
Founders often misread this slowdown. They treat it as a product problem. Maybe the dashboard needs work? Maybe the model needs another release? Maybe the pilot report needs more evidence?
The customer may already believe the product works. What they are deciding is whether adopting it creates risk, complexity, cost, or accountability the organization is not ready to carry.
Mobeen gets to the heart of it: “You’re not selling a product. You are selling a change in their process.”
Everyone Likes It. Nobody Owns It.
Positive feedback is useful, but it can hide what matters most.
Support and authority are not the same. The person who brought in the pilot may not control budget. The person who sees the use case may not approve rollout. The person who likes the technology may not carry the risk if it fails.
That is why the champion question must be asked earlier than most founders ask it.
Mobeen Khan shared an example from a chemicals manufacturer that identified its real stakeholders before the pilot began. The team focused on production managers responsible for the biggest downtime problems. They were not looking for innovation. They wanted the line running.
A real champion is not just someone who believes in the product. A real champion is someone whose own outcome improves if the deployment succeeds.
Alistair Fulton put the human side of this well: when the rollout helps someone gain credibility, recognition, or a bigger role, that person has a reason to fight for it when the organization slows down.
Founders often keep selling to the person who already believes. The better question is whether anyone with authority cares.
Monday Morning Matters More Than the Final Readout
The final review is where the pilot gets celebrated. Monday morning is where the deployment either begins or quietly starts to fade.
The pilot ended on Friday. Then the normal operating week starts again.
The vendor is no longer in the room. The project sponsor has other priorities. The plant has production targets. IT has other systems to protect. Procurement has a queue. Finance has a budget cycle. Security has standards that do not disappear because the pilot went well.
This is where the word “pilot” can become a trap. A pilot is safe, temporary, contained, and reversible. It lets the customer learn without committing and lets the vendor get in the door.
That can be useful. It can also become a holding pattern where everyone agrees the work was interesting, and nobody must decide what happens next.
Chris van Dyke, CEO of Momenta Portfolio company Overview AI, made an important point on this:
As Overview AI matured, the team increasingly tried not to frame early engagements as pilots at all. They pushed towards initial purchases tied to a real operating need.
The difference is subtle but important. A pilot asks whether something is worth exploring. An initial purchase asks whether something belongs in the operating plan.
Ken Forster’s phrase fits this logic: “Think global, act local, grow organically.” Start with the end state, prove something locally, and use that proof to build the next milestone.
The pilot is not the prize. It is evidence.
If no one can explain what happens after success, the pilot may still produce learning, confidence, and a useful reference. It may not be a buying process. Founders should know the difference before committing their best people to it.
A Great Pilot Can Still Make Operators Nervous
Some of the strongest pilots are also the most misleading.
They have attention, urgency, a controlled scope, and a committed sponsor. Problems get escalated quickly. Exceptions are made. The vendor team is close to the work. For a short period, the organization behaves in a way it will not behave once the system becomes normal.
Production is normal. It is shifts, sites, maintenance windows, procurement rules, infrastructure constraints, cyber requirements, budget cycles, and users who were never part of the original excitement.
It is what happens when the special attention disappears.
Alistair’s line is the cleanest version of this: “It works is not the milestone. It scales is the milestone.”
A pilot proves the solution can work under favorable conditions. Production asks whether it can survive normal ones.
The Question Founders Should Ask Earlier
Most founders ask what they need to prove during the pilot.
Operators ask what needs to be true for the result to become part of the business.
That question leads to a very different conversation. Who owns it if it works? Who funds the next phase? Who supports it when the vendor is gone? Who signs off on security? Who can change the way they work? Who benefits enough to fight for it? Who carries the risk when something goes wrong?
These questions do not sound as exciting as model performance or pilot ROI, but they are usually where production is decided.
The technology starts the conversation. The organization decides whether it will continue.
That is what founders need to understand before starting the pilot, not after the final readout. In industrial AI, a pilot may win the room. Production must win the organization.
Continue the Conversation: Watch the Webinar
Many of the insights discussed in this article originated from Momenta's webinar, From Pilot to Production: Where Industrial AI Wins or Fails, featuring industrial operators, founders, and industry leaders sharing lessons learned from real-world deployments: Watch the webinar on demand here
Are you building an industrial AI company and finding that growth slows after successful pilots?
The technology may not be the problem. Enterprise adoption often comes down to ownership, deployment readiness, organizational alignment, and risk management.
At Momenta, we work with industrial innovators navigating exactly these challenges. If you're working to move from pilot to production, we'd welcome the conversation.
Connect with Jerry O'Gorman at jerry@momenta.vc
Momenta is the leading Industrial Impact® venture capital firm, accelerating industrial innovators across energy, manufacturing, smart spaces, and the supply chain. Our team of deep industry operators has helped scale industry leaders and innovators to improve critical industries, the environment, and people's quality of life for over a decade. For more information, please visit http://www.momenta.vc
