Competitive Intelligence · August 2026

IFS Loops:
The Industrial Pivot Bet

How a San Mateo customer-support AI startup became the tip of the spear for IFS's €15B industrial agentic AI push — and whether the pivot from "CX ops" to "Digital Workers" actually holds together.

HEADQUARTERSSan Mateo, CA (IFS HQ: Linköping, SE)
FOUNDED2020 · Acquired by IFS, Jun 2025
PARENT ARR€1B+ (IFS, 30%+ YoY)
STATUSIFS Business Unit
COVERAGEtheloops.io
$8.75M
TheLoops Seed (2021)
€15B
IFS Valuation (Apr '25)
Jun 2025
Acquisition Close
10 → 50
Digital Workers → Skills
65+
App Integrations
45%
MTTR Cut (Legacy CX)

Who Is IFS Loops?

IFS Loops is the rebranded, reoriented remnant of TheLoops — a San Mateo, California customer-support intelligence startup founded in 2020 by Somya Kapoor, a former SAP and ServiceNow product executive. TheLoops raised a modest ~$8.75M seed round in 2021 (Dell Technologies Capital, Tidal Ventures, Westwave Capital) and spent four years building a narrow, well-reviewed product: real-time case context, QA automation, and escalation prediction for SaaS support and success teams.

On June 26, 2025, TheLoops was acquired by IFS — a Swedish enterprise software company selling ERP, EAM (enterprise asset management), and field service software to asset-heavy industries, itself valued at roughly €15 billion as of April 2025 (EQT and Hg as co-control shareholders, TA Associates, ADIA, and CPP Investments as minority holders) and reporting more than €1B in ARR growing 30%+ year-on-year. IFS did not fold TheLoops into an existing product line — it renamed the entire company "IFS Loops," kept Kapoor as CEO, and repositioned the platform almost overnight from a SaaS customer-support tool into an "industrial-grade agentic AI platform" for manufacturing, energy and utilities, telecom, aerospace and MRO, and construction.

Core Thesis IFS Loops is not a single product story — it is two products wearing one brand. Underneath the "Digital Workers for industrial operations" marketing sits the same case-intelligence, QA, and workflow-automation engine that TheLoops sold to SaaS support teams for five years. IFS acquired a working product and a capable team, then asked them to sell into an entirely different buyer, in an entirely different industry, on a timeline measured in months. Whether that repositioning is substance or a coat of paint is the central question this report tries to answer.

Leadership & Corporate Structure

👤

Somya Kapoor — CEO, IFS Loops

Co-founder of TheLoops; retained as CEO post-acquisition. Former SAP and ServiceNow enterprise software leader. Public face of the "Digital Workers" narrative — frequent conference speaker (Ai4, HumanX, IFS Industrial X Unleashed) on why most agentic AI pilots fail.

👤

IFS Executive Leadership

IFS Loops now reports into IFS's broader product and AI organization. IFS's own leadership (CEO Mark Moffat and team) has publicly framed the acquisition as the foundation of an "Industrial AI Workforce" strategy spanning IFS Cloud, EAM, and field service.

👤

TheLoops Founding Team

The original engineering and product organization built the case-intelligence and QA-automation stack now being re-marketed as "Digital Worker" infrastructure. Team continuity is a genuine asset — this is not a from-scratch industrial AI build.

👤

IFS Ownership Group

EQT (majority control) and Hg Capital, with TA Associates, ADIA, and CPP Investments as minority investors following the April 2025 stake sale that valued IFS at €15B. A PE-controlled cap table with growth-at-scale expectations sits above every product decision Loops makes.

Evolution Timeline

2020
TheLoops founded in San Mateo, CA
Somya Kapoor builds an "intelligent support operations" platform bringing product and customer context into the support agent's workspace.
2021
$8.75M seed round closes
Led by Dell Technologies Capital with Tidal Ventures and Westwave Capital participating. Funds R&D and early SaaS/CX go-to-market.
2022–2024
Product-market fit in SaaS support ops
Ships Agent Assist Copilot, Auto QA Analyst, Knowledge Generation, and CX Analyst. Lands customers including Bloomreach, Outreach, KOHO, Sauce Labs, Tricentis, and Gainsight. G2 reviewers cite QA coverage jumping from ~1% to 100% within 90 days and a 45% cut in mean time to resolution at reference accounts.
Jun 2025
Acquired by IFS
IFS frames the deal publicly as launching "the Industrial AI Workforce — the first agent platform built for mission-critical operations." TheLoops' AI agent technology is repositioned around field dispatch, supplier coordination, and asset-heavy workflows.
Q4 2025
"Digital Workers" launch — 10 workers, 50 skills
IFS Loops ships templated Digital Workers (customer order manager, field technician persona, supplier coordination) with a stated near-term roadmap to 100+ agentic skills by December 2025.
Q1–Apr 2026
Agent Studio launches
Self-serve tooling lets customers build custom Digital Workers via natural language. IFS reports "strong and accelerating momentum" for the Digital Workers line at launch.
Aug 2026
"Industrial Convergence Crisis" narrative push
theloops.io leads with a "Digital Workers + ERP: Solving the Industrial Convergence Crisis" story — the clearest signal yet that IFS is positioning Loops as the agentic layer sitting on top of its ERP/EAM core, not a standalone product.

Industry Landscape & Competitive Positioning

Market Context

IFS Loops now sits at the intersection of two very different, fast-moving markets: the crowded, VC-flooded AI customer-support agent category (Decagon, Sierra, Forethought, Intercom Fin, Ada) that TheLoops originally competed in, and the emerging, incumbent-dominated enterprise agentic AI / industrial AI category (SAP Joule, ServiceNow, Salesforce Agentforce, Microsoft Copilot) that IFS is now asking it to win. Both markets are converging on the same underlying pattern — "LLM plus tools in a loop," orchestrated with governance and audit trails — but the buyers, budgets, and proof requirements are entirely different.

Enterprise Agentic AI TAM

Analysts describe a $1.2T+ opportunity as Microsoft, Salesforce, ServiceNow, SAP, Oracle, and Palantir race to embed autonomous agents into core enterprise workflows. Salesforce Agentforce alone reached $1.4B in ARR with 114% growth in its first year.

Industrial / Asset-Heavy Software

IFS's core market — ERP, EAM, and field service for manufacturing, energy, aerospace and defense, and construction — is large, sticky, and historically slow to adopt AI relative to horizontal SaaS. IFS's own 30%+ ARR growth suggests the AI narrative is already pulling incremental spend.

AI Customer Support Agents

Decagon and Sierra are both well-funded unicorns; Intercom's Fin and Forethought compete on helpdesk augmentation. This is the market Loops actually has five years of production data and customer proof in — and it's the market IFS's messaging has quietly de-emphasized since the acquisition.

Competitive Map

CompanyModelMoatOverlap With IFS LoopsThreat
SAP JouleERP-native agent layer inside S/4HANADeepest ERP data model in the industry; massive installed baseIndustrial/ERP-embedded agentic AI, same buyer (ops & finance leaders)HIGH
ServiceNow (Now Assist)Workflow-native governance platform + AI Control TowerITSM/enterprise workflow incumbency; governance-first trust storyGoverned agent orchestration, ops workflow automationHIGH
Salesforce AgentforceCRM-native autonomous agents$1.4B ARR, 114% growth, huge CRM install baseCustomer-facing agent workflows — direct hit on Loops' CX heritageHIGH
Decagon / SierraPure-play autonomous customer-support agentsDeep VC funding, unicorn valuations, fast iteration on CX-only use casesDirectly competes with Loops' legacy Agent Assist / AI Autopilot layerHIGH
Intercom Fin / Forethought / AdaHelpdesk-augmentation AI agentsNative integration with existing support stacks (Zendesk, Intercom)Overlaps with Auto QA Analyst, Knowledge Generation, CX AnalystMEDIUM
Microsoft Copilot / Copilot StudioProductivity-suite + Dynamics-embedded agentsM365 ubiquity, Azure OpenAI relationship, low-friction distributionEnterprise agent building; also one of Loops' own integration partnersMEDIUM
C3.ai / Palantir FoundryBroad industrial/enterprise AI + data platformsLong OT/IT integration history, federal and industrial reference accountsCompetes for the "industrial AI platform" narrative and budget lineMEDIUM
Aveva / Rockwell / Honeywell ForgeOT-layer industrial software adding AI copilotsDecades of plant-floor and process-engineering trustAdjacent — asset/process layer rather than workflow/ops layerLOW–MEDIUM

Industry Trends Shaping Loops' Fate

🤖

ERP Incumbents Are Building Their Own Agents

SAP Joule and ServiceNow's Now Assist mean the two most obvious channels for reaching industrial and enterprise-ops buyers are also building competing agent layers natively into systems those buyers already run. IFS Loops has to win on being IFS-native — a much smaller aperture than "industrial AI" broadly.

🏭

"Industrial Convergence" Is a Real, Contested Framing

The idea that ERP systems of record and agentic "systems of action" need to converge is gaining real traction — IFS is betting its acquisition on being early to that framing. But SAP, Oracle, and Microsoft are making the identical argument with far larger R&D budgets and distribution.

🎯

Governance Is Becoming the Differentiator

As agentic pilots mature, buyers are shifting focus from "can it act autonomously" to "can I trust, audit, and roll back what it did." ServiceNow's AI Control Tower and SAP's compliance-anchored Joule agents are explicitly selling governance. IFS Loops' SOC 2/HIPAA/GDPR posture is necessary but not sufficient here.

🔁

CX AI Is Consolidating Fast

Decagon and Sierra have raised at unicorn valuations specifically to win the support-agent category Loops originally built for. A mid-sized, newly-acquired business unit competing on both fronts at once is structurally under-resourced against either pure-play.

Key Success Factors in This Domain

Winning in enterprise/industrial agentic AI in 2026 requires strength across four axes simultaneously:

System-of-Record Depth

Agents are only as good as the operational data model beneath them. ERP-native players (SAP, IFS itself) have a structural advantage over bolt-on tools.

Governance & Auditability

Mission-critical workflows in aerospace, energy, and manufacturing require approval chains, rollback, and audit trails — not just accuracy.

Proof, Not Promise

Buyers in these categories are conservative. Published, verifiable case studies with hard metrics move deals; roadmap slides don't.

Distribution Leverage

Whoever already owns the buyer relationship (the ERP, the ITSM tool, the CRM) has a durable wedge that a point-solution AI vendor lacks.

What IFS Loops Actually Sells

The product line is genuinely two layers stitched together: the legacy CX Ops layer TheLoops built and sold for five years, and the new Industrial Digital Worker layer IFS is building on top of the same platform. Both are live on theloops.io today, under the same navigation, priced and sold through what appear to be two different motions.

Layer 1 — CX Ops (TheLoops Heritage)

Agent Assist Copilot
Guides human support agents at every step

Surfaces case context, suggested next actions, and product/customer signals inside the agent's existing workspace (Zendesk, Salesforce, ServiceNow, Jira, HubSpot, Slack, Teams). This is the original TheLoops product core.

Auto QA Analyst
Automated, 100%-coverage support QA

Replaces manual sample-based QA review. G2 reviewers report QA coverage moving from ~1% to 100% within 90 days of deployment at reference accounts.

AI Autopilot / Knowledge Gen / CX Analyst
Self-service deflection, knowledge-gap detection, always-on CX intelligence

Rounds out the CX suite — AI-powered self-service, automatic detection and filling of knowledge-base gaps, and continuous sentiment/escalation-risk scoring across the support queue.

Layer 2 — Industrial Digital Workers (IFS Layer)

Digital Worker Marketplace
Prebuilt, persona-modeled agents for industrial operations

Templated Digital Workers — customer order manager, field technician, supplier coordinator — that autonomously manage multi-step tasks: dispatch, supplier coordination, inventory replenishment, across ERP, EAM, and field-service systems. 10 workers and roughly 50 agentic skills at launch, with a stated roadmap to 100+.

Agent Studio
Self-serve digital worker builder

Lets customers create, monitor, and deploy their own agents for complex workflows using natural language — reducing dependence on IFS professional services for customization. Launched around Q1–April 2026.

OEM Program
Embed IFS Loops' agentic engine inside a third party's own product

A genuinely distinct GTM motion: rather than selling only to IFS's own customer base, IFS Loops offers itself as embeddable infrastructure for other ISVs — "accelerate your agentic roadmap" without building an agent platform from scratch.

Target Customer Segments

SegmentBuyerProblem SolvedRepresentative Customers
SaaS support & success orgsVP Support / CX, Head of Support OpsManual QA, inconsistent case handling, slow escalation detectionBloomreach, Outreach, KOHO, Sauce Labs, Tricentis, Gainsight
Manufacturing operationsVP Operations, Plant IT / Digital Transformation leadFragmented operational, service, and quality data across systemsNot yet publicly disclosed with named case studies
Energy, utilities & resourcesHead of Field Service / Asset ManagementRegulated, complex asset operations; compliance and response speedNot yet publicly disclosed with named case studies
TelecommunicationsNetwork Operations leadershipHigh-volume, event-driven network and service signalsNot yet publicly disclosed with named case studies
Aerospace & MROMaintenance & Compliance leadershipPrecision maintenance, inspection, and documentation workflowsNot yet publicly disclosed with named case studies

Key Metrics & Recent Performance

📉

45% MTTR Reduction

Reported at reference CX accounts post-implementation — one of the few hard, third-party-verifiable (G2) metrics available for the platform.

QA Coverage: 1% → 100%

Cited improvement within 90 days of rollout, moving support teams from sample-based to full-coverage quality review.

💬

CSAT 4.1 → 4.6

Customer satisfaction improvement reported by reviewers — modest but directionally consistent with the QA and MTTR gains.

📈

37% Efficiency Gain — Bloomreach

Christina Augustine, COO of Bloomreach, is the platform's most visible customer reference, citing impact on both frontline support and success functions simultaneously.

All CX-layer metrics predate or are independent of the IFS acquisition and reflect the original TheLoops product. No equivalently specific, named metrics have been published yet for the industrial Digital Worker layer.

Two Buyers, One Brand

The starkest strategic fact about IFS Loops is that its go-to-market now has to serve two structurally different buyers through one website, one brand, and — as far as public information shows — largely the same underlying platform.

Buyer A — SaaS Support/CX Leader

Fast-moving, product-led, comfortable buying and deploying point solutions in weeks. Cares about MTTR, CSAT, QA coverage, and agent productivity. This is the buyer TheLoops built five years of credibility with.

Buyer B — Industrial Operations Leader

Risk-averse, compliance-driven, multi-quarter procurement cycles, deeply embedded in incumbent ERP/EAM relationships. Cares about auditability, uptime, integration with existing OT/IT systems, and vendor stability. This is the buyer IFS is asking Loops to win.

These two segments do not just have different needs — they evaluate vendors on almost opposite criteria. Buyer A rewards speed and iteration; Buyer B rewards governance and proof of scale. Selling to both from a single undifferentiated homepage risks under-serving both: CX buyers may see "industrial-grade" framing and wonder if the product has drifted from their use case, while industrial buyers may find a support-QA case study (Bloomreach) unpersuasive for a plant-floor dispatch decision.

The Real Segmentation Question It is not yet clear from public materials whether IFS intends to sunset the CX Ops layer over time and fully commit to industrial, run both as permanently separate businesses under one brand, or find a genuine synthesis (e.g., "product-aware support" concepts applied to field-service dispatch). Each path implies a very different roadmap, and the current site gives no signal which one IFS has chosen.

Product Strategy Assessment: What's Real, What's Risk, What's Missing

IFS Loops inherited a genuinely well-reviewed, metric-backed CX product and a capable, retained founding team — that is a real asset most acquirers don't get. The critique below focuses on the gap between the "industrial agentic AI platform" IFS is marketing and what is publicly demonstrable today.

⚠ Positioning Risk
The Industrial Claim Is Running Ahead of the Proof
Every hard, named, third-party-verifiable metric on theloops.io — the 37% Bloomreach efficiency gain, the 45% MTTR cut, the 1%→100% QA coverage jump, the 4.1→4.6 CSAT lift — comes from the legacy CX product, sold to SaaS companies. Not one publicly named manufacturing, energy, telecom, or aerospace customer with a comparable metric appears on the site as of this writing. "Industrial-grade" is asserted in copy nine times over; it is demonstrated zero times. Buyers in aerospace and energy — categories with genuinely high switching costs and audit requirements — will notice this gap immediately.
◈ Strategic Gap
"Industrial LLMs" Is a Marketing Claim With No Technical Backing
The platform page states that "Industrial LLMs understand context, compliance, and operational rules, making AI actionable from day one" — but discloses no model provider, no fine-tuning methodology, no benchmark, and no published eval. Compare this to SAP, which is explicit about Joule's native S/4HANA data grounding, or ServiceNow, which publishes specifics on its AI Control Tower governance model. Vague "industrial LLM" language reads as repositioned marketing copy from a CX product rather than a substantiated technical differentiator — and it invites exactly the scrutiny this report is applying.
⚠ Structural Risk
Two Buyers, One Undifferentiated GTM Surface
As detailed in §04, the site serves SaaS CX buyers and industrial operations buyers through the same navigation, the same case studies, and apparently the same core platform, with no visible segmentation in messaging, pricing, or proof points. This isn't a cosmetic issue — it actively weakens both pitches. A plant operations leader evaluating "governed, audit-ready compliance" claims will not find them evidenced anywhere near as rigorously as the CX metrics are.
◈ Execution Gap
An Aggressive Skill-Shipping Cadence in a Low-Tolerance Category
IFS Loops went from 10 Digital Workers/50 skills at launch to a stated target of 100+ skills within roughly two months (by December 2025) — a shipping velocity more typical of a horizontal SaaS product than mission-critical industrial software. Aerospace, energy, and regulated-asset workflows are precisely the domains where shallow, quickly-shipped "skills" create the most downside if they fail an audit or make an incorrect autonomous decision. Speed and rigor are in tension here, and the public roadmap language doesn't yet show how IFS is resolving it.
✦ Opportunity
The OEM Channel Is the Most Interesting Strategic Bet on the Site
"Ship agentic AI inside your product" — offering IFS Loops as embeddable infrastructure for other ISVs — is a genuinely differentiated move relative to SAP Joule and Salesforce Agentforce, both of which are built to keep customers inside their own ecosystems. If executed well, OEM turns Loops from a single-vendor bolt-on into a distribution layer that scales beyond IFS's direct sales force. It is currently a single line item in the nav, not a headline strategy — that looks under-invested relative to its potential.
✦ Opportunity
IFS's 6,000+ Account Installed Base Is an Unmatched Distribution Asset
Whatever the positioning confusion, IFS Loops has something almost no AI-agent startup has: a large, existing base of asset-heavy enterprise customers already paying for ERP/EAM software, with procurement relationships already in place. If IFS cross-sells Loops methodically — starting with customers already live on IFS Cloud, rather than trying to win net-new industrial logos cold — the proof-point gap in §05 above becomes solvable within a few quarters rather than years.
⚠ Retention Risk
Founder-Led Continuity Is Fragile in a PE-Owned Conglomerate
Kapoor's retention as CEO and her active public role (Ai4, HumanX, IFS Industrial X Unleashed) are the clearest signal that IFS wants Loops to remain a distinct, founder-driven unit rather than be fully absorbed. But IFS sits under an EQT/Hg-led ownership structure with growth-at-scale return expectations; if the industrial pivot underdelivers against those expectations before the proof points catch up, the operational and cultural continuity that makes Loops valuable is exactly what's at risk.

Strengths, Weaknesses, Opportunities, Threats

Strengths
  • Five years of production CX data with verifiable, third-party (G2) metrics
  • Founder-CEO retained post-acquisition with SAP/ServiceNow pedigree
  • SOC 2 Type 2, HIPAA, and GDPR compliant; SSO via Okta/Google/Microsoft
  • 65+ integrations spanning Zendesk, Salesforce, ServiceNow, Jira, Slack, Teams
  • Backed by IFS's €1B+ ARR balance sheet and 30%+ growth momentum
  • OEM program creates a distribution path beyond IFS's own sales force
Weaknesses
  • Zero publicly named industrial customer case studies as of this writing
  • "Industrial LLM" and compliance claims are asserted, not technically substantiated
  • Two structurally different buyers served through one undifferentiated GTM surface
  • Skill-shipping cadence (50 → 100+ in ~2 months) is fast relative to category norms
  • Small original team scale relative to the ambition of the new mandate
Opportunities
  • Cross-sell into IFS's existing enterprise ERP/EAM installed base
  • Scale the OEM channel into a genuine distribution multiplier
  • Publish rigorous industrial case studies to close the proof gap
  • Digital Worker Marketplace as an ecosystem/app-store model
  • Claim the "agentic layer for asset-heavy industries" niche before SAP/ServiceNow fully commit to it
Threats
  • SAP Joule's native ERP data advantage on IFS Loops' own target buyers
  • ServiceNow's governance-first trust story out-messaging Loops on auditability
  • Salesforce Agentforce's scale ($1.4B ARR, 114% growth) reshaping CX-agent buyer expectations
  • Decagon/Sierra out-competing on the legacy CX business while Loops' attention shifts industrial
  • PE-owned parent's growth expectations outpacing the pivot's actual proof-point timeline
  • Industrial buyers' slower, more conservative adoption cycles than the SaaS market Loops was built for

Product Strategy 2026–2028: From Two Products to One Coherent Platform

Document Type This is a mock product strategy document written from the perspective of a Senior PM/CPO at IFS Loops. It is directionally grounded in real company data but represents analytical recommendations, not IFS's actual internal roadmap.
01

Strategic Vision & North Star

Vision: IFS Loops becomes the trusted, auditable agentic execution layer across IFS's enterprise installed base — and, via OEM, across other ISVs' products — proving out one shared "Digital Worker" abstraction across both support-ops and industrial-ops workflows rather than running two disconnected businesses under one name.

North Star Metric: Autonomous Task Completion Rate — the percentage of Digital Worker actions executed end-to-end without human intervention across live, paying industrial accounts (not pilots). This single metric forces the organization to prioritize proof over positioning. Target by end of 2027: 40%+ of in-scope workflow steps completed autonomously, up from an unreported (likely low single-digit) baseline today.

The Strategic Pivot: From "one brand marketing two products" to "one platform, two proven motions" — CX Ops and Industrial Ops — each with its own named case studies, its own success metrics, and a clearly articulated shared technical core.

02

Three Strategic Bets (2026–2028)

Bet 1: Split the Go-to-Market, Not the Platform

Formally segment messaging, case studies, and buyer journeys into two tracks — Loops for Support Ops (the proven CX motion) and Loops for Industrial Ops (the new IFS-driven motion) — while keeping one shared underlying agent platform and skill framework. Buyers self-select into the track built for them instead of wading through undifferentiated "Digital Worker" messaging.

Why This First Every other initiative below depends on buyers trusting that the product in front of them was built for their use case. Segmentation is a packaging and content project, not a rebuild — it can ship in a single quarter and immediately improves both pipelines.

Bet 2: Prove the Industrial Claim With Named, Audited Case Studies

Commit to publishing 3–5 rigorous, named industrial case studies — manufacturing, energy/utilities, and aerospace/MRO — within two quarters, each with hard, verifiable metrics (dispatch time reduction, first-time-fix rate, compliance audit pass rate) held to the same evidentiary bar as the existing Bloomreach CX reference. No case study, no claim in the marketing copy.

Bet 3: Make OEM the Real Distribution Wedge

Invest disproportionately in Agent Studio and OEM self-serve tooling so that other ISVs building on IFS Loops become a distribution multiplier beyond IFS's own sales force — the one strategic advantage neither SAP Joule nor Salesforce Agentforce is structurally positioned to offer at the same openness.

Why This Matters IFS's direct sales force can only move as fast as IFS's own enterprise sales cycle. A credible OEM motion decouples Loops' growth from IFS's account-by-account pace and turns the platform into infrastructure other vendors depend on — a much harder position for SAP or ServiceNow to dislodge.
03

Prioritized Initiative Roadmap

INITIATIVE
PRIORITY / TIMELINE
SUCCESS METRIC
GTM Segmentation (CX vs. Industrial)
Separate messaging, landing pages, and case-study tracks on shared platform.
P0 · Q4 2026
Distinct conversion funnels live; qualified-lead mix tracked by track
Named Industrial Case Studies (3–5)
Manufacturing, energy/utilities, aerospace/MRO — audited, hard-metric proof points.
P0 · Q1 2027
3+ published, named case studies with third-party-verifiable metrics
Governance & Audit Trail Transparency
Publish technical detail on approval chains, rollback, and compliance logging.
P1 · Q1 2027
Public governance whitepaper; parity messaging with ServiceNow AI Control Tower
Agent Studio OEM Self-Serve GA
Full self-service OEM onboarding without IFS sales involvement.
P1 · Q2 2027
25 OEM partners onboarded self-serve within two quarters of GA
IFS Installed-Base Cross-Sell Motion
Structured playbook to attach Loops to existing IFS Cloud renewals.
P2 · Q2 2027
15% of IFS Cloud renewals include a Loops attach by Q4 2027
Skill Quality Bar for Regulated Workflows
Formal review gate before any skill ships into aerospace/energy/regulated accounts.
P2 · Q2 2027
Zero compliance-related autonomous-action incidents in regulated accounts
Digital Worker Marketplace Ecosystem
Third-party developers publish and monetize skills on the platform.
P3 · 2028
50+ third-party-published skills; marketplace GMV tracked
04

OKRs — 12-Month Targets (2026–2027)

O1: Close the Industrial Proof Gap
  • KR1: 3+ named, audited industrial case studies published by Q1 2027
  • KR2: Governance whitepaper published with third-party (SOC 2-equivalent) validation for autonomous actions
  • KR3: Zero unsubstantiated "industrial-grade" or "industrial LLM" claims remaining in marketing copy without a linked proof point
O2: Stand Up a Genuine OEM Distribution Channel
  • KR1: Agent Studio OEM self-serve GA shipped by Q2 2027
  • KR2: 25 OEM partners onboarded within two quarters of GA
  • KR3: 10% of new ARR attributable to OEM-embedded deployments by Q4 2027
O3: Convert IFS's Installed Base Into Loops' Primary Pipeline
  • KR1: Structured cross-sell playbook live for IFS Cloud account teams by Q1 2027
  • KR2: 15% of IFS Cloud renewals include a Loops attach by Q4 2027
  • KR3: Loops-attached accounts show 10+ point higher net revenue retention than non-attached accounts
O4: Protect the CX Business While the Industrial Bet Matures
  • KR1: Maintain or grow existing CX customer logo count (no net attrition attributable to positioning confusion)
  • KR2: MTTR and QA-coverage metrics held at or above current reference-account levels
  • KR3: Dedicated CX-track landing page and case studies live by Q4 2026 (Bet 1)
05

Key Risks & Mitigations

RiskSeverityLikelihoodMitigation
Industrial pivot fails to produce proof before PE-driven growth targets force a re-prioritizationHIGHMEDIUMFast-track 3–5 named case studies (Bet 2) within two quarters; report interim leading indicators (pilot-to-paid conversion) to IFS leadership monthly.
SAP Joule or ServiceNow out-message Loops on governance before the whitepaper shipsHIGHHIGHPrioritize governance transparency (Initiative 3) ahead of new feature marketing; borrow credibility from IFS's own compliance posture in EAM.
CX customers churn due to perceived deprioritization as industrial messaging dominatesMEDIUMMEDIUMShip the CX-track segmentation (Bet 1) first; maintain visible CX product investment and roadmap communication.
A shipped "skill" causes a compliance or safety incident in a regulated industrial accountHIGHLOW–MEDIUMFormal review gate (Initiative 5) before any skill ships into regulated workflows; conservative autonomy defaults with human-in-the-loop escalation.
Kapoor or founding team depart before the pivot's proof points materializeMEDIUMLOWRetention packages tied to OKR milestones (O1–O3); document institutional and technical knowledge outside any single individual.
06

Strategic Don'ts (What to Stop or Avoid)

Don't ship new "skills" faster than they can be governance-reviewed

The 50-to-100+ skill sprint is impressive velocity but a liability in regulated workflows. Slow the shipping cadence for anything touching compliance-sensitive industrial accounts until the review gate (Initiative 5) exists.

Don't keep using CX metrics to imply industrial proof

The Bloomreach 37% efficiency gain and the MTTR/QA/CSAT figures are real and valuable — for the CX audience. Presenting them near "industrial-grade" copy without a clear label invites exactly the credibility gap this report identifies.

Don't let "industrial LLM" remain an undefined marketing term

Either publish the technical substance behind the claim or retire the phrase. Vague model claims are a bigger reputational risk in industrial/regulated buyers than in the SaaS market Loops came from.

Don't try to out-market SAP and ServiceNow on scale

Loops cannot out-spend or out-distribute the ERP incumbents. Its differentiated angle is proof, focus, and OEM openness — competing on marketing volume plays to IFS Loops' weakness, not its strength.

The Verdict

IFS Loops is a genuinely interesting acquisition built on a genuinely solid product. TheLoops' CX ops platform earned real, verifiable customer results — a 45% MTTR reduction, full QA coverage, a named COO testimonial — the kind of proof most AI startups spend years chasing and never get. IFS was smart to keep the founding team and CEO rather than absorb and dissolve the business.

But the "industrial agentic AI platform" IFS is now marketing to manufacturing, energy, telecom, and aerospace buyers is, as of today, a repositioning exercise running well ahead of its evidence. Every hard number on the site belongs to the old business. The new business is described entirely in adjectives — "industrial-grade," "governed," "context aware" — with no named customer, no published metric, and no disclosed technical substantiation for its most specific claims. That's a normal and forgivable state for a pivot fourteen months old. It becomes a real strategic risk if IFS's growth expectations for the €15B business outrun the two-to-three quarters it will realistically take Loops to generate credible industrial proof.

The path forward is not complicated, even if it is not easy: stop trying to sell one undifferentiated story to two very different buyers, publish the proof the industrial claim needs, and lean into the one structural advantage — IFS's existing enterprise distribution and the OEM channel — that neither Decagon nor SAP Joule can easily replicate.

Bottom Line IFS Loops is a strong product wearing an unproven story. The strategy to close that gap is straightforward: segment the go-to-market, publish named industrial case studies, make governance claims verifiable, and scale OEM as the real differentiator. The credibility window is roughly 12–18 months before "industrial-grade" either becomes true or becomes a liability.

Sources: theloops.io, ifs.com, IFS press releases and investor updates, PRNewswire, G2 reviews, Crunchbase, PitchBook, Verdantix, ERP Today, TA Associates, EQT, White & Case, Futurum Group, HumanX 2026 agenda, Tech Talks Daily podcast. Analysis as of August 2026. Metrics are company- or reviewer-stated as cited; no independent audit was performed.