This is written from the buyer's seat, because that is the seat I sit in. But there are two people who need it.
If you are taking a company on, whether as an acquirer, a new CEO, or a founder's successor, this is the sequence I use, and the mistakes I have made in it.
If you are the founder handing one over, read it as a diagnostic. A handover done well and a handover done badly look nearly identical in the first fortnight. They diverge around day forty, and by then the damage is structural.
The first hundred days are not for deciding. They are for learning what you actually bought, at a resolution the financials could never show you.
There is nothing magic about a hundred days. It is borrowed from politics and it is arbitrary. What it is useful for is forcing a deadline on the part of the job that has no natural one: the learning. Left alone, learning expands to fill whatever time you give it, and you can spend a year being thoughtful while the business waits.
THE ONE RULE
Change nothing in the first ninety days that you cannot explain the original reason for.
Not change nothing. Change nothing you do not yet understand. Almost every expensive mistake I have watched a new owner make, including my own, is a version of removing something load-bearing because its purpose was not written down anywhere.
The gap between signing and close is usually four to eight weeks. It feels like waiting. It is the cheapest preparation time you will ever get, because you have information rights and no responsibility yet.
Staff will remember how they found out for years. Get the order right and the sequence tight, ideally inside a single day.
The founder's inner circle. Three or four people who will be asked before you are. They should never be surprised in front of someone else.
Whole company, live. Same room, same moment. Written-only announcements read as evasion.
Top customers, by phone. Before they read it. A call from the founder with you on the line beats an email from you.
Everyone else. Suppliers, partners, the wider list.
"Are there going to be layoffs?" If no, say no plainly. If you do not know, say so and give a date by which you will. Never say "there are no plans." Everyone hears the gap in it.
"Is the founder leaving?" Say exactly what the transition agreement says, including the end date. Vagueness here starts a rumour that runs for months.
"What's going to change?" The honest answer is that you do not know yet and will not for ninety days. Say that, then say what will not change in that window, specifically enough to be held to it.
The temptation on day one is to demonstrate competence. Resist it. Nothing you can say in week one will land as well as being visibly, unusually interested in what already exists.
Keep it under twenty minutes. Cover four things and stop: why this business, specifically and truthfully; what is not changing for ninety days; what you will do instead (meet everyone, one to one); and how to reach you.
Do not present a strategy. Do not use the word synergy. Do not mention growth targets. Every one of those tells the room that the decisions are already made and the listening is theatre.
Thirty minutes, every single person, no exceptions and no seniority filter. In a forty-person company that is twenty hours over two weeks. It is the highest-return time you will spend all year.
Ask the same three questions every time. The repetition is the instrument: you are looking for the answers that recur.
THE THREE QUESTIONS
What should I be careful not to change? Surfaces the load-bearing things before you can break them.
What is broken that everyone already knows about? There is always a list. It is usually unanimous and usually unspoken. Fixing one item from it is the fastest credibility you will ever buy.
If you had my job, what would you do first? Tells you what they think the job is, which tells you how the company sees itself.
Underneath the questions you are building the decision map: who people genuinely consult before acting, as distinct from who the org chart says is accountable. These overlap far less than you would expect.
You cannot get this by asking. Ask who decides and people describe the org chart, honestly, because that is the version everyone has agreed to believe. Instead, watch: when something urgent breaks in week two, note who gets called. That person is the answer, and they are frequently three levels below where you were looking.
The financial statements are not the business. They are a record of decisions the business made, at a resolution too coarse to show you any of them. This phase is about getting underneath them.
A fence is anything that exists for a reason nobody currently remembers. Software companies of any age are dense with them: a pricing tier grandfathered years ago that a handful of customers are still on; a nightly job that must finish before a specific hour, cause unknown; a feature built for one customer that still ships to everyone; a retry loop added after an outage that now masks a fault worth fixing properly.
None of these were irrational. Each was a sensible answer to something real. The problem is that the something is often gone and the answer is still here, drawing salary and slowing every release.
Keep a running list. For each: what it is, who knows why, what happens if it goes. Do not remove anything yet. You are cataloguing, not clearing.
You will hear this constantly. It produces two wrong reactions: deference, which buys you a museum, and dismissal, which walks you into the same wall.
The right response is a question: what exactly happened? Not did it work, which asks for a verdict. Who did it, when, what specifically went wrong, and what was true at the time. Roughly half the time the constraint has genuinely dissolved. The other half it is structural and permanent, and you have saved yourself a year.
Find out when list price last moved, and when it last moved for existing customers. In founder-run software these are frequently different by years. A decade of not raising prices is a liability dressed up as goodwill, and usually the single largest piece of recoverable value in the business.
Most new owners hand this to engineering and ask for an estimate. That is the wrong frame, and it produces a number nobody trusts. Deferred technical work is a loan the previous owner took out against your first three years. Treat it like any other liability: what is the principal, what is the interest, and when is it callable?
Debt you understand is a schedule. You know what it costs and roughly when it must be paid. Debt you inherited and never interrogated is a fence. You will discover its size at the worst possible moment.
Every company has one. Flagged during diligence as resistant to change. He is almost never resistant to change. He is protecting something. Ask what he is worried about, then fix one of the answers inside a month. Not all of them. One, visibly, early.
By day forty-five you have a fence register, a decision map, and a list of things everyone already knows are broken. Now you start, carefully and in a specific order.
The first visible change should come from the "what is broken that everyone knows about" answers. Small, unambiguous, fast. It is the cheapest possible demonstration that the listening was real.
TRIAGING THE FENCE REGISTER
Live. The original reason still holds. Leave it, and write the reason down so the next person need not rediscover it.
Dead. The reason is gone and verifiable. Remove it, say publicly why, and credit whoever explained it.
Unknown. Nobody can explain it. Leave it and keep asking. Unknown is not permission.
Fill the shape the decision map revealed, not the shape the org chart implies. Frequently the right first hire is not a new person at all: it is giving the eleven-year support lead the title, authority, and pay that match what she has actually been doing.
There is a short window, and it closes, where you can still see the company as an outsider while already understanding it as an insider. Capture it before it goes.
Five to ten pages, written for yourself and shared with whoever runs this next: how the business actually makes money (the mechanism, not the P&L); the unwritten agreements you found; the fence register with its three states marked; who really decides what, and what breaks if each of them leaves; and what you got wrong in the first hundred days. That last page is the most useful one and the one people quietly omit.
The single question that determines whether this is a long hold or a long job: who runs this in year five?
If the honest answer is "me," you have bought yourself employment rather than an asset, and the clock on that is your own stamina. The clearest sign a business is built to outlast its owner is that its best operator is actively working to become unnecessary.
Year one runs on momentum and the benefit of the doubt. Year two is when you find out what you actually bought.
What is the original reason this exists, and who told me?
Is that reason still true, and how did I verify it?
Who benefits from it today, including people who would not think to speak up?
What breaks the day after it is gone?
Has anyone tried removing it before? What actually happened?
Is this on the list of things everyone already knows is broken, or only on mine?
Who needs to hear it from a person rather than an email?
What is the smallest reversible version of this change?
If I am wrong, how long until I find out, and how much will it cost?
Does this still look right in year five, or only this quarter?
You will not run this cleanly. I never have. Something will force a decision in week three that this guide says to defer to week sixty, and you will make it with a fraction of the information you wanted.
That is fine. The point of a sequence is not that you follow it perfectly. It is that when you depart from it, you know you are departing from it, and you can say why. That is the whole difference between inheriting a company and being inherited by one.
If you are working through a handover now, on either side of it, I read every reply.
— Ahmad
THIS WEEK'S MOVE
Start the fence register. Three entries, whatever comes to mind first. Twenty minutes. Remove nothing yet.
Talk through the decision with me.
I set aside a small number of 30-minute founder conversations each month. We'll use the time to understand where the business is today, pressure-test one important question, and identify what deserves attention next.
One operating framework, every Thursday. Free, and you can unsubscribe anytime.