top of page
Industrial & Manufacturing
Manufacturing Technology
ERP
IFS
Won asset- and service-intensive industries by combining ERP, EAM and field service around the physical asset lifecycle, despite SAP and Oracle’s broader ERP reach and vertical software specialists.
1
MODEL
BUSINESS MODEL
SaaS
- Founded in 1983 in Sweden by five university friends focused on industrial and financial systems.
- Built ERP, EAM, supply-chain and field-service capabilities for asset-intensive industries.
- Unified these capabilities in IFS Cloud, a composable platform for ERP, EAM, SCM, ITSM and FSM.
- Expanded through acquisitions including Ultimo, Copperleaf, EmpowerMX and Softeon to deepen asset, maintenance and supply-chain workflows.
- Reached more than €1 billion ARR in FY2024, with FY2025 ARR up 23%, cloud revenue up 30% and 114% net revenue retention.
1. Identify a physical or operational asset whose uptime, utilization or service outcome drives customer economics.
2. Build the system of record around that asset before adding generic back-office modules.
3. Connect planning, maintenance, field service and finance around the same asset and work-order data.
4. Use industry-specific workflows to earn trust in demanding environments.
5. Add AI only where it improves uptime, scheduling, safety or service outcomes—not merely reporting.
Avoid: selling a broad ERP suite before the operational workflow is reliable; asset-intensive customers buy outcomes, not module counts.
DISTRIBUTION MODEL
IFS prioritized the operational needs of companies that make, maintain and service physical assets before pursuing a generic ERP suite. By combining ERP, enterprise asset management and field service around asset uptime, work orders and service delivery, it built a differentiated workflow rather than competing only on financial modules.
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Direct Sales, Enterprise Sales, Channel Partners, Partnerships
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Direct enterprise sellers targeted industrial firms, utilities, airlines, manufacturers and service organizations.
- Partners and systems integrators delivered localization, migration and complex implementation.
- Industry-specific expertise in aerospace, energy, construction, manufacturing and telecom created credibility in demanding sectors.
- Acquisitions and partner ecosystems expanded reach into maintenance, asset investment planning and supply-chain execution.
What worked: Sell into an industry where the operational outcome is measurable and the buyer already owns a budget for downtime, maintenance or service; domain proof beats generic ERP positioning.
Trap if copied blindly: Industry-led distribution fails when every vertical requires separate compliance, integrations and implementation expertise; the cost is long delivery cycles and diluted product focus.
| PATTERNS OF THIS MODEL
PATTERNS IN ASSET-INTENSIVE ERP PLATFORMS:
1. The asset is the system of record. Once maintenance, service, inventory and finance revolve around the same asset, each module increases switching cost.
2. Uptime is the buying metric. Customers pay when the platform reduces downtime, improves first-time fix rates or extends asset life.
3. Industry depth creates pricing power. Specialized workflows and regulatory knowledge justify premium pricing over horizontal ERP.
THE WEAKNESS: Deep verticalization can slow expansion because each industry requires distinct data models, integrations and implementation expertise.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — ASSET-LEVEL AI OPERATIONS. The next layer is not dashboards but prescriptive maintenance, scheduling and parts planning tied to asset condition, technician availability and cost.
GOLDMINE 2 — SERVICE-AS-A-PRODUCT INFRASTRUCTURE. Manufacturers can sell uptime, availability or outcome-based service contracts; software that prices and manages those outcomes can capture a share of service revenue.
GOLDMINE 3 — AGENT-READY FIELD OPERATIONS. Technicians need AI copilots for diagnostics, parts, safety and work-order execution; agents must operate within maintenance and compliance constraints.
THE PIT — ERP MODULE BLOAT. Adding finance, supply chain, EAM and FSM without a shared asset model recreates the fragmentation the customer was trying to eliminate.
THE SECOND PIT — IMPLEMENTATION DEPENDENCE. Complex industrial deployments can become consulting projects, limiting software-like scalability.
MOVE WITH CAUTION: Do not deploy autonomous maintenance or field-service agents without human approval, safety controls and auditability; a wrong work order can create safety, regulatory and asset damage.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
IFS competed against SAP, Oracle, Microsoft Dynamics and vertical EAM/FSM vendors. Its differentiation was industrial focus: IFS connected ERP, asset management and field service around the physical asset lifecycle, rather than treating service and maintenance as add-ons to financial ERP.
MARKET TYPE
Consolidated Market
ENTRY STRATEGY
Brownfield Entry
WHY THEY WON
Enterprise ERP is consolidated around SAP, Oracle and Microsoft, while EAM and FSM have strong vertical specialists. IFS exploited a blind spot: asset-intensive companies needed one operational system for asset uptime, technicians, parts, compliance and finance. Its industry depth and composable IFS Cloud changed the comparison from “which ERP has more modules” to “which platform improves asset and service performance.”
EXECUTION
IFS entered by replacing legacy ERP, maintenance and service systems in asset-intensive industries. Its initial bet was that companies would adopt a platform if it connected operational execution to financial and asset data. This was viable because downtime, compliance and service costs were already budgeted, while fragmented systems created operational friction. The prerequisites were industry knowledge, implementation capacity and reliable asset data; the approach fails where customers are deeply tied to SAP or require highly bespoke industrial systems.
FOOTHOLD STRATEGY
Beachhead Strategy
IFS first built a beachhead in asset- and service-intensive European industrial firms, especially aerospace, energy, manufacturing and construction. These customers were reachable through industry expertise and partners, could pay to reduce downtime and service cost, and had complex operational needs. The path outward was global expansion, cloud transition and adjacent asset-management workflows.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: IFS’s strongest campaign reframed ERP around asset uptime and service outcomes, allowing it to sell into operational budgets rather than competing only for IT’s ERP budget.
KEY LEARNING: In industrial software, the winning narrative connects software to downtime, safety, asset utilization and service revenue.
HOW TO USE: If your product touches physical operations, quantify avoided downtime or improved first-time fix before positioning it as a platform.
KEY LEARNING
THE STANDARD: In a consolidated ERP market, entrants win by owning an operational outcome the incumbent treats as secondary.
RULE 1 — TARGET THE ASSET OR WORKFLOW WITH MEASURABLE COST: Downtime, maintenance and field service create clear budgets.
RULE 2 — BUILD A SHARED OPERATIONAL RECORD: Asset, work-order and technician data should connect finance and supply chain.
RULE 3 — USE INDUSTRY PROOF TO REDUCE RISK: Demanding customers validate the platform under real operational constraints.
RULE 4 — KNOW WHEN ENTRY FAILS: If the incumbent’s ecosystem, integrations and global support are decisive, entry requires a vertical wedge or partner route.
MARKET TYPE: Consolidated Market (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN INDUSTRIAL PARTNER-LED ERP GROWTH:
1. Industry credibility opens enterprise doors. Customers trust vendors with proven deployments in comparable operating environments.
2. Partners determine implementation capacity. Complex ERP transformations depend on integrators and domain specialists.
3. Operational metrics drive expansion. Uptime, service cost and asset utilization create a stronger renewal case than software features.
4. THE WEAKNESS: Partner-led delivery can create inconsistent implementation quality and make growth dependent on scarce industry expertise.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Brownfield entry is appropriate when legacy systems still function but fragment the operational workflow and create downtime, compliance or service cost.
RULE 1 — SELL COEXISTENCE FIRST: Enable phased migration from legacy ERP, EAM and FSM systems.
RULE 2 — PROVE OPERATIONAL CONTINUITY: The customer must trust that maintenance, compliance and service workflows will not break during migration.
RULE 3 — TARGET THE OPERATIONS BUYER: Maintenance, service and operations leaders often feel the pain before IT sponsors the ERP replacement.
RULE 4 — REJECT WHEN INDUSTRY DEPTH IS MISSING: If the customer requires specialized compliance, safety or asset workflows, generic ERP capability is insufficient.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A beachhead strategy works when one demanding industry validates the product before expansion into adjacent industries.
RULE 1 — CHOOSE AN INDUSTRY WITH HIGH DOWNTIME COST: Asset-intensive sectors have clear budgets and measurable outcomes.
RULE 2 — BUILD REFERENCEABLE OPERATIONAL PROOF: Early customers should demonstrate uptime, service or cost improvements.
RULE 3 — EXPAND ALONG THE ASSET LIFECYCLE: Move from maintenance to planning, service, supply chain and finance.
RULE 4 — AVOID VERTICAL SPRAWL: Each new industry adds implementation and compliance complexity; expand only when the core model transfers.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
IFS expanded accounts from ERP into EAM, FSM, supply-chain and asset-investment planning. FY2025 net revenue retention was 114%, ARR grew 23%, cloud revenue grew 30%, and recurring revenue reached 83% of total revenue.
REVENUE MODEL
Subscription, Service Fee
PRICING MODEL
Custom Enterprise Pricing, Tiered Pricing, Value-Based Pricing
WHY THEY WON
Customers pay recurring subscription fees for IFS Cloud modules, with implementation and support services around deployment. Revenue expands through users, assets, work orders, modules and AI capabilities; recurring revenue is strong, but implementation complexity affects time-to-value and margin.
IFS uses quote-based enterprise pricing based on users, modules, assets, locations and deployment scope. The strategic consequence is that ERP becomes part of an operational transformation, with pricing tied to the breadth of asset and service workflows rather than finance seats alone.
TARGET AUDIENCE
Manufacturers (Enterprise; want ERP, production and supply-chain integration); Asset-intensive operators (EAM; want uptime, maintenance and compliance); Field-service organizations (FSM; want scheduling, technician productivity and first-time fix); Airlines, utilities and construction firms (Enterprise; want asset, compliance and service workflows).
CUSTOMER BUYING BEHAVIOUR
Aging systems, downtime, compliance pressure, service expansion or digital-transformation programs trigger evaluation. Operations, maintenance, IT and finance stakeholders assess workflow fit and migration risk; executive sponsors approve multi-year contracts before phased rollout.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Asset-intensive companies are not buying ERP; they are buying uptime, technician productivity and control over physical operations.
RULE 1 — PRICE THE ASSET LIFECYCLE: Assets, work orders and users determine the operational scope better than finance seats alone.
RULE 2 — SELL AVOIDED DOWNTIME: The comparison is lost production, emergency maintenance, compliance penalties and poor service outcomes.
RULE 3 — EXPAND ALONG THE WORK ORDER: Maintenance, scheduling, parts and service create a natural expansion path.
RULE 4 — WATCH IMPLEMENTATION DRAG: If deployment requires heavy customization, time-to-value and renewal economics weaken.
The buyer is purchasing asset reliability and service execution, proven by managed assets, work orders and uptime outcomes.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
ERP incumbent pressure: SAP and Oracle can bundle ERP, asset management and industry solutions into broader agreements.
Implementation complexity: Long deployments delay value realization and increase cost-to-serve.
Industry concentration: Demand can be affected by aerospace, energy, construction and manufacturing cycles.
Customization debt: Heavy configuration can make upgrades and cloud migration difficult.
Partner dependency: Growth depends on qualified integrators and industry experts.
AI safety risk: Autonomous maintenance or field-service recommendations can create safety and compliance exposure.
IFS reported FY2024 revenue of €1.228 billion and ARR above €1 billion; FY2025 ARR grew 23%, cloud revenue grew 30%, and NRR was 114%.
Where the model can break
4
MOTION
motion ge cs
IFS sells complex, multi-year industrial platforms through operations, maintenance, IT, finance and executive stakeholders. Its 114% net revenue retention, 23% ARR growth and 30% cloud growth reflect a structured enterprise motion built on industry proof, implementation partners and module expansion.
GROWTH EXPANSION MODEL
Land & Expand, Platform Expansion
HOW THEY EXPAND
IFS landed with ERP and asset-intensive operational workflows, expanded within accounts through EAM, FSM and supply-chain modules, then used acquisitions to deepen asset planning and maintenance. IFS Cloud unified these capabilities into a composable industrial platform.
COMPETITIVE STRATEGY
Focus Strategy
HOW THEY COMPETE
Against SAP and Oracle, IFS focused on asset- and service-intensive industries where operational outcomes mattered more than generic ERP breadth. Against vertical EAM and FSM vendors, it encircled the asset lifecycle with ERP, supply chain and finance integration.
GROWTH ENGINE
GTM
Content Flywheel
An operations or maintenance leader adopts IFS for asset or field-service workflows → the platform becomes the asset and work-order system of record → finance, supply chain and planning connect to the same data → additional modules and AI capabilities expand the account. The loop compounds when uptime and service outcomes justify broader deployment.
IFS runs an enterprise-led GTM supported by industry partners and systems integrators. Direct sales targets operations and IT leaders; industry specialists shape vertical solutions; partners deliver migration and rollout; account teams expand modules and geographies. The primary motion is enterprise sales, with partners essential to implementation. The transferable implication is that industrial software needs operational proof and partner capacity, not merely a broad product catalog.
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is the connected asset and work-order record: maintenance history, technician workflows, parts, compliance records and financial data become difficult to migrate once they drive operations.
| MOAT INTELLIGENCE
THE STANDARD: Industrial-platform moats last when the vendor owns the operational system of record for physical assets.
RULE 1 — ASSET HISTORY CREATES FRICTION: Maintenance records, compliance evidence and service history are costly to reconstruct.
RULE 2 — MULTI-MODULE ADOPTION DEEPENS LOCK-IN: ERP, EAM, FSM and supply chain share the same asset and work-order data.
RULE 3 — OPERATIONAL OUTCOMES REINFORCE RENEWAL: Customers stay when uptime, service performance and planning improve.
THE SIGNAL: 114% NRR, 83% recurring revenue and 30% cloud growth indicate expanding account dependence; the moat does not protect against superior ERP bundling, implementation failure or restricted AI adoption in safety-critical environments.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — PROVE INDUSTRIAL OPERATIONS VALUE. After its 1983 founding, IFS had to prove that software could improve asset, service and financial operations for demanding industrial customers.
$1–5M ARR — WIN INDUSTRIAL BEACHHEADS. Aerospace, energy and manufacturing customers validated the platform under complex requirements.
$5–10M ARR — EXPAND THE ASSET LIFECYCLE. EAM and FSM became the operational expansion layer.
$10–50M ARR — BUILD GLOBAL INDUSTRY DEPTH. Partners and vertical expertise enabled broader enterprise adoption.
$50–100M ARR — MOVE TO CLOUD AND COMPOSABILITY. IFS Cloud unified ERP, EAM, SCM and FSM around a common platform.
$100M+ ARR — SCALE INDUSTRIAL AI. IFS surpassed €1 billion ARR in FY2024; FY2025 ARR grew 23%, cloud revenue rose 30% and NRR reached 114%.
Rule: Own the asset workflow, then expand into the systems that determine uptime and service outcomes.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Build around a physical or operational asset whose performance drives customer economics, then expand into the workflows that determine its lifecycle.
SEQUENCE:
1. First, own the asset or work-order system of record; prerequisite: the customer has measurable downtime, service or compliance costs.
2. Next, connect planning, execution and finance around the same asset data; gate: the shared record reduces operational fragmentation.
3. Then, add AI only where it improves uptime, safety or service outcomes; gate: recommendations are explainable and can be reviewed before action.
WORKED: IFS used ERP, EAM and FSM to own the asset lifecycle, then expanded through IFS Cloud and industrial AI.
CAUTION: Do not pursue generic ERP breadth before the operational workflow is proven. Also avoid heavy customization that makes cloud migration and product scaling difficult.
bottom of page