A Compostable Composable Platform

Rich Byard
Chief Technology Officer
An easy autocorrect misunderstanding, but something I couldn’t shake off as an analogy for the platform we need in today’s changing world. A platform that ensures each investments in applications, data and AI, should be built from the foundational building blocks of our unique organizations, our own data. We’ve all been pointing that way for some time, but perhaps, if you’re like me, not really able to visualize how we get to this apparent Nirvana. So let’s take a walk through the journey we’ve all followed (some steps of it at least as there have been many branches) and why this analogy fits so well as the logical next step.
Pre-history
Cave drawings, papyrus, slates, paper, punchcards, magnetic tapes etc… Life’s too short and tbf mostly before my time.
The push into the big blue(s)
The mainframes and ERPs, arguably the first mass migration into systems trying to capture the business processes and data of the organization. To their credit they had the vision to try and model the data in a holistic manner, but of course this first foray had its complications and limitations. I personally remember, some 30 years later, a number of those shortcut codes to navigate around the first few mainframe and ERPs I worked on. UI’s certainly improved but shortcut codes remained the expert navigation of choice for these systems. AC16 anyone?
Craving to see
Building systems around processes and data captured a lot, but made very little truly visible outside of the management of the single record/case itself. So the next phase I experienced was the desperate desire to be able to see that data. To report, to aggregate, to be able to make decisions from it. The same systems that captured the data struggled to evolve to meet this need. Excel bounded onto the scene and made our lives way more interesting. We’ve all seen the best/worst of excel models. My personal masterpiece/monster had about 70 linked files (all many linked sheets deep) which resolved actuals and planning for all levels of reasonable size, and reasonably famous, organization; from roles to teams, to departments, to business units and finally to a full group level roll up. It was amazing as an exercise in how far you can push things, but there was obviously a better, and less error prone, way.
The Data Warehouse epoch
What self-respecting organization has not plunged into the crevasse of the data warehouse project. Don’t get me wrong, I loved designing graceful data transformations and modeling celestial star schemas, and making big advances to reporting and analysis in the process. This was a great period to be a data ‘nerd’, those who could see the relationships in the data now had the ability to let others see the same. But, the downside of such capable depth was that it took a huge amount of time to do well and maintenance a significant burden and resource drain.
Dump it in the lake
Let’s assume the tools are smart enough and just dump all this data into one place. Let’s not even structure it as surely the tech is good enough to make sense of it, right? It’s a great idea, perhaps it was a little before its time to meet the expectations the marketing had you believe. But all these steps bring us to this new world we find ourselves with the promise of answers to everything without putting in any effort at all, hurrah! Well, almost.
I want it all, I want it all, I want it all, and I want it now!
Large language models (LLMs, as if you needed me to add that), the supernova that has eclipsed everything before, at least as far as user expectations are concerned. So are we now coming to the era where we can have everything we always dreamed of? Unfortunately, not if you want it to grasp your specific organization’s challenges, and not without the expense, effort and risk of some very significant projects/programs along the way… But that’s where the compostable analogy kicks in, a new paradigm perhaps.
Composable applications, compostable data!
Imagine your data managed holistically, your applications integrated seamlessly, no silos and vendor constraints, enabling the capture of structured and unstructured data as needed, a true composable platform for your Organization.
Now imagine a swarm, a fleet, a gaggle, a pride of bots (what is that collective noun?) tailored for your organization, always processing as data changes, ‘breaking down’ that data into key nutrients (not insights yet, as they come with application) continually evolving and adjusting their learned outputs, adding to your nutrient library. Let the data be ‘decomposed’ (not the original data of course) for your organization, your context, your processes to give your organization the nutrients it needs to grow, to be guided with true context, to meet it’s ultimate potential.
Now you have the base, a real base, for a supercharged RAG approach informed and augmented by the core nutrients of your organizations learning. Continuously evolving and tuning itself for your organization, and never leaving the confines of your data boundaries. And all this running on a composable platform where all of the pieces of the orchestra (the building blocks) are themselves evolving and improving whilst maintaining and improving your apps, your agentic workflows, your composed views and layouts. Nothing stationary, everything incrementally improving every week whilst maintaining the integrity of your processes…
Now that’s an application and AI strategy I can totally get behind!
Credits: Kudos to Adrian Parker at Differentia Consulting who triggered this little moment of mind wandering about the nature of a compostable approach to data and AI.
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?
