The number is committed. What's underneath it is the question.
Maybe the changes that should have worked are behind you — the new commercial leader, the strategy process that named the right problems, the product investment aimed at the gap buyers kept naming, the repositioning meant to cut through a market where every vendor sounds the same. Each one moved something. None of them compounded.
Maybe the changes are still ahead — new solutions coming to market, a commercial seat in transition, a board expecting a number the machinery doesn't deliver yet.
Either way: your revenue is moving. It is not compounding.
Vince King
Founder, Align Growth Advisors
Built in the seat — three exits and five digital health engagements. One framework, designed so the work holds without me in every room.
I build the architecture that makes value visible, defensible, and measurable for the buyer — and monetizable for you.
Durable ARR is what equilibrium between value realized and value monetized produces. Most companies build the seller side and call it the system.
A capable team, running correctly, not compounding.
Here's how I think about this — and what I saw when I got called into a PE-backed digital health company last year. The CEO read it as a commercial execution problem. He wasn't wrong. It was a commercial execution problem. But the condition sat one layer underneath the commercial process, where none of the functions could see it from their own seat.
The business was missing targets. Leadership was asking the questions you'd expect: do we have the right sales leaders, the right ICs, are we pitching the right product. Every question was fair. None of them were pointed at the thing producing the miss.
A capable team running the motion that had always worked. Same conversations, same buyers, same product, into a market that had changed underneath them. The motion was correct for the business they used to be, not the business they were trying to become.
Under pressure to perform with targets they couldn't confidently set. Demand was legacy tradeshow-based and expensive, top of funnel declining, deals stuck. Doing the work, but unable to tell the CEO what success looked like or what investment would move it.
CEO and board support for innovation. CPO driving the roadmap. Still re-explaining the value every SLT meeting, with friction about launch timing. Air cover at the top of the company, and no shared decision framework at the altitude where trade-offs actually got made.
Watching pipeline decline and Marketing spend grow, asking what the return was and what was shrinking the pipeline. Right questions at the wrong altitude. The cause sat upstream of Finance's data.
If you've sat in this SLT meeting, you know what happened next. Sales spoke from their numbers, Marketing from the funnel, Product from the roadmap, Finance from the return — each position grounded in the metrics that function answers to. The missing piece was a shared orientation that would let four correct positions resolve into alignment. Without it, every decision surfaced the same trade-offs and returned to the next meeting unresolved.
No one in that room was failing. The team was running without the operating logic that sits underneath the commercial process — and what that produces is value owned by no one: outcomes buyers realize but can't take credit for to their own board, differentiation that exists in the product and disappears before it reaches the buyer's economics.
The question that would have given the SLT a shared orientation — and that nobody had asked yet — was simple enough that the team answered it quickly once it was on the table:
What's the value to the patient if we connect one more to our network?
That's a number. Patients seen, revenue per provider, capacity per facility. The team didn't have it because no one had asked the question in that order.
And the answers were what told Sales what to sell, Marketing what demand to generate, Product what to prioritize, and Finance what to measure the return against. Once they existed, the four correct positions resolved into one direction. Decisions held. The same trade-offs stopped returning to the next meeting. The commercial process stopped producing transactions and started producing a compounding motion.
Underneath that question sat two that every business has to answer. If you performed one percent better tomorrow, how would your customers feel it and experience it? And how would you hold the business accountable for executing against that? At that company, the patient was the connective tissue between the two. Somewhere else it's something different — but the two questions don't change.
I run every engagement against two things. The value the customer is realizing — and whether they can take credit for it in their own business. The value we're monetizing — and whether we're doing it in a way that compounds with the first. They don't have to be equal. They have to be in equilibrium. When they are, the business produces Durable ARR. When they aren't, it produces growth that doesn't compound, no matter how correctly each function runs its process.
At one company, the question wasn't whether to expand from the legacy buyer to the enterprise buyer. The board wasn't going to dilute, the market wasn't going to get easier, and we were protecting EBITDA against an exit multiple. The equilibrium ran against time, not just against trade-offs.
Every decision a leadership team makes — pricing, product, hiring, a new market, a new channel — runs through one question. Does this drive value the customer can take credit for, and revenue we can monetize against it? If not, what are we doing?
Surfacing the question is the easy part. The harder work is bringing the team into the answer — including the people whose identity was built on the prior model, who need to come into the new one without being made wrong by it. The architecture doesn't land if the people inside it stay where they were.
The architecture I built to make this run consistently is the Enterprise Client Value Framework. It's the shared orientation that lets correct functions resolve into one direction, and the compounding motion that produces Durable ARR.
Built so the execution is repeatable.
Built so the work holds without me in every room.
One problem. It shows up differently.
I get called in for all sorts of reasons, and they turn out to be the same problem. Value realization and value monetization have come unmoored — and which one a leadership team is living depends on where they sit.
Same diagnosis, same architecture, different situations. Here's what compounding looks like once the architecture is in place.
The framework I built so this holds.
I built this in the seat. Twenty-five-plus years of leadership spanning commercial and operating functions in digital health — three exits, a P&L scaled from $15M to over $1B at one of them, and five operating seats since. The framework is the architecture I kept rebuilding, company to company, until it held without me in every room. The advisory practice came after — productized from the operating seat, not the other way around.
Before anyone hires this, they ask the same quiet question: how is this different from running a strategy engagement, or from just making the hire? The CEO of a PE-backed digital health company answered it on the last day of an engagement: "somebody on the outside with a very specific agenda, who is not open nor accountable for ten thousand things… I've never been able to get this work done here." That's the difference in the buyer's words. A strategy engagement produces the analysis and leaves before it has to operate. A single-slot hire fills one seat — and this problem sits upstream of any one seat.
What you're hiring here is the operator. The framework is how the operator's work holds after the engagement — built so the execution is repeatable, built so the work holds without me in every room.
The architecture is the Enterprise Client Value Framework — the operating logic that sits underneath the commercial process. It holds every function — Sales, Product, CS, Finance, Operations — accountable to the same two questions: what value is the customer realizing and taking credit for, and what are we monetizing against it. When those two stay in equilibrium, the result is ARR that holds through renewal and survives ownership change — Value Realization ↔ Value Monetization → Durable ARR. Individual components of this exist in the market. The integration as a complete operating system is the whitespace.
Three architecture moves do the load-bearing work. Each one starts where the same trade-offs keep returning.
Value Alignment
Differentiation must be diagnosed before it is designed.
Four functions can each be right and still pull in four directions. The work starts upstream of the commercial process: surface the organizing question the team hasn't asked yet, define the value unit it gets answered in, and translate that unit into the language every function operates against. Sales knows what to sell, Marketing knows what demand to generate, Product knows what to prioritize, Finance knows what to measure the return against.
The Operating Contract
The Point of View and the Revenue Map working in concert.
A new value model only lands if the people inside the company come into it — including the ones whose identity was built on the prior model. The Point of View names where the value is — on its own, that's positioning. The Revenue Map converts it into an operating contract: the value mapped to the revenue it produces, with named owners, so every function answers to the same thing — what Sales sells against, what Product prioritizes against, what CS delivers against, what Finance measures against.
Expansion Model
Value must be deliverable before it is monetized.
Expansion overestimates when near-term revenue and long-cycle build get counted as one number. Two buyer populations, separated by structural condition: one reachable with existing capability today — revenue now (Activate); one requiring a purpose-built pathway, where investment precedes revenue and break-even logic governs the path (Build & Expand). Separating the two keeps the business case honest, and each population gets monetized against the value it can actually realize.
The architecture produces artifacts at multiple altitudes — each one answering a different question at a different altitude. The Customer Business Case is the central one: the artifact that ties Value Realization and Value Monetization to the buyer's commitment and the buyer's measurement of delivery.
Two moves produce it. First, an upstream perspective reset — the calculator exposes what the buyer is currently carrying: cost and opportunity sitting outside the frame they've been buying in. The buyer's read on the problem gets bigger, and the value the seller can monetize grows with it — one move, both sides.
A calculator alone gets misread as a sales tool. Inside the architecture, it's the instrument that converts the reset problem into a model the buyer owns — adjusted in the room, signed off before execution.
Calculator used to expose the opportunity at the altitude that makes the actual problem visible. Population sized. Per-unit realizable value attached. Buyer's frame on the problem changes — from what they're currently selling to what they're currently carrying. The seller's frame on the opportunity changes at the same time — from monetizing against the existing unit to monetizing against the realigned ceiling.
Seller and buyer reach shared understanding of exactly what problem is being solved and what the buyer is doing about it today.
The buyer names how they'll measure whether the problem got solved. Sets the realization measurement.
Solution shaped to the buyer's actual problem, sized to the realization the buyer will measure against.
First-pass model. The input to the joint work, not the output.
Buyer adjusts inputs in the room. Output changes live. Model becomes theirs.
Published, fixed. Inputs the buyer cannot move because they're anchored to public reference points.
Confirm with partner. Inputs the buyer adjusts inside their own organization with a named owner.
Openly adjustable. Inputs the buyer sets in the room. Their numbers, their assumptions, their commitment.
A contract the buyer defends internally. It holds across renewal because the buyer set what was theirs to set.
The framework is the architecture. An engagement is how we deploy it.
How an engagement actually runs.
I work as an operator alongside the leadership team. The work runs from inside the seat — fractional or full-time — not from across the table. Engagements I've run have stayed inside the SLT, inside the operating cadence, inside the rooms where the trade-offs actually get made. The architecture is the deliverable; the operator-alongside posture is how it gets installed.
At one company, the CEO and I both went in believing we were running a growth motion. The framework, working through the Revenue Map and the buyer lens together, surfaced inside the first weeks that the play was a retention motion built around P&L architecture and solution expansion, not new logos.
That work has run from a President, COO, or GM seat — where commercial, product, finance, and CS sit in the same accountability — and from CGO/CCO/CRO seats structured with single-seat cross-portfolio authority rather than single-slot scope. It has also run in advisory engagements, where the architecture gets installed alongside the operator who's going to own it. And it has run on the buy side — in deal review and diligence, where the question is whether a company's value architecture holds under the ownership thesis: whether its customers can see, credit, and measure the value they realize, whether the monetization is conditioned on that, and whether the ramp is earned or assumed. The same lens that builds the architecture inside a company tests it from outside one — pre-LOI, through integration, and in the first hundred days after close. The mode follows what the company actually needs. The posture doesn't change.
The work runs on three moves, regardless of the seat.
I surface the upstream organizing question. The one the leadership team has not asked yet, and that the recurring trade-offs are the symptom of. Naming that question is what gets every function pointing at the same thing instead of resolving each trade-off in isolation.
I install the architecture moves. Not as deliverables on a slide, but as operating discipline the team carries forward. The Point of View becomes the contract every function answers to. The Customer Business Case becomes the artifact every deal runs through.
The team has built the artifacts with me. Calculators, business cases, the Customer Business Case process itself. Produced inside the work, not handed over at the end of it. The people who will run it after me are the ones who built it.
By the time the engagement closes, the leadership team is making decisions from the same operating logic without my prompting.
If the diagnosis sounds like yours.
If your commercial motion isn't compounding — let's talk.
Always open to a conversation about the work.
First conversations run about 30 minutes. We work the problem you're actually carrying.