You have made the changes that should have worked.
A new commercial leader brought in to own the number. A strategy process that named the right problems and produced the right initiatives. A product investment targeted at the gap buyers kept naming. A repositioned message designed to cut through a market where every vendor sounds the same.
Each one moved something. None of them compounded.
Your revenue is moving. It is not compounding.
Vince King
Founder, Align Growth Advisors
One framework, built across three exits and five digital health engagements. Designed so the work holds without me in every room.
I build the architecture that makes value visible to the buyer, defensible 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. Sales was underperforming. Leadership was asking the questions you'd expect a leadership team to ask — do we have the right sales leaders, do we have the right ICs, are we pitching the right product. Every question was fair. None of them were wrong. And none of them were pointed at the thing that was actually producing the miss.
Running the motion that had always worked. Same conversations, same buyers, same product — into a market that had changed underneath them. The team wasn't the problem. 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. The team was doing the work — but couldn't 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, and friction with the CEO about timing of new solution launch. Air cover at the top of the company. No shared decision framework at the altitude where trade-offs actually got made.
Watching pipeline decline and Marketing spend grow. Asking the right questions — what's the return on the investment, what's causing the pipeline to shrink. Right questions at the wrong altitude. The cause sat upstream of Finance's data.
The SLT was the room where all of this collided. Sales spoke from their numbers. Marketing spoke from the funnel. Product spoke from the roadmap. Finance spoke from the investment return. Each position was grounded in the metrics that function was accountable to. What was missing wasn't alignment. It was the shared orientation that would have let those positions resolve into alignment. Without it, every decision surfaced the same trade-offs and returned to the next meeting unresolved.
That's not a leadership failure. It's what happens when a capable team is running without the operating logic that sits underneath the commercial process — the orientation that would let four correct positions resolve into one direction.
Value that is real but owned by no one inside the company. Outcomes buyers realize but cannot take credit for to their own board. Differentiation that exists in the product and disappears by the time it reaches the buyer's economics.
The question that would have given the SLT that shared orientation — and that nobody in the room had asked yet — was simple enough that the team would have answered it quickly if someone had put it 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 leadership team didn't have it, because no one had asked the question in that order.
These aren't gotcha questions. They're questions the team needed to answer together, because the answers were what would tell Sales what to sell, Marketing what demand to generate, Product what to prioritize, and Finance what to measure the return against. Once those answers existed, the four correct positions resolved into one direction. Decisions started to hold. The same trade-offs stopped returning to the next meeting. The commercial process stopped producing transactions and started producing a compounding motion.
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. Those two 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 is running 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 and 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 operating logic that sits under the commercial process — 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. Four presenting symptoms.
I get called in for four different reasons. They all turn out to be the same problem. Value realization and value monetization came unmoored, and the business is presenting the symptom that's most visible from where leadership sits.
Same diagnosis, same architecture, four different presenting symptoms. Four versions of what compounding looks like once the architecture is in place.
The framework I built so this holds.
I built this in the seat. Two decades running commercial and operating functions inside digital health companies — through three exits, scaled a P&L from $15M to over $1B at one of them, and held the seat in five other operating roles since. The framework was the architecture I built to make the work hold consistently across companies. The advisory practice came after — productized from the operating seat, not the other way around.
That distinction matters because the buyer's other options are advisor-only. A strategy consultancy produces an analysis and a deck — not the operating logic that makes the analysis land inside the company. A single-slot operating hire fills one seat — and the architecture problem sits upstream of that seat. A generalist advisory practice carries range — and range without operating altitude in digital health produces strategy that doesn't survive contact with how value actually realizes between vendor and buyer.
What I sell is the operating architecture I held the seat to build. The advisory practice is the discipline of installing it alongside the operator who's going to own it.
The architecture is the Enterprise Client Value Framework. It runs across Sales, Product, CS, Finance, and Operations as a single operating system accountable to one chain — Value Realization ↔ Value Monetization → Durable ARR. Value the customer realizes compounds into value the company monetizes, and that compounding is what produces ARR that holds across renewal and survives ownership change. 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 names a structural commitment that holds across every deployment, and each one names what gets installed at architecture altitude — not the tactic underneath it.
Value Alignment
Differentiation must be diagnosed before it is designed.
The work starts upstream of the commercial process — surfacing the organizing question the leadership team has not asked yet, defining the value unit it gets answered in, and translating that value unit into the language of every function that has to operate against it. Sales, Product, CS, and Finance stop running four correct positions in four different directions and start resolving into one.
Change Management
The POV is an operating contract, not a marketing asset.
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 architecture move is installing the POV across Sales, Product, CS, and Finance as the operating contract every function answers to. That installation is the change-management work. There's no version of this where the architecture lands and the people inside it stay where they were.
Expansion Model
Value must be deliverable before it is monetized.
Two populations, separated by structural condition. Layer 1 buyers are reachable with existing capability today — immediate revenue, standard pricing, the population the business is currently serving correctly. Layer 2 buyers require a purpose-built pathway — investment precedes revenue, break-even logic governs the path. The architecture move is separating the two so the business case doesn't conflate near-term revenue with long-cycle build, and so 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. It's the artifact produced by the work that ties Value Realization and Value Monetization to the buyer's commitment and the buyer's measurement of delivery. That's the point on the chain where the architecture operates on both sides of the arrow rather than just the seller's side.
Two moves produce it. An upstream perspective-reset that surfaces what the buyer's current frame is rendering invisible — and expands the value the seller can monetize at the same time. The 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 from monetizing against the existing unit to monetizing against the realigned ceiling.
Then the process that converts the realigned problem into a contract the buyer adjusts in the room and signs off before execution.
A calculator runs at both altitudes. Upstream, it exposes a carried opportunity the buyer didn't know they owned — and the realization ceiling the seller didn't see when monetizing inside the prior frame. Downstream, inside the joint iteration step, it operates as the instrument that converts the realigned problem into a model the buyer owns.
The misdiagnosis isn't the calculator. It's the calculator without the architecture that gives it altitude.
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 in deal review and diligence, where the same lens surfaces value gaps standard diligence misses. 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 POV 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.