What a fractional CTO does in the first ninety days at a mid-market company

Many mid-market companies do not have a technology leader. They have a CEO or CFO making technology decisions alone, a CRM that does not talk to the phone system or the billing tool, a back office that runs on copy-paste and memory, and a growing pile of AI vendors whose claims nobody can evaluate. A fractional CTO is the seat that owns all of that, without a full-time salary. This is what the seat does in its first ninety days.

Days 1 to 30: the map and the baseline

Every system you run, what it costs, where the data lives and where it leaks. Most businesses have never seen this drawn. Alongside it, a baseline: hours spent on the repetitive work, turnaround times, the manual handoffs between tools. McKinsey's automation research estimated about 30 percent of activities in most occupations as automatable with technology already demonstrated; the map shows where your 30 percent actually sits. By day thirty the two or three integrations worth the most are named, and so is the number the seat will own.

Days 31 to 60: connect and automate

The core systems integrated so data moves without re-keying. The first automations live on the highest-volume back-office work: intake, documents, scheduling, reporting assembled without anyone building it. Deloitte's 2022 survey of 479 executives found organisations that scaled intelligent automation beyond pilots reported an average cost reduction of 32 percent; in a mid-market company the same work returns hours to the people who sell and deliver.

Days 61 to 90: the roadmap and the rhythm

An AI roadmap for the year, sequenced by revenue impact rather than by what is fashionable, agreed with your leadership. Vendor decisions made against the map: build, buy or retire, contracts renegotiated, duplicates gone. Security and continuity basics brought to a standard a buyer or an insurer would accept. A monthly technology review installed, so decisions keep being made after the ninety days end.

What the seat is not

It is not a developer; the build team builds and runs the automation and the integrations. It is not a vendor's representative; the fractional CTO's only interest is the map and the number. And it is not a reason to rebuild everything. McKinsey found only 7% of organisations had scaled AI into results; most of the rest bought technology before they understood the workflow. The first job of this seat is to understand the workflow.

What you should see

A one-page map by day thirty. Hours returned by day sixty, measured against the baseline. A roadmap and a review rhythm by day ninety. If you cannot see those three things, the seat is not working, and you should say so.