Lesson 3: Scaling Across Plants
Winning your first deal with a Fortune 500 manufacturer feels like breaking through. You’ve navigated a complex sales cycle, secured a budget, and deployed at a flagship plant. If the natural assumption is that now you’ll rapidly expand across their 20+ other facilities, reality soon catches up.
Why? Because in manufacturing, each plant operates as a quasi-independent business unit with its own P&L, operations leadership, and technology priorities. Budget authority is localised. Technology stacks are fragmented.
The plant manager in Stuttgart has little incentive to adopt a solution championed by her counterpart in Lyon.
This decentralisation means your “enterprise deal” is actually 15–30 individual sales cycles wearing a trench coat.
The solution requires a pincer movement: simultaneously advancing from the plant floor up and the C-suite down to win locally, and then ramping up FOMO between plants:
- Win Locally with Change Management — Prove undeniable value at the plant level
- Unlock Executive Alignment — Build top-down momentum and resourcing
- Drive Inter-Plant FOMO for Scale — Create competitive dynamics between facilities
In some cases, the right corporate venture (CVC) arm can fast-track executive alignment and create instant credibility across plants, though this path requires careful evaluation as we will explore.
In this chapter, top industrial tech founders reveal how they transformed a single-site breakthrough into company-wide adoption.
1) Win Locally with Change Management
You’ve won over your buyer — the plant manager or operations leader who signed the contract. But your journey doesn’t end there. Now you need to win over the people who will actually use your product daily. Success at a new plant hinges on turning shopfloor users into advocates who drive adoption across shifts and teams.
Here are key goals to think about when you’re planning your first plant kick-off with the team on the ground.
Identify Your Shopfloor Ambassadors
Identify operators, technicians, or line leads who are naturally curious, respected by their peers, and open to trying new approaches. These aren’t your executive sponsors, they’re the people in steel-toed boots who will validate whether your tool actually makes their job easier. Work with your buyer to identify these individuals, ask who the go-to problem solvers are, who trains new hires, or who others turn to when something breaks.
Then, get them using the product ASAP. When a Line 3 operator discovers your tool helped them diagnose a recurring issue faster, they’ll tell their colleagues. When a quality technician sees it eliminates 30 minutes of manual data entry from their shift, they become your evangelist. This grassroots credibility is what carries adoption forward when you’re no longer in the building.
Enable the Improvement Teams
Process engineers, lean leads, and CI teams are the bridge between your insights and operational change. They’re accountable for driving measurable improvement, and your tool needs to accelerate their existing workflow — not create a parallel one.
Run hands-on, outcomes-oriented workshops with these teams. Don’t just show them dashboards; work through real problems together. Help the CI lead use your analytics to identify the root cause of a quality issue they’ve been chasing. Show the process engineer how to turn an insight into an experiment they can run next week. When these teams see your tool as a force multiplier for their mandate, they’ll embed it into daily improvement routines.
Address the Job Security Question Head-On
Resistance to automation rarely stems from the technology itself; it stems from fear about what it means for people’s livelihoods. Don’t let concern fester.
In your plant kickoff, be explicit: explain what the tool automates (tedious data gathering, manual report generation) and what it doesn’t replace (human judgment, problem-solving, process knowledge). Frame it clearly — this tool eliminates the work nobody wants to do so teams can focus on the work that actually matters.
When operators understand that automation is making their job better rather than making them obsolete, resistance turns into advocacy. And those advocates become the foundation for rolling out to the next plant.
→ FOUNDER TIP: Build change management as an integral part of any rollout. Adoption never happens by accident, and the more you help users succeed, the faster your product will take root. As part of this, celebrating small early wins — whether it’s reduced rework, lower energy use, or smoother handovers — creates the momentum that larger organisations need to justify expanding the solution further.
“When people saw it made their job easier — not obsolete — they leaned in…Adoption sticks when teams feel ownership — not when change is imposed.” Alexander Lagreze, Head of Manufacturing Engineering & Planning, IWC Schaffhausen
2) Unlock Executive Alignment
Plant-level traction gets you started, but enterprise-wide rollout requires the central organisation to put strategic and operational weight behind you. This becomes critical for solutions that touch IT infrastructure, require data integration, or depend on cross-plant standardisation.
Executive alignment delivers three things that local wins alone cannot: central budget that removes plant-by-plant funding friction, technical infrastructure that makes deployment repeatable, and internal pressure that turns your solution from “nice to have” into a corporate priority.
Build the Technical Foundation with Central IT
For any solution requiring data integration - connecting to MES, ERP, historians, or quality systems - central IT becomes your gateway to scale. Approached poorly, IT becomes a blocker. Approached well, they become your deployment engine.
→ FOUNDER TIP: Managing Central IT Teams. Treat IT engagement with the same intentionality you bring to end users. The most common mistake is showing up with vague requests that force IT to figure out the details -which defaults to “no”.
Instead, eliminate ambiguity: define exactly what you need from them, why it matters operationally, and realistic timelines. Provide thorough playbooks and technical documentation - essentially an enablement toolkit tailored for IT teams. When requirements are clear and comprehensive, IT shifts from cautious gatekeepers to confident partners who can champion your integration internally.
Secure Executive Sponsorship for Rollout Momentum
Technical infrastructure alone doesn’t drive adoption — you need a senior leader creating organisational momentum. This means finding a VP of Operations, Chief Digital Officer, or Head of Manufacturing who sees your solution as strategic, not just tactical.
The right executive sponsor does three things. First, they allocate central budget so individual plants aren’t hunting for local funding - removing a major friction point. Second, they create visibility by tracking deployment progress across sites and making adoption part of plant performance conversations. Third, they provide air cover when individual plant managers resist change or drag their feet.
Example: Makersite’s partnership with Siemens demonstrates what executive alignment delivers in practice. By securing SVP-level sponsorship early and tying their solution directly to Siemens’ sales targets, an executive-level concern, they transformed the relationship from vendor-customer to strategic partnership.
Building this relationship requires framing your solution around corporate-level goals, not individual plant pain points. Show how standardising on your platform across 20 plants delivers strategic value: consolidated data for enterprise visibility, benchmarking across sites, or measurable impact on corporate sustainability commitments. Make the executive look good to their board, and they’ll make adoption happen at the plant level.
3) Drive Inter-Plant FOMO for Scale
Plants rarely communicate directly with one another, but they absolutely notice when a peer site is winning. A breakthrough at one location can sit unnoticed — or it can become the spark that ignites adoption across the network. The difference comes down to whether founders deliberately amplify success in ways that create productive pressure.
Make Success Impossible to Ignore
Your job is to ensure that wins at Plant A become visible to Plant B’s leadership. This rarely happens organically in decentralised organisations, so you need to work the channels that do reach across sites:
Work with your executive sponsor from Section 2 to showcase results in corporate operations reviews or monthly performance calls. When the VP of Manufacturing highlights that Plant A improved OEE by 12% using your solution, every other plant manager on that call takes notice.
HOW TO: Create lightweight internal case studies — one-pagers with before/after metrics, quotes from the plant manager, and clear ROI — that HQ can distribute. The goal isn’t marketing collateral; it’s giving other plants proof that this works in their environment, with their constraints.
Position your champion as the hero. Use the exact language they use when describing the impact. When Plant B hears from Plant A’s operations manager — someone they know, whose judgment they trust — that “this tool helped us finally solve our changeover time problem” — it carries infinitely more weight than anything you could say.
Create Productive Competition
The most powerful FOMO comes from peer comparison. If possible, work with your executive sponsor to create visibility into plant-by-plant performance on the metrics your solution improves. When plant managers see a regional dashboard showing that three of their peer sites are outperforming them on downtime or quality, the competitive instinct kicks in.
Facilitate peer-to-peer sharing. Offer to set up calls where your champion at Plant A walks Plant B’s team through their deployment and results. These conversations answer the unspoken question every plant manager has: “Will this actually work for us?” Hearing it from a peer makes it real.
Leverage Network Effects
By the time you reach plants three, four, and five within an organisation, the dynamics shift in your favour. You have internal proof points, established integration patterns, and advocates scattered across the network. Sales cycles compress because you’re no longer fighting scepticism — you’re responding to demand from plant managers who’ve already heard about your results from their peers.
The goal is simple: make neighbouring plants ask, “Why do they get these results and we don’t?” Once that question takes hold, you’ve turned plant-level traction into enterprise momentum.
Potential Bonus: Accelerate Through Strategic CVC Partnerships
Some corporate venture arms can fast-track the executive alignment and inter-plant momentum you’d otherwise spend years building. The key word is some.
The strongest manufacturing CVCs don’t just provide capital, they offer executive-level sponsorship that prioritises your rollout across plants, connecting you directly to the business units that control implementation. This backing can turn what would be 15 individual plant sales cycles into a coordinated enterprise deployment with air cover from the top.
However, not all CVCs deliver this. Before considering a corporate venture relationship as your scaling strategy, clarify what you’re actually getting:
- Investment thesis and operational leverage: Are they strategically investing to deploy your solution internally, or purely seeking financial returns? Ask for specific examples of portfolio companies they’ve helped scale within their parent organisation.
- Business unit ownership: Which division owns the relationship post-investment? Do they have the authority to drive implementation across plants, or are you still starting from scratch with each facility?
- PoC requirements: Do they require proof-of-concept deployments before investing? Understanding this timeline helps you plan resources accordingly.
The right CVC partnership can collapse your path to executive sponsorship and create built-in FOMO — when corporate venture backs you, plant managers pay attention. But approach selectively: some CVCs promise influence they don’t actually have. Validate their track record of turning portfolio investments into internal deployments before betting your go-to-market strategy on the relationship.
What Comes Next
The network effects you’ve built — internal champions, executive sponsorship, and inter-plant competition — fundamentally change your scaling dynamics. Plants four through ten move faster than plants one through three because you’re responding to internal demand rather than fighting scepticism.
But all of this momentum depends on one thing: an undeniable proof point at your first plant. Without concrete, measurable results that plant managers can’t ignore, the entire flywheel never starts spinning. Next, we turn to how to run an effective pilot that creates that foundation. JUMP IN!
You are reading our Manufacturing Software GTM Founder Guide for early-stage b2b manufacturing Saas founders. Read our intro here. With thanks to Sid Khullar (Aris Machina), Maximilian von Düring (AiSight), Alex Grots (Proglove), Yohann Rousselet (BAC), Sabine Erlinghagen (Siemens Grid), Matthias auf der Mauer (Juna.ai), Thibauld Martin (Altrove), Omar Fergani and Josh Vernon (Carbon Re).
Authors: Jess Burley, Kim Dang, Christoph Gras, Sam Baker.
About us
Planet A is an early-stage European tech VC backing founders solving the world’s greatest systemic challenges. We use rigorous scientific impact assessments to identify solutions the world cannot afford to ignore. Investments include Carbon Re, Aris Machina, AUAR, INERATEC, Makersite, C1, HIVED, traceless materials and 44.01. Follow us on LinkedIn!
