$200M of spend, hiding in the vendor book

A wealth management roll-up built a large platform through dozens of acquisitions. Every deal added vendors nobody managed. A six-week Outerland Blueprint quantified the opportunity, designed the future-state operating model, proved it with a working prototype, and produced build-ready requirements.

$200M
Annual spend brought under management
$12–24M
Modeled recurring annual savings path
90%
Vendor demand targeted through one front door

Savings benchmark per Ardent Partners, corroborated by Bain & Company (8–12%).

The Problem

Procurement built for a boutique,
spend built by a serial acquirer

The roll-up model creates extraordinary enterprise value and a specific liability: every acquisition arrives with its own vendor book, and none of it passes through a common intake. Roughly $200M of annual third-party spend sat outside procurement.

What we found
  1. Ad hoc intake by email, chat and hallway conversation
  2. Security tiering by spreadsheet, run after commitment
  3. Every contract reviewed by hand
  4. Invoices paid with no purchase order or contract match
  5. Firm-wide silent renewals and orphaned vendor owners
Why it mattered
  1. Recurring cost is capitalized
  2. Savings compound at the deal multiple
  3. Every silent renewal erodes the synergy case
  4. Procurement is where cost synergies are captured or lost
  5. You cannot deploy AI against spend you cannot see
The Blueprint

Define the work,
then build the tool

Six weeks, sitting at the pre-build control point between the business and any platform decision: Align · Map · Model · Prioritize · Prove · Hand Off.

StageTodayFuture state
Demand & IntakeEmail, chat, verbal. No routing or audit trail.Structured Front Door, auto-routed by spend, risk and category
Sourcing & SelectionNo RFP framework; procurement bypassed.Threshold-based RFP triggers; scan of the existing tech footprint
Risk & DiligenceManual spreadsheet tiering, run too late.Questionnaire auto-issued at intake; risk score drives diligence depth
ContractingEvery contract reviewed by hand.Clause library and enforced signatory matrix; e-signature auto-triggered
OnboardingAnyone could create a vendor; data entered after the fact.Setup gated by clearance and signed contract
PaymentNo purchase order or contract-to-invoice match.Match enforced end to end; AP handles exceptions only
Lifecycle & ExitSilent renewals; orphaned vendors.Risk-tiered renewal alerts; ownership review; auto-deactivation
What Was Delivered

Four outputs,
not a deck

Business case

The opportunity quantified against sourced benchmarks, with the success measures the programme would be held to.

Operating model

A seven-stage future-state source-to-pay framework covering every vendor type, from a SaaS subscription to an acquisition-inherited relationship.

Validated experience

The Front Door: one structured intake for all vendor demand, delivered as a working application design with role-aware screens and piloted across technology, legal, finance, services and marketing.

Execution-ready requirements

A full technical specification and a scored automation backlog, sequenced foundation-first, with one vendor record tied across ERP, risk, contracts and accounts payable.

The Result

A build-ready handoff,
not a recommendation

What the organization walked away with

Operating model
One shared model across procurement, finance, legal, infosec and accounts payable. Agreed, not proposed.
Proof
A validated future-state workflow, demonstrated with a working prototype that real users across five functions had already used.
Path to execution
A package complete enough to build in-house, select a vendor against, or configure a platform already owned, plus a clear route to vendor control, automation and later AI deployment.

The value is not the document. The value is that the requirements are used to guide execution, de-risk implementation, drive adoption and capture the modeled return.

See how the Blueprint works →Source-to-Pay workflow & automation →

Start a Blueprint

A 30-minute call to understand the problem and tell you honestly whether a Blueprint is the right next step.

Talk to Outerland
hello@outerland.ai