AbstractOps as Back-Office Control Layer
Hari Raghavan, CEO of AbstractOps, on the composable enterprise
This signals that back office software is being rebuilt as interchangeable building blocks, which helps AbstractOps more than it hurts it. If Carta exposes cap table data, Mercury exposes banking actions, and Deel exposes hiring and payroll workflows through APIs, AbstractOps can sit above them and coordinate the actual job to be done, like onboarding an employee, wiring a vendor, or closing a financing, without replacing each specialist system.
-
AbstractOps is not trying to own payroll, banking, or equity records. It is trying to create one operating layer across HR, finance, and legal, where data from many systems is standardized so repeatable workflows can run in one place, with humans only stepping in for exceptions.
-
The partner set has moved closer to this model over time. Mercury gives every account read and write API access, Carta now offers issuer, investor, portfolio, and launch APIs, and Deel positions its API for contract creation, payroll, and global hiring workflows inside other products.
-
That changes competition. A company like Rippling or Deel can still bundle more surface area, but infrastructure friendly products are easier to plug into a broader stack. In practice, the fight shifts from who owns one workflow to who becomes the control layer for many workflows.
The next step is a back office stack where the system of record and the system of action are increasingly separate. The winners will be products that expose clean data, permissions, and triggers, because that makes them easier to embed into larger operational workflows and harder to rip out once connected.