The ERPs of Past, Present and Future

David Thorpe
Director of Sales Engineering
I recently attended the UK Oracle User Group event in collaboration with our partners at Differentia Consulting, and it got me thinking about the trajectory that the ERP marketplace has been on. As a technology type that has been around for decades, in various guises with multiple widely-known market leaders, like many others is undergoing a huge transformation, largely thanks to AI-powered automation.
ERP of the Past:
A quick history lesson: ERP’s roots trace back to the 1960s, where Material Requitements Planning (MRP) began to be developed and implemented. These systems focused on inventory management and production scheduling – largely in the manufacturing industry.
As MRP systems developed, they evolved further functionality into broader areas of manufacturing process, such as scheduling and production control, moving through the 70s and 80s this began to bring together finance, production, inventory into a single platform.
This then gave rise to the ERP system as we largely know it, encompassing other business functions such as human resources, supply chain management and customer relationship management. ERPs became more scalable, and through the 2000s these became modular – with customers implementing only the relevant components for their business.
ERP of the Present:
Along came cloud computing. Modularised ERP approaches took web-based technologies and truly revolutionised the marketplace. Software-as-a-Service (SaaS) model approaches taken by the likes of Oracle, Microsoft and SAP moved these products to the cloud.
Businesses began to benefit further from lower upfront costs, easier scalability and automated updates that these cloud platforms delivered, making integrations with emerging technology and pre-existing non-ERP datasets easier.
Bigger volumes of more easily accessible data, in finer granularity than had ever been seen before now means that organisations can deploy analytical techniques, machine learning, artificial intelligence to increasingly real-time data, driving decision making at levels
The Customisation Trap:
What started as a vanilla ERP implementation many years ago has become so complex with so many moving parts – many of which there is no manual; no support – we’re almost too afraid to touch it. Many current ERP deployments are heavily engrained with module customisations, the work of consultants, specialists with knowledge and therefore introducing high levels of key person dependency.
Often these customisations balloon, and when the time comes to upgrade, migrate and modernise legacy ERP implementations to the modern SaaS stack offerings of the major players, as support is being withdrawn and putting users at risk of non-compliance, it triggers costly challenges. This is particularly important, as organisations seek to benefit from the rise of the emerging technologies mentioned earlier, such as AI.
We have seen this play out recently as Birmingham City Council (interestingly, where the OUG conference was held) are expected to spend £216 million in migration costs. [1]
ERP of the Future:
AI-Powered Automation
AI will become further embedded into ERP end-user processes, supporting enhanced decision making, repetitive task automation and sitting alongside the user experience in the form of bots and agents, streamlining workflows.
Continued Cloud
Cloud-based ERPs are no longer optional for most organisations, as they seek to benefit from the scalability, flexibility and security they bring. A market expected to double in size, by 2028, reaching $130bn.
Mobile ERP
In an increasingly mobile and decentralised world, ERP providers are making their applications prove more robust, as they are designed foremost for the mobile-led workforce.
How to Avoid Being Stuck
One such solution to avoiding the customisation trap is to keep your ERP as ‘vanilla’ as possible, leveraging the standard functionality of your ERP’s built-in features. By embracing no-code and low-code platforms layered on top of your core system reduces the reliance on heavy coding and therefore upgrade challenges.
Ever considered questions such as:
“I need to deploy a basic CRM without having to license the full cost of an ERP module”
“I would like to swap out my ERP HR application module for something best-in-class”
“I want to leverage AI models and third-party data into my process flows”
Conclusion:
ERPs are hugely valuable, but customisations can be costly, especially when not managed correctly – hampering your ability for timely upgrades and introducing risk into your business.
Cyferd can answer each of these challenges, creating functionality to augment your existing ERP, support with upgrades through seamless integration into your ERP and third-party datasets, all while embedding Neural GenesisTM AI for enhanced decision making and process improvement.
[1] https://www.theregister.com/2024/08/20/birmingham_oracle_cost/
Find out more About Cyferd
New York
Americas Tower
1177 6th Avenue
5th Floor
New York
NY 10036
London
2nd Floor,
Berkeley Square House,
Berkeley Square,
London W1J 6BD
Request a Demo
Comparisons
BOAT Platform Comparison 2026
Timelines and pricing vary significantly based on scope, governance, and integration complexity.
What Is a BOAT Platform?
Business Orchestration and Automation Technology (BOAT) platforms coordinate end-to-end workflows across teams, systems, and decisions.
Unlike RPA, BPM, or point automation tools, BOAT platforms:
- Orchestrate cross-functional processes
- Integrate operational systems and data
- Embed AI-driven decision-making directly into workflows
BOAT platforms focus on how work flows across the enterprise, not just how individual tasks are automated.
Why Many Automation Initiatives Fail
Most automation programs fail due to architectural fragmentation, not poor tools.
Common challenges include:
- Siloed workflows optimised locally, not end-to-end
- Data spread across disconnected platforms
- AI added after processes are already fixed
- High coordination overhead between tools
BOAT platforms address this by aligning orchestration, automation, data, and AI within a single operational model, improving ROI and adaptability.
Enterprise BOAT Platform Comparison
Appian
Strengths
Well established in regulated industries, strong compliance, governance, and BPMN/DMN modeling. Mature partner ecosystem and support for low-code and professional development.
Considerations
9–18 month implementations, often supported by professional services. Adapting processes post-deployment can be slower in dynamic environments.
Best for
BPM-led organizations with formal governance and regulatory requirements.
Questions to ask Appian:
- How can we accelerate time to production while maintaining governance and compliance?
- What is the balance between professional services and internal capability building?
- How flexible is the platform when processes evolve unexpectedly?
Cyferd
Strengths
Built on a single, unified architecture combining workflow, automation, data, and AI. Reduces coordination overhead and enables true end-to-end orchestration. Embedded AI and automation support incremental modernization without locking decisions early. Transparent pricing and faster deployment cycles.
Considerations
Smaller ecosystem than legacy platforms; integration catalog continues to grow. Benefits from clear business ownership and process clarity.
Best for
Organizations reducing tool sprawl, modernizing incrementally, and maintaining flexibility as systems and processes evolve.
Questions to ask Cyferd:
- How does your integration catalog align with our existing systems and workflows?
- What is the typical timeline from engagement to production for an organization of our size and complexity?
- How do you support scaling adoption across multiple business units or geographies?
IBM Automation Suite
Strengths
Extensive automation and AI capabilities, strong hybrid and mainframe support, enterprise-grade security, deep architectural expertise.
Considerations
Multiple product components increase coordination effort. Planning phases can extend time to value; total cost includes licenses and services.
Best for
Global enterprises with complex hybrid infrastructure and deep IBM investments.
Questions to ask IBM:
- How do the Cloud Pak components work together for end-to-end orchestration?
- What is the recommended approach for phasing implementation to accelerate time to value?
- What internal skills or external support are needed to scale the platform?
Microsoft Power Platform
Strengths
Integrates deeply with Microsoft 365, Teams, Dynamics, and Azure. Supports citizen and professional developers, large connector ecosystem.
Considerations
Capabilities spread across tools, requiring strong governance. Consumption-based pricing can be hard to forecast; visibility consolidation may require additional tools.
Best for
Microsoft-centric organizations seeking self-service automation aligned with Azure.
Questions to ask Microsoft:
- How should Power Platform deployments be governed across multiple business units?
- What is the typical cost trajectory as usage scales enterprise-wide?
- How do you handle integration with legacy or third-party systems?
Pega
Strengths
Advanced decisioning, case management, multi-channel orchestration. Strong adoption in financial services and healthcare; AI frameworks for next-best-action.
Considerations
Requires certified practitioners, long-term investment, premium pricing, and ongoing specialist involvement.
Best for
Organizations where decisioning and complex case orchestration are strategic differentiators.
Questions to ask Pega:
- How do you balance decisioning depth with deployment speed?
- What internal capabilities are needed to maintain and scale the platform?
- How does licensing scale as adoption grows across business units?
ServiceNow
Strengths
Mature ITSM and ITOM foundation, strong audit and compliance capabilities. Expanding into HR, operations, and customer workflows.
Considerations
Configuration-first approach can limit rapid experimentation; licensing scales with usage; upgrades require structured testing. Often seen as IT-centric.
Best for
Enterprises prioritizing standardization, governance, and IT service management integration.
Questions to ask ServiceNow:
- How do you support rapid prototyping for business-led initiatives?
- What is the typical timeline from concept to production for cross-functional workflows?
- How do licensing costs evolve as platform adoption scales globally?
