Start with an operating question, not a benchmark
A portfolio rollup is useful when it helps an operating partner decide where to investigate, where to set a boundary, and where to support a management team. A long table of requests or tokens without workload ownership, cost basis, control posture, reliability, and business context cannot answer those questions.
Begin with a small comparable operating vocabulary and label every measure by source. Do not present an external benchmark as portfolio evidence, a company estimate as gateway measurement, or an association as proof that one practice caused an outcome.
Keep four evidence classes separate
A credible portfolio view labels where every number came from and prevents one class from masquerading as another.
- Gateway-measured: requests, provider/model mix, configured and reported tokens, cost basis, budget adherence, failures, fallback, latency, and control coverage.
- Company-approved finance evidence: an operator-entered provider, period, and USD statement subtotal compared with retained gateway evidence; never a raw invoice or accounting approval.
- Company-supplied: named initiative, business purpose, accountable role, baseline, target, approved spend, period result, and evidence-strength label. The value record contains no uploaded document or evidence URL.
- Independent context: sourced research with publisher, sample, geography, period, methodology, and publication date.
Respect company boundaries while producing a rollup
The portfolio owner should see aggregate posture and only the company detail explicitly delegated to that role. Finance reconciliation and business outcomes each require a separate, explicit owner-approved scope; aggregate reporting alone reveals no statement amount, variance, baseline, current result, or owner role. Provider keys, statement labels, raw invoices, prompts, responses, customer identities, and payment details do not belong in a portfolio rollup. Revocation removes the associated figures from the next read. A parent template may propose a control; it must not silently weaken or overwrite a company boundary.
Turn measurement into an operating queue
Prioritize companies with unowned workloads, missing hard budgets, concentrated model spend, single-target routes, degraded credentials, repeated provider failures, spend without a current business result, or weak evidence sources. Record the recommendation, expected impact, approver, resulting change, and measured before/after period. Do not rank employees or treat request volume as productivity.