Actors
The people, systems, automation and AI agents that initiate or participate in operational work.
The operating layer for the AI enterprise.
We created Abaci to enable businesses to coordinate people, systems and AI through a shared operational model, with the controls, approvals and audit required to operate with confidence.
Software was built around applications. The next era is built around coordination.
Individual applications are capable within their own domains but were not designed to operate as a single business system, leaving the organisation to bridge the gaps with manual processes, integrations, workflow tools and data platforms whilst the underlying operating model remains fragmented.
Over time, the business starts adapting to how its software works rather than the software reflecting how the business actually operates.
When the process changes, the operating model should change with it rather than requiring the business to be rebuilt around each underlying application.
Abaci starts from a different premise: the process should be the organising principle, not the application.
Businesses have digitised their functions, but fragmented their operations.
Every new system was introduced to solve a problem. But every new addition creates another integration, reconciliation and control problem.
Businesses are paying twice: once for the software and again to make the software estate operate as one - often through brittle and inefficient solutions.
Sources: MuleSoft Connectivity Benchmark 2025; Asana Anatomy of Work 2023.
897
applications managed by the average enterprise.
29%
of those applications are integrated.
58%
of knowledge-worker time is spent on coordination and work about work.
The next generation of business software needs context, execution and governance together.
Automation and AI can now perform meaningful operational work, but enterprises cannot give autonomous systems unrestricted access to applications and data.
In the 2025 MuleSoft research, 80% of businesses cited data integration as a major challenge to AI adoption.
Source: MuleSoft Connectivity Benchmark 2025.
Context
What can the actor access and is the information trusted?
Execution
What can the person, system or agent change and how does the action enter the workflow?
Governance
Who approves it, what controls apply and how is the outcome audited for every actor?
A shared language for business operations.
Abaci replaces the manual stitching between systems with a shared operational model.
Instead of coordinating work across disconnected applications, the operation is defined once and reused across processes, decisions and interfaces.
This creates a consistent foundation for people, systems, automation and AI to collaborate, without losing control.
Blueprints
The live models of the entities, relationships and operational state that represent the organisation.
Actions
The controlled operations that can be performed within the operating model.
Controls
The permissions, policies, approvals, risk checks and audit requirements that govern Actions.
Interfaces
The applications, workflows, APIs and other surfaces through which the operational model is accessed, presented or invoked.
Who starts the work can change. The controls do not.
Ensure that your organisation's governance controls are applied, regardless of who initiated the work.
Explore governed automation
Process
Initiator
Who triggered the work
A person
A system
An AI agent
Context
What the work relates to
Invoice · INV-10482
or an entity, a report, a position, a client record
Action
What is being initiated
Approve
or create, export, revalue, archive
Controls
What it has to clear
Permissions
Approval threshold
Risk checks
Audit trail
Incremental adoption compounds into a more valuable operating model.
Value compounds across the model
Each process adds reusable context, capabilities and relationships for the next.
Consistent governance
Controls apply consistently across the platform.
Connected capability
Applications and agents become more valuable as the operating model becomes richer.
Built to expand with the business.
The challenge is bringing existing systems, processes and people together without disrupting the business. Abaci provides a practical path forward: solve immediate operational problems, then extend the same operating layer across the organisation.
01
Solve a focused problem
Create immediate operational value without requiring wholesale transformation.
02
Extend across operations
Bring more teams, systems and processes into the same foundation.
03
Unify operational context
Connect entities, relationships, state and processes into a shared operational model.
04
Operate at enterprise scale
Support people, automation and AI agents across increasingly complex operations without rebuilding the underlying foundation.
One foundation. Multiple entry routes.
Reaching a shared operating model should not require a prescribed transformation programme. Organisations can start with the problem that matters now, then extend Abaci as priorities change without creating another isolated system.
abaci Intelligence
Connect and understand operational data for processes, reporting and decisions.
Explore Intelligenceabaci Cortex
Introduce governed AI that can reason and participate inside controlled processes.
Explore Cortexabaci Builder
Create operational experiences around the information and actions each participant needs.
Explore Builderabaci Applications
Deploy ready-made business capabilities without creating another disconnected foundation.
Explore Applicationsabaci Publisher
Distribute governed reports, outputs and communications from operational data.
Explore PublisherAI should operate inside the business, not beside it.
As software becomes capable of initiating work rather than simply supporting it, the operating model becomes part of the control boundary.
01
Understand
Access trusted operational context, including available data, relationships and capabilities.
02
Initiate
Determine the required action and begin the appropriate process.
03
Control
Operate within defined permissions, policies, approvals and governance requirements.
04
Execute
Complete the action and produce an auditable operational outcome.
Typical integrations connect systems. Our operating layer defines how the business operates across them.
Connected by design
Records, processes and decisions share context.
Governed from the start
Controls travel with the work.
Composable
Capabilities can be reused across solutions.
Extensible over time
Solve one problem today without constraining tomorrow.
From fragmented software estates to programmable businesses.
The end state is not simply more automation. It is an organisation whose operating model can evolve as quickly as the business does.
