The first 90 days of a fractional CTO engagement decide whether you’ve bought senior leadership or an expensive advisor who attends meetings. Here’s what a good fractional CTO should actually deliver in each 30-day block — use it to set expectations up front and to judge the engagement honestly at day 90.
Quick answer
In the first 90 days a fractional CTO should deliver: days 1–30, an independent assessment of your technology, team and risks in plain English; days 31–60, a prioritised roadmap with architecture and hiring decisions made — not just recommended; days 61–90, a working operating rhythm: delivery cadence, board-ready reporting and measurable movement on the top risks. If day 90 arrives and you can’t name three things that changed, the engagement isn’t working.
Days 1–30: find the truth
The first month is about establishing an independent view of where the technology actually stands — not the view your agency reports, or the one in last year’s board deck.
- Stack and architecture assessment — what’s built, how it’s built, and where it will break under growth. Read the code, not just the diagrams.
- Team and vendor review — who is doing good work, where the gaps are, whether you’re getting what you pay your agency or offshore team for.
- Risk register — the genuine top risks (security, key-person, scalability, compliance), ranked by business impact, in language the board can act on.
- Cost baseline — cloud spend, licences and vendor contracts; there is almost always waste here that funds part of the engagement.
- Quick wins shipped — a handful of low-effort, high-impact fixes (backup discipline, access control, a deployment fix). Early proof matters.
The deliverable is a written assessment a non-technical founder can read in twenty minutes. If month one produces only meetings, say so — out loud, in week three, not at day 90.
Days 31–60: decide and commit
Month two converts findings into decisions. The distinction matters: an advisor recommends; a CTO — fractional or not — decides and carries the consequences.
- Technology roadmap — a prioritised, costed plan for the next two to four quarters, tied to business goals rather than engineering preferences.
- Architecture decisions made — the two or three structural calls that unblock growth: what gets decoupled, what gets replaced, what gets deliberately left alone.
- Hiring plan — the roles that actually move the needle, realistic Australian salary bands, and job descriptions written; interviews started where roles are critical.
- Security baseline set — proportionate controls (Essential Eight-style basics first), with owners and dates rather than aspirations.
- Vendor decisions — renegotiated, replaced or retired where the month-one review found problems.
Days 61–90: build the rhythm
Month three is where the engagement either becomes an operating system or degrades into a standing meeting.
- Delivery cadence running — releases on a predictable rhythm, work visible, deployment no longer an event to fear.
- Board and investor reporting — a repeatable technology update: progress, risk movement, spend — in the format your board actually reads.
- Metrics that matter — a small set (release frequency, incident count, uptime, cost per customer) tracked and trending, not a vanity dashboard.
- Top risks measurably moved — the day-30 register revisited, with the top items retired or visibly shrinking.
- Knowledge captured — decisions and architecture documented, so the value survives the engagement and any single person.
How to judge day 90 honestly
Ask three questions, and require specific answers:
- What do we know now that we didn’t at day zero? There should be a written, independent picture of the platform, team and risks.
- What decisions got made? Roadmap, architecture, hiring, vendors — decisions, not discussion papers.
- What can we measure that moved? Even one number — release cadence, incidents, spend — trending the right way.
If the answers are thin, the polite move is a direct conversation; the professional move from the CTO’s side is to have raised it first. Scope, cadence or fit can all be fixed at day 90 — at day 180 you’ve simply paid twice as much to learn the same thing.
What this costs while it’s happening
The 90-day arc above is realistic on 10–20 hours per month — A$5,500–A$11,000/month on our published plans, which is where most growth-stage engagements sit. A 2-hour advisory tier reviews decisions; it doesn’t run this program. Full market numbers are in our 2026 cost guide, and our published pricing shows exactly what each tier includes.
Frequently asked questions
Is 90 days enough to see real change?
Yes — visible, measurable change. It’s not enough to finish a re-architecture or rebuild a team, but cadence, reporting, risk movement and made decisions are all reasonable to demand by day 90.
What if our platform is in worse shape than expected?
Then the day-30 assessment says so plainly, and the day-60 roadmap gets re-scoped with you — that’s the point of an independent view. What shouldn’t change is the honesty of the reporting.
Should we set these expectations in the contract?
Set the deliverables (assessment, roadmap, reporting rhythm) in the SOW; leave the specific findings open — you’re buying judgement, not a predetermined answer. Our hiring guide covers contract terms in detail.
What does the fractional CTO need from us to hit this?
Access from day one (code, infrastructure, numbers), introductions to team and vendors, and a standing slot with the founder. Engagements stall on access more than on anything technical.
Want this program run on your platform? See our published pricing, read how to hire a fractional CTO in Australia, or book a discovery call.