
You try something new in your business.
Miraculously, it works.
So you do more of it.
New vendor. New channel. New agency. New contractor. Each one solving a real problem, each one making sense in the moment. This is how you got to $4M. This is how you'll get to $10M.
Probably.
But at some point, without meaning to, you stopped building and started borrowing. Solutions that work, stacked on top of one another. Revenue ticking upward, dopamine hitting so hard how could it be a bad thing?
Until you hear a question that stops you dead in your tracks.
What do you actually own here?
Not what's working. What's yours. Because those are two different questions. And the gap between them is where many seven-figure companies get stuck.
The Phantom Asset Problem
Every founder I've worked with at the seven-figure ceiling has the same instinct when something works.
Add more.
Something's working, so you do more of the thing that's working, or you add the next thing that might. You build by accumulation. One problem solved, next problem identified, next solution bolted on.
Nobody's doing this wrong. It's exactly what scaling looks like from inside the house.
But there's a question that almost never gets asked in the middle of all that adding.
What does the business actually own?
Not what's working. Not what's producing. What's actually, genuinely, irreversibly yours — the kind of yours that survives a bad quarter, a vendor walking, a key person leaving, or the founder disappearing for six weeks to "find clarity" in Portugal.
Because something can look like an asset, function like an asset, produce like an asset... and still not belong to the business.
And nobody on your team is hired to ask which is which.

The Accumulation Trap
Recently I started working with a $8M ARR company.
Growing. Margins solid on paper. Founder sharp, team capable, product validated. They'd built something that actually converted — which, at that stage, is more than most can say.
When I asked the founder why he was coming to me for help, he said what most founders do:
How do we scale?"
It makes sense. When the machine's running, you want more of it. They needed to grow faster. Marketing was working, spend was increasing, and they wanted help pouring more in.
That's the presenting problem at almost every company I walk into at this stage. And on the surface, it's completely reasonable.
Then I look under the hood...
My first discovery call was with one of their VPs. Ten minutes in, I asked how leads were being tracked and attributed. Her answer: "Nobody in the company fully does."
UTMs coming in ad hoc. No lead scoring model. No confidence in attribution. I wrote "Attribution Chaos Deep Dive" in my notes and kept pulling the thread.
Over the next few weeks, every call uncovered another layer. One lead gen vendor was charging $4,000 per deal... while the company's best channel was producing deals at $800. Plus a 50/50 revenue split on top. And here's the part that still gets me: they were essentially just retargeting the company's own organic traffic and claiming credit for the conversions. When the team finally told them to stop, they were "pretty pissed."
Another vendor had promised 25 sales calls per day. Actual performance? Two. For months. If an employee promised 25 calls a day and consistently delivered two, they'd be gone by Friday. But vendors get a pass. Nobody's watching.
By the time I added it all up, the number was staggering.
85% of revenue was flowing through channels the company didn't own or control. About $200K a month going out the door.
And the VP — the one who'd been there from the early days, who knew where every body was buried — she said the thing that stopped me cold:
"I think we're successful despite ourselves."
A VP at a $8M+ company, saying the quiet part out loud. My response was something like: "You're just sitting there going... how the hell did I even get here? This is all broken."
Nobody caused this on purpose. Nobody was lying. The founder had a hunch something was off (that's why he hired me). But when I put the number on paper, it blew past what even he expected. And his first instinct? Cut everything. Tomorrow. Kill the vendors, bring it all in-house, move fast.
Which is exactly the wrong move. You can't rip out the infrastructure you're renting before you've proven you can replace it. That's how you go from "leaking margin" to "no revenue." The sequencing matters more than the speed.
Nobody subtracted. And nobody audited what the accumulation had actually produced versus what it had merely borrowed.
The brain doesn't audit wins. It just says, "Get me more of that."
This is what I'd call the Accumulation Trap. It's not a strategic failure. It's the natural endpoint of doing the right thing repeatedly, without ever stepping back to ask what you actually retained from all of it.
What Accumulation Hides
The vendor situation is just the most visible version of this. But I see the same pattern everywhere, in different forms.
Institutional knowledge that lives in one person's head – not in a system, not documented anywhere. Works great, until they leave.
Audience relationships that belong to the founder's personal brand, not the company's.
Revenue that follows a person, not the business.
A team that "runs itself" because one ops person is manually holding it together behind the scenes, every week, invisibly. (The one-liner burned in my head after talking to this type of person? "If I won the lottery tomorrow, that would cause some problems for the business.")
In every case, the pattern is identical.
If it looks like a duck, swims like a duck, and quacks like a duck… You might as well assume it’s a duck, because who has the time to look into it anyway?

Your business looks like an asset, functions like an asset, and produces like an asset – but nobody on the team is hired to ask whether the company actually owns it like an asset.
I call these Phantom Assets. Things that don’t appear on a balance sheet as a liability, that produce real revenue, that feel like proof you've built something... but that you don't actually own. The Accumulation Trap is how you end up with them. Phantom Assets are what you're left holding.
Most founders at this stage have been so focused on adding (and have been so rewarded for it) that subtraction feels like going backwards. Auditing what you actually own feels like slowing down when you should be speeding up.
But you can't scale what you don't own. You can only ensure your dependency on it stays intact as you accumulate more of it.

The Question Worth Asking
The company I mentioned is working through this now. Building internal capability, slowly replacing what they'd been renting. Truly, it’s some of the least glamorous work I do. Just the slow subtraction of ghosts and addition of real assets.
But before any of it could start, someone had to stop adding long enough to ask the question.
The problem with Phantom Assets is they're almost impossible to see from the inside. You're too close to the revenue they produce, too aware of the problems they solved, too busy adding the next thing to audit what the last thing actually left behind.
Knowing what you own is just step one. Knowing which gap to close first, in what order, without creating new problems downstream... that's a different skill. And it's the part that's nearly impossible to do alone, from inside the thing you built. This is the part of my diagnostic I spend the most time on in a new engagement, sequencing the problems.
Here’s the question I’ll leave you with. Before you’re tempted to add the next vendor, the next channel, the next initiative — ask this first:
What does this business actually own?
The relationships. The knowledge. The capability. The infrastructure. If three key people left, if three vendors walked, if you stepped back tomorrow – what would be left?
Whatever's still there... that's your actual asset.
Everything else is phantoms.
—Chris Piper
The Growth Operator

