What does a Fractional CTO actually do? A typical month.

The most common question we get on a discovery call isn't about price. It's some version of: what would you actually be doing here?

The job title is part of the problem. "Chief Technology Officer" sits in the same conceptual bucket as CEO and CFO — an executive role that runs an entire function. When you compress that to a 6–10 hour-a-month engagement, the natural skepticism is: how do you do an executive's job in two hours a week?

The honest answer is that you don't. You concentrate on the parts of the executive's job that have the highest leverage and the longest half-life: the decisions that shape the next two years rather than the work that fills tomorrow. What follows is what a real month looks like in that role — not a brochure version, the actual rhythm.

Week one: the strategic check-in

Most months start with a 60-minute working session with the founder or COO. Not a status report — a working session. Agendas come from a running list of decisions that need an experienced technical voice in the room: a vendor up for renewal, a new system being scoped, a hire being interviewed, a piece of technical debt that's started to slow the team down.

A typical agenda might read:

• Decision needed: Renew the current ERP at the new contract price, or evaluate alternatives? (We're now 14 months in.)
• Risk to flag: Two senior engineers reported the same complaint about the deployment process. Worth investigating before it becomes a hiring issue.
• Open question: The CRM vendor announced a 40% price increase for next year. Push back, switch, or eat it?
• Roadmap touch: The AI rollout plan we set in Q1 — what's actually shipped, what's at risk?

You'll notice none of these are build a thing. The Fractional CTO's job in week one is to surface the decisions, frame the trade-offs, and make sure the founder isn't sleepwalking into one of them. We leave with three or four decisions either made or scheduled.

Week two: vendor calls and architecture review

Most of week two is spent on the work that came out of week one. If a vendor decision is on the table, that means scheduling pricing calls, reading the contract clauses that actually matter (data ownership, exit terms, SLAs), and putting together a one-page recommendation.

The architecture review is its own thing. Once a quarter we'll sit with the senior engineer or developer and walk the system — what's running, what's brittle, what's been hacked-around-rather-than-fixed for too long. The output is a short document: top three risks, top three opportunities, and what we'd do about each in the next 90 days.

The architecture review is where most engagements pay for themselves. Companies don't have technical debt because they're sloppy — they have it because nobody with the experience to triage it has sat down and named it.

Heavy weeks — a vendor migration in flight, a major incident — have a different shape. The CTO is on standby, not running the migration. The team runs the migration. The CTO calls the harder judgment calls: when to roll back, what to communicate, who to escalate to, when to accept that the timeline has slipped.

Week three: hiring and team

If you're hiring an engineer or technical lead, week three is when most of the work lands. The Fractional CTO writes the job spec (most companies' specs are too generic to attract real talent), helps design the interview — especially the technical screen — and sits in on the final-round interviews to assess fit.

If you're not hiring, this is where mentorship and process work happens instead. A 30-minute office hour with the senior developer to talk through whatever's on their mind. A review of the last sprint's deployment cadence. A conversation about what's slowing the team down that the team won't volunteer to leadership.

Mid-Atlantic talent markets are tight. A bad hire costs 3–6 months of salary plus the team disruption. An experienced technical voice in the interview loop — someone who can pressure-test technical depth in 45 minutes — pays back fast.

Week four: the heavy lift

The last week of the month tends to be the heaviest. This is when the deferred decisions come due: the budget for next quarter, the technology roadmap update, the hiring plan, the post-mortem on whatever didn't ship. It's also when the leadership team reads the monthly written summary — what we decided, what's at risk, what's coming.

The written summary matters. Most fractional engagements get into trouble when the work feels invisible — founders pay for hours and don't see what they bought. A two-page memo at the end of every month, listing decisions made and decisions coming, makes the value visible and gives leadership something to react to.

What it's not

Worth being explicit about what this doesn't include, because the gap between expectation and reality is where engagements break.

It's not writing production code as the deliverable. Some hands-on work happens — an architecture prototype, an evaluation script, occasionally a piece of glue code to unblock the team — but the engagement isn't priced as engineering hours. If you need code shipped, that's a separate scoped build.

It's not 24/7 availability. Same-day response when something breaks; next-day otherwise. If your business runs a 24-hour operations floor, you need an operations leader, not a fractional CTO.

It's not vendor reselling. Most managed-service shops earn a margin on the tools they recommend. We don't. Vendor recommendations are based on what's right for the engagement, not what carries a kickback.

It adapts to whatever value the leader actually wants. For some engagements that's a decisive technical voice in the chair — decisions queue behind bandwidth that doesn't exist, or no one in the room has the experience the call requires. For others it's an advisory seat at decision time — the leadership team will make the call, but they want a sounding board, a second opinion, or a fresh angle from someone with the scars to recognize the failure modes. And for some companies it's something closer to a trusted voice on call — the leader knows what to do most of the time, but wants someone to think out loud with when a hard call surfaces, a vendor turns hostile, or a hire isn't working. All three are legitimate, and most engagements are some blend of the three. The only consistent anti-fit is consensus rituals that don't produce decisions — meetings about meetings, perpetual steering committees, deferred calls. We can sit at the table; we just can't be the table.

What the founder gets out of it

Three things, in rough order of importance:

First, better decisions, on time. Most companies under 50 people don't lack good ideas; they lack an experienced practitioner who can pressure-test the ideas and make a call. A Fractional CTO removes the bottleneck where every decision queues behind the founder's bandwidth.

Second, fewer mistakes. Vendor lock-in, architecture choices that don't scale, hires that look great on paper and underwhelm on the team — the cost of these is hidden until it isn't. An experienced read in the room ahead of the decision is cheaper than fixing it after.

Third, a calmer relationship with technology. The founders we work with stop dreading the technology conversation. There's someone they trust whose job is to know what's coming, what's at risk, and what to do about it. That's a quieter mind, and a quieter mind makes better business decisions everywhere else.

If you're trying to figure out whether this shape of role would fit your company, the free 30-minute discovery call is the right starting point. Worst case you walk away with a clearer view of what your technical leadership gap actually is — and whether a fractional CTO is the right answer or not.