Private equity03 · Operate

Every portfolio company.One operating view.

FinOps and cyber remediation on the same agents, the same evidence model and the same approval gates - deployed once and reused across the portfolio.

Illustrative · example data
FUND III · 12 COMPANIESAtlasNorthwindHelixQuarryVelaOrielKestrelMosaicTernLumenBrookSableAPPROVALSNorthwindRightsize prod clusterverifiedVelaPatch payments-svcverifiedLumenReclaim 140 seatsverifiedACTIONS VERIFIED THIS QUARTER35363738

Two workflows

Choose where to start.

Most firms begin with one workflow at two or three companies, then extend the same setup across the fund.

Portfolio FinOps Command Center

Create one operating view of technology spend across the portfolio.

OpenAna brings cloud, SaaS, ownership, and operating context together so portfolio teams can find opportunities, route decisions, and verify approved actions.

01

No common baseline

Every portfolio company reports cloud and SaaS spend differently, limiting meaningful comparison.

02

Distributed ownership

Finance, engineering, procurement, and business leaders each hold part of the decision context.

03

Recommendation fatigue

Cost tools generate lists, but owners still need to validate risk, timing, and business impact.

04

Savings without proof

Approved actions are often logged once and not checked against subsequent bills or service health.

Operating workflow

From signal to
verified outcome.

  1. 1

    Connect spend data

  2. 2

    Normalize & benchmark

  3. 3

    Investigate variance

  4. 4

    Prepare actions

  5. 5

    Approve changes

  6. 6

    Verify outcomes

01

Portfolio spend normalization

Map cloud accounts, SaaS contracts, owners, and business units into a consistent operating taxonomy.

02

Anomaly investigation

Detect unusual changes, assemble likely drivers, and route questions to the right owner.

03

Rightsizing preparation

Combine utilization, commitments, architecture, and service criticality into a reviewable recommendation.

04

SaaS license intelligence

Surface unused seats, overlapping tools, renewal windows, and unclear ownership.

05

Approval orchestration

Route each action by materiality, risk, company, and responsible executive.

06

Outcome verification

Compare approved actions with subsequent cost and service signals and preserve the evidence.

What changes for the team

  • Consistent technology-spend visibility across companies
  • Decisions connected to technical and business context
  • Clear accountability from recommendation through approval
  • Verified results rather than spreadsheet-only savings

What the agent never decides alone

  • Read-only connectors at the start
  • Company-level data boundaries
  • Named financial and technical approvers
  • No infrastructure change without approval

Start small

A focused
first deployment.

  1. 01

    Two to three portfolio companies

  2. 02

    Cloud billing plus one SaaS source

  3. 03

    A defined spend category

  4. 04

    Finance and engineering owners

OpenAna vs. point tools

One agentic layer vs.
separate vendors.

CapabilityOpenAnaPoint tools
One control plane for spend and cyber risk
Evidence-linked prioritization
Prepares fixes and rightsizing for approval~
Same governance model reused per company
Read-only start, human-approved actions~

Next stage · 04 Platform

Ancore investment platform

The fund’s memory: documents, deal pipeline, DDQs and LP reporting, searchable in plain language.

Illustrative · example data
change-of-control clauses across Fund IIIAsk31 CLAUSES · 12 COMPANIES · 4,812 DOCUMENTS SEARCHEDMSA_Northwind_2024.pdf§14.2 assignment on change of control[1]SaaS_Agreement_Vela.pdf§9.1 termination right on acquisition[2]Supply_Helix_2023.pdf§22 consent required for transfer[3]

Ready when you are

Start with one workflow.
Scale it across the fund.

Two or three companies, one data source each, named owners. We’ll scope it around the systems you already run.