← THE PORTAL
ECONOMIC VALUE CONTROL · PROCUREMENT / SPEND GOVERNANCE

From a renewal calendar to a spend-leakage loop.

Today, spend is a renewal calendar and exposure is visible only after lock-in. In Future Finance, utilization and pricing drift are monitored per vendor, renewal packets arrive ahead of every negotiation, and leakage is surfaced before it compounds.
LEARNING RETURN 01 SIGNAL drift detected · utilization {D} price 02 EXPOSURE renewal exposure · overpay sized 03 CHOICE renew {D} renegotiate {D} cut 04 OWNER ACTION procurement {D} budget owner 05 OUTCOME was leakage stopped? EVIDENCE GATE 06 · VALUE PROOF avoided spend validated The governed loop, cast for this function – the same circuit as every Finance function, carrying spend leakage risk instead of a report.
01 · THE TRANSFORMATION

From a renewal calendar to a spend-leakage loop.

TODAY
A renewal calendar and periodic spend analysis.
Exposure visible only after the renewal locks in.
Utilization guessed at, not measured.
Shadow and duplicate tooling undetected.
IN FUTURE FINANCE
Utilization and pricing drift monitored per vendor
Renewal packets ahead of every negotiation {D} leverage inside
Commitments checked against actual consumption, continuously
Shadow spend and duplicate tooling surfaced automatically
SPEND LEAKAGE → ACTION ROUTE
02 · WHERE TO START – THE WORKFLOWS, RANKED

Five workflows. One operating pattern.

Every workflow in this function becomes the same governed loop – cast differently. Below, each one in full: what it becomes, who does what, what it needs, and where the human boundary sits.
RANKED BY · ownership (who holds the lever) · value (from this domain’s sizing) · autonomy ceiling (Tier 1 = human-only → Tier 4 = highest permitted autonomy) · control sensitivity · scope (core vs conditional)   weighting leans value + ownership
AGENTS prepare DETERMINISTIC SYSTEMS calculate HUMANS approve OWNERS execute FINANCE validates
1Tier 3 of 4
Vendor renewal governance
The renewal calendar becomes an action workflow {D} renewals surfaced ahead of the negotiation with leverage, benchmarks, and exposure inside, and owners acting before the date.
Who does what
Agentsprepare the renewal packet with leverage and exposure
Systemscalculate spend baseline and run-rate
Humansapprove the negotiation or demand action
Ownersbudget owners reduce demand or renegotiate
Financevalidates avoided spend against baseline
ARCHETYPE signal-to-actionCADENCE renewal-drivenDATA vendor · contract · usageSENSITIVITY medium
THE BOUNDARY · owners approve and act before the renewal date; Finance validates avoided spend, never claims it unearned.
OWNERSHIP Finance co-governsVALUE High – feeds the sized poolAUTONOMY Tier 3 of 4CONTROL Medium sensitivitySCOPE Core
2Tier 3 of 4
Software license and entitlement optimization
License waste becomes an owner-action workflow {D} utilization and entitlement gaps surfaced, sized, and routed to the owner who can reclaim them.
Who does what
Agentssurface under-used licenses and entitlement gaps
Systemscalculate utilization against entitlements
Ownersfunctional owners reclaim or downgrade
Financevalidates the realized reduction
ARCHETYPE signal-to-actionCADENCE continuousDATA usage · entitlement dataSENSITIVITY medium
THE BOUNDARY · functional owners execute the reclaim; Finance validates, it does not cancel licenses by claim.
OWNERSHIP Finance validatorVALUE High – feeds the sized poolAUTONOMY Tier 3 of 4CONTROL Medium sensitivitySCOPE Core
3Tier 3 of 4
Contractor spend governance
Contractor run-rate becomes governed {D} run-rate monitored against plan, drift routed to owners, with business owners acting on the demand.
Who does what
Agentsmonitor contractor run-rate and flag drift
Systemscalculate run-rate against plan
Ownersbusiness owners act on demand
ARCHETYPE cadence-to-decisionCADENCE monthlyDATA vendor · HR · GL · POSENSITIVITY medium
THE BOUNDARY · business owners act on the demand; Finance co-governs the run-rate, it does not staff.
OWNERSHIP Finance co-governsVALUE Medium – run-rate disciplineAUTONOMY Tier 3 of 4CONTROL Medium sensitivitySCOPE Core
4Tier 3 of 4
Third-party spend consolidation
Fragmented spend becomes a routed consolidation opportunity {D} duplicate vendors and consolidation candidates surfaced, with sourcing decisions kept human.
Who does what
Agentssurface duplicate and consolidation candidates
Systemscalculate the consolidation opportunity
Humanssourcing decisions are human-owned
ARCHETYPE scenario-to-choiceCADENCE recurringDATA vendor master · spendSENSITIVITY medium
THE BOUNDARY · sourcing decisions are human-owned; agents surface the opportunity, they do not consolidate vendors.
OWNERSHIP Finance co-governsVALUE Medium – consolidationAUTONOMY Tier 3 of 4CONTROL Medium sensitivitySCOPE Core
5Tier 2 of 4
Procurement policy exceptions
Spend policy exceptions become governed approvals {D} exceptions surfaced against policy and delegation-of-authority, with human approval required.
ranked last: a control workflow, not a value pool.
Who does what
Agentsassemble the exception with policy context
Systemscheck against policy and DOA
Humanshuman approval required
ARCHETYPE policy-to-complianceCADENCE event-drivenDATA procurement policy · DOASENSITIVITY medium
THE BOUNDARY · exceptions are human-approved; the workflow enforces policy, it does not waive it.
OWNERSHIP Finance policy ownerVALUE Control valueAUTONOMY Tier 2 of 4CONTROL Medium sensitivitySCOPE Core
03 · THE SIZING – FULL EVIDENCE TRAIL

The number, carried the way every claim is carried.

The figure on the front page arrives here as what it is – a governed packet. Range, basis, inputs, benchmarks, derivation, assumptions, and the strongest objection to it, all in one place.
PROCUREMENT SIZING PACKET
PROC-SZ-06 · SOFTWARE-SPEND POOL
OUTSIDE-IN
RANGE
$8–22M / yr · annual recurring
BASIS
Hybrid · Confidence: Medium-Low
WHAT IT IS
Governed spend loops surface renewal overpayment, under-utilization, price drift, and duplicate/shadow SaaS before renewals lock them in. Applied to addressable internal software/SaaS spend, a conservatively haircut share is typically recoverable at renewal. Conditioned on procurement owners acting before renewal dates. Cloud-infrastructure governance is excluded {D} it is co-owned with Engineering.
INPUTS
Employee headcount of a representative large-cap SaaS company; internal software/SaaS spend derived from a per-employee benchmark
BENCHMARKS
Unused/underused SaaS licenses ~30% (30–53% range; Gartner-attributed / Zylo / BetterCloud, corroborative) · avg enterprise waste on unused licenses (Zylo / JumpCloud)
DERIVATION
1 · addressable software/SaaS base = derived from per-employee spend
2 · recoverable-at-renewal share = 9–25% (heavily haircut from the 30–53% headline)
3 · range → ~$8M/yr low · ~$22M/yr high
ASSUMPTIONS
(1) derived software base (Tier 3 per-employee rate) · (2) 9–25% recoverable (haircut) · (3) cloud-infrastructure spend explicitly excluded
SENSITIVITY
The recoverable-share moves it most – halving to 4.5–12.5% gives ~$4M–11M/yrsanity bound: high end ($22M) is ~25% of the derived base – at the recoverable ceiling for a mature buyer, and cannot exceed the spend base
THE ATTACK
“Vendor waste studies are marketing.” — Agreed: the 30–53% figures are labeled Tier 3, used only for corroboration, and haircut to a 9–25% recoverable share on a conservatively derived base.
OUTSIDE-IN · ILLUSTRATIVE · SUBJECT TO VALIDATION
Modeled on a Representative SaaS Company · outside-in, illustrative
A target-state vision · every value claim subject to validation