For private-equity operating teams

Know what every company spends on AI and what it can show for it.

Compare AI cost, governed activity, business results, and safety across participating companies. Prompts, keys, customer records, and local controls remain separate.

Portfolio operating review Company-approved
Illustrative 30-day reporting window · USDWhere management attention is needed
Fictional values
Observed AI cost$72.4k 8.2% vs. prior period
Spend under a hard limit96%6 participating companies
Spend with result evidence71%4 management baselines
CompanyObserved costControlResult evidenceNext review
Atlas$18.6k94%82%Review ready
Harbor$14.2k88%61%Source follow-up
Juniper$21.4k76%74%Control review
Meridian$18.2k91%46%Result gap
Cost · work · results · controlNo prompts, provider keys, or employee ranking
One plain-language review: cost, work supported, measured result, and operating safety
Separate company approval for operations, provider-statement comparison, and business outcomes
A short evidence-based action queue while local management keeps control
The four-question review

Replace token totals with a management conversation.

Each answer names its source and reporting scope. A blank answer becomes the next action instead of a fabricated score.

01

What did it cost?

Review observed provider cost, gateway fees, approved spend, coverage, and any company-approved statement comparison.

02

What work did it support?

Named workloads, governed requests, model mix, owner role, and the business purpose the company selected.

03

What changed?

Compare the baseline with the latest result. The report names the source quality and makes no automatic claim that AI caused the change.

04

Was it responsible?

Budget discipline, failures, fallback, safety interventions, essential controls, and the evidence still missing.

A bounded 12-week operating cycle

Start with three to five participating companies.

The 30-day example above is one reporting window inside a proposed 12-week design-partner review. Before connecting data, the parties agree on company owners, approved measures, data sources, responsibilities, success criteria, and commercial terms.

Weeks 0–2

Agree on the questions and boundaries

Name the participating companies, executive recipients, four operating questions, consent scopes, owners, identity requirements, retention expectations, and stop conditions.

Weeks 3–6

Connect records without pooling company data

Each company controls its own workspace, provider credentials, budgets, and approvals. The portfolio receives the operating, finance, and outcome totals that company has approved.

Weeks 7–12

Run the management review

Deliver the comparable operating view, company drill-down, action queue, and audience-specific executive report. Record decisions and evidence gaps for the next cycle.

Success is a repeatable decision process, not a manufactured ROI claim.

The review identifies each initiative owner, approved and observed spend, supported results, weak controls, missing proof, and management's next decision.

Discuss the review
In plain language

See what each company spent, what the spend supported, and what changed.

AI Gateway HQ connects four questions in one review: What did AI cost? What business work did it support? What measurable result changed? Was the usage safe and reliable? Gateway records cover the operating activity, while each company supplies the business baseline and result.

The portfolio outcomeOperating partners can find responsible operators, missing evidence, uncontrolled spend, and initiatives ready for a continue, change, or stop decision. Each company retains its own security, identity, provider, payment, and data controls.
For the operating team

Make the management conversation comparable, not the companies.

Every company is reviewed with the same evidence vocabulary, while its goals and baselines remain company-specific. The output is an action queue, never an employee leaderboard or universal AI score.

What administrators configure
Company permission

A company owner must approve aggregate reporting and can revoke it immediately. No portfolio view appears before that approval.

Separate outcome permission

Business measures require a second, explicit company-owner approval. Aggregate operating access alone reveals no baseline, current result, owner role, or evidence strength.

Comparable operating facts

Review observed cost and activity, budget discipline, reliability, model mix, and essential safeguards using the same definitions.

Company-specific results

Pair a named workload with its business purpose, accountable role, baseline, approved spend, latest result, and evidence source.

Actionable review

Turn missing limits, weak evidence, unexplained cost, failures, fallbacks, and missing safeguards into follow-up work. The report does not issue an automatic verdict or change live settings.

What happens to each request
  1. 01
    Observe

    The gateway measures cost, requests, model choice, budget posture, failures, fallbacks, and safety interventions for named workloads.

  2. 02
    Define

    A company names the result that matters, its owner, the before-AI baseline, target, evidence source, and approved monthly spend.

  3. 03
    Confirm

    The owner or a connected system records a bounded period result; corrections are voided and replaced instead of erasing history.

  4. 04
    Review

    The portfolio sees only separately approved rollups and a company-level queue showing what is ready, incomplete, or needs attention.

See the working control

Move from the portfolio signal to the evidence behind one company for portfolio oversight.

For portfolio oversight, a full-page company view connects consented spend, named work, outcome evidence, operating controls, and explainable exceptions without exposing prompts, credentials, or individual activity.

  • This portfolio oversight view runs in the working customer console
  • Exercised with safe OpenAI- and Anthropic-compatible simulators
  • The portfolio oversight capture excludes keys, prompt text, responses, and private email
Follow the operating workflow
Company evidence drill-downMove from the portfolio signal to the evidence behind one company for portfolio oversight.

For portfolio oversight, a full-page company view connects consented spend, named work, outcome evidence, operating controls, and explainable exceptions without exposing prompts, credentials, or individual activity.

What administrators can change

What a portfolio team can review.

Operating partners see only company-approved rollups. Each company keeps control of its local settings and source data.

01

A shared view without a shared data pool

Provider keys, prompts, responses, customer identities, payment details, routes, and policies stay inside each company account. The portfolio view receives only the totals each company approves for review.

02

Connect spend to a result without inventing ROI

The gateway supplies cost, activity, reliability, and policy facts. A business owner supplies the outcome baseline and latest result. The report shows source quality, the reporting period, approved spend, and any missing proof. It does not claim that AI caused a result unless the evidence supports that conclusion.

03

Start with the decisions that need attention

Start with initiatives that have spend but no reported result. Also flag weak evidence, exceeded approvals, missing budgets, unsafe usage, repeated failures, excess fallback, and results that do not support more investment.

Evidence, not assertions

Review every company on consistent terms.

The portfolio command center brings together operating activity, company-approved statement summaries, and business results. Reporting gaps remain visible, and each company retains control of what it shares.

Review security boundaries and current status
  • Company approval and revocation recorded for every reporting relationship
  • Comparable activity, configured cost, budget, reliability, model mix, and essential safeguards
  • Exact-versus-estimated cost coverage shown with the reporting window and event limit
  • Separately consented business baselines, period results, accountable roles, and evidence-strength labels
  • Outcome records with an audited correction history
  • Prompts, responses, credentials, identities, payment details, routes, and policies excluded
  • Executive follow-up queue linked to the company that owns the evidence and change
Questions teams ask

What operating partners need to know.

Access, evidence, and decision boundaries for a portfolio review.

Can a fund see every portfolio company's prompts?

No. The portfolio report contains approved operational aggregates. Provider keys, prompt and response bodies, customer identities, payment details, and local route or policy configuration are excluded.

Can a parent policy override a company's security rule?

Not in the current portfolio release. The portfolio view identifies gaps and supports operating review; company administrators retain control of local routes, budgets, and security policy.

How should external benchmarks appear in a portfolio review?

Only as labeled, reviewed context. Reports keep third-party research separate from gateway facts and company-supplied results. Every benchmark names its source period and method.

Can it tell us whether AI caused a business result?

No. It correlates gateway-observed activity and spend with a company-supplied baseline and period result for the same named workload. The source and evidence strength remain visible, and the report explicitly does not infer causation.

What can a portfolio team evaluate now?

Start with the guided multi-company example. After each company approves aggregate reporting, review spend, activity, budgets, reliability, model mix, and safeguards. A separate approval can add business baselines, current results, source strength, and review readiness.

Start safely

See the portfolio view with realistic company data before connecting a company.

Use the no-login guided example to inspect the measures and company evidence, then request a focused briefing for your fund or operating team.

Request the briefing