What a fractional CTO actually does in the first 30 days.

You hire a fractional CTO. They're senior, they're confident, they have the right LinkedIn. They show up Monday morning, ask for Slack and GitHub access, and disappear. Two weeks later you get a Calendly invite for a status call. The status update is "I'm getting up to speed." Three weeks in, you get an invoice. By Day 30 you have nothing to show your board, your engineering team has not changed direction, and you can't articulate what specifically improved.

That's the disappointing version. It is the most common version. It happens because most fractional CTO engagements have no defined first-30-day outcome — just an open-ended retainer and a vague hope that "having a senior person in the room" will translate into something useful.

This post describes the version where it works. A real fractional CTO produces four specific, written, audit-able deliverables in the first 30 days. If yours can't, you're paying for company instead of work. Fire them.

Week 1 — The audit (no decisions yet)

The first seven days are not about fixing anything. They are about understanding the system in enough depth to make a decision worth signing your name to. A fractional CTO who proposes a technical strategy in week 1 is bullshitting. They have not yet read the code, talked to the team, or sat with the founder long enough to know what's true.

What the audit actually involves:

1. Read every line of production code. Not skim — read. The fractional CTO needs to know which files are old, which are fragile, which lock-in is real, which is theatre. This usually takes 6–12 hours for a typical Series-A SaaS codebase.
2. Map every external dependency. Vendors, APIs, third-party libraries, paid SaaS. Cost per month, replacement cost, lock-in level, last security review. This is a spreadsheet, not a vibe.
3. Talk to every engineer. 30-minute 1:1s, no founder in the room. Ask: what's broken? What scares you? What would you fix tomorrow if you could? What did your last manager get wrong?
4. Talk to five customers. Not the loudest. Not the friendliest. The ones who churned, the ones who almost churned, the ones who upgrade silently. Ask what they wish the product did better.
5. Sit with the founder. Two long conversations. The first is a download from them — what's the strategy, what keeps you up at night, what does winning look like in 18 months. The second is a confrontation — here's what I think the gap is between strategy and execution.

The deliverable at the end of Week 1 is a written technical audit, 3–6 pages, with a section per area: codebase, infrastructure, team, dependencies, customer signal, founder strategy. No recommendations yet. Just observations.

If your fractional CTO does not produce a written audit by Day 7 — fire them. They are not doing the work.

Week 2 — The decision

The second week is about identifying the single biggest constraint and proposing the single biggest leverage move.

This is the hardest part of the engagement. Most engineers, when asked what to fix, will list 15 things. A fractional CTO's job is to pick one. The criterion is not "what is the most broken thing" — it is "what is the constraint that, if removed, unlocks the next 6 months of progress?"

For an early-stage SaaS company, the answer is usually one of these:

• You ship too slowly. Cycle time from "merged to main" to "in production" is greater than 24 hours. Fix this first; everything else compounds.
• You don't know what's broken in production. No structured logging, no error tracking, no SLO, no single source of truth for "is the system healthy right now." Fix this second.
• The team can't make decisions without the founder. Every architectural call, every vendor call, every "should we build vs buy" goes back to the founder. Fix this by hiring or promoting a tech lead with the explicit authority to decide.
• The roadmap is not connected to revenue. Engineers ship things that nobody asked for and nobody pays for. Fix this with a written prioritization rubric tied to revenue, retention, or strategic positioning — and a quarterly review to enforce it.
• The codebase is one bad outage away from a rewrite conversation. A specific module — usually the oldest one — is fragile, unowned, and undocumented, and a single bug there could take the company down for a day. Fix this with a focused 4-week rewrite or replacement, fully scoped, before it bites.

The fractional CTO's deliverable at the end of Week 2 is a one-page Decision Memo. It states the constraint, why it's the constraint (with numbers, not vibes), the proposed leverage move, the cost in engineering hours, the cost in calendar weeks, and the expected measurable result. The founder signs it. The engineering team is briefed on it.

"I don't write recommendations. I write decisions. A recommendation is something the founder can ignore. A decision is something we are going to do, signed by both of us, with a date."

That's the bar. If your fractional CTO is producing recommendations instead of decisions, they are still hedging — and you are still paying for someone who has not committed.

Week 3 — The 90-day plan

Week 3 is where the engagement gets executable. The Decision Memo becomes a 90-day plan, with named owners, written milestones, and a budget — both engineering hours and any new spend.

The 90-day plan is not a Gantt chart. It is a small, opinionated document with five sections:

The plan is signed by the founder, the fractional CTO, and (where it matters) the affected engineering leads. It goes in a place everyone can find — a shared doc, a Notion page, a Linear cycle. It is reviewed at the end of every sprint.

If your fractional CTO has not produced this by Day 21, you have an expensive consultant, not a fractional executive.

Week 4 — Ship something

By Day 30, something measurable has shifted. This is the deliverable that distinguishes a fractional CTO from a fractional analyst.

What "something" looks like depends on what the constraint was. Concretely:

• If the constraint was deployment speed: a faster CI pipeline, a deployment that used to take 25 minutes now takes 6, observable in the GitHub Actions logs.
• If the constraint was production observability: structured logging in place across the three highest-traffic services, an error-tracking tool instrumented and showing real errors, a Sev-1 runbook in the team's hands.
• If the constraint was team decision-making: a tech lead promoted or hired, with the founder explicitly stepping out of architectural calls in standup. (You can hear this change in standup recordings.)
• If the constraint was roadmap discipline: the next 6 weeks of work re-prioritized against the rubric, with at least two pre-existing items explicitly killed and removed from the backlog.
• If the constraint was the fragile module: a written replacement plan with specific files, a feature flag in place, and the first 25% of the migration shipped to production behind the flag.

The point of Day 30 is not to declare victory. It's to demonstrate that the engagement produces motion, not just analysis. The fractional CTO who reaches Day 30 with no shipped change is one who hedges, debates, and bills — not one who leads.

The weekly pulse going forward

After Day 30, the cadence settles into a weekly Friday pulse. The pulse is a single short email or doc with five items, the same five every week:

1. What shipped this week against the plan.
2. What slipped this week against the plan, and why.
3. The single most important thing that needs to happen next week.
4. One open question or risk the founder needs to weigh in on.
5. The current numbers — the metrics tied to the constraint, week-over-week.

The pulse is short on purpose. Five items, four bullets each, no more. A fractional CTO who writes a 12-page status report every Friday is performing instead of executing. The pulse is a forcing function for clarity — and a record the founder can hand a board, an investor, or the next CTO without translation.

Five red flags your fractional CTO is faking it

If you are inside an engagement and you are not sure whether the fractional CTO is delivering, look for these five signals.

What to ask before you sign

If you're about to hire a fractional CTO, here are the four questions to ask in the first call. Their answers will tell you everything.

1. "Walk me through your last engagement, week by week." A real fractional CTO will narrate the audit, the decision, the plan, and the shipped change with specifics. A pretender will give you a generic methodology and dodge the names of clients and the specific numbers that moved.
2. "What's the smallest thing you've done that mattered most?" A real fractional CTO has a story about a 30-line code change, a vendor switch, or a single conversation that unlocked a quarter. A pretender talks about "transformation."
3. "What's the worst engagement you've had, and what was your role in why?" A real fractional CTO can describe their own contribution to a failure. A pretender blames the founder, the team, or the market.
4. "Send me a sample audit and a sample decision memo, both anonymized." If they can't, they don't produce these documents. You will not be the first time they start.

The shape of the engagement, in numbers

For a typical 10–25-person SaaS company, a fractional CTO engagement that delivers the four deliverables above costs roughly $5,000–$15,000 per month for 8–15 weekly hours. The hourly rate looks high; the cost relative to a missed quarter is small. (At Triad Global Solutions, our fractional CTO retainer is $8,000 per month for 10 weekly hours, capped at one client at a time so the engagement gets the senior judgment it's paying for, not someone splitting attention across six logos.)

The first 30 days are the most important. They establish whether the engagement will produce work or company. If your fractional CTO can produce the four deliverables above — written audit, signed decision memo, signed 90-day plan, first measurable shipped change — they will earn their retainer for the next 12 months. If not, the engagement is already over; you just haven't admitted it yet.

Hire well. Set the expectations clearly. And on Day 7, ask to see the audit.