What to Expect in Your First 90 Days with a Fractional CTO

Hiring a fractional CTO is not the same as hiring a permanent one, and the first 90 days should not look the same either. The time horizon is shorter. The brief is usually tighter. And the way value gets created is different.

I've started a lot of these engagements, across SaaS businesses, PE-backed platforms, and founder-led companies that needed senior tech leadership before they were ready to hire full-time. The first 90 days almost always follow a recognisable shape. Not a rigid playbook, but a pattern. Understanding that pattern helps both sides get more out of the engagement.

This is what you should expect, what you should push for, and what to watch out for.

Days 1 to 14: Assessment

The first two weeks are about understanding the landscape. A good fractional CTO will spend this period asking more than they talk. If someone comes in on day one with a transformation plan, that's a warning sign, not a selling point.

What I focus on in the first fortnight:

• The technology. Reading the code, reviewing the architecture, understanding the deployment setup. Not to judge, but to know what's there and what it means for the business.
• The team. One-to-ones with every engineer, lead, and relevant stakeholder. Who's good? Who's stretched? Where are the bottlenecks?
• The roadmap. What's been promised to customers, investors, or the board, and how realistic is it given what the team can actually deliver?
• The debt. Technical debt is always present. The question is whether it's manageable background noise or something that's actively slowing the business down.
• The quick wins. What can be fixed or improved in the first 30 days without major risk? These matter, not because they prove anything in isolation, but because they build trust with the team early.

By the end of day 14, there should be a written assessment. Not a 40-slide deck with recommendations. A clear, honest document that says: here's what I've found, here are the three or four things that matter most, and here's how I think we should approach them.

If that document surprises the founders or the board, that's useful information in itself.

Days 15 to 45: Priorities and Quick Wins

Once the assessment is done, the work shifts to setting the agenda and beginning to move on the most important things.

This is where a fractional CTO engagement starts to feel different from a consulting engagement. The job is not to produce recommendations. It's to get things done, or to unblock the people who can.

In this window, I focus on:

• Establishing cadence. Weekly engineering meetings, a clear sprint rhythm, regular one-to-ones. If these don't exist, put them in place. If they exist but aren't working, fix them. Cadence is what turns a group of engineers into a team.
• Fixing the obvious things. Every technology function has things that are quietly slowing it down and that everyone knows about. Broken deployment pipelines. Undocumented APIs. Test coverage that exists on paper but not in practice. These get addressed now.
• Setting the 90-day plan. With the assessment as the foundation, agree a focused plan with the leadership team. Not a five-year roadmap. What matters in the next two months, why, and how we'll know it's done.
• Starting the team development work. If there are gaps, that conversation starts now. If there are people who need to grow into bigger roles, that becomes part of the plan. A fractional CTO who isn't developing the team around them is not doing the job fully.

By day 45, there should be measurable progress on at least one or two things that the business cares about. Not everything. But enough to show that the engagement has traction.

Days 46 to 90: Delivery and Rhythm

The final third is about moving into a sustainable pattern and proving that the fundamentals are in place.

This looks different depending on the context. In a seed-stage startup, it might mean shipping faster and with fewer bugs. In a PE-backed platform, it might mean getting the technology function ready for an acquisition or integration. In a business preparing to hire a permanent CTO, it might mean making the handover as clean as possible.

But there are a few things that tend to show up across most engagements in this window:

• Board and investor reporting. If the company has investors, they need to understand the state of the technology. Clear, honest reporting builds confidence and surfaces issues early. A fractional CTO should be able to write or present the technology section of a board pack.
• Architecture decisions. The bigger decisions, the ones with long-tails, tend to come into focus around the 60-day mark. Cloud platform choices, data infrastructure, API architecture. These should be made with the team, with the evidence from the first two months behind them.
• Hiring plans. If there are gaps in the team, a hiring plan should be taking shape. Role definitions, seniority levels, process. The fractional CTO should be leading or at minimum shaping this.
• Documentation. Boring but important. What should the next person know? Whether that's a permanent CTO joining later, or the team continuing without senior external support, the knowledge needs to be written down.

What Good Looks Like at Day 90

By the end of a well-run fractional CTO engagement, you should be able to see:

• A technology assessment that the leadership team has read and agrees with.
• Two or three meaningful things shipped or fixed that wouldn't have happened otherwise.
• A team that knows what it's working on, why, and how it fits together.
• A roadmap that's honest about trade-offs, not just a list of features.
• A board or investor pack that describes the technology function clearly and credibly.
• A hiring plan if headcount was needed.
• Either a permanent CTO who's ready to take over, or a clear recommendation on what that hire should look like.
• A handover document that means the engagement can end without creating a gap.

None of these are complicated in theory. What makes them hard in practice is that they all require focus, difficult conversations, and consistent follow-through, which is exactly what the engagement is there to provide.

What Bad Looks Like at Day 90

Not every fractional CTO engagement delivers what it should. Some warning signs that an engagement hasn't worked:

• The assessment never happened, or it was vague. If there's no clear view of the technology landscape after 90 days, the time wasn't well spent.
• Nothing was shipped. Advice without delivery is consulting. A fractional CTO should be moving things, not just commenting on them.
• The team doesn't know who they're working for. If the engineers are confused about priorities, authority, or direction after three months, that's a leadership failure.
• The board still can't describe the technology. If the investors still have no idea what's going on in the technology function after 90 days, the fractional CTO hasn't done the communication work.
• The engagement keeps extending without a plan. A fractional CTO role should have an end state, or at least a direction of travel. If it's just rolling over every month with no clear purpose, something is off.

These things can usually be fixed if spotted early. The risk is that neither side raises them until too late.

Working With Me

I take on a small number of fractional CTO engagements at any one time. Most are with PE-backed businesses, SaaS companies between Series A and Series C, and founder-led companies that need senior technology leadership before they're ready for a permanent hire.

For more on what the role involves day to day, read what does a fractional CTO actually do. If you're in a post-acquisition context, the post-acquisition integration playbook covers the specific dynamics of that window.

If you want to talk through whether a fractional engagement is the right fit, the advisory page has more detail on how I work, and the about page has background on my experience.

Frequently Asked Questions

How long does a fractional CTO engagement typically last?

Most engagements run for three to six months. Some extend beyond that if the need is ongoing, particularly where a permanent CTO hire is taking longer than expected. A few are shorter, perhaps six weeks, where the goal is a specific assessment or a handover. The length should match the purpose. An engagement that just keeps rolling without a clear end state is usually a sign that the brief needs revisiting.

What does a fractional CTO actually do in the first week?

The first week is almost entirely listening and reading. Conversations with the engineering team and leadership, working through the codebase and architecture, understanding the roadmap and what's been promised to customers or investors. The goal is to understand what's actually there before forming any views about what should change. Anyone who arrives with a fixed plan on day one hasn't done this work.

How is a fractional CTO different from a consultant?

A consultant typically produces analysis and recommendations. A fractional CTO is in the business, working alongside the team, making decisions, and being accountable for outcomes. The engagement is closer to a part-time employee than an external adviser. That distinction matters when it comes to trust, authority, and what the role can realistically achieve.

How do I know if my business is ready for a fractional CTO?

The most common trigger is a technology function that's grown to a point where it needs senior leadership, but where a permanent CTO hire isn't yet warranted or funded. You might have five to ten engineers, a product that's getting more complex, and a founder or CEO who's been managing the technology function by default. If that describes your situation, a fractional engagement is probably the right next step. The fractional CTO page covers this in more detail.

What should I have ready before the engagement starts?

The most useful thing is access. Codebase, documentation, the backlog, any existing architecture diagrams, recent board packs, and introductions to the key people in the team. The more context is available from day one, the faster the assessment phase goes. If documentation is thin, that's fine, it's common. But it's better to know that going in than to discover it in week two.