# How do software and equipment vendors sell to manufacturers?

> **The short answer:** Software and equipment vendors sell to manufacturers on the capex calendar. For MES, quality, connected worker and OT security tools, the buying unit is often one plant with its own P&L. By Panelhop’s estimate, software deals take 4–12 months and involve 5–13 people; capital projects take longer. In 2022 the US had 5,042 manufacturers with 250 or more staff.

- Page: https://panelhop.com/industries/manufacturing/
- Section: Home › Industries › Manufacturing
- Updated 5 October 2026 · Based on Panelhop research, October 2026
- Written for: Vendors selling to manufacturers
- Publisher: Panelhop (https://panelhop.com/)

**The plant says yes. The deal waits for capex.** You sell software, sensing or automation to manufacturers: 5,042 US companies and 4,415 German enterprises with 250 or more staff. Your champion likes the product but cannot get it funded. Pilots pass without a multi-site contract, and technically won deals wait for a capital request or the next budget year.

- Large US manufacturers: 5,042
- Large German manufacturers: 4,415
- Studied vendors likely to stall on capex: 13 of 20

## Manufacturing · How a deal really moves

**You sell to the parent. The plant buys. Deals stall at the champion, the pilot, capex and the next site.** (Illustrative)

With Panelhop: The same deal, on the plant’s capex calendar. Plants tiered, vetoes mapped and close dates set by capex.

One manufacturer, often one plant, 5–13 people and an estimated 4–12 months to signature, longer for capital projects.

What opens a deal:

- **New plant or line announced** (Funding)
- **Quality escape or recall** (Regulation)
- **ERP end of maintenance** (Technology)
- **Carve-out or acquisition** (Consolidation)
- **NIS2 and Cyber Resilience Act** (Regulation · EU, DE)
- **Budget season and shutdowns** (Budget)

The buyer: **A manufacturer**. Each plant often buys on its own P&L. 5,042 US · 4,415 DE firms, 250 or more staff.

Who decides:

| Seat | What worries them | Can veto |
|---|---|---|
| COO or Geschäftsführer | A pilot that never scales, or a cut-over that stops the line. | Yes |
| CFO or plant controller | Committing capex in a year of trade uncertainty. | Yes |
| CIO and enterprise IT | Shadow IT from plants in the middle of an ERP migration. | Yes |
| CISO and OT security | NIS2 gaps that leave management liable. | Yes |
| Controls and automation | An outage on the control network, or open remote access. | Yes |
| Works council (DE, AT) | Shop-floor data used to rate individuals. | Yes |
| Production and CI | Double entry on the line, and being rated as individuals. | No |
| System integrator | An unproven product that puts their delivery at risk. | No |

How the deal moves:

| Stage | Typical time | Where it stalls today | With Panelhop | Service |
|---|---|---|---|---|
| Targeting | 2–8 weeks | Sequences reach HQ while the plant buys | Tiers drafted from closed-won data, counting plants as well as parents | Panel Check (GTM audit · 2–3 weeks): https://panelhop.com/services#audit |
| Demand generation | – | – | – | – |
| First meeting | – | – | – | – |
| Discovery | 4–12 weeks | Champion loves the tool, can’t fund it | A role map puts finance, OT, security and any works council on the deal | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Evaluation | 6–24 weeks | – | – | – |
| Pilot | 2–8 weeks | One line passes. No multi-site price agreed | Charter, scale-up criteria, multi-site price and owner before day one | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Security review | 4–12 weeks | – | – | – |
| Commercial close | 3–6 weeks | Technically won, still waiting on capex | A budget-pending stage, and close dates that follow budget milestones | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Go-live | At shutdown | – | – | – |
| Plant expansion | – | One happy plant, and the rest never follow | Expansion triggers worked monthly, accounts re-tiered each quarter | Panel Ops (We run it monthly): https://panelhop.com/services#run |

With Panelhop across the deal: Signal Desk · weekly on what opens a deal (in-market accounts, scored and mapped); Panel Check on the buyer (coverage baselined); Panel Ops · monthly from the last stage back to the next trigger (scores and plays tuned against the baseline).

*Source: Stages, seats, triggers and stalls from Panelhop research, October 2026; [National Center for Science and Engineering Statistics and U.S. Census Bureau](https://www.ncses.nsf.gov/pubs/nsf25303/assets/data-tables/tables/nsf25303-tab037.pdf); [Eurostat](https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/data/sbs_sc_ovw/A.ENT_NR.C.GE250+50-249+TOTAL.EU27_2020+DE+AT/?format=SDMX-CSV&startPeriod=2024&endPeriod=2024); 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

| Fact | Value |
|---|---|
| Typical software deal | €40–400k a year, from single-plant tools to enterprise planning (Illustrative) |
| Sales cycle | 4–12 months for most deals (Illustrative) |
| Buying panel | 5–13 people across operations, IT, OT, security, quality and finance (Illustrative) |
| Manufacturers with 250 or more staff | 5,042 in the US (2022), 1,240 in the UK (2025) and 15,975 across the EU27, Germany’s 4,415 included (2024) |
| How deals start | A plant trigger, then a demo request, a fair meeting or an integrator’s shortlist |
| Main triggers | NIS2, the Cyber Resilience Act, cyber incidents, quality escapes, new plants, carve-outs and ERP migrations |

*Source: Panelhop research, October 2026; [National Center for Science and Engineering Statistics and U.S. Census Bureau](https://www.ncses.nsf.gov/pubs/nsf25303/assets/data-tables/tables/nsf25303-tab037.pdf); [Eurostat](https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/data/sbs_sc_ovw/A.ENT_NR.C.GE250+50-249+TOTAL.EU27_2020+DE+AT/?format=SDMX-CSV&startPeriod=2024&endPeriod=2024); [Department for Business and Trade](https://www.gov.uk/government/statistics/business-population-estimates-2025/business-population-estimates-for-the-uk-and-regions-2025-statistical-release).*
*Note: Values marked Illustrative are Panelhop estimates from our research, not measurements.*

## Where do manufacturing software deals leak?

**Manufacturing pipeline leaks in the sales system, not the market.**

Manufacturing pipelines leak at the plant list, the single champion, the pilot, the security and works council gates, the capex calendar and the second plant.

**Exhibit 1: Where the pipeline leaks: 6 points across 10 stages.**

1. **Sequences reach headquarters while the plant buys** (stage: Targeting). What you see: Marketing reports engagement at the parent while reps work one plant. Sequences reach corporate IT instead of the plant or operations manager. Why it happens: Firmographic data is keyed to the legal entity, and industry codes cannot separate a bakery from a fab. Plant managers are missing from most contact databases.
2. **Your champion likes it but can’t get it funded** (stage: Discovery). What you see: Opportunities still show one contact role after several meetings, and no budget holder has joined a call. Why it happens: Discovery never maps the approval path from the plant to finance and corporate operations. Only 2 of the 20 vendors in Panelhop’s analysis name finance as a buyer on their websites. ROI doubt with finance entering late is a likely bottleneck at 8 of 20 vendors in that analysis.
3. **Pilots pass, then run for quarters with no purchase order** (stage: Pilot). What you see: Pilots are extended quarter after quarter with no purchase order, and the pilot stage fills with deals that never age out. Why it happens: No pilot charter sets scale-up criteria, a multi-site price and an executive owner before day one. None of the vendors in Panelhop’s analysis publishes one. Pilot purgatory is a likely bottleneck at 5 of 20 vendors in that analysis.
4. **Security and the works council arrive after the price** (stage: Security review). What you see: A deal waits for a TISAX label the vendor has not started, or a signed German contract cannot go live. Why it happens: Security, OT engineering and the works council are not mapped at discovery. In Panelhop’s analysis, 15 of 20 vendors publish no vendor-security evidence. Where a German plant has a works council, a system able to monitor staff needs the works council’s agreement before it is introduced.
5. **Technically won deals slip quarter after quarter** (stage: Commercial close). What you see: Close dates on technically won deals move quarter after quarter, and forecast misses are explained as budget timing. Why it happens: Stages do not model capital requests, fiscal year-ends or shutdown windows, and the champion never formally submits the request. Capital timing is a likely bottleneck at 13 of 20 vendors in Panelhop’s analysis.
6. **The flagship plant never brings the rest** (stage: Plant expansion). What you see: Customer count grows while plants per customer stay flat, and the original rep handles expansion alongside new logos. Why it happens: Nobody keeps a plant-level whitespace map or a group sponsor. Plant-by-plant expansion is a likely bottleneck at 10 of 20 vendors in Panelhop’s analysis.

*Source: Panelhop research, October 2026.*

## What triggers a manufacturer to buy new software or equipment?

**Dated rules and plant events open budgets.**

Manufacturers buy new software and equipment after a dated rule, a cyber incident, a quality escape, a new plant, a carve-out, an ERP migration or budget season. The same events can freeze a deal. Most are public, so each belongs on the account record as a dated field with an owner who acts that week.

**Exhibit 2: The 8 events that open or close the window for a deal.**

- **NIS2 duties in Germany** (Regulation). What happens: Since December 2025, Germany’s NIS2 law covers manufacturers in listed sectors with at least 50 staff, or more than €10M in both turnover and balance sheet. Where to spot it: BSI registration statistics, with 4,095 manufacturing registrations by mid-2026, plus ISMS and OT security job posts and it-sa in Nuremberg each October. Window: Management liability, supply-chain duties and audits keep security purchases open through 2026 and 2027.
- **Cyber Resilience Act and Machinery Regulation** (Regulation). What happens: Makers of connected products must report actively exploited vulnerabilities from 11 September 2026, and the Machinery Regulation applies from 20 January 2027. Where to spot it: Job posts for product security, PSIRT and conformity roles, and machine builders showing connected products at Hannover Messe and SPS. Window: Product security, SBOM and documentation work must land before the CRA’s main obligations apply on 11 December 2027.
- **Cyber incident at the company or a peer** (Security). What happens: Ransomware or an intrusion halts production at a manufacturer or a close peer in the same industry. Where to spot it: Material-incident disclosures by US-listed companies to the SEC, and trade and security press. Window: Weeks for the victim; peers fund visibility, segmentation and backup over the following months.
- **New plant, line or greenfield site** (Funding). What happens: A manufacturer announces a new factory, a new line or a capacity expansion. Where to spot it: Planning permits, investment announcements, regional development agencies and hiring for a named new site. Window: MES, OT security and ERP choices are made in the integrator’s functional design, long before start of production.
- **Quality escape, recall or regulator action** (Regulation). What happens: A recall, a regulator production cap, a warning letter or a major customer escalation forces a corrective action plan. Where to spot it: FDA, USDA FSIS and NHTSA recall lists, FDA warning letters and customer quality escalations. Window: QMS, traceability, MES and supplier quality tools get funded in the months after the event.
- **Carve-out, spin-off or acquisition** (Consolidation). What happens: A business separates from its parent or is acquired, and must replace parent systems before its transition services agreement ends. Where to spot it: Separation announcements, stock exchange filings and the Bundesanzeiger. Window: Selections open soon after the announcement and must finish before the transition services agreement expires. Acquirers consolidate ERP, MES and quality systems.
- **ERP migration or end of maintenance** (Technology). What happens: A manufacturer moves off a legacy ERP release as mainstream maintenance ends, which reopens MES, quality, planning and integration choices. Where to spot it: Job posts for ERP migration and data-migration roles, go-live announcements and user-group surveys. Window: Adjacent purchases often freeze until cut-over, so record the planned date and return to the account then.
- **Budget season and shutdown windows** (Budget cycle). What happens: Capex and IT budgets are set in the months before fiscal year-end, and installations wait for planned summer and year-end shutdowns. Where to spot it: Fiscal year-ends in annual reports, and plant and automaker shutdown schedules in trade press. Window: Projects missing from next year’s plan usually wait a full year.

*Source: Panelhop research, October 2026; [BSI – Bundesamt für Sicherheit in der Informationstechnik](https://www.bsi.bund.de/DE/Themen/Regulierte-Wirtschaft/NIS-2-regulierte-Unternehmen/NIS-2-in-Zahlen/nis-2-in-zahlen.html); [Bundesministerium der Justiz (gesetze-im-internet.de)](https://www.gesetze-im-internet.de/bsig_2025/__28.html); [European Commission](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act); [European Commission, DG Internal Market, Industry, Entrepreneurship and SMEs](https://single-market-economy.ec.europa.eu/sectors/mechanical-engineering/machinery_en); [BSI (Bundesamt für Sicherheit in der Informationstechnik)](https://www.bsi.bund.de/DE/Service-Navi/Presse/Pressemitteilungen/Presse2025/251205_NIS-2-Umsetzungsgesetz_in_Kraft.html).*

## Who signs off on a manufacturing software deal?

**The champion rarely holds the budget or the veto.**

The COO, VP Operations or Geschäftsführer usually owns a manufacturing software deal. IT, OT engineering, security, finance and, in Germany, the works council can each stop it, and so can quality in certified plants. Procurement and the board join as the deal grows, and a system integrator often writes the shortlist without a vote.

**Exhibit 3: At a typical discrete manufacturer, 5–13 people sit on the panel and 6 seats can stop the deal.** (Illustrative)

At a typical discrete manufacturer: 5–13 people.

| Seat | Typical titles | Cares about | Worries about | Can veto |
|---|---|---|---|---|
| Operations executive or owner-manager | COO, Plant Manager / Werkleiter, Geschäftsführer | OEE, scrap and a payback the plant P&L can carry. | Another pilot that never scales, or a cut-over that stops the line. | Yes |
| Production and continuous improvement | Production Manager, Meister / Shift Supervisor, CI or OpEx Manager | Usable shop-floor screens, less double entry and real downtime reasons. | Extra data entry on the line and being rated as individuals. | No |
| Enterprise IT and architecture | CIO / IT-Leiter, Enterprise Architect, Head of Manufacturing IT | ERP integration, identity and a support model IT can run. | Shadow IT from plants and integration debt during an ERP migration. | Yes |
| OT and automation engineering | Head of Automation, Controls Engineer, Process Control Manager | PLC, SCADA and historian connectivity inside agreed change windows. | Anything on the control network that causes an outage, and open vendor remote access. | Yes |
| Security | CISO, OT Security Manager, Informationssicherheitsbeauftragter | Segmentation, asset inventory and vendor security evidence. | NIS2 gaps that leave management liable, and an IT compromise spreading into OT. | Yes |
| Finance | CFO / Kaufmännischer Geschäftsführer, Plant Controller, FP&A Lead | Payback, capex or opex treatment and multi-year cost with services included. | Committing capex in a year of trade uncertainty, and project overruns. | Yes |
| Works council (Germany and Austria) | Betriebsratsvorsitzender, Gesamtbetriebsrat | No individual performance monitoring, data minimisation and role-based access. | Shop-floor data used to rate individuals, and scope creep after go-live. | Yes |
| System integrator or selection consultant | System integrator, ERP selection consultant, Made Smarter or MEP adviser | Repeatable delivery and a low-risk outcome for the manufacturer. | An unproven product that puts their own delivery at risk. | No |

*Source: Panelhop research, October 2026.*
*Note: The panel size is a Panelhop estimate from our research, not a measurement.*

## Which manufacturers buy industrial software and automation?

**Most segments are small enough to list by name.**

The main manufacturing buyers of industrial software and automation are automotive OEMs and suppliers, machinery builders, aerospace and defence firms, electronics makers, process manufacturers and mid-sized firms. A large manufacturer is often several buying units, because each plant has its own manager, budget and priorities. Count plants as well as parent companies before you tier the list.

**Exhibit 4: Mid-sized firms are the largest group we could count: 19,806 US and 14,017 German manufacturers with 50–249 staff.**

| Segment | What they are | Region | Accounts |
|---|---|---|---|
| Automotive OEMs and Tier 1 and Tier 2 suppliers | OEMs push IATF 16949 quality certification and, for anyone handling OEM data, a TISAX label down the supply chain. Supplier margins are thin, so payback cases must be short. | US | 425 companies with 250 or more staff |
| Automotive OEMs and Tier 1 and Tier 2 suppliers | OEMs push IATF 16949 quality certification and, for anyone handling OEM data, a TISAX label down the supply chain. Supplier margins are thin, so payback cases must be short. | DACH | 204 in Germany with 250 or more staff |
| Automotive OEMs and Tier 1 and Tier 2 suppliers | OEMs push IATF 16949 quality certification and, for anyone handling OEM data, a TISAX label down the supply chain. Supplier margins are thin, so payback cases must be short. | EU | about 1,140 across the EU27 with 250 or more staff, Germany included (Eurostat estimate) |
| Machinery and equipment builders | Most are engineer-to-order or configure-to-order firms that buy CPQ, PLM, ERP and field service software and sell connected machines themselves. VDMA’s 3,500 mostly medium-sized members are a ready core list for Germany. | US | 527 companies with 250 or more staff |
| Machinery and equipment builders | Most are engineer-to-order or configure-to-order firms that buy CPQ, PLM, ERP and field service software and sell connected machines themselves. VDMA’s 3,500 mostly medium-sized members are a ready core list for Germany. | DACH | 801 in Germany with 250 or more staff |
| Aerospace, defence and transport equipment | Aerospace and defence programmes run for years under strict configuration control and export-control rules on technical data. US defence suppliers still self-assess against NIST and DFARS rules while CMMC Phase II is suspended. | US | 63 aerospace companies with 250 or more staff |
| Aerospace, defence and transport equipment | Aerospace and defence programmes run for years under strict configuration control and export-control rules on technical data. US defence suppliers still self-assess against NIST and DFARS rules while CMMC Phase II is suspended. | DACH | 65 in Germany with 250 or more staff, across aircraft, ships, rail and military vehicles |
| Electronics, electrical equipment and EMS | Short product cycles and component supply risk keep PLM, planning and quality central, including at contract electronics manufacturers (EMS). Makers of connected products now carry Cyber Resilience Act duties. | US | 287 electronics and 153 electrical equipment companies with 250 or more staff |
| Electronics, electrical equipment and EMS | Short product cycles and component supply risk keep PLM, planning and quality central, including at contract electronics manufacturers (EMS). Makers of connected products now carry Cyber Resilience Act duties. | DACH | 232 electronics and 283 electrical equipment enterprises in Germany with 250 or more staff |
| Process manufacturers: chemicals, plastics, food and beverage | Batch and continuous plants buy historians, asset performance, laboratory, quality and traceability systems, and management of change reviews cover new software and control system changes. FDA will not enforce the FSMA 204 food traceability rule before 20 July 2028, but large grocery retailers already ask suppliers for traceability data. | US | 678 food, 268 chemical (pharmaceuticals excluded) and 479 plastics and rubber companies with 250 or more staff |
| Process manufacturers: chemicals, plastics, food and beverage | Batch and continuous plants buy historians, asset performance, laboratory, quality and traceability systems, and management of change reviews cover new software and control system changes. FDA will not enforce the FSMA 204 food traceability rule before 20 July 2028, but large grocery retailers already ask suppliers for traceability data. | DACH | 629 food, 259 chemical and 323 plastics enterprises in Germany with 250 or more staff |
| Mid-sized manufacturers and the Mittelstand | In the Mittelstand, owner-managed firms with one or a few plants, the Geschäftsführer is often initiator, budget holder and blocker in one person. There are too many mid-sized manufacturers to work account by account, so signals decide which ones to call this week. | US | 19,806 with 50–249 staff |
| Mid-sized manufacturers and the Mittelstand | In the Mittelstand, owner-managed firms with one or a few plants, the Geschäftsführer is often initiator, budget holder and blocker in one person. There are too many mid-sized manufacturers to work account by account, so signals decide which ones to call this week. | DACH | 14,017 in Germany with 50–249 staff |

*Source: Panelhop research, October 2026; [National Center for Science and Engineering Statistics and U.S. Census Bureau](https://www.ncses.nsf.gov/pubs/nsf25303/assets/data-tables/tables/nsf25303-tab037.pdf); [Eurostat](https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/data/sbs_sc_ovw/A.ENT_NR.C10+C11+C20+C22+C23+C24+C25+C26+C27+C28+C29+C30.GE250+50-249.EU27_2020+DE+AT+CH/?format=SDMX-CSV&startPeriod=2024&endPeriod=2024); [VDMA – Verband Deutscher Maschinen- und Anlagenbau](https://www.vdma.eu/en/); [U.S. Food and Drug Administration](https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods).*

## What do manufacturers ask vendors during a deal?

**Manufacturers ask about scale, the control network and payback.**

Manufacturers ask whether a pilot will scale to every plant, whether anything touches the control network and what the payback is with services included. These questions come from Panelhop’s research into how manufacturers buy and the objections their operations, IT, security and finance leaders raise.

**COO or VP Operations**

- “We have run pilots before and they never scaled. What is different this time?”
- “What happens to output while we cut over, and which shutdown window do you need?”
- “Which plant like ours has rolled this out to every site?”

**CIO or ERP lead**

- “We are in the middle of an ERP migration. Should this wait until cut-over?”
- “How does it integrate with our ERP and identity systems, and who supports it?”
- “Will you still be here, and who will own you next year?”

**Head of Automation or CISO**

- “Does anything touch our control network, and who controls remote access?”
- “Can we see your ISO 27001 or SOC 2 evidence, your IEC 62443 mapping and, for OEM data, a TISAX label?”

**CFO or plant controller**

- “What is the payback with integration and validation services included?”
- “Is this capex or opex, and can we phase it if trade uncertainty freezes capex?”

## How does a manufacturing software deal move from trigger to signature?

**Many deals stall after the evaluation is won.**

A manufacturing software deal moves from a plant trigger through budget approval, requirements, demos, a pilot and security review to a contract timed to the capex calendar. Mid-sized firms often swap the formal RFP for a short RFI and a paid pilot. The durations show the manufacturer’s side and are Panelhop estimates.

**Exhibit 5: Stage by stage: what you do, what the manufacturer does, and what changes at the 5 stages where deals stall.** (Illustrative)

| Stage | Typical time | What you do | What the manufacturer does | Today | With Panelhop | Service |
|---|---|---|---|---|---|---|
| Targeting | 2–8 weeks to frame the problem | Builds the list from parent companies and a broad manufacturing industry filter. | An incident, a rule, an ERP migration, a new plant or a quality escape exposes a gap, and a sponsor baselines OEE, scrap or downtime. | One record per parent, filtered by a broad industry code. Stalls: The parent logo hides the plants. One parent record can hide many plants, each with its own manager and budget, so scoring and outreach miss the site that buys. | A Panel Check tests your target list against closed-won data and drafts tiers that count plants as well as parents. It baselines the share of pipeline from your top tiers. | Panel Check (GTM audit · 2–3 weeks): https://panelhop.com/services#audit |
| Demand generation | – | Gates technical content, runs webinars and exhibits at fairs, then waits for a demo request. | Engineers research in technical publications, peer networks and AI assistants before they contact a supplier. | Content and fair booths wait for a demo request. | Each week, manufacturers with a live, dated signal arrive in your CRM, scored on fit and signal strength. Each comes with the signal that fired and a reviewed brief. Typical signals are a new line, a capex disclosure, a new plant manager or OT security hiring. | Signal Desk (In-market accounts, weekly): https://panelhop.com/services#signal |
| First meeting | – | Books a demo with whoever filled in the form, often an engineer or a plant contact without budget. | Plant and operations leaders take meetings through peers, integrators and reference plants, rarely from cold outreach. | Reps meet whoever filled in the form. | Each account brief maps the roles needed, budget holder included, and the buying group found so far. It suggests a first touch your rep reviews and owns. Verified contacts are added only where each country’s law allows. | Signal Desk (In-market accounts, weekly): https://panelhop.com/services#signal |
| Discovery | 4–12 weeks for budget approval, or a wait for the next budget year | Qualifies the problem with a single champion, usually in operations or IT. | Places the spend in the annual plan or a capital request routed through tiered approvals by cost, plant and asset type. | A single champion carries the deal. Stalls: A champion without budget. The plant manager or CI lead rarely holds budget above local limits, so finance or corporate operations arrive late and reset the timeline. | A qualified-account model scores account fit plus engagement. A role map per tier puts finance, OT engineering, security and, in Germany, the works council on every account. Buying-group coverage is tracked per account. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Evaluation | 12–24 weeks for a formal MES RFP, 6–10 with a paid pilot | Answers the RFI, runs scripted demos and lines up reference calls. | Writes a weighted requirements catalogue (a Lastenheft in Germany), scores a long list down to a shortlist and visits comparable plants. | Finance sees the business case after a preferred vendor is named. | Stage exit criteria require a costed baseline of scrap, downtime or OEE and an engaged finance contact before the shortlist decision. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Pilot | 2–4 weeks for an MES pilot, 4–8 for an ERP proof of concept | Funds a pilot on one line or site to get in. | Tests data, OEE and usability on a single line, often beside existing systems, against agreed KPIs. | A pilot starts on a handshake and runs until someone stops it. Stalls: Pilot purgatory. The pilot passes its technical goals, but nobody agreed scale-up criteria, a multi-site price or an executive owner before it started. | The pilot becomes a stage with entry criteria: a written charter, scale-up criteria, a multi-site price and a named executive owner, agreed before day one. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Security review | 4–12 weeks, often in parallel | Meets the security questionnaire and the architecture review, and in Germany learns that the works council should have been involved before the pilot. | Security, OT engineering, legal and the works council review certificates, data flows, remote access and monitoring limits. | Security questions and the works council arrive after the price. | Required labels, hosting and works council status become qualification fields, with a named security owner on every deal past discovery. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Commercial close | 3–6 weeks to negotiate, plus any wait for capex approval | Negotiates terms, then moves the close date quarter after quarter on a technically won deal. | Submits the capital request, waits for approval or the next budget year and times installation to a shutdown window. | Close dates follow the rep’s quarter. Stalls: Technically won, waiting on capex. Pipeline stages built for short SaaS cycles cannot hold a capital request, a fiscal year-end or a shutdown window, so the forecast calls these deals slipping. | A budget-pending stage holds technically won deals, with each account’s fiscal year-end and shutdown windows as fields. Close dates follow budget milestones, and forecast accuracy is tracked. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Go-live | Timed to the next shutdown or changeover window | Hands over to delivery, often with ERP integration deferred. | Schedules go-live around planned shutdowns and model-year changeovers, while operators decide whether to use the tool or go back to paper. | What sales promised lives in one rep’s head. | A handoff document, built from the deal, records the agreed success measures, the integration scope and the shutdown window. A health score follows adoption. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Plant expansion | – | Leaves expansion to the original rep, who is also chasing new logos. | Each further plant decides on its own P&L unless a group executive or a centre of excellence sets a standard. | Expansion waits for the renewal. Stalls: Every plant is its own P&L. Winning the flagship plant does not commit the rest of the network, and no plant-level whitespace map or group sponsor exists to carry the next site. | 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): https://panelhop.com/services#run |

*Source: Panelhop research, October 2026.*
*Note: Typical times are Panelhop estimates from our research, not measurements.*

## How does Panelhop change the way a manufacturing deal moves?

**Panelhop baselines each stage, then fixes the leaks.**

Panelhop changes how a manufacturing deal moves by starting with a Panel Check (GTM audit) that baselines each stage of your pipeline from your own CRM data. 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. AI drafts the research, we review it and your reps own every first touch; nothing here is a promised result.

What we baseline and report:

1. Plants with an engaged buying group, by tier, against the baseline
2. Days that technically won deals wait for budget approval, against the baseline
3. Share of pilots that start with a charter, scale-up criteria and an executive owner, against the baseline

## Which vendor types sell to manufacturers?

**Read the pipeline for your vendor type.**

These are the vendor types we map in manufacturing, each with its own buying panel, pipeline and triggers.

- [Enterprise manufacturing software: ERP, planning, PLM, QMS and CPQ](https://panelhop.com/industries/manufacturing/enterprise-manufacturing-software): ERP, supply chain planning, PLM, quality and CPQ software for multi-site manufacturers and engineer-to-order machine builders.
- [Plant-floor AI, sensing and connected worker platforms](https://panelhop.com/industries/manufacturing/plant-floor-ai-connected-worker): Machine monitoring, condition sensors, industrial AI and no-code shop-floor apps sold plant by plant, usually starting with a pilot.
- [OT security, compliance and product cybersecurity software](https://panelhop.com/industries/manufacturing/ot-security-product-cybersecurity): OT asset visibility, monitoring and vulnerability management for plants, plus SBOM and CRA reporting tools for machine and device makers.
- [Automation lines and engineered capital equipment](https://panelhop.com/industries/manufacturing/automation-systems-capital-equipment): Custom automation lines, special-purpose machines and turnkey production systems sold to manufacturers as capital projects.

## What do terms like “MES” and “OEE” mean in manufacturing?

**The words your buyers use, defined.**

Plain definitions of the terms that come up when you sell to manufacturers.

- **MES**: Manufacturing execution system: the software that tracks and directs production on the shop floor, from orders and work instructions to quality data and genealogy. It sits between ERP and the machines.
- **OEE**: Overall equipment effectiveness: a line’s availability, performance and quality combined into one score. Plant leaders judge most shop-floor investments by what they do to OEE, scrap and downtime.
- **Capital appropriation request**: The business case a sponsor submits to fund capex. It is routed through tiered approvals by cost, plant and asset type, and the largest requests go to the board.
- **OT**: Operational technology: the PLCs, SCADA, historians and control networks that run production. OT engineering owns them and puts uptime and safety ahead of IT-style change.
- **Pilot purgatory**: A pilot that meets its technical goals but never becomes a multi-site contract. Usually nobody agreed scale-up criteria, a price or an executive owner first.
- **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.
- **Lastenheft (requirements specification)**: The buyer’s requirements specification in a German selection, often with weighted criteria and written with an integrator or consultant. Vendors respond to it in their bid, and the chosen supplier answers with a Pflichtenheft.
- **System integrator**: An engineering firm that designs and implements automation and plant software. Integrators write functional design specifications and often decide which platform reaches the shortlist.
- **TISAX label**: The result of an information security assessment for suppliers that handle automotive OEM data. Automotive OEMs often require a valid label before they award a contract.
- **Mittelstand**: Owner-managed and family-owned mid-sized firms, concentrated in Germany, Austria and Switzerland. The Geschäftsführer is often initiator, budget holder and blocker in one person.

## What do vendors ask about selling to manufacturers?

**Answers before your next manufacturer deal.**

### How long does it take to sell software to a manufacturer?

Selling software to a manufacturer typically takes 4–12 months, by Panelhop’s estimate. By the same estimate, single-plant point solutions take 1.5–9 months, mid-market ERP replacements 3–12 months and enterprise ERP or planning 6–18 months. Aerospace and defence suppliers take an estimated 6–24 months because of export-control and security reviews. Owner-managers decide faster, while capex approval and shutdown windows add time after the evaluation is won.

### Who is in the buying group when a manufacturer buys software?

A manufacturer’s buying group usually has 5–13 people, by Panelhop’s estimate, with more at multi-plant groups and fewer at owner-managed firms. The COO, VP Operations or Geschäftsführer owns the decision. IT, OT engineering, security, quality and finance can each veto it, and in Germany and Austria so can the works council. A system integrator or selection consultant often writes the shortlist without a vote, so engage every veto holder alongside the champion before the shortlist forms.

### How do you get meetings with plant managers at manufacturers?

Meetings with plant managers at manufacturers come through peers, system integrators and reference plants, rarely from cold outreach. Time each approach to a plant signal, such as a new line, a new leader or a dated rule. Plant managers also rarely hold the budget. At most mid-sized manufacturers, budget sits with the VP Operations, the COO or the Geschäftsführer, so engage them too and bring the plant manager in as the champion.

### Is cold email legal when selling to German manufacturers?

Cold email to German manufacturers needs prior express consent: under Section 7 of the German Act against Unfair Competition (UWG), advertising email without it counts as unreasonable harassment. That applies to business recipients too, apart from a narrow exception for existing customers. Vendors selling to German manufacturers and the Mittelstand rely on fairs, partners, introductions and consent-based channels instead, backed by German-language, same-industry references. This answer summarises the rule; take legal advice before relying on it.

### How do you sell software to the German Mittelstand?

Vendors sell software to German Mittelstand manufacturers through the Geschäftsführer. At owner-managed firms with one or a few plants, the Geschäftsführer is often initiator, budget holder and blocker in one person. Cold email needs prior consent under Section 7 of the UWG, so first meetings come from fairs, partners and introductions, and trust rests on German-language, same-industry references. Requirements often arrive as a Lastenheft, and where a plant has a works council, any system able to monitor staff needs the council’s agreement before it is introduced.

### How do you forecast manufacturing deals that wait for capital approval?

Give manufacturing deals that wait for capital approval their own budget-pending stage. Record each manufacturer’s fiscal year-end, whether the capital request has been formally submitted and the shutdown window the installation needs. Tie close dates to those milestones rather than to the rep’s quarter, and report the forecast against a baseline. In Panelhop’s analysis, capital timing is a likely bottleneck at 13 of 20 vendors selling into manufacturing.

### What signals show a manufacturer is about to buy software?

Manufacturers usually buy software after a dated rule, a cyber attack at the company or a close peer, or a company event. The main rules are NIS2 and the Cyber Resilience Act, which mostly open budgets for security and product software. The events are a quality escape, a new plant or line, a new COO, CIO or plant manager, a carve-out or an ERP migration. Topic-based intent data catches few of these signals, so record each one on the account as a dated field with an owner.

### How do you build a target account list of manufacturing plants?

Build a manufacturing target account list at plant level, because for MES, quality, maintenance and OT security tools the buying unit is often one plant. Start from the parents: in 2022 the US had 5,042 manufacturing companies with 250 or more employees, and in 2024 Germany had 4,415 such enterprises. Find each parent’s plants in annual reports, site lists, permits and job posts. Record every plant as its own account under its parent, with its manager, process type and installed systems.

## Sources

**Where the numbers come from.**

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.

1. [National Center for Science and Engineering Statistics and U.S. Census Bureau, Table 37: Companies, by industry and company size: 2022 (2023 Annual Business Survey, NSF 25-303) (2025)](https://www.ncses.nsf.gov/pubs/nsf25303/assets/data-tables/tables/nsf25303-tab037.pdf)
2. [Eurostat, Enterprises by size class, manufacturing (sbs\_sc\_ovw): EU27, Germany and Austria, 2024 (2026)](https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/data/sbs_sc_ovw/A.ENT_NR.C.GE250+50-249+TOTAL.EU27_2020+DE+AT/?format=SDMX-CSV&startPeriod=2024&endPeriod=2024)
3. [Eurostat, Enterprises by size class and NACE division (sbs\_sc\_ovw): EU27, Germany, Austria and Switzerland, 2024 (2026)](https://ec.europa.eu/eurostat/api/dissemination/sdmx/2.1/data/sbs_sc_ovw/A.ENT_NR.C10+C11+C20+C22+C23+C24+C25+C26+C27+C28+C29+C30.GE250+50-249.EU27_2020+DE+AT+CH/?format=SDMX-CSV&startPeriod=2024&endPeriod=2024)
4. [Department for Business and Trade, Business population estimates for the UK and regions 2025: statistical release (2025)](https://www.gov.uk/government/statistics/business-population-estimates-2025/business-population-estimates-for-the-uk-and-regions-2025-statistical-release)
5. [BSI – Bundesamt für Sicherheit in der Informationstechnik, NIS-2 in Zahlen (2026)](https://www.bsi.bund.de/DE/Themen/Regulierte-Wirtschaft/NIS-2-regulierte-Unternehmen/NIS-2-in-Zahlen/nis-2-in-zahlen.html)
6. [VDMA – Verband Deutscher Maschinen- und Anlagenbau, VDMA (2026)](https://www.vdma.eu/en/)
7. [European Commission, Cyber Resilience Act (2026)](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act)
8. [European Commission, DG Internal Market, Industry, Entrepreneurship and SMEs, Machinery (2026)](https://single-market-economy.ec.europa.eu/sectors/mechanical-engineering/machinery_en)
9. [Bundesministerium der Justiz, Section 87 BetrVG (co-determination rights) (2026)](https://www.gesetze-im-internet.de/betrvg/__87.html)
10. [Bundesministerium der Justiz (gesetze-im-internet.de), Gesetz gegen den unlauteren Wettbewerb, Section 7: Unzumutbare Belästigungen (2026)](https://www.gesetze-im-internet.de/uwg_2004/__7.html)
11. [Bundesministerium der Justiz (gesetze-im-internet.de), BSI-Gesetz (BSIG), Section 28: Besonders wichtige Einrichtungen und wichtige Einrichtungen (2026)](https://www.gesetze-im-internet.de/bsig_2025/__28.html)
12. [BSI (Bundesamt für Sicherheit in der Informationstechnik), Cybersicherheitsrecht: NIS-2-Umsetzungsgesetz ab morgen in Kraft (2025)](https://www.bsi.bund.de/DE/Service-Navi/Presse/Pressemitteilungen/Presse2025/251205_NIS-2-Umsetzungsgesetz_in_Kraft.html)
13. [U.S. Department of War, Under Secretary of War for Acquisition and Sustainment, Implementing Department of War Chief Information Officer’s Suspension of the Advancement to Cybersecurity Maturity Model Certification Phase 2 Requirements (2026)](https://dowcio.war.gov/Portals/0/Documents/Library/ImplementingSuspensionCMMC-PhaseII.pdf)
14. [U.S. Food and Drug Administration, FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods (2026)](https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods)
- Panelhop research, October 2026: our analysis of the vendors, buying panels, pipelines and triggers in manufacturing, from public sources. Vendor names are not published.

## Next step

Find where your pipeline to manufacturers leaks.

[Book a GTM audit](https://panelhop.com/book) · [What the Panel Check covers](https://panelhop.com/services#audit)