A fractional CTO should not spend the first month announcing that everything must be rebuilt.
Sometimes a rebuild is needed. Sometimes the real problem is that nobody knows who owns the integration and the backup has never been tested.
The first month should make your technology situation easier to understand and safer to manage. Here is a practical engagement outline—not a promise that every business needs the same work.
Week one: find the business constraints
Start with the commercial plan. What must improve in the next quarter? Which customers or teams are affected? What cannot stop working?
Review the people, systems, suppliers and contracts involved. Identify who controls domains, hosting, source code and key accounts. Record ownership without circulating passwords in a spreadsheet called “FINAL passwords.”
The output should be a readable system map and a list of unanswered questions.
Week two: rank risks by consequence
A long risk register is not useful if every item is red.
Separate urgent operational exposure from inconvenient technical debt. Ask what could interrupt service, lose data, block delivery or create an expensive dependency.
Check evidence. “We have backups” is not the same as “we have recently restored the data we would need.” Agree who is responsible for follow-up.
Where specialist security, legal or compliance advice is needed, identify it explicitly rather than pretending one role covers everything.
Week three: make the next decisions easier
Clarify which work should be built, bought, delayed or stopped. Document why.
Review an important vendor proposal or delivery estimate against the business need. Establish a small set of acceptance criteria. “Looks good” should not be the entire test plan.
For AI projects, define what the system may access, which actions require approval and what success will be measured against.
Week four: leave a usable plan
The first-month deliverables should include priorities, owners, dependencies, expected outcomes and a review rhythm.
A good roadmap explains what will not happen yet. That protects the team from a backlog that quietly contains three years of work and a motivational deadline.
Ask for plain-language recommendations. If the board needs a translator to understand the technology update, communication is still unfinished.
A fractional CTO provides senior direction without automatically replacing your developers, agency or internal lead. Make those boundaries clear in the agreement.
