Almost everyone in professional services says the same thing: it’s all about relationships.
Then look at how the actual work happens. Chase the project. Land it. Deliver it. Close it out. Move on to the next one. Repeat.
That’s not a relationship. That’s a transaction with a longer runway than a single meeting, but it’s still just a transaction. And the gap between what we say and how we actually behave is exactly where enterprise value quietly leaks out of a lot of practices that should be building it.
The Tell Is in What’s Left When You’re Gone
Enterprise value is what’s left when you’re not in the room. Not the revenue from the project you just finished- what’s still there, still generating value, still connected to you, after that engagement is over.
If the honest answer is “nothing, until the next project starts,” that’s the tell. You can genuinely care about your clients, do excellent work, build real trust in the moment – and still be running a fundamentally transactional business, because nothing about the structure carries the relationship forward on its own.
Relationships that actually behave like relationships don’t reset to zero every time a scope of work ends. Transactions do. That’s the difference, and it’s a structural one, not a matter of how much you genuinely care.:
Recurring Revenue Isn’t a Pricing Trick. It’s Proof.
This is why recurring revenue matters more than it gets credit for. It’s not just a nicer cash flow pattern. It’s the actual artifact of a relationship that kept producing value after the original deliverable was done proof, not just a promise, that the relationship was real.
A one-time project can be excellent and still say nothing about whether the relationship continues past it. Recurring revenue can only exist if something kept the two of you connected on purpose. That’s the whole difference. It’s not a billing structure. It’s evidence.
There’s No Single Right Way to Build It
Here’s where a lot of advice oversimplifies this: it treats “add a retainer” or “build a subscription” like a universal fix. It isn’t. What creates durable recurring revenue depends entirely on what your actual business model supports – and forcing a structure that doesn’t fit the work usually produces something that looks recurring on paper but doesn’t behave that way in practice.
A few different shapes this can take, depending on the work:
- An ongoing advisory retainer: for practices where the value is judgment and access, not a deliverable with a natural endpoint.
- A maintenance or support relationship: for work where something built once needs continued attention to keep producing value.
- A recurring service contract: for practices where the client’s need doesn’t end when the first cycle does, it just repeats.
- A membership or cohort structure: for practices where ongoing access to expertise, community, or resources is the actual product.
- An embedded, lighter-touch continuation: a scaled-down version of the original engagement that keeps you connected without requiring the full scope every time.
None of these are automatically right. The question isn’t “which of these should I bolt onto what I already do.” It’s “what does my actual business model support, and what would a client genuinely need on an ongoing basis, versus what am I trying to sell them because recurring revenue sounds appealing.”
Start With the Honest Audit
Before building anything new, it’s worth being honest about the current pattern: how many of your client relationships actually continue past the original scope, on purpose, by design – versus how many just happen to come back if you’re lucky and they remember you?
If it’s mostly the second category, that’s not a client problem or a quality problem. It’s a structural one. And it’s fixable – but only once you’re honest that “we’re relationship-focused” and “our revenue resets to zero after every project” can’t both be true at the same time.
If you want a clearer read on where this shows up in your own practice, not just “you might have a recurring revenue gap” in general, but which specific structural gap is actually driving it – the Fractional Gap Assessment is built for exactly this. 15 questions, about 3-4 minutes, and it names the gap precisely instead of leaving you to guess.
[Take the Fractional Gap Assessment →]
