I have talked companies out of hiring us more times than I have talked them into it.
That is not a humblebrag. It is the job. Most calls that come in are not actually asking "should we hire an operating advisor." They are asking something narrower and more urgent, and if you answer the narrow question honestly, the advisor is usually not the answer.
So let's separate the two questions, because conflating them is how companies waste a year and a budget on the wrong fix.
Things feeling hard is not a diagnosis. Revenue dipped, a launch slipped, a key hire didn't work out. Those are events. Events happen to well-run companies constantly and they do not require an outside operating advisor, they require management doing its job.
The right reason to call us is structural, not situational. It shows up as the same three or four problems recurring every quarter regardless of who is in which seat.
The scaling ceiling is the point at which the complexity of a business exceeds the capacity of the informal system running it. It is set by operational complexity, not revenue, which is why a $12M company can hit it and a $40M company can still be under it.
You know you are near it when the same problems keep resurfacing under different names. Last quarter it was a hiring mistake. This quarter it is a missed handoff between sales and delivery. Next quarter it will be something else, but it will feel identical.
That repetition is the tell. A situational problem gets solved and stays solved. A structural one comes back wearing a new hat.
We do not come in, interview your leadership team for six weeks, and hand you a hundred-slide deck with a maturity curve and some arrows. That artifact changes nothing because nobody owns turning it into a system.
What we actually do is rebuild the specific mechanisms that are failing. Decision rights that route through one person get reassigned to outcome owners. Processes that live in someone's head get written into the system they run through, usually the CRM or ERP you already have. Reporting that nobody trusts gets rebuilt on data everyone agrees is correct before anyone touches a dashboard.
None of that is glamorous. It is also the only part that survives after we leave.
Advisory tells you what is broken and why. Implementation actually rebuilds it. Companies that buy advisory alone get a correct diagnosis and then nothing changes, because the internal team that was too stretched to fix the problem in the first place is still too stretched to fix it after the report lands.
Companies that buy implementation alone without the diagnostic work often rebuild the wrong thing well. They automate a process that should have been eliminated, or they buy an ERP to solve what was actually a decision rights problem.
We insist on both, in sequence, for that reason. Diagnose first, using the actual mechanism at fault rather than the symptom someone is describing. Then rebuild it, and stay through the point where the new system runs without us in the room.
If your problem is that you have not made your first eight hires yet, you do not need an operating model, you need a business. Come back after you have something to systematize.
If your problem is a single underperforming executive, you need a personnel decision, not an operational transformation. Firing the right person is often cheaper and faster than any engagement we could sell you.
And if leadership is not willing to change how it makes decisions, no engagement fixes that. We can rebuild the system. We cannot make someone stop being the bottleneck if they have decided, consciously or not, that being needed for every decision is the job.
Revenue outpaced infrastructure two or three years ago and nobody stopped to notice, because growth covers a lot of sins. Then growth slowed slightly, or a key person left, or a bad quarter hit, and the informal system that always found a way to cope suddenly could not.
The founder or executive team is still in the middle of decisions that should have moved to a manager a year ago. Managers are absorbing operational work instead of managing outcomes. Priorities exist on a slide somewhere but nobody on the floor could name them without checking.
None of that is a crisis. It is what happens when the entrepreneurial operating model that built the company keeps running past the point where it can carry the company's current complexity. Success broke the system that created it, which is the least surprising outcome in business and the one almost nobody plans for.
We are explicit about this at the start of every engagement because it changes how we build things. If we design a process that only works while we are in the room enforcing it, we have failed, even if it looks good on the day we leave.
The test we hold ourselves to is simple. Six months after we are gone, does the decision still get made by the right person, does the report still get trusted, does the process still run without a specific individual holding it together. If yes, the engagement worked. If no, we did advisory theater, and that is exactly the thing we tell clients not to buy from anyone, including us.
How do I know if I've hit the scaling ceiling or I'm just having a bad quarter?
A bad quarter resolves and stays resolved. A scaling ceiling problem returns in a different shape every few months even after you think you fixed it. Look at the last four issues that felt like emergencies and check whether they are actually variations on the same root cause.
Should I hire a COO first or bring in Debsan first?
Hire the operating model first, then hire the COO to run it. A strong operator dropped into an undefined system usually inherits the same bottleneck the founder had, just with a new name on the door.
What if I'm not sure the company can afford this right now?
Then you likely cannot afford not to fix it, because decision concentration and process dependency both get more expensive with every month they compound. The cost of the ceiling does not pause while you wait for a better time.
How long does an engagement actually take?
Long enough to rebuild the mechanism, not the org chart. It is measured in the months it takes to move a decision, a process, or a reporting system into a form that survives without us, not in a fixed number we quote before we understand what is actually broken.
Most companies that call us are not broken. They are outgrowing the system that made them successful, which is a much better problem to have and a much easier one to fix, if someone is willing to name it before it names itself.