For finance leaders
You are scaling a portfolio
Every holding reports revenue differently, so you cannot compare them or reuse what worked in one at the next.
What is usually wrong underneath
An operating partner sees the same revenue problems in one holding after another: a stack bought tool by tool, a forecast kept by hand, discounting nobody can size. Each company solves them alone, from scratch.
The numbers that reach the sponsor are not comparable, because each company defines a stage, a qualified lead, and a renewal in its own way. A portfolio view built on them compares definitions, not performance.
A shared method fixes both. The same diagnostic, run the same way, gives each management team its own findings and gives the sponsor one comparable view. What is built in one holding becomes a pattern for the next.
What we would build for this
By area of work: Transaction readiness; Forecast, capacity, and board; Pricing and quote-to-cash.
- Entry and exit readiness. The commercial questions a buyer's diligence team asks, answered from live data.
- Retention reporting. Gross and net revenue retention computed from billing records.
- AI ROI proof. What your AI and revenue-tool spend returned, measured in your own systems.
- Pricing intelligence. Price guidance built from your own transaction history.
- Relationship transferability scoring. How much of each account relationship lives in your systems, and how much in one person.
The Margin Diagnostic
Every engagement starts with a fixed-price diagnostic. You keep the findings whether or not you continue.
The price is fixed per diagnostic and quoted on the first call.
What you walk away with
- Realized price against list price, by segment, seller, and product
- What your AI and revenue-tool spend returned, measured in your own systems
- The approval and quoting steps where discount leaks
- A ranked list of fixes, each with the evidence behind it
- A scoped build plan you can run with us or without us
How it works
We read quoting, discounting, billing, and tool-usage data through scoped, read-only access. We reconcile what was quoted against what was invoiced, and tie tool spend to revenue measured in your own systems.
Data access
Read-only service accounts on credentials you own. Access is time-boxed, logged, and revoked when the diagnostic ends.
Who it is for
- Finance leaders who suspect discounting is unmanaged
- Companies facing a forced CPQ migration
- Leaders whose board or sponsor wants proof of what AI spend returned
- Companies preparing for a transaction
Who it is not for
- Companies with no quoting or discounting data in a system
- Teams looking for a pricing strategy study rather than a data review
What happens after the diagnostic
Build. We build the ranked fixes inside your systems, on credentials you own. The person who runs your diagnostic leads the build.
Managed operations. If you want us to run the layer with your team, we do, under the same documentation you hold.
Migration. When a platform change is forced on you, we carry the rules that matter across and drop the ones that do not.
Ownership. You keep what we build: the data models, the workflows, and the documentation. Nothing depends on us staying.
Objections, answered
Will management teams see this as the sponsor checking up on them?
Each team keeps its own findings and its own system, and gets value from them directly. The sponsor sees a comparable summary. We are open with both sides about who sees what.
Can we start with one company?
Yes, and we recommend it. One diagnostic in one holding shows whether the method is worth running across the rest.
We already use an operations consultancy. How is this different?
A consultancy advises on the operating model. We build the data layer inside each company's systems and leave it running. The two fit together well.
What do we own at the end?
Everything. The data models, the workflows, the documentation, and the credentials stay in your environment. If you stop working with us, the system keeps running.
What access do you need?
For a diagnostic, read-only service accounts on credentials you own. Access is time-boxed and logged, and you can revoke it at any moment. Write access is scoped per area of work during a build and only with your approval.
Who will do the work?
We do. The person who runs your diagnostic leads the build that follows.
What happens if you are unavailable?
You own everything we build: the data models, the workflows, the documentation, and the credentials, all in your environment. Your team or another firm can run it without us.
Start with a fixed-price diagnostic
It begins with a free 45-minute call that commits you to nothing. You leave the diagnostic with a ranked plan you can run with us or without us.