The first 90 days after acquiring a service business.
A first 90 days operating plan for a service business acquisition: protect client continuity, listen to staff, clarify decisions and improve one handoff.
The first ninety days
A narrated companion to this article, created with the photographs and visual language of Emerson North.
Read video transcript
The first ninety days after an acquisition are not a race to replace every process. Clients need continuity, and employees need to know who makes decisions. Start by listening: map the promises already made, the routines that work, and the exceptions that keep returning to the former owner. Fix one painful handoff with the team and show that the new system helps them serve clients. Earn the right to make the next change. Emerson North. Ideas worth putting to work.
The first 90 days after buying a service business set the tone for clients and employees. A buyer may arrive with a long improvement list, but the first job is to understand the promises already in motion and protect the routines that keep them.
Begin with continuity. Listen to staff and clients, document active commitments, clarify decision rights and make one visible improvement with the team. Sequence larger changes only after the operating facts are known.
Day one is about clarity, not reinvention
Employees want to know who leads, what changes now and how to get a decision. Clients want to know whether their work will still be delivered. Answer those questions plainly. Introduce the people responsible for operations and communication. Keep the current schedule, commitments and customer contact routes visible.
That does not mean promising that nothing will change. It means distinguishing immediate facts from future choices. “Your existing project contact remains the same this month; this is who will handle escalations” is more useful than a broad assurance that leaves everyone guessing.
Prepare a live list of active client work before the transaction closes if access and agreements allow it. Include the client, work in progress, next promised date, delivery owner and known exception. Review it daily during the first week. The list is a continuity tool, not a new bureaucracy.
Weeks one to four: listen to the people who run the work
Meet the people closest to clients, scheduling, billing and exceptions. Ask each what works, where work stalls and which rule they wish a new owner would not change. Compare their answers to actual job records. Different teams often describe the same handoff from different sides.
Listen for informal strengths as well as risks. A dispatcher may have a clever way to prioritize urgent calls. A senior technician may train new colleagues without a formal title. A billing coordinator may know which customers need a different invoice format. Those details are assets worth preserving.
Make a decision map: frontline decisions, manager decisions and owner decisions. If the former owner approved every exception, the new owner must provide a response path immediately. Otherwise the team inherits a bottleneck with a different phone number.
Sequence the work so improvement does not interrupt service.
Weeks five to eight: fix one painful handoff
Choose a recurring problem that the team already recognizes. A job may be sold without delivery knowing the scope. A client request may arrive in an inbox no one owns. An invoice may wait because the completed work has no clear sign-off. Pick one of these, not all of them.
Define what the receiving person needs to see, who supplies it and what happens when information is missing. Test the new handoff on real work for two weeks. Ask both sides whether it saved a question, prevented rework or simply added another field. Keep the improvement if the work becomes clearer.
An illustrative example: a service manager and salesperson agree that every sold job must include the customer's desired outcome, site constraints, first appointment and approved scope. The team tries that checklist on ten new jobs. If it misses a critical fact, they revise it together rather than imposing a longer form from above.
Weeks nine to thirteen: decide what to change next
By now the buyer should understand which processes are essential, which are fragile and where a better system will help. Prioritize changes by client impact, employee burden and reversibility. A new meeting rhythm may be easy to test. Replacing core software while work is unstable is a larger commitment.
Use a simple transition scorecard: active commitments on time, open exceptions, staff roles without coverage, client concerns and cash collection status. These are discussion prompts, not targets to game. A number that suddenly improves because people stopped reporting issues is not progress.
Close the first 90 days with a plain account of what was learned, what changed and what is next. Share it with the team. A transition feels more credible when people can see how their observations affected decisions.
Trust is an operating asset
Client and employee confidence grows from repeated, ordinary proof: answers arrive, commitments are kept and changes make work easier. A buyer cannot demand that trust on closing day. It can build it through the operating habits established in the first 90 days. That is the intent behind Emerson North's long-term ownership approach.
Published by Emerson North, an Atlanta operating company that runs, builds and owns businesses. Examples and workflow diagrams are illustrative and do not describe client results.