The First 90 Days with a Fractional CTO

Here's the test I'd give any fractional CTO before signing: ask what they'll do in the first two weeks. If the answer is a rebuild proposal, a platform migration, or a shiny roadmap deck, walk away. They're selling you their answer before they've seen your problem.

The first move of a real technology leader is a map of your reality. Not a pitch. A fractional CTO who shows the work in 90 days de-risks the whole engagement, because you can see exactly what you're paying for at every stage. Here's what that should look like.

Days 1 to 30: Shut Up and Map

The first month is listening and inventory. Not opinions. Not changes. Reconnaissance.

Map the systems. Every application, every integration, every server, every spreadsheet pretending to be a database. Most founders have never seen their own stack drawn on one page. That drawing alone changes conversations.

Map the spend. Software subscriptions, cloud bills, contractor invoices. Nearly every company I've looked at is paying for tools nobody's opened in months and cloud resources nobody can explain.

Map the contracts. Renewal dates, auto-renew traps, lock-in terms, licensing you've drifted out of compliance with. Surprises in contracts are expensive. Surprises found early are just line items.

Map the team. Who holds critical knowledge, who's stretched thin, who's about to quit, and which system dies if one specific person wins the lottery.

Map the risks. Security gaps, single points of failure, backup processes nobody's ever tested. Ranked by how much damage each one does, not by how interesting each one is to fix.

At day 30, you should hold a document that describes your technology reality better than anyone inside the building could. If you don't get that, stop paying.

Days 31 to 60: Prioritize and Execute

Now the map turns into action. This is straight from Ergon's pillars: Prioritize and Execute. Identify the highest-impact problem, put full effort on it, solve it, move to the next one.

Notice what that's not. It's not fixing everything at once. It's not a two-year transformation program. It's a ruthless stack-ranking of every problem on the map by one question: what happens to the business if we fix this, and what happens if we don't?

Usually the top of the list is unglamorous. Kill the zombie subscriptions and the unexplained cloud spend, which often covers a chunk of the CTO's own fee. Close the security gap that would end a customer relationship if it got exploited. Document the system that only one person understands. Fix the deployment process that makes every release a gamble.

By day 60 you should have finished fixes you can point to, with numbers attached. Dollars saved. Risks closed. Hours returned. Not progress reports. Results.

Days 61 to 90: Build Systems That Outlast Me

This phase is where a fractional CTO proves they're not building a dependency. The goal of the third month is to install systems that keep working when the engagement scales down or ends.

Documentation that lives. Architecture, runbooks, vendor contacts, decision history. Written so the next person, or the next crisis, doesn't start from zero.

Metrics that run themselves. A handful of numbers, reviewed on a schedule, that tell you whether technology is getting healthier or sicker. If the CTO has to hand-build the report every month, it's not a system. It's a hostage situation.

Decision frameworks. How you'll evaluate the next tool, the next vendor, the next hire, without needing me in the room. Clarity means your team can make the call and defend it.

Board reporting. Technology translated into risk, cost, and opportunity that a board can act on. If your board updates on technology are a slide of jargon, that's a leadership gap, not a communication style.

An organization should run on systems, not on individuals staying late. That includes the fractional CTO. If your consultant makes themselves harder to remove every month, that's not leadership. That's rent-seeking.

What This Costs You to Verify

Here's the practical part. A full-time CTO runs $250K to $400K or more per year in salary, bonus, and equity. Fractional engagements typically run a few thousand to low five figures per month, from ten hours a month up to three days a week. Which means 90 days is a cheap experiment with clear checkpoints: a map at day 30, finished fixes at day 60, running systems at day 90.

Miss a checkpoint, and you can walk with a small bill and a useful map. That's what de-risked looks like.

If you want to see what the first 30 days would surface in your business, start with fractional technology leadership.

Demand the map before the proposal. Anyone who won't show the work is hiding what the work would show.