Most businesses that hire a fractional CTO have the same quiet worry: will this person spend three months producing a strategy deck, then leave? A good engagement looks very different. The first 90 days are about earning the right to make decisions, then making a few that stick.
Here is what that looks like in practice.
Days 1 to 30: listen, map and stop the bleeding
The first month is mostly listening. We meet the leadership team, the people who run the systems day to day, and the main suppliers. We read the contracts, the invoices and whatever documentation exists. We look at the platforms themselves, not just the diagrams of them.
By the end of the month there are three outputs. A map of every system, what it costs and who owns it. A short risk register, ranked by likelihood and impact. And a list of things that need to stop now.
That last list matters. There is almost always something: an admin account shared by six people, a supplier renewing automatically at a higher price, backups that nobody has ever restored. These are rarely glamorous, but fixing them in the first month builds trust and reduces real risk.
Days 31 to 60: decide what matters
The second month turns the map into priorities. Not a long list of everything that could be improved, but the three to five things that will most change the business in the next year.
Each priority gets a one-page decision memo: the problem, the options, what each costs, what we recommend and why. The leadership team reads it, challenges it and decides. The decision is written down, with the reasons, so it survives the next restructure or staff change.
This is also when the operating rhythm starts. A short monthly report on spend, risks, decisions and progress. A regular slot with the leadership team. A clear line for suppliers about who approves what.
Days 61 to 90: the first decisions that stick
By the third month, the first decisions are in motion. A supplier has been renegotiated or replaced. A hiring plan has been agreed. A platform change has been specified, with a fixed price and a clear owner. An AI acceptable-use policy is in place, so the team knows which tools are approved for company data.
None of these are huge on their own. Together, they change how technology is run: decisions are made deliberately, written down and reviewed, rather than made by whoever shouts loudest or whichever supplier calls first.
What you should expect to see
At day 90, you should be able to answer four questions without calling anyone:
- What does our technology cost, and what do we get for it?
- What are our biggest technology risks, and who owns each one?
- What are we doing in the next six months, and why those things?
- Who decides what, and how do suppliers know?
If your fractional CTO cannot help you answer those by the end of the first quarter, something is wrong.
When it is the wrong model
A fractional CTO is not right for every business. If you are building a software product and need someone writing code every day, you need an engineering lead, not a part-time executive. If you have a strong full-time CTO already, you may only need an advisor for specific decisions.
The fractional model works best for businesses where technology is critical but not the product: retailers, lenders, logistics groups, professional firms. They need senior judgement a few days a month, not a full-time executive salary.
If you are not sure which you need, a CTO Diagnostic is a fixed-price way to find out.