AI in Sales: Factory AI Vendor Comparison
KI & Automatisierung · 23. Oktober 2026 · Joseph Flesh
AI in sales meets factory AI: Compare Siemens/NVIDIA, Microsoft/Körber, KUKA, and Amplifa – and evaluate your roadmap now.
On October 19, 2026, Dow Jones reported via Morningstar that Siemens and NVIDIA unveiled new AI applications for autonomous factory planning at the electronics manufacturing facility in Erlangen. One day later, CNBC reported on NVIDIA's European investment package of nearly 10 billion US dollars and on Friedrich Merz's appeal to German companies to adopt AI faster. This is not background noise for production managers. It is a signal to sales, COOs, and executive management: if production ramp-ups are to become up to 40 percent shorter, AI in sales can no longer be treated as a toy for email subject lines.
Siemens cites up to 85 percent less engineering effort and up to 20 percent lower planning costs through AI agents for the virtual ramp-up of new printed circuit board assemblies. Source: Morningstar/Dow Jones from October 19, 2026, supplemented by CNBC from October 20, 2026. I do not take these figures as an independent benchmark. I take them as a market statement. Anyone selling machinery, assemblies, electronics, or automation in the DACH region will face a new question from customers over the next 24 months: If your factory can plan with digital twins, why is your sales department still an Excel spreadsheet tied to a telephone system?
Why This Comparison Is Necessary for AI in Sales
The discussion around industrial AI is often kept neatly separated from sales. On the left, the factory: digital twins, simulation, robotics, MES, Siemens Xcelerator, NVIDIA Omniverse. On the right, sales: CRM, sequences, trade fairs, LinkedIn, quote follow-ups. That was convenient. It was also wrong. For a manufacturer with 180 employees in East Westphalia, factory capabilities directly dictate sales strategy. If a company can release product variants faster through virtual commissioning, sales must prioritize different accounts, make different delivery commitments, and enter projects earlier. Otherwise, the production advantage evaporates in the inbox of a procurement officer at Schaeffler, Phoenix Contact, or Webasto.
I am not writing this comparison as an analyst. With my team at Amplifa, I build systems that connect sales data, market triggers, account prioritization, and outreach in mid-market B2B organizations. I see where AI truly takes hold. And where it is pure theater. Well, almost. Sometimes theater is useful if it unlocks budgets. But by the third pilot project without any pipeline effect, the mood sours. A CSO from Stuttgart told me in September 2026 after a board meeting: "We have a digital twin for the line, but no twin for our pipeline." That hit home. Not because of the phrasing. Because of the gap.
That is why I am comparing four approaches that have become particularly relevant following Erlangen: Siemens/NVIDIA as integrated factory AI, Microsoft/Körber as cloud and process AI in regulated environments, KUKA/NVIDIA as a robotics and vision track, and Amplifa as a sales AI layer for pipeline generation, lead generation, and account management. Yes, Amplifa is included in this comparison. I am CTO and Co-Founder. I am not pretending to be neutral. But I lay out the criteria transparently, and I also state where we are not the right solution.
Evaluation Criteria for AI in Sales and Factory AI
For a managing director of a manufacturing company with 50 to 500 employees, the wrong question is: "Which AI tool is the most modern?" The better question is: "Which bottleneck will cost us margin, delivery capability, or pipeline in 2027?" At Trumpf, DMG Mori, or Festo, this question is handled differently organizationally than at a supplier with 120 people and two key account managers. But the pattern is similar. Bottlenecks shift. First, there is a lack of leads. Then, a lack of solid quotes. Then, planning gets blocked. Then, materials are missing. Then, capacity is available, but there are no orders. A beautiful chaos.
I evaluate the candidates according to seven criteria:
- Business leverage: Does the solution impact production costs, time-to-market, delivery reliability, pipeline generation, or quoting speed?
- Data foundation: Does the system require clean CAD, MES, ERP, CRM, or web data, and how demanding is the integration effort?
- Architecture: Does the solution operate with digital twins, AI agents, LLMs, computer vision, classical optimizers, or a hybrid approach?
- Feasibility in the Mittelstand: Can a company with 50 to 500 employees realistically get started without spending 18 months on master data archaeology first?
- Sales integration: Does the solution tangibly help sales with target accounts, timing, quoting, forecasting, or existing account development?
- Cost model: Are costs project-driven, usage-based, license-based, or dependent on infrastructure such as GPUs and integration partners?
- Risk: Where do lock-in, data privacy issues, misguided automation, or operational dependencies arise?
A technical detail that is often underestimated: context windows and token costs are far more important in sales than in marketing hype. A sales agent that only sees the last three emails and a CRM note hallucinates politely. An agent that can connect quote revisions, bills of materials, customer complaints, site visit reports, website signals, and corporate group structures within a retrieval system becomes genuinely useful. For LLM APIs, publicly listed prices in 2024 for high-performance models ranged from low single digits to double-digit US dollars per million input or output tokens; by 2026, packages vary more widely, and many enterprise contracts are not public. My rule: model costs are rarely the primary expense. Poor data flows are more expensive. Always.
"That doesn't work for us," Andrea, Head of Sales at a components manufacturer in Bielefeld, told me. Two weeks later, it turned out: it didn't work because 41 percent of active customers in the CRM had no industry specified.
— Joseph Flesh, CTO & Co-Founder, Amplifa
Candidate 1: Siemens/NVIDIA – Industrial AI with Digital Twins
In Erlangen, Siemens and NVIDIA rely on the combination of digital twins, industrial AI agents, and simulation. The core is not "a chatbot for the shop floor." The core is a virtual representation of production systems that allows planners and engineers to test how new PCB assemblies ramp up, which line gets blocked, where materials are missing, and which sequence works better—all before physical interventions. According to Morningstar/Dow Jones from October 19, 2026, Siemens reports up to 85 percent less engineering effort during virtual production ramp-ups and up to 40 percent shorter time-to-market. These figures are company-reported. Nonetheless: if even half of that materializes in a real mid-sized setup, it fundamentally changes the sales promise.
The strength of this approach lies in its depth. Siemens Xcelerator, automation hardware, PLM, simulation, production planning, and NVIDIA Omniverse fit together strategically. For an electronics manufacturer in Bavaria or a machinery builder handling high-mix production in Baden-Württemberg, this can mean: digitally validating new product variants, mitigating ramp-up risk, and calculating delivery windows earlier. For sales, this means no longer relying on "we need to check with production planning" as the default answer. Instead, it provides reliable delivery commitments during the quoting process. That may sound dry, but it sells. Especially to customers like Brose, ZF, or Kärcher, where project milestones and delivery penalties are not negotiated on gut feeling.
The weakness is just as clear: the barrier to entry. If you don't have a reliable data model of your production today, an NVIDIA keynote won't magically give you an autonomous planner. Digital twins require geometry, process data, business rules, historical cycle times, variant logic, and interfaces. Plus humans who can challenge the system. A COO named Markus from Augsburg, running a company of 220 employees, told me in October 2026: "I can't explain to my shop floor why an agent is doing the planning now when we don't even properly log our setup times." Exactly. That's not entirely true—you can still start. But not with the grand Erlangen vision on the wall and an empty MES underneath.
What Siemens/NVIDIA Really Means for Sales
The sales leverage does not stem from rendering the digital twin. It emerges at the interface between production capability and market outreach. When a manufacturer can industrialize new assemblies faster, sales needs to know which existing accounts are open to variants, redesigns, or replacing legacy platforms right now. This is AI in sales acting as a translation layer. Example: an electronics supplier saves four weeks on the project schedule thanks to virtual ramp-up. Without account intelligence, this advantage ends up buried in a sales presentation worded almost identically to 19 other suppliers. With account intelligence, it transforms into a list of 37 target accounts with ongoing product changes, competitor supply issues, new engineering job postings, and relevant procurement contacts. That is the difference between technology and revenue.
I would be very cautious with mid-sized companies looking to buy Siemens/NVIDIA simply because the board needs a flagship project. If production, engineering, and sales do not jointly define which product line, which target market, and which sales motion should benefit, it becomes an expensive demo. The smell of fresh control cabinet paint in a pilot cell does not replace go-to-market logic. Put bluntly: anyone introducing factory AI in 2026 while still sorting their pipeline based on trade fair business cards is burning velocity.
Candidate 2: Microsoft/Körber – Cloud AI for Processes and Regulated Production
In 2026, Körber announced an AI focus for pharma manufacturing with Microsoft Azure. That is a different starting point than Siemens/NVIDIA. Less factory metaverse, more process data, compliance, cloud architecture, and industrial workflows. For regulated industries such as pharmaceuticals, medical technology, or food production, this is crucial because the hurdle is not just technical. It is validation, audit trails, data access, role-based permissions, and GxP compliance. A managing director from Basel, let's call him Lukas, put it dryly in July 2026: "For us, the AI isn't the problem; it's the auditor who wants to know why it recommended something."
The strength of Microsoft/Körber lies in its interoperability. Many mid-sized manufacturers already use Microsoft 365, Teams, Azure Active Directory, Power BI, or Dynamics. It is not glamorous; it is practical. When AI agents are embedded into existing identities, access controls, data rooms, and reporting structures, organizational friction decreases. For sales teams, this matters because many sales processes already live in Microsoft environments: proposals as Word documents, cost calculations in Excel, appointments in Outlook, customer notes in Teams. Messy? Yes. Reality? Even more so.
The weakness: cloud process AI does not automatically resolve challenges in the physical world. If you want to optimize line layouts, robotics, cycle times, and real material flows, you need more than Azure workflows. Furthermore, companies often underestimate the costs of data cleansing, governance, and change management. With LLM-based assistants, a second factor emerges: context. A 128k or 200k token window sounds massive, but it fills up fast when functional specifications, meeting notes, quoting histories, and technical drawings are dumped in unfiltered. Good architecture uses retrieval, metadata, permission checks, and summarization. Poor architecture relies on hope.
Microsoft/Körber from a Sales Perspective
For sales leaders, Microsoft/Körber becomes compelling when sales operations are tightly coupled with regulated processes: technical sign-offs, quality agreements, engineering change orders, and documentation mandates. At a medical device supplier in Tuttlingen, an AI assistant capable of surfacing legacy validation files, customer approvals, and approved quote modules can save more pipeline than a fancy lead scoring tool. Why? Because deals rarely fall apart at the first discovery call; they collapse at the sixth technical inquiry. "Can you prove this modification won't require re-qualification?" If sales takes three days searching internally, the momentum is gone.
My frank take: many mid-market sales organizations need less generative magic and more access to what they already know. Microsoft-centric architectures can excel here, provided they are not scattered like Copilot confetti. A Copilot that writes meeting summaries is nice. A system that analyzes 900 historical quotes to determine which assemblies won deals at Phoenix Contact in similar account setups—and which objections arose—is revenue infrastructure.
Candidate 3: KUKA/NVIDIA – Physical AI for Robotics and Vision
At NVIDIA GTC Berlin in October 2026, KUKA demonstrated AI-powered vision based on NVIDIA's Jetson Orin platform alongside software that integrates robot programming with 3D manufacturing simulation. This is the pragmatic sibling of the massive digital twin: robots see better, programs originate closer to simulation, and commissioning becomes more predictable. For facilities dealing with welding, handling, packaging, assembly, or quality inspection, this is tangible. You can sometimes even hear it: less stop-and-go at the cell, less frantic clicking on the teach pendant, and fewer calls for "get the system integrator" right before a shift change. KUKA is not abstract theory in the DACH region. Many shop floors are more familiar with those orange robotic arms than with their own CRM hygiene.
The strength is machine proximity. When computer vision lowers scrap rates or enables flexible variant handling, capacity is unlocked. The weakness: sales only benefits indirectly if nobody translates these newly acquired capabilities into specific market segments. I see this frequently in automation projects. After six months, the cell runs more stably, yet the website still reads: "Your reliable partner for custom engineering solutions." That won't do. If the KUKA cell now makes low-volume production economical, sales must proactively target accounts struggling with variant complexity. Otherwise, automation merely serves as cost defense.
Candidate 4: Amplifa – AI in Sales as a Pipeline Operating System
Amplifa does not operate at the robot cell. We operate where production capacity must be converted into revenue: identifying target accounts, detecting buying signals, setting account priorities, preparing tailored outreach, enriching CRM data, managing follow-ups, and making sales playbooks measurable. For manufacturing companies, this means concretely: if your new line makes smaller batches profitable, the system does not just find generic "leads," but companies experiencing relevant product transitions, capital expenditure announcements, hiring surges, supply chain disruptions, standard revisions, or expansion signals. That is not magic. It is data engineering plus models plus sales discipline.
From our implementations, we know: across manufacturing and industrial clients with 80 to 420 employees, we almost always see the same pattern within the first 90 days. Between 18 and 35 percent of existing CRM accounts are misclassified or categorized too broadly—such as "mechanical engineering" instead of "custom machinery for battery handling." In accounts with over 5,000 historical contacts, we consistently discover 12 to 22 percent duplicates or outdated roles. And the biggest lever is rarely more cold outreach. It lies in reprioritizing 40 to 120 accounts because an authentic buying signal is present. One customer in the Nuremberg area tripled their qualified discovery meetings within nine months without hiring a single additional sales rep. Not because the model wrote with exceptional charm. Because it made timing visible.
Our limitation? We do not plan production lines. We do not simulate robot cells. If you need to solve setup times, PLC code, or layout variants, you need Siemens, KUKA, an integrator, or in-house OT expertise. Amplifa becomes powerful when a technical capability, a market segment, and a sales process must be aligned. Especially following factory AI projects. Because that is often when a dangerous phrase surfaces: "Now we just need to sell it." That sentence comes too late.
Amplifa Product: AI in Sales for Industrial Companies Account intelligence, lead generation, and sales automation for mid-market B2B teams across the DACH region.
Comprehensive Comparison: Vendors, Architecture, and Sales Leverage
The following table is deliberately unromanticized. No vendor wins across the board. Anyone claiming otherwise is selling slide decks. An electronics manufacturer near Erlangen with high variant complexity operates under different priorities than a contract manufacturer in Styria or a medical tech supplier in Tuttlingen. Still, structure helps, because budget discussions otherwise get bogged down in brand names: Siemens, NVIDIA, Microsoft, KUKA, Agile Robots. Names impress. Bottlenecks pay the bills.
| Candidate | Technical Core | Strength | Weakness | Best Sales Leverage |
|---|---|---|---|---|
| Siemens/NVIDIA | Digital Twin, Industrial AI Agents, Simulation, Omniverse connectivity | Virtual ramp-up, production planning, time-to-market; Siemens reports up to 85% less engineering effort | High data and integration requirements, significant OT/IT expertise required | Earlier and more reliable delivery commitments for complex products |
| Microsoft/Körber | Azure, Process AI, data platform, regulated workflows | Seamless embedding into Microsoft environments and compliance workflows | Limited physical simulation and direct assembly line optimization | Accelerated proposal and approval cycles for documentation-heavy deals |
| KUKA/NVIDIA | Robotics, Vision AI, Jetson Orin, 3D simulation | Shop-floor automation, quality assurance, variant handling | Sales benefits remain indirect without dedicated segmentation | Targeted selling of newly acquired production capabilities to niche markets |
| Agile Robots | AI robotics for manufacturing, logistics, healthcare; highlighted in NVIDIA investments in 2026 | More flexible robotics and delicate gripping/handling capabilities | Maturity level and integration complexity heavily depend on the specific use case | New automation offerings or capacity guarantees in customer communications |
| Amplifa | Sales AI, Account Intelligence, LLM/Retrieval, CRM enrichment, workflow automation | Translates market and production triggers into pipeline generation | Does not resolve shop floor scheduling or robotic engineering challenges | More qualified target accounts, superior timing, cleaner follow-up cycles |
Pricing Comparison: What Does AI Cost in Sales and Manufacturing?
Pricing comparisons in industrial AI are difficult because few providers publish clear packages. Siemens and KUKA projects depend on facility locations, integration scope, existing infrastructure, licenses, hardware, and integration partners. Microsoft Azure costs depend on data volume, usage, model choice, security layers, and support services. Sales AI solutions depend on user seats, account volumes, data sources, automation levels, and integrations. Anyone expecting a simple price list will usually only find one with tools that barely scratch the surface of the underlying problem. Bitter, but true.
When evaluating LLM costs in projects, I make a distinction that many find helpful: model consumption, data preparation, workflow integration, and human oversight. Tokens are visible and therefore widely debated. The broken handoffs between CRM, ERP, website, email, and proposal folders are invisible and cost far more. A 200k context window won't save a sales process if the most critical site report is stored as a scanned PDF on SharePoint named "finalfinalnew".
| Candidate | Typical Cost Structure | Mid-Market Entry Point | Hidden Costs | When ROI Becomes Plausible |
|---|---|---|---|---|
| Siemens/NVIDIA | Enterprise licenses, project integration, simulation, OT/IT interfacing, partial GPU infrastructure | Selective adoption: product family, line, or ramp-up project rather than entire plant | Data modeling, process mapping, engineering hours, training | When ramp-up times, scrap rates, or engineering overhead decrease measurably |
| Microsoft/Körber | Cloud consumption, platform licensing, consulting, and validation costs | Strong when Microsoft infrastructure and process data are already in place | Governance, permissions, data quality, compliance documentation | When sign-offs, document retrieval, or operational decisions accelerate |
| KUKA/NVIDIA | Robotics hardware, vision modules, software licenses, systems integrator fees | Strong for defined cells with a clearly quantified operational challenge | Commissioning, safety concepts, training, regular maintenance | When cycle times, scrap rates, operator workload, or variant agility improve |
| Agile Robots | Robotic solution, software licenses, systems integration, support agreements | Use-case dependent, often compelling for flexible handling applications | End-effectors, environmental adaptation, process stability | When manual bottlenecks or unstable handling processes prove costly |
| Amplifa | SaaS subscriptions, data integration, onboarding, user and account volumes | Very strong when CRM, target segments, and clear sales ownership exist | CRM cleanup, playbook development, internal team responsiveness | When qualified meetings, proposal opportunities, or win-back rates increase |
What Does This Mean for COOs and Managing Directors?
COOs naturally tend to look for AI where they can see physical machines. That is understandable. A robotic cell is more tangible than a better-prioritized target account. You can stand next to it, clock the cycle time, and smell warm plastic and cooling lubricants on the shop floor. A sales pipeline smells like nothing. That doesn't make it any less concrete. If sales closes the wrong projects, the best factory runs in the wrong direction.
I consider pure inbound strategies in the industrial space increasingly risky from 2026 onward. Put bluntly: if you are a mid-sized manufacturer merely waiting for an OEM, Tier-1, or machine builder to submit a web form, you have already surrendered your margin. High-value projects originate earlier: during platform changes, supplier failures, facility expansions, regulatory shifts, or the formation of new engineering teams. These signals are public, semi-public, or hidden in internal data. AI in sales is not a text generator in this context. It is radar.
Siemens/NVIDIA shows where manufacturing is heading: simulation before retooling, agents before manual scheduling, digital models before gut feeling. Sales must make the exact same leap. Not by automating blindly. Not by replacing the people who nurture customer relationships. But the legacy routine—trade fair, Excel list, three follow-ups, and hope—will lose against systems that connect market dynamics with internal capabilities. A sales director named Jens from Heilbronn told me in August 2026: "We've gotten technically stronger, but our customers don't find out fast enough." That is a sales problem. Not a marketing problem.
How to Get Started Without the AI Theater
I rarely recommend grand corporate rollouts. Not because I think small. But because large-scale overhauls in mid-market organizations often collapse due to three things: data access, accountability, and a lack of patience for the unglamorous 20 percent. You cannot properly leverage a digital twin if no one takes cycle-time deviations seriously. You cannot properly leverage sales AI if no one decides which accounts to stop chasing. AI forces decisions. That is precisely why it feels uncomfortable.
- Identify the core bottleneck: Is your biggest hurdle ramp-up, scheduling, quality, quote turnaround, lead generation, or forecasting? Choose only one primary bottleneck. Not five.
- Map your data landscape: Which systems house the relevant facts—ERP, MES, PLM, CRM, SharePoint, email, website, commercial registers, job postings, press releases?
- Establish concrete metrics: For example, engineering hours per new assembly, planning costs per week, qualified discovery calls per month, quote turnaround time, or account win-back rates.
- Keep the pilot scope lean: One product line, one target segment, one sales team, one line. Avoid enterprise-scale programs dressed up for the Mittelstand.
- Define human oversight: Who is authorized to approve, override, or reject AI recommendations? In sales: who decides whether an account gets contacted?
- Enforce sales alignment: Every factory AI initiative must answer which specific customer accounts will be approached differently as a result.
Amplifa Sales Audit Assess where your sales operations lose pipeline: data quality, target accounts, follow-up cadence, automation, and account prioritization.
FAQ: Does Factory AI Replace Building a Sales Organization?
No. Factory AI does not replace building sales operations. It merely compounds the damage of poor sales operations. If Siemens/NVIDIA-style systems can truly compress time-to-market by up to 40 percent, a new pace is set across the market. Someone must translate that velocity into target accounts, proposals, and commercial agreements. Otherwise, you end up with a faster factory feeding into the same sluggish demand channel.
FAQ: Does Every Mid-Sized Manufacturer Need a Digital Twin?
No. Honestly? I cannot answer that for every individual business. But I know this: not everyone will need a full digital twin of their entire plant in 2027. Many first need a twin of their specific bottleneck. For an electronics manufacturer, that might be ramping up a new assembly. For a contract manufacturer, proposal cost calculation. For an automation provider, the robotic work cell. For a sales team, the account landscape. Trying to model everything usually results in modeling straight past revenue.
FAQ: Is AI in Sales Just Cold Emailing with Polished Copy?
No. Cold email is merely a channel. AI in sales is an operating system for decision-making before, during, and after outreach. Which company fits right now? Why now? What technical capability is relevant? Who in the buying center is feeling the pressure? Which case study applies? What objections arose with similar accounts? Which line item is stalling the quote? If a software tool only writes emails, it is not a sales AI platform. It is a typewriter with an API.
Personal Recommendation: Sequence Beats Tool Selection
If I were the managing director of a manufacturing firm with 150 employees, I wouldn't start by debating whether Siemens/NVIDIA, Microsoft/Körber, KUKA, or Amplifa is "the best" option. I would first determine whether our growth constraint sits inside or outside. Inside means: we could sell, but production, scheduling, quality, or engineering are holding us back. In that case, look first at Siemens/NVIDIA, KUKA/NVIDIA, or a Microsoft-aligned process architecture. Outside means: we could deliver, but the right customers don't notice, arrive too late, or are never systematically worked. In that case, AI in sales takes priority.
My second recommendation is less comfortable: connect these initiatives earlier. When the COO plans a new flexible manufacturing cell, sales must simultaneously define which customer segments will be targeted with it. When sales plans to penetrate a new vertical, production must specify which variants remain profitable and which merely generate operational noise. With a custom machinery client in spring 2026, we discovered the issue was not the volume of leads, but an imprecise technical narrative. After narrowing the focus down to three concrete applications, the total accounts contacted dropped, yet discovery call conversion surged noticeably. Less breadth. Higher impact.
Amplifa Resources & Tools Free tools and audits for sales pipeline management, lead generation, and AI maturity in B2B sales.
Decision Framework: 3 Questions Before Calling Any Vendor
Before any vendor meeting—whether with Siemens, a Microsoft partner, a KUKA integrator, Agile Robots, or ourselves—three questions should already be answered. Not hashed out in a workshop. Answered beforehand. Otherwise, the vendor dictates the problem definition. That is convenient, but rarely effective.
- Which bottleneck will cost us more revenue next fiscal year: sluggish production ramp-up, unstable scheduling, manual administrative processes, or insufficient qualified pipeline?
- What data proves this bottleneck: engineering hours, planning overhead, scrap rates, delivery delays, quote turnaround times, CRM conversion rates, or customer churn?
- Which decision should AI specifically improve: production line sequencing, robot program generation, document approvals, target account selection, follow-up timing, or proposal prioritization?
If you cannot answer these three questions yet, don't worry. But don't purchase AI software in that state. You are purchasing strategic clarity. That is completely fine. Just call it what it is.
The Bottom Line After Erlangen
The Siemens-NVIDIA demonstration in Erlangen is significant because it shifts a boundary. AI is breaking out of isolated pilot experiments and moving closer to planning, simulation, hardware, and delivery execution. KUKA illustrates the same dynamic from a robotics perspective. Microsoft and Körber demonstrate it through processes and the cloud. NVIDIA is applying further market pressure with nearly 10 billion US dollars in European investment commitments. And Friedrich Merz is publicly urging German businesses to embrace AI. Political speeches do not build pipeline, but they do shift expectations.
For sales directors, COOs, and managing directors in the DACH Mittelstand, the takeaway is simple and challenging: manufacturing AI and sales AI cannot remain separate slides in separate quarterly reviews. If the factory can plan faster, sales must know earlier whom to approach. When sales creates new demand, the factory must be able to signal which orders it actually wants. Between the digital twin and the CRM lies not an IT project. That is where margin is created.
I suspect that in two years, we will talk less about "AI projects" and far more about responsiveness. Who realizes first that a customer needs to switch suppliers? Who can verify faster whether a variant can be delivered? Who gives sales a reliable answer before a competitor books the meeting? In some facilities, a robot will begin gripping more quietly. In some sales offices, an outdated Excel sheet will finally disappear. Neither sounds monumental. Both generate revenue.