Part of our work on private equity
Principal Investors and Private Equity
What a Search Fund Buyer Should Automate in Year One, and What to Leave Alone
Big Sky Consulting Group · September 25, 2026 · 8 min read

The clock that starts at close
You spent two years finding this company. You raised the search capital, sat through dozens of owner conversations, survived the LOI, the QoE and the lender. Now you own a business with a few dozen employees, a seller who has agreed to stay on for a while, and a list of things you noticed in diligence that could obviously run better.
That list is where most first-year mistakes start.
The clock that matters in year one is not the one on your investor update. It is the seller's transition period. The 2024 Stanford search fund study puts the median post-close engagement of sellers at six months, up from four in the prior study, and only 12 percent of searchers intend to keep the seller involved indefinitely (Stanford GSB 2024 Search Fund Study). Six months is the window in which the person who built the business still answers the phone. After that, whatever they knew and never wrote down is gone.
What the search content skips
Almost everything written about search funds is about the search. Fundraising mechanics, deal sourcing, how to talk a founder into selling, LOI to close. The operating years get a sentence, usually some version of "the searcher then transitions into the CEO role."
That imbalance matters because the operating years decide the outcome, and the people running them are mostly doing it for the first time. The same Stanford study found 79 percent of searchers who launched in 2022 and 2023 were 35 or younger. The median company they bought had 34 employees and a 27 percent EBITDA margin. It also noted an increase over the last ten years in the share of acquisitions that reported a loss.
When post-close advice does exist, it tends to be one rule: do not change anything in year one. Listen, learn, meet every employee, sit in on customer calls. That rule is mostly right. It is wrong in one specific place, and that place is where the money is.
The asset that walks out the door
Ask what you actually bought. Not the equipment, not the customer list, not the software stack. In a company this size, a large share of the value is judgement that lives in the owner's head and nowhere else.
It usually looks like this:
- Pricing exceptions. The list price is in the system. The real price, for the customers who matter, is a set of discounts and deals the owner remembers. Some of them were agreed on a handshake a decade ago.
- Terms. Which customers get net 60, which get extended credit when they are late, which ones you never chase because they have always paid eventually.
- Supplier relationships. Which supplier calls get returned the same day, which vendor will expedite as a favour, and which one quietly carries the business through a shortage.
- Exception handling. The unusual order, the customer complaint that needs a phone call rather than a credit, the employee who needs a different conversation. Staff route these to the owner because the owner has always handled them.
None of this is a secret. The seller is not hiding it. From the inside it does not feel like knowledge, it feels like running the business.
The market already knows what this is worth. One advisory analysis of owner dependence reports businesses that could run without the owner valued at roughly 4.49 times pre-tax profit, against 2.93 times for businesses where the owner knew every customer by name (Duran Advisors). That is a gap of more than 50 percent in the multiple. Whatever you paid, you paid it partly on the premise that the business would keep working once the owner stepped away. Year one is when that premise gets tested, whether you test it deliberately or not.
An owner who taps their temple and says "it's all up here" is telling you the truth. It is also the only server in the building with no backup.
Our position: automate the dependence, and nothing else
We think "automate nothing in year one" is too blunt, and "fix everything you saw in diligence" is how searchers burn their first year. The rule we give is narrower.
In year one, automate the things that reduce your dependence on the departing owner. Leave everything else for twelve months.
That sounds like a small category. It is, and that is the point. It covers the places where a decision the owner currently makes, from memory, needs to become something the business makes without them. Pricing exceptions recorded as data rather than recalled. Customer terms held in the system rather than in a person. Approvals that route to a role rather than to a name. The goal is not speed. The goal is that when the seller's transition period ends, the business still knows what the seller knew.
Two things about this category are worth saying plainly.
First, much of it is not automation in the sense a vendor would sell you. The hard part is getting the rule out of the owner's head and onto paper, and deciding which of the owner's habits are policy and which were just habit. A tool can apply a rule. It cannot tell you what the rule should be. That work has to happen while the owner is still around to answer questions, which is why it cannot wait.
Second, it is the only category where waiting costs more than moving. Almost every other improvement gets cheaper if you delay it. This one gets more expensive every week the transition period runs down, and after month six it may not be possible at any price.
This is the general shape of the problem. Which parts apply to your process depends on answers only your systems can give.
Put us on it, from $5,000What waits, and why it gets cheaper
Everything else on the diligence list can wait a year. That includes the obvious back office wins: accounts payable automation, a CRM replacement, a new ERP, the AI tool someone in your investor group keeps sending links about.
The reason is not caution for its own sake. It is that these projects are bets on your understanding of the business, and your understanding in month three is a fraction of what it will be in month thirteen. Automate an invoicing process you have watched for eight weeks and you will automate the version you watched, including the parts that only happen in March, or only with one customer, or only when a particular person is out. Wait a year and you will have seen the full cycle, including the parts nobody mentioned.
There is also a capacity argument. A company of 34 people is already absorbing the biggest change it has ever had: a new owner. Every additional change in that year competes for the same limited attention from the same few people, several of whom are quietly deciding whether they trust you. We covered the larger-company version of this in why the 100-day plan almost never includes the process that is actually broken: each sensible workstream puts load on the fragile, person-dependent processes nobody can see from outside. In a search fund acquisition, the most fragile person-dependent process is the owner.
And there is a cost argument. The same project scoped in year two is usually smaller, because by then you know which steps can simply be deleted rather than automated. We make that case more generally in when not to use AI in your business. Deletion is cheaper than automation, and you cannot see what to delete until you understand why each step exists.
Vendors will tell you the savings start the day you sign. The savings start the day the process is right, and in year one you do not yet know what right looks like.
The test for any year-one project
When something lands on your desk in the first twelve months, whether it is a vendor pitch, an employee's idea, or a note from an investor, one question sorts it.
Does this reduce what only the seller knows?
If it does, it belongs in the next six months, while the seller can still tell you whether you got it right. If it does not, it goes on a list for month thirteen. Most things go on the list. That is fine. The list will be better informed when you come back to it, and some items on it will have solved themselves or turned out not to matter.
The test is simple. Applying it is not. The hard part is seeing the dependence in the first place, because it hides inside processes that look routine. The quote that goes out on time because the owner glances at it. The collections call that never happens for three accounts, for reasons nobody remembers. The supplier who gives priority because of a relationship, not a contract. These are the same blind spots a quality of earnings report misses, which we wrote about in what operational diligence finds that financial diligence will not. The numbers are real. What produces them is the question.
Where this leaves a new owner
The pattern is simple to state. The company works. It works partly because of one person. That person is leaving on a known date. The first year should be organised around that date, not around the list of improvements that looked obvious from the data room.
Knowing that is the easy part. Finding exactly where the owner's judgement is load-bearing in a specific business, and which of those decisions need to become rules before the transition ends, is work that happens inside the company, alongside the seller, while there is still time to ask.
If you have just closed, or are about to, and the seller's transition clock is already running, talk to us. We will help you find what only the seller knows and get it into the business before month six, and we will tell you which items on your list can wait.
