Founders hire a fractional CTO when they need senior technical leadership without a full-time executive hire—often pre-seed through Series A, sometimes during a transition after a lead engineer left. The engagement fails when the CTO delivers slides instead of production outcomes. The first 90 days should produce clarity, a credible architecture, and something shipped.
This is the playbook I use as a hands-on CTO-for-hire: architecture plus code, with weekly accountability to the founder.
Days 1–14: Technical audit and truth map
Week one is not roadmap theater. It is an honest inventory of what exists and what is blocking revenue or fundraising.
- Code and repo access — branches, deploy process, test coverage, dependency risk
- Production systems — hosting, databases, secrets, backups, incident history
- Product surface — auth, roles, payments, admin, analytics, support tooling
- Team reality — who can ship, where knowledge is trapped, contractor vs employee gaps
- Compliance and security baseline — PII flows, logging, access control, SOC2 path if needed
Deliverable: a one-page risk register ranked by business impact (revenue, churn, security, velocity)—not a 40-slide assessment.
Days 15–30: Architecture decisions and sequencing
With the truth map in hand, the fractional CTO makes the few decisions that are expensive to unwind later:
- Monolith vs services for the next 12 months (default: monolith until pain is real)
- Primary data store and migration strategy
- Auth model — sessions, OAuth providers, RBAC shape
- CI/CD and environments (dev/staging/prod parity)
- Build vs buy for payments, email, search, and AI features
Deliverable: a 90-day engineering sequence with one “north star” milestone—e.g. paid beta, marketplace liquidity, or enterprise pilot—and explicit deferrals.
A fractional CTO who cannot say “not yet” to features is not leading; they are staffing a backlog.
Days 31–60: Execution, standards, and team leverage
The middle month shifts from decisions to rhythm. I typically:
- Establish PR review standards, definition of done, and release cadence
- Ship or supervise the highest-risk remediation (auth holes, payment edge cases, data model fixes)
- Clarify hiring: next role (senior full-stack vs infra), interview rubric, trial project
- Unblock contractors with concrete tickets and acceptance criteria
- Introduce lightweight observability — errors, latency, key business events
Founders should expect the fractional CTO to be in the codebase during this phase, not only in meetings. If your CTO cannot demo the staging environment from memory, you have an advisor, not an operator.
Days 61–90: Ship the milestone and handoff clarity
The last month ties work to an external proof point:
- Cut scope to what the north star requires
- Run a stabilization week — bugs, monitoring, rollback plan
- Document runbooks for deploy, on-call, and data restores
- Present a post-90-day plan: hire, extend fractional, or hybrid
Deliverable: production milestone shipped plus a written operating model for engineering (who owns what, how releases work, where architecture docs live).
What founders should ask before day one
- What did you ship in your last fractional engagement, and can I talk to that founder?
- How many hours per week are hands-on engineering vs meetings?
- What will you refuse to build in the first 90 days?
- How do you work with existing agencies or offshore teams?
When a fractional CTO is not the right fit
If you need 24/7 on-call for a mature product, a full-time VP Engineering is appropriate. If you only need UI mockups, hire design. If you need growth marketing, do not disguise it as engineering. Fractional CTO work wins when the company needs architecture plus execution under time pressure.