There is a moment that almost every new business owner experiences, usually somewhere between sixty and ninety days in.
The deal is done. The excitement of the acquisition has settled into the reality of running the thing. You are in the building, you have met the team, you have started to understand the clients, the processes, the history. And then, quietly, a feeling creeps in that is hard to name at first.
Everything is moving. But nothing feels like it is moving forward.
Meetings happen, but the same issues keep coming up. The team looks to you for decisions that should not require you. You are working harder than you expected, but the business does not seem to be gaining any real traction. And somewhere in the back of your mind, a question starts forming: is this normal?
It is. And there is a reason for it.
"Move fast on structure, and slow on operations."
The acquisition hangover no one talks about
When you acquire an established business, you inherit something that has been running on an invisible operating system — a set of norms, habits, assumptions, and informal agreements that kept things moving under previous ownership. Most of it was never written down. Much of it lives in the heads of long-tenured employees. Some of it works well. Some of it should have been replaced years ago.
The challenge is that you cannot see any of it clearly from the outside. And by the time you are on the inside, you are too busy keeping things running to stop and examine the infrastructure underneath.
This is what I call the acquisition hangover. It is not a reflection of the quality of the business you bought. It is a structural condition that affects almost every acquired company, regardless of industry, size, or deal quality. The business was built around a specific person’s way of doing things. Now that person is gone, and the business has not yet been rebuilt around yours.
Until that happens, you are not really running the business. You are managing the gap between who it was and who it needs to become.
What an operating system actually is
When most people hear “business operating system,” they picture software. That is not what I mean.
An operating system for your business is the set of disciplines that answer six fundamental questions:
Vision. Where are we going, and does everyone know it? Not a mission statement on a wall — a specific, written picture of what this company looks like in one year, three years, ten years, and what it stands for in the world.
People. Do we have the right people, and are they in the right seats? Not based on tenure or loyalty — based on whether they share the company’s values, whether they genuinely want to do the work in front of them, and whether they have the capacity to do it well.
Data. Are we measuring the right things, weekly, with clear ownership? Not financial reports that arrive a month after the fact — a live scorecard of the five to fifteen numbers that tell you, right now, whether the business is healthy.
Issues. Do we have a disciplined way to surface, prioritize, and actually solve our problems? Not a complaint channel — a structured process that turns recurring frustrations into resolved issues that never come back.
Process. Is the way we do our most important work documented, followed, and continuously improved? Not an employee handbook — a clear description of what we do and how we do it, specific enough that a new person could follow it.
Traction. Do we have a rhythm of accountability that keeps the most important priorities moving, every week, every quarter? Not aspirational goals — concrete 90-day rocks with named owners and visible progress.
Most acquired businesses have fragments of some of these. Very few have all six, working together, in a form the new owners can actually use.
Why the first 120 days are so important — and so dangerous
The period immediately following an acquisition is uniquely high-stakes. The team is watching. They are forming impressions of new leadership that will be difficult to change later. Clients are paying closer attention than they let on. And the habits that take hold in this period — how decisions get made, how problems get surfaced, what accountability looks like — tend to calcify into the culture of the business going forward.
The instinct of most new owners is to move carefully. Do not change too much too fast. Learn before you act. Respect what exists.
This instinct is right. But it can be misapplied.
The mistake is confusing operational caution — not disrupting service delivery, not making personnel changes without sufficient information — with structural caution. Waiting to build the infrastructure is not the same as respecting the culture. In fact, running without a clear operating structure for too long sends its own message to the team: that things will continue as they always have, and that new ownership may not mean meaningful change after all.
The businesses that come out of acquisitions strongest tend to do something counterintuitive: they move fast on structure, and slow on operations. They establish clear vision, accountability, and rhythm early — not because they have all the answers, but because establishing that infrastructure is how they begin to find them.
The audit before the overhaul
One of the most valuable things a new owner can do in the first few months is conduct a structured audit — not just of the financials, but of the full operating picture.
What technology is the business running on, and is it the right technology? What processes are documented? Who owns what, formally and informally? What are the three or four numbers that actually tell you whether the business is healthy? Where is accountability clear, and where does it blur?
This is not about finding fault with what the previous owner built. The audit is about understanding what you have — clearly, specifically, and honestly — so that you can make good decisions about what to keep, what to modernize, and what to let go.
Without that foundation, the implementation of any operating system will struggle. You will be trying to build structure on top of assumptions rather than facts. And when the structure does not hold, it is often the system that gets blamed rather than the incomplete foundation it was built on.
A practical path forward
If you have recently acquired a business, or if you are several years in and still feeling like the business is running you more than you are running it, here is what I have seen work:
Start with a clear-eyed assessment of where you actually are. Not where you plan to be, not where you hope you are — where you actually are, across all six components of the business. The EOS Organizational Checkup is a useful starting point. So is a structured conversation with someone who can ask the questions you have been too busy to ask yourself.
Then build the foundation deliberately. Vision before metrics. Accountability structure before process documentation. Rhythm before tools. It is tempting to reach for software and systems early — but tools amplify whatever is already there. Build the habits first.
Finally, treat the first 90 days of implementation as a learning period, not a performance period. The goal is not to have everything figured out. The goal is to establish the disciplines that will allow you to figure things out together, consistently, over time.
The businesses that run well do not get there by having better people or better ideas than everyone else. They get there by having a better operating rhythm — a shared language, a reliable cadence, and a culture in which the most important things always get done.
That is what an operating system gives you. And it is never too early — or too late — to build one.
Andrey is an Fractional Swiss-army knife Executive at Curated Soft LLC, based in Salt Lake City, Utah. He works with entrepreneurial businesses to help them get more of what they want from their companies — through better vision, stronger accountability, and sustainable execution.