Manufacturing · Plant-floor AI, sensing and connected worker platforms
Your pilot passes, then nobody owns the rollout.
You sell sensors, machine monitoring, industrial AI or no-code apps for the shop floor, and you land one line at a time. The pilot hits its targets, then waits for a budget and a group sponsor nobody lined up. Pilot purgatory and capital timing are each a likely bottleneck at 4 of the 5 plant-floor platforms in Panelhop’s analysis.
- Typical deal
- About €57k a year Illustrative
- Sales cycle
- 1.5–9 months, one plant Illustrative
- Buying panel
- 8–15 people, multi-site Illustrative
Updated 5 October 2026 · Based on Panelhop research, October 2026
At a multi-site manufacturer, from the pilot plant to the group8–15 people Illustrative
The short answer
How do plant-floor AI and connected worker vendors sell to manufacturers?
Plant-floor AI, sensing and connected worker vendors sell to manufacturers one plant at a time, usually through a pilot on a single line. Single-plant deals take 1.5–9 months, by Panelhop’s estimate, but pilots often pass and never become multi-site contracts. The pilot charter, a group sponsor and a plant-level expansion map decide revenue more than the first site does.
Plant-floor AI, sensing and connected worker platforms · How a deal really moves
The first line is live. The network isn’t. Pilots run at your cost, and each plant buys on its own budget. The same pilot, designed to roll out. Charter and group owner up front, works council status tracked.
One plant first, then the group: an estimated 1.5–9 months for the first site, 8–15 people for the group deal.
What opens a deal
- Quality escape or recall: Regulation
- New line or greenfield plant: Funding
- New plant manager: Leadership
- Platform end of life: Technology
- Budget season and shutdowns: Budget
- Grant or depreciation window: Funding · UK, DE
Signal Desk · weekly: In-market accounts, scored and mapped
Your buyer and who decides
A manufacturer’s plant
One line first, then every other site
54% of plants worldwide on paper or spreadsheets
Panel Check · coverage baselined
- Plant manager, can Veto: Another pilot that never scales, or downtime from the pilot.
- Group operations, can Veto: Funding a rollout that no plant asked for.
- Finance, can Veto: Capex under trade uncertainty, and a rollout that overruns.
- Works council (DE, AT), can Veto: App or sensor data used to rate individual operators.
- Controls engineering, can Veto: A sensor or gateway that opens remote access to the line.
- Enterprise IT, can Veto: A plant-bought tool that IT must support later.
- CI and production: Extra data entry and screens nobody reads.
- Maintenance: False alarms and another system to maintain.
How the deal moves
Targeting
- Where it stalls
- HQ gets the email. The plant has the budget
- With Panelhop: Panel Check
- Tiers from closed-won data by plant count, process type and systems
Demo
Pilot Typical time: 2–4 weeks planned
- Where it stalls
- Your sensors, your cost, no purchase order
- With Panelhop: Leak Fix
- Charter, scale-up criteria, multi-site price and group owner up front
Works agreement Typical time: Often months
- Where it stalls
- No works agreement, no go-live
- With Panelhop: Leak Fix
- Works council status, HR contact and signature date for DE and AT deals
Site contract
- Where it stalls
- The champion says the budget is coming
- With Panelhop: Leak Fix
- Each plant’s fiscal year-end and shutdowns set the close date
Adoption
Rollout
- Where it stalls
- The next plant asks for its own pilot
- With Panelhop: Panel Ops
- Expansion triggers worked monthly, plants per customer reported
Panel Ops · monthly: Scores and plays tuned against the baseline
Illustrative Source: Stages, seats, triggers and stalls from Panelhop research, October 2026; IoT Analytics; the services as described on the Services page. Note: Durations, panel sizes and cycle lengths are Panelhop estimates from our research, not measurements.
At a glance
| Typical deal | About €57k a year Illustrative |
|---|---|
| Sales cycle | 1.5–9 months, one plant Illustrative |
| Buying panel | 8–15 people, multi-site Illustrative |
| How deals start | A hands-on demo on the plant’s own machine data, then a pilot on one line |
Source: Panelhop research, October 2026. Note: Values marked Illustrative are Panelhop estimates from our research, not measurements.
Plant-floor deals leak between the pilot and the network.
Where do plant-floor platform deals with manufacturers leak?
Plant-floor platform deals leak at the vendor-funded pilot, the late works council, the stalled site budget, flat adoption and per-site contracts that keep the flagship plant alone. The paper status quo is the main rival. IoT Analytics estimates that 54% of plants globally used pen, paper or spreadsheets to manage operations in 2024, and reported in December 2025 that only 8% use a commercial MES.
Where the pipeline leaks: 5 points across 7 stages.
Vendor-funded pilots buy logos, not rollouts
- What you see
- Sensors and gateways stay on the customer’s line at your cost, and a successful pilot report triggers no budget request.
- Why it happens
- Pilot fees are too low to create internal commitment, and the plant sponsor has no authority over a rollout. No charter sets scale-up criteria, a multi-site price and a group owner before the hardware ships.
Stage Pilot
The works council arrives after the pilot
- What you see
- A German pilot cannot start, or a signed site cannot go live, until a works agreement is signed.
- Why it happens
- The sales kit has no data protection concept, permission model or draft works agreement (Betriebsvereinbarung), and HR is missing from the stakeholder map.
Stage Works agreement
Won sites wait on a capital request
- What you see
- A technically won site moves from quarter to quarter while the plant champion says the budget is coming.
- Why it happens
- Stages do not model plant budgets, fiscal year-ends or shutdown windows. Capital timing is a likely bottleneck at 4 of the 5 plant-floor platforms in Panelhop’s analysis.
Stage Site contract
Usage flattens and renewals turn into price talks
- What you see
- Operators are back on clipboards weeks after go-live, and the renewal opens with a request for a lower price.
- Why it happens
- No shared definition of success was agreed at signature, ERP integration was deferred and frontline staff fear surveillance.
Stage Adoption
The flagship plant is happy, and the group never hears
- What you see
- Net revenue retention stays flat despite a happy flagship plant, and group operations has never seen its results.
- Why it happens
- Pricing and contracts are written per site, and nobody briefs a group sponsor or a centre of excellence. Plant-by-plant expansion and ROI doubt are each a likely bottleneck at 3 of the 5 plant-floor platforms in Panelhop’s analysis.
Stage Rollout
Plant events open the window for a pilot.
What makes a manufacturer buy machine monitoring, industrial AI or connected worker software?
Manufacturers buy plant-floor software after a quality escape, a new line, a new plant leader, a platform end of life, a new budget year or a grant window. Each event shows at plant level, so record it on the account with the plant named.
The 6 events that open or close the window for a deal.
Regulation
Quality escape or recall
- What happens
- A recall, a customer escalation or a regulator action forces a corrective action plan at the plant.
- Where to spot it
- FDA, USDA and NHTSA recall lists and customer quality escalations.
- Window
- Traceability, quality and monitoring tools get funded in the months after the event.
Funding
New line or greenfield plant
- What happens
- A new line or site is built, and its plant-floor systems are chosen before start of production.
- Where to spot it
- Planning permits, investment announcements and hiring for a named new site.
- Window
- Choices are made in the integrator’s functional design, long before the line runs.
Leadership
New plant manager or operations leader
- What happens
- A new plant manager or VP Operations reviews tools and priorities at the site.
- Where to spot it
- Company announcements and job changes at target plants.
- Window
- The first months in the role, while priorities are still open.
Technology
Platform end of life or ownership change
- What happens
- An IoT platform, connectivity software or the operating system on HMIs and shop-floor PCs loses support or changes owner, and its installed base re-evaluates.
- Where to spot it
- Divestment filings, user communities and end-of-life or end-of-support notices.
- Window
- The months after the announcement, while customers weigh a migration.
Budget cycle
Budget season and shutdown windows
- What happens
- Plant budgets lock before fiscal year-end, and installations wait for planned shutdowns.
- Where to spot it
- Fiscal year-ends in annual reports, and summer and year-end shutdown schedules in trade press.
- Window
- A rollout must be in next year’s plan months before fiscal year-end.
Funding
Grant or tax window
- What happens
- Made Smarter in England and Digitalbonus.Bayern co-fund digital projects at smaller manufacturers, and Germany’s degressive depreciation favours movable assets acquired by the end of 2027.
- Where to spot it
- Regional programme cohorts and deadlines, and the buyer’s finance team.
- Window
- Application deadlines and the end-2027 depreciation cut-off pull plant projects forward.
The plant champions it; the group must scale it.
Who decides on a plant-floor platform at a manufacturer?
At a manufacturer, the plant manager sponsors a plant-floor platform, while OT engineering, IT, the plant controller and, in Germany, the works council can each stop it. The pilot needs a plant sponsor, but the multi-site contract needs a group executive and a capital request that finance approves. Shift supervisors and operators decide whether the platform gets used.
At a multi-site manufacturer, from the pilot plant to the group, 8–15 people sit on the panel and 6 seats can stop the deal.
At a multi-site manufacturer, from the pilot plant to the group: 8–15 people
Plant manager
Can Veto
Werkleiter · Director of Manufacturing
- Cares about
- OEE, downtime and scrap on the bottleneck line.
- Worries about
- Another pilot that never scales, or downtime caused by the pilot itself.
Group operations executive
Can Veto
COO · VP Operations / VP Manufacturing · Head of Operational Excellence
- Cares about
- One standard across plants and a lower cost per plant.
- Worries about
- Funding a rollout that no plant asked for.
Continuous improvement and production
CI or OpEx Manager · Production Manager · Meister / Shift Supervisor
- Cares about
- Real-time downtime reasons and less paper on the line.
- Worries about
- Extra data entry and screens nobody reads.
Maintenance and reliability
Maintenance Manager
- Cares about
- Fewer unplanned stops and sensor data the team can trust.
- Worries about
- False alarms and another system to maintain.
OT and automation engineering
Can Veto
Head of Automation · Controls Engineer · OT Engineer
- Cares about
- PLC and SCADA connectivity with no impact on the control network.
- Worries about
- A sensor or gateway that opens remote access to the line.
Enterprise IT
Can Veto
Head of Manufacturing IT · CIO / IT-Leiter
- Cares about
- Integration with ERP and identity, and no shadow IT.
- Worries about
- A plant-bought tool that IT must support later.
Finance
Can Veto
Plant Controller · CFO / Kaufmännischer Geschäftsführer
- Cares about
- A short payback, and capex or opex treatment for sensors and licences.
- Worries about
- Committing capex under trade uncertainty, and a rollout that overruns the plant P&L.
Works council (Germany and Austria)
Can Veto
Betriebsratsvorsitzender · Betriebsrat IT committee member
- Cares about
- Aggregate reporting only, short retention and role-based access.
- Worries about
- App or sensor data used to rate individual operators.
You sell results on one line, then the network.
What do plant-floor platform vendors sell, and to whom?
Plant-floor platform vendors sell AI, sensors and no-code apps to single plants of manufacturers, layered on existing machines and systems, with fast first results and nothing replaced. Each plant has its own manager and budget. Most of the revenue sits in the plants that follow.
What vendors of this type sell
- Machine monitoring and industrial IoT
- Condition monitoring and predictive maintenance sensors
- Industrial AI on existing plant data
- Connected worker and digital work instruction apps
- App-based (composable) MES
Which manufacturers buy it
- Single plants of multi-site discrete and process manufacturers
- Job shops and mid-market discrete plants
- Aerospace and automotive suppliers with certified quality systems
- Mittelstand firms with one or a few sites
Revenue depends on what happens after the pilot.
How does a plant-floor platform deal move from pilot to rollout?
A plant-floor platform deal moves from a plant trigger and a hands-on demo to a pilot, a site contract and, if anyone planned it, a multi-site rollout. Mid-sized firms often skip the formal RFP for a short RFI and a pilot. Durations are Panelhop estimates of the manufacturer’s side.
Stage by stage: what you do, what the manufacturer does, and what changes at the 5 stages where deals stall.
| Stage | What you do | What the manufacturer does | Today | With Panelhop |
|---|---|---|---|---|
| Targeting | Targets parent logos and horizontal segments, often well beyond manufacturing. | A downtime problem, a quality escape, a skills gap or a new line sends a plant leader looking for help. | Parent logos and horizontal segments. Stalls: Logos instead of plants. Site-level platforms are sold to parent companies, so the plant with the problem and the budget never sees the outreach. | A Panel Check drafts tiers from your closed-won and closed-lost data, testing plant count, process type and installed systems as fit factors, and baselines pipeline from target accounts. Panel Check GTM audit · 2–3 weeks |
| Demo | Runs a hands-on demo, ideally on the plant’s own machine data. | The plant manager and CI lead test usability, and OT engineering checks connectivity. | Demos go to whoever asks. | Each week, manufacturers with a live plant signal arrive in your CRM, scored, with the buying group mapped and the signal that fired. Typical signals are a new line, a quality escape or a new plant manager. Signal Desk In-market accounts, weekly |
| Pilot Typical time: 2–4 weeks for an MES-style pilot, often extended | Runs a pilot on one line, often with vendor-funded hardware. | Tests the platform on a bottleneck line against OEE, downtime or scrap, beside existing systems. | Pilots start on a handshake. Stalls: Pilot purgatory. The pilot meets its technical goals, but no scale-up criteria, multi-site price or group owner were agreed before it started. | The pilot becomes a stage with entry criteria: a written charter, scale-up criteria, a multi-site price and a named group owner. Leak Fix We build the fixes |
| Works agreement Typical time: Often months, in parallel with the pilot | Treats co-determination in Germany and Austria as the customer’s problem. | HR and the works council negotiate purposes, data use and monitoring limits, often from before the pilot until productive use. | The works council is left to the customer. Stalls: No works agreement, no go-live. In Germany, a system able to monitor staff needs the works council’s agreement, where one exists, before it is introduced, even when it is called a pilot. | Works council status, the HR contact and a target signature date become required fields on every opportunity in Germany and Austria. Leak Fix We build the fixes |
| Site contract | Converts the pilot into a contract for the first plant. | The plant controller and procurement fund the site from the plant budget or a capital request. | Close dates ignore the plant budget. Stalls: Waiting on the plant budget. The technically won site waits for a capital request the plant champion never formally submits, or for the next budget year. | A budget-pending stage and each plant’s fiscal year-end and shutdown windows tie close dates to budget milestones. Leak Fix We build the fixes |
| Adoption | Tracks logins after go-live. | Operators decide whether to use the platform or drift back to paper and spreadsheets. | Logins stand in for adoption. | A handoff document records the agreed success measure, and a health score tracks adoption against it, with renewal tasks well before the renewal date. Leak Fix We build the fixes |
| Rollout | Leaves expansion to the original rep and the renewal. | Each further plant decides on its own P&L unless a group executive sets a standard. | Expansion waits for the renewal. Stalls: The next plant wants its own pilot. Each further plant says every plant is different and standard software will not fit, so without a group standard the rollout restarts as a new pilot. | With your team, Panel Ops operates the expansion triggers that Leak Fix builds and re-tiers your target accounts each quarter on new won and lost data. It reports progress against the baseline every month. Panel Ops We run it monthly |
Design the expansion before the pilot starts.
How does Panelhop help plant-floor platform vendors sell to manufacturers?
Panelhop helps plant-floor platform vendors with a Panel Check (GTM audit) that drafts tiers counting plants as well as parent companies and baselines each stage. Signal Desk (in-market accounts, weekly), Leak Fix (we build the fixes) and Panel Ops (we run it monthly) then work the stages that leak. Every result is reported against the Panel Check baseline.
What we baseline and report
- Plants per customer, against the baseline
- Share of pilots with a charter, scale-up criteria and a group owner, against the baseline
- Days from pilot success to purchase order, against the baseline
Other vendor types in manufacturing.
What other vendors sell to manufacturers?
The same manufacturers buy from these vendor types too, through different panels and pipelines.
- Vendor type
Enterprise manufacturing software: ERP, planning, PLM, QMS and CPQ
ERP, supply chain planning, PLM, quality and CPQ software for multi-site manufacturers and engineer-to-order machine builders.
Read the pipeline - Vendor type
OT security, compliance and product cybersecurity software
OT asset visibility, monitoring and vulnerability management for plants, plus SBOM and CRA reporting tools for machine and device makers.
Read the pipeline - Vendor type
Automation lines and engineered capital equipment
Custom automation lines, special-purpose machines and turnkey production systems sold to manufacturers as capital projects.
Read the pipeline
The words your buyers use, defined.
What do terms like “Connected worker” and “Composable MES” mean?
Plain definitions of the terms that come up when you sell plant-floor AI, sensing and connected worker platforms to manufacturers.
- Connected worker
- Apps and devices that give frontline staff digital work instructions, checks and training on the shop floor. Plants usually trial them line by line.
- Composable MES
- Manufacturing execution built from configurable apps rather than a single suite, so a plant can start with one process and add more over time.
- Pilot charter
- A written agreement, made before a pilot starts, on the scale-up criteria that trigger rollout, the multi-site price and the executive who owns the scale-up decision.
- Centre of excellence
- A group team that standardises a platform across plants with a template and lowers the cost per plant. Multi-plant MES programmes rely on one.
- Bottleneck line
- The line that limits a plant’s output. Pilots often start there because gains in OEE or downtime show up directly in plant throughput.
- Works agreement (Betriebsvereinbarung)
- A written agreement between employer and works council in Germany. Where a plant has a works council, a system able to monitor staff behaviour or performance needs the council’s agreement before introduction, pilots included.
Answers before your next manufacturer deal.
What do vendors of plant-floor AI, sensing and connected worker platforms ask about selling to manufacturers?
How do you avoid pilot purgatory when selling plant-floor software to manufacturers?
Vendors avoid pilot purgatory with manufacturers by charging for the pilot and agreeing how it ends before it starts. A pilot charter sets the scale-up criteria, such as OEE, downtime or scrap against a baseline, the multi-site price and the group executive who owns the rollout decision. A free pilot without them can pass every technical test and never become a purchase order. Pilot purgatory is a likely bottleneck at 4 of the 5 plant-floor platforms in Panelhop’s analysis.
What signals show a plant is about to buy MES or machine monitoring?
Plants usually buy MES or machine monitoring after a quality escape, a new line, a new plant manager, a platform end of life or a new budget year. Most of these signals are public at plant level, in recall lists, planning permits, job changes and end-of-support notices. Record each one on the manufacturer’s account with the plant named, a date and an owner. Then reach the plant manager and the group operations executive while the window is open.
How do you expand from one plant to every plant of a manufacturer?
Expanding from one plant to every plant of a manufacturer takes a separate motion from the first sale. Each plant has its own manager, budget and priorities, so map the remaining plants in the CRM, find a group sponsor above plant level and agree multi-site pricing early. Brief group operations on the flagship plant’s results against its baseline. Treat each further plant as a new opportunity with its own buying group.
Does the works council need to approve plant-floor software in Germany?
Yes, where the plant has a works council. In Germany, plant-floor software able to monitor staff behaviour or performance needs the works council’s agreement before it is introduced, under Section 87 of the Works Constitution Act. A deadlock goes to a conciliation board, and calling the rollout a pilot does not avoid it. Negotiating the agreement can take months, so bring a data protection concept, a permission model and a draft works agreement to the first plant meeting.
How long does it take to sell a plant-floor platform to a manufacturer?
Selling a plant-floor platform to a single plant of a manufacturer takes 1.5–9 months, about 4 months in a typical case, by Panelhop’s estimate. An owner-manager can decide directly, and a paid pilot route is quicker than a formal RFP. A works agreement in Germany, a capital request or the next budget year can add months, and every further plant is a new sales cycle.
Who is the economic buyer for MES or plant-floor software at a manufacturer?
At a manufacturer, the economic buyer for MES or plant-floor software depends on scope. For one site it is usually the plant manager or VP Operations, within local budget limits. For a multi-site contract it is a group operations executive, such as the COO or VP Manufacturing. OT engineering, enterprise IT, finance and, in Germany and Austria, the works council can each stop the deal, so plant-floor vendors should engage the group executive before the pilot ends.
Where the numbers come from.
Sources
Sourced figures link to their source below. Figures marked Illustrative, and figures given as estimates, are inferred from Panelhop research. Vendors appear only as types, never by name.
- IoT Analytics, Manufacturing Execution Systems: The 300+ vendors looking to displace pen, paper, and spreadsheets in the factory (2025)
- Bundesministerium der Justiz, Section 87 BetrVG (co-determination rights) (2026)
- Bundesministerium der Justiz (gesetze-im-internet.de), Einkommensteuergesetz, Section 7: Absetzung für Abnutzung oder Substanzverringerung (2026)
- Bayerisches Staatsministerium für Wirtschaft, Landesentwicklung und Energie, Digitalbonus.Bayern: Förderprogramm (2026)
- Made Smarter Adoption: Leading UK manufacturing into the future (2026)
- Panelhop research, October 2026: our analysis of the vendors, buying panels, pipelines and triggers for plant-floor AI, sensing and connected worker platforms in manufacturing, from public sources. Vendor names are not published.
Find where your pipeline to manufacturers leaks.
