What is operational intelligence? A guide for portfolio operators
Operational intelligence is the practice of mapping every account, identity, system, and dollar in your business into a single connected graph. Here is how it works and why portfolio operators need it.
Most growing businesses do not run on a single stack. They run on dozens of SaaS subscriptions, cloud accounts, internal services, and shared identities — often spread across multiple brands, entities, or product lines. Operational intelligence is the discipline of turning that sprawl into a single connected map you can actually reason about.
From spreadsheets to a connected graph
Most operations teams begin with a spreadsheet. It works for a few months, then drift sets in: new tools are added, ownership changes, and the spreadsheet stops matching reality. Operational intelligence replaces that document with a live graph in which every account, identity, payment method, and subscription is a node, and every relationship between them is an edge.
The result is queryable. You can ask — in plain language or through structured filters — which subscriptions belong to which entity, which credit card pays for which tool, who has access to a given system, and what would break if a particular account disappeared.
Why portfolio operators need it
If you operate one brand, a careful spreadsheet may be enough. If you run several — or you manage shared infrastructure across many product teams — the cost of not having a single map compounds quickly:
- Untracked spend ends up on the wrong P&L because no one mapped the subscription to an entity.
- Compliance reviews stall because access lists live inside individual tools, not in one place.
- Migrations and divestitures take months because the dependency graph exists only in people's heads.
What a good operational graph looks like
A useful operational graph is more than an inventory. It is structurally honest about the relationships in your business. At minimum it should connect five layers: legal entities, brands and products, accounts and subscriptions, identities and access, and the payment methods and billing addresses behind them.
When those five layers are linked, ordinary operational questions stop being projects. Allocating cost to the right entity, finding orphaned accounts, rotating a credit card, or onboarding a new finance lead all become queries against the same graph rather than another spreadsheet.
How to get started
Start with the layer that is causing the most pain — usually billing or access. Pull every subscription into one place, attach each one to the entity that owns it and the payment method that pays for it, and resolve the gaps. Once that loop is honest, expand outward to identities, internal services, and infrastructure. The graph compounds: every node you add makes the rest easier to reconcile.