How to become a fractional CTO or CIO
Short answer: you don't need to learn technology leadership again. You need to turn the seat you held into something a founder can understand, scope and buy. Here's where I'd start.
First, which one are you selling?
CTO when the thing at the center is a technology product or an engineering team: architecture, engineering leadership, the technical roadmap.
CIO when the thing at the center is how the company uses technology to run: business systems, data, vendors, integration and security governance.
Use both only when the buyer really needs both and your record supports both. The scope settles it, not the slash.
Sort what you did into three columns
The judgment transfers. The machinery often doesn't.
| Carries over as it is | Has to be rescaled | Has to be dropped |
|---|---|---|
| Making build, buy, partner and retire decisions. The trade-offs are real at any size. | Architecture standards keep the principles but drop most of the required artifacts and review bodies. | Designing for enterprise scale before the business has enterprise demand. |
| Challenging vendor claims and contract assumptions. | Formal RFPs become a short requirement set, reference checks, a commercial comparison, exit terms and a decision record. | Running a six-month selection for a tool the company can test safely in two weeks. |
| Explaining technical choices to a board or a non-technical team. | Board reporting becomes a small set of decisions, exposures, commitments and changes. | Dashboards with dozens of indicators and no owner, threshold or decision attached. |
Three rows of fifteen. Do the rest for your own career, and delete anything you can't prove from direct experience.
Then say what you'd own, in one sentence
An offer isn't your biography. This is closer:
I work with founder-led operating companies with 50 to 250 employees when systems, vendors, data and cybersecurity decisions have become fragmented, to establish technology ownership and investment priorities, ending with a current-state map, a decision register, a 12-month roadmap and an operating cadence the internal team can run.
That's one example, not your market. Put in the kind of company you know, the moment they'd call you, what you'd own, and what they have when you're done. Then read it to a founder. If they don't recognize the problem straight away, keep working on it.
One line to hold: a short review isn't an audit, a penetration test or a legal conclusion. Don't call it one.
What this page doesn't cover
Whether to go fractional at all, how to shape the engagement, what the published price spans are, or who to approach first. Those take more than a page.
Next step
Still deciding whether to make the move? Start with the free Go Fractional workbook.
Already decided and it's the CTO or CIO seat? The CTO/CIO Pack has the full fifteen-row inventory, the fill-in offer structure with three worked examples, three engagement shapes with published US price spans, and the tracking sheet and outreach notes for your first approaches.