The First 100 Days After Close: Where Operating Plans Meet Reality

Rebuilding day-to-day operating processes taught me to pay close attention to the handoffs between departments. A change can look sensible within one team and create confusion for the next. After an acquisition, that distinction matters: the buyer must decide what to change while the business still has customers to serve and obligations to meet.

I approach the first 100 days as a period for testing the operating plan against the business as it actually runs. The goal isn't to complete every improvement imagined before close. It's to establish a workable sequence, protect daily operations, and revise assumptions before they become expensive commitments.

Separate the purchase decision from the operating sequence

The reasons for buying a business don't automatically establish the order in which to change it. An attractive opportunity may still require preparation before anyone can act on it responsibly.

I separate the plan into what needs immediate attention, what needs verification, and what can wait. An urgent control issue deserves different treatment from a proposed system replacement. Putting both on the same undifferentiated task list makes it harder to allocate attention.

For each proposed change, I want a plain explanation of the business problem, the person responsible, and the conditions that must be in place first. If those aren't clear, the item needs more definition before it becomes an instruction to the team.

Follow the work across departments

My operations background includes clarifying roles and handoffs between sales, administration, transaction support, and client service. That experience shapes how I read a post-close plan: I look beyond department-level assignments to the work moving between them.

I would start by tracing how customer commitments become scheduled work, completed service, invoices, and cash collection. The purpose isn't to redesign every step. It's to identify where the plan assumes a connection that hasn't been verified.

At each handoff, I want to know what information moves, who accepts responsibility, and how an exception gets resolved. A new reporting requirement isn't much help if the people supplying the information don't agree on what it means or who maintains it.

Give employees usable decisions

An acquisition plan can ask for accountability without giving employees enough direction to exercise it. I look for that gap early.

People need to understand which decisions remain with them, which require approval, and where to take a conflict between old instructions and new expectations. I prefer those rules in language employees can use during the workday, rather than broad statements about alignment.

I also want a clear way to report when a new process makes work harder. That feedback doesn't automatically mean the change is wrong. It gives leadership something specific to investigate: missing information, an unclear responsibility, or a sequence that doesn't fit the work.

Treat the plan as something to verify

I distinguish between completing an activity and improving an operation. Publishing a procedure confirms that a document exists. It doesn't establish that people can follow it or that the underlying problem has been addressed.

Before a change begins, I would define what evidence would justify continuing, adjusting, or stopping it. The measure should fit the problem, and someone should be responsible for checking it. Where the starting information is unreliable, establishing a usable baseline belongs in the plan.

The same discipline applies to technology. I start with the operating problem, not the software purchase. AI may improve capacity or economics in a suitable workflow, but I would examine costs, constraints, and human review before treating that possibility as part of the operating case.

Make the transition commitments explicit

For buyers and sellers, I would separate informal expectations from agreed transition responsibilities. What information must be provided, who can make decisions, and how unresolved issues will be handled deserve explicit attention.

The operating plan shouldn't substitute for the transaction documents. Where transition services, employment terms, contractual obligations, or tax treatment are material, qualified legal, financial, and tax advisers should review the relevant arrangements.

Finish with a better-grounded plan

At the end of the first 100 days, I would judge progress by whether leadership has a clearer view of the operation: which assumptions held, which changes deserve to continue, and which decisions need reconsideration.

I wouldn't mistake a completed checklist for a functioning transition. I would look for clear responsibilities, workable handoffs, and evidence strong enough to guide the next decision.