CEO & Leadership 9 min read

The first 90 days as an incoming CEO.

What changes after 90 days is mandate. This is the playbook I would use to spend the time before that window closes.

Updated

The “first 90 days” framing exists because something real changes at that point. The accommodation period ends. The questions a new CEO can ask without political cost (why is this contract structured this way? why does this team report to that person? why is this client paying half the standard rate?) start carrying weight. Decisions that were “I am new, I am still understanding” become “this is your call now, what are you doing about it?”

The first 90 days are for extracting enough information to make a small number of irreversible decisions, and for making them before the window closes. Planning happens, listening and learning happens. But where does the work start?

This is the playbook I would use: it applies to incoming CEOs taking over a going concern, not to founders building from zero. The arrival pattern and the constraints are obviously different.

Day 1: four artefacts, no exceptions

Before the welcome lunch, before the first all-hands, before the email introducing yourself, please ask for four things and do not accept fuzzy versions.

1. P&L by client (or revenue concentration table).

Who pays you, how much, what for, how long they have been paying. If this exists in finance, it is a printable spreadsheet. If it does not exist, that is the first finding. Strange fact but still: most struggling B2B businesses do not actually know which clients are profitable.

2. Contract repository with material terms summarised.

Every signed agreement with clients, vendors, partners. Termination notice periods, payment terms, governing law, exclusive obligations, auto-renewal clauses. If there is no central repository, you have found the second finding. You will be operating blind on commercial risk for at least six weeks while you build one.

3. Churn or retention cohort, however informal.

Who left in the last 12 months and why. “We had some churn” is barely an alternative, you need a list of names with reasons. If this does not exist, ask the head of client operations/product person/sales to write it down from memory in 24 hours. Memory is biased, but it is better than nothing.

4. Cash position with a 90-day forecast.

Cash on hand, AR aging, AP aging, committed expenses, expected receipts. The forecast can be wrong, so the point is to see what assumptions are baked into it.

These four artefacts give you the operating reality of the business. P&L by client tells you concentration risk and pricing inconsistency. The contract repository tells you the legal architecture. Churn tells you the failure modes of the product. Cash tells you how much time you actually have.

If three out of four do not exist in usable form, you have already learned the most important thing about the business. The previous leadership was not operating on facts. You will not be either, until you build the systems.

Weeks 2 to 4: the three-meetings sequence

I take three meetings with each direct report in the first month, in a deliberate sequence.

Meeting 1: how do you see your role.

What does success look like? What are you measured on? What did you commit to in your last review? What are you working on this week? It is a chance for them to articulate the job as they understand it, not a test. Most direct reports do not get asked this question often, and the answers reveal the gap between role-as-defined and role-as-actually-performed.

I take notes and do not push back. The point is to hear them out fully.

Meeting 2: what is broken.

What would you fix if you had a magic wand? What has been on your “should fix this” list for six months? Where do you spend time you should not be spending? Where do you not spend time you should?

This is where you find out what the previous leadership was unable or unwilling to address. People mostly tell you the truth in this meeting because they have been waiting for someone to ask. Please, take detailed notes. Some of what they say will be wrong. Some will be the most valuable information you get in the first quarter.

Meeting 3: who else should I be talking to.

Inside the company and outside. Who is the person you check with when you are not sure? Who is the client we should never lose? Who is the vendor you would recommend? Who is the ex-employee we should hire back?

This builds the second-degree map. By the end of week 4, you have direct reports plus their key relationships, plus the informal network of advisors and ex-colleagues who actually know the business.

The sequence matters. If you ask “what is broken” in meeting 1, you get a defensive answer or a polished list someone prepared. If you ask in meeting 2, after they have described their role and felt heard, you get the real answer.

Days 30 to 60: the decision window

By day 30, you have enough information to make decisions on a defined set of questions. You do not have enough to make decisions on anything strategic. The mistake new CEOs make runs in the wrong direction: they make strategic decisions too fast and operational decisions too slow.

Operational decisions for days 30 to 60.

Make people decisions on direct reports first. Anyone who should not be in their seat by day 90 should be on a path out by day 60. The honest 30-day diagnostic plus the three-meetings sequence will tell you which seats are wrong. Deferring this past day 90 is the single most expensive mistake in CEO transitions.

Pricing or commercial discipline corrections. If you have found that the company has 11 price points for similar offerings, sells without discount discipline, or has structurally underpriced contracts, the corrections start now. Not the renegotiations, those take longer. The internal policy shift starts now.

Vendor and tooling decisions. The accumulated stack of duplicate tools, unused subscriptions, vendor contracts that auto-renew. This is low-stakes, high-volume cleanup, so do it in this window.

Strategic decisions to defer past day 90.

Product roadmap changes beyond removing obviously broken things. Market positioning or category changes. Major organisational restructures beyond direct-report level. Acquisition, fundraising, or market entry decisions.

The temptation to make strategic moves early is high because everyone is watching. The correct response is to make a small number of clearly correct operational decisions, communicate them well, and signal that strategic work is happening in the background and will not be announced prematurely.

Days 60 to 90: communication cadence

In the second month, you start setting a communication cadence that will run for the rest of your tenure. Get this wrong and you spend the next year fixing it.

Internal cadence.

Weekly direct-report 1:1s. Bi-weekly skip-levels with their direct reports. Monthly all-hands with a consistent format: business state, key decisions made, key decisions pending, recognition. The format matters because predictability builds trust. People should know what is coming in the all-hands and what to expect.

Board cadence.

Monthly written update before the call, never instead of it. The written update covers five items: revenue and pipeline, key wins, key concerns, decisions needed from the board, decisions taken since last update. The call discusses the update, it does not recreate it. Boards that get verbal updates instead of written ones eventually stop trusting the CEO. Boards that get written updates with discussion calls afterwards stay aligned.

External cadence.

For client-facing CEOs, set a rhythm of senior executive contact with top clients. A quarterly check-in with each top-five client by revenue is enough for relationship maintenance and signal collection. Clients tell their senior contact things they will not tell their account manager.

Setting this cadence in days 60 to 90 means you start month 4 with the systems running. Setting it in month 4 means you start month 6 with the systems running. The cost of the delay is two months of erratic communication that you have to undo.

After 90 days: what calcifies

The asymmetry of the 90-day window is this. Decisions you make in the first 90 days are explained by your newness. Decisions you defer past 90 days become “the way things are now.”

The team gets used to the colleague who is not performing.
The board gets used to the executive who never gives clear answers.
The client gets used to the irregular billing.
The vendor gets used to the unenforced contract.

And none of these get easier to fix at month 4. They get harder, because changing them now requires explaining why you did not change them earlier.

There is no magic in the number 90. The political cost of decisions follows a curve that bends sharply upward after about three months. Use the time when the cost is low.

What I would tell incoming CEOs

Get the four artefacts on day 1. If you cannot get them, the first project of your tenure is to build them. And do not try to operate without them.

Run the three-meetings sequence in weeks 2 to 4. Do not compress it into one meeting, because the sequence matters.

Make operational decisions on a faster timeline than feels comfortable. Defer strategic decisions for longer than feels comfortable. Most new CEOs do the opposite, and it costs them the rest of their tenure.

The 90-day window closes whether you used it or not. The question is what is already true at month 4: you operate on facts, with a working communication cadence, with the right people in the right seats, and with strategic decisions queued up for serious work. Or you are still in observation mode, operating on impressions, with the wrong people in seats you have not dared touch, and a board that has started wondering what you are actually doing.

The choice is made in the first 90 days, by what you do and what you do not.

CEO transition Executive leadership Operational turnaround First 90 days
Ivan Sharov
Ivan Sharov

CEO at Crassula

Ivan Sharov is CEO of Crassula, a white-label digital banking platform. He writes on fintech infrastructure, pricing, market entry, and CEO leadership.

More about Ivan →