You raised the round.
You're still not standing on your own.
You hit the targets. You hired ahead of plan. You bought the growth the board wanted to see — and the engine underneath it never got built.
So the growth costs more than it returns. The forecast keeps missing. The renewal comes back lower than your team predicted. And every quarter you're a little more dependent on the next round to cover the gap the last one left.
That's not a sales problem. It's structural — and you already suspect it. You're right.
Growth at any cost isn't a strategy. It's a loan against your company's future — it serves this round and quietly mortgages the next.
The founders who get free build the revenue engine in sequence with their ARR — the right architecture for the stage they're actually in. Build it in time, and each raise becomes optional fuel toward standing on your own, instead of life support for growth you couldn't hold. A, B, and C still come. They're fuel you choose, not a rescue you need.
That's what “Win and Last” means — the engine that lets you stand on your own is the same engine that compounds the value your investors underwrote. Built right, you don't have to choose.
If you're a VC or PE operating partner, it's the same read from the other side of the table. Growth that outruns the engine caps the return — capital spent on growth that can't compound. The disciplined build is the one that pays.
Everything on this page rests on three premises. If they don't hold, none of the rest does.
Three premises. Everything below — the diagnostic, the sequence, the engagement — follows from them.
Revenue operations is no longer the CRM and the reporting. It exists to keep the revenue engine performing.
The CRM is still there. The dashboards still run. But treating them as the job confuses the instrument for the engine — a dashboard tells you what already happened; it doesn't make the engine produce. Revenue operations, done right, owns whether the engine performs at all: pipeline that converts, retention that compounds, a forecast you'd put your name on. The tooling serves that work. It was never the work itself.
Revenue Data Debt™ is what you inherit when you specialize. It collects in the seams between the functions — not inside them.
Specializing was the right call. Nobody runs Marketing, Sales, Client Success, and Client Support from a single seat past a certain size, and pretending otherwise caps the company. But every function you split off creates a seam, and the data that should cross that seam degrades a little each time it's handed off — or doesn't cross at all. Marketing's context doesn't reach Sales intact. What Sales promised doesn't reach Client Success intact. The debt is quiet, and it compounds. By the time it surfaces — churn nobody forecast, expansion that never happened — the decisions that caused it are already months old. It isn't a people failure. It's the structural cost of the specialization that made you bigger.
You don't report your way out of Revenue Data Debt. You architect your way out — and that's a distinct discipline, run by a distinct role.
You can't dashboard a seam closed. Clearing the debt means redesigning how the functions connect — what data has to cross each handoff, in what shape, enforced by the system instead of by whoever happens to remember. That's architecture, and it isn't the same job as running a function well. The revenue architect designs the connective structure, transfers it to the operators who'll run it, and leaves before anyone comes to depend on them. The measure of the work isn't a longer engagement. It's an engine that keeps performing after the architect is gone.
That's the frame. The rest of this page is what follows from it — starting with a way to see where the debt has already settled in your own engine.
Structural problems don't announce themselves. They show up as patterns — pipeline you can't trust, retention you can't predict, deals that went to someone you don't respect.
AI is the newest of these patterns and the most exposing. Engines that compound AI as leverage were already coherent before AI arrived. Engines that industrialize the wrong work, faster, were already broken — AI just made it visible.
88% of organizations use AI.
Only 1% have reached operational maturity.
The gap is architectural, not technological. Your revenue engine either absorbs AI as leverage — or industrializes the wrong work, faster.
The Revenue Data Debt™ Diagnostic is 24 statements across your four revenue functions and the six seams that connect them. About ten to fifteen minutes. A defensible read on the gap between the client data you have and the data your AI needs — and exactly where it's accumulating.
24 statements · four functions, six seams · about 10–15 minutes · nothing to sign up for
Most of what looks like a sales problem at around $5M is structural.
The reps aren't broken. The team you hired isn't broken. You aren't broken.
The engine is broken — and the engine can be architected.
Marketing optimizes for one outcome. Sales for another. Client Success for a third. Client Support absorbs whatever falls through. Finance and Product, operating from outside the revenue organization, bring their own disciplinary orientations — unit economics and forecast precision for Finance, feature velocity and roadmap optionality for Product. Each function looks productive. The company doesn't compound. By the time it shows up — churn nobody saw coming, expansion that didn't happen, renewals that quietly downgrade — the operating choices that produced it were made months ago.
No tooling fixes this. No methodology fixes this. No fractional executive fixes this by stepping into the role and operating it.
That structural fragmentation — four specialized cylinders and two support systems, each optimizing for its own outcome, with no one accountable for the seams between them — is the dominant reason most companies can't operationalize AI. The 1% aren't running better AI — they're running engines where Marketing, Sales, Client Success, and Client Support inside the revenue organization, plus Finance and Product participating from outside it, are operating as close to a singular revenue architecture as a real company gets. AI compounds in engines that were already coherent. It exposes the ones that weren't.
It is fixed by architecting the engine, transferring it to the operators who will run it, and exiting before dependence forms.
The path is sequential. Skip a stage and the next one breaks.
Most revenue problems get solved out of order. Velocity tools deployed onto unaligned organizations. Alignment programs run on data nobody trusts. Work attempted before there's clarity about what the engine is even being built to produce.
The Scale Sequence is the discipline that produces that clarity — five stages, in fixed order. The companies that escape the pattern run them in sequence.
The honest present state: clean, structured, timely data and a single source of truth. You can't know whether you're moving until you know where you started — and without it, the forecast is fiction and AI processes garbage faster.
What the baseline gets measured against. Not “more revenue” — a definition of what kind of revenue you're building, specific enough to be falsifiable.
The four cylinders and two support systems — Marketing, Sales, Client Success, and Client Support inside the revenue organization, plus Finance and Product participating from outside it — operating from one architecture, one source of truth, one shared definition of the client outcome. Reached by listening first, not announcing.
A named person answerable for each definition and each seam. The stage most often skipped — and the one that makes alignment hold when leadership changes.
The consequence of the first four being honored. The architecture running. Forecast accuracy you trust. Net retention compounding. The engine producing results without the founder as the bottleneck — and it can't be manufactured by working harder or bought with a round.
The sequence is not negotiable. Companies that try to skip stages typically end up paying for the same work twice — once in the wrong order, once in the right one.
The Future of B2B SaaS Under AI
SaaS isn't dying. It's evolving faster than your roadmap.
The loudest take is the wrong one. The verified read is more useful — and more unsettling: the ground under B2B SaaS is moving faster than most operators are repricing their assumptions. Here's where it's actually heading. Seven shifts. Every one sourced to a primary report, or cut. The rest is noise.
are resetting.
The 80% margin that defined SaaS isn't coming back.
For two decades, near-zero marginal cost gave software its 80% gross margins. AI broke that — every model call is real, variable compute. The average AI-product gross margin now sits around 52%, and the reset is structural, not a bad quarter. This is the shift that forces all the others.
gross margin · classic SaaS → AI-product average
The seat is becoming the wrong thing to sell.
When one agent does the work of ten people, charging per seat punishes your client for getting more value — and punishes you for delivering it. The live proof is already shipping: Zendesk, Intercom, and Salesforce now bill by resolution and outcome, not by login. IDC expects pure seat-based pricing to be obsolete by 2028.
is changing.
Software is moving from where you record the work to where it gets done.
The dashboard was the product for twenty years. The next layer doesn't wait for you to log in — it reads context, acts across systems, and surfaces a human only when judgment is required. Bain frames it as routine tasks moving from "human plus app" to "agent plus API" within a few years.
The moat was never the model. It's your data.
A generic model can write an email. It can't know which accounts are about to churn, which contracts will slip, or which approvals are required — that lives in your data, your workflows, your domain. As models commoditize, the defensible thing moves from the interface to the depth underneath it.
is changing.
Your client can now build the thing you sell.
AI cut the cost and time of building software by two to three times. A third of teams have already replaced at least one SaaS tool with a custom build, and most plan to build more. But it's concentrated — workflow automation, internal admin, BI. Deep, regulated, system-of-record software is exactly what they won't build — and gets more defensible for it.
"SaaS is dead" is the wrong question. Which SaaS is the right one.
The smartest people in the room disagree in public — one CEO calls SaaS dead, another calls that the most illogical thing in the world. The verified read isn't extinction; it's a sorting. Disruption is mandatory; obsolescence is optional. And the dividing line isn't how old the company is — it's how deep the workflow goes.
nobody puts on the slide.
95% of AI projects produce nothing. The 5% aren't who you'd guess.
MIT studied 300 deployments. Only about 5% delivered real P&L impact; the rest stalled. The failure isn't the technology — it's the approach: integration, data, and where the work was pointed. Buying and partnering beat internal builds roughly three to one. Adoption is high. Value capture is rare.
None of it works on data you can't trust.
Every shift above assumes the data underneath is clean enough for AI to use. Mostly, it isn't. Data privacy and security top the enterprise concern list, governance hasn't caught up, and the AI projects that fail mostly fail on data readiness — not model quality. The least glamorous finding is the most reliable one.
Where this leaves you
SaaS isn't ending. It's compounding — or it's being left behind. And the clock runs faster every quarter.
The engines that absorb these shifts as leverage were coherent before AI arrived. The ones that industrialize the wrong work, faster, were already broken — AI just made it visible.
None of these directions is in doubt. The only open question is whether your revenue engine is built to move at the speed they're arriving.
This is the part of the site that's supposed to be about me. It's really about whether you get what you came for.
So here's the one thing worth knowing, and it decides everything else: I'm only finished when you're standing on your own. You're the hero of this — your company, your win, your engine. I'm the guide who gets you there and then goes. Done right, the last thing I do is become unnecessary.
Everything else about my background earns its place by one test only: what it lets me do for you. Here's the short version.
For most of my career I spent ten months a year on the road — different industries, different stages, the same work every time: walk in, see what was happening underneath what leadership said was happening, build what was missing, hand it to the people who would run it, and leave. Back then one person carried marketing, sales, client success, and client support in a single seat. That job should not come back — but it's why I can walk into your engine and find the seam that's quietly costing you, the one no dashboard has named yet, before the bill comes due.
That experience taught me the thing worth more to you than any war story: your revenue problem is structural, not personal. The reps aren't broken. You aren't broken. The engine is — and an engine can be architected. That's not consolation. It's the most useful thing I know, because a structural problem has a structural fix, and a personal one doesn't.
There's a standard the work is held to. It isn't a methodology — it's a posture, and you should hold me to every line of it:
Know your operation better than you'd expect an outsider to.
Sell you the outcome you came to buy — never the feature I happen to have.
Build systems that keep running after I'm gone.
Put operators in your seats who want to win and won't tolerate compromise.
Leave when the work is done. Never stay for the fees.
That last line is the one most engagements quietly break, and it's your best protection. A guide who stays becomes a dependency — the opposite of what you hired the work to produce. The exit isn't the end of the value; it's the proof of it.
It's the posture that once produced clients who simply didn't leave, in an era before the industry decided depth was inefficient and replaced it with handoffs. Those handoffs are exactly where the debt in your engine collects now.
If you want the whole architecture, it's in the book I'm writing, Truly Built to Win and Last: How B2B SaaS Founders, Leaders, and Investors Architect Companies That Compound — and it's yours to read whether we ever work together or not. Alongside it I publish The Revenue Data Debt™ Discussion; Issue 01, “The Bill Has Arrived,” is available now.
I hold myself to two or three clients at a time, because the victory I'm describing — yours — takes a presence I can't fake at scale. I'm only victorious when you are. Everything above is just how I make sure that's how it goes.
If that sounds like the work you need,
I'd want to hear about your situation.