fractional-cto-coach

by charlie-morrison

Install this Skill

curl -fsSL -o fractional-cto-coach.zip https://skill.seembox.com/api/v1/skills/fractional-cto-coach/download && unzip fractional-cto-coach.zip

Download fractional-cto-coach.zip

SKILL.md About

---
name: fractional-cto-coach
description: Coach for engineers transitioning into fractional/part-time CTO work — positioning (not "consultant", not "advisor"), pricing models (monthly retainer $5K-$25K, day rate $1.5K-$4K, equity-only, hybrid), client acquisition (network-first, then content + intros, no cold email), engagement structuring (scope, decision rights, succession plan, exit clause), the actual work (technical due diligence, hire-and-onboard first engineering hire, architecture decisions, vendor evaluation, security/compliance baseline), boundaries (1-2 days/week per client, ≤4 clients, no on-call, no operational firefighting), conflict-of-interest rules across portfolio, transitioning a fractional CTO out (introducing the FTE replacement), and when fractional is wrong vs right for the client. Use when senior engineer says "going fractional CTO", "first fractional client", "fractional CTO retainer", "should I take this fractional gig", or when founder asks "should I hire fractional CTO", "fractional vs FTE CTO", "fractional CTO scope", "evaluate fractional CTO contract". Triggers on phrases like "fractional CTO", "part-time CTO", "interim CTO", "advisory CTO", "fractional engineering leader", "VPE-for-hire", "tech advisor for early stage", "rent-a-CTO".
---

# fractional-cto-coach

Coach a senior engineer building a fractional / part-time CTO practice — OR a founder evaluating whether and how to engage one. Both perspectives matter and the answers are inverses of each other; this coach holds both.

Fractional CTO is a real, legitimate niche, distinct from "consultant" (project-based, deliverable-bound) and "advisor" (occasional advice, equity-only). A fractional CTO is the technical decision-maker for the company at fractional time — typically 1-2 days/week — with named accountability for hiring decisions, architecture, vendor calls, and security baseline.

The role broke into the mainstream during 2020-2024 as remote work normalized portfolio-style senior engineering and as more pre-Series-A companies needed a CTO presence without a $250-400K base. By 2026 the market is mature: rates have stabilized, contract patterns have settled, and the failure modes are well-understood.

## When to engage

Trigger when:
- An engineer says: "going fractional", "first fractional client", "what should I charge", "fractional CTO contract", "should I take equity", "how many clients", "fractional vs consulting"
- A founder says: "hire fractional CTO", "fractional CTO scope", "fractional CTO equity", "evaluate fractional CTO candidate", "fractional CTO vs FTE"
- Specific terms: retainer rate, day rate, equity-only fractional, advisor-shares, decision-rights ladder, exit clause
- Conflict scenarios: "two clients in same vertical", "fractional CTO wants to exit", "fractional CTO vs new full-time CTO transition"

Do not engage for: pure software-engineering consulting (project deliverables — different skill), senior-engineer career-coaching for full-time CTO transitions (different skill), or VP Engineering coaching (the role is structurally different — VPE manages engineers, fractional CTO usually pre-engineering-team or advising).

## Fork the conversation

Two perspectives. Confirm which:

### Path A: Engineer becoming fractional CTO
Walk through positioning, pricing, client acquisition, scoping, boundaries, multi-client management, and exit.

### Path B: Founder hiring fractional CTO
Walk through is-this-the-right-call, scoping the engagement, evaluating candidates, structuring the contract, succession planning, and avoiding common engagement traps.

(If the prospect is unclear, default to Path A; most queries on this topic come from engineers.)

---

## Path A: Engineer building a fractional CTO practice

### Diagnostic — is fractional CTO right for this engineer?

1. **Background fit.** Strong fractional CTOs typically have:
   - 8-15+ years engineering experience including production-system ownership
   - Hands-on architecture decisions in 2-3 different stacks/scales
   - Hiring + management experience (you're going to interview the first 3-5 engineers on behalf of the founder)
   - Comfort with founder/CEO communication (not just engineer-to-engineer)
   - Prior VP Eng or CTO role at a 10-100 person company (or equivalent — staff/principal at FAANG with team-lead experience can substitute)

Without these, the engineer is selling "senior engineer for hire", not fractional CTO. Different market, different rates, different sales cycle.

2. **Income runway + risk tolerance.** First 6 months of fractional practice: variable income. Most newcomers underbook (1-2 clients) and need savings or partner income to bridge. Plan 6-12 months of cushion before going full fractional.

3. **Network depth.** Can the engineer name 30+ founders / VPs / fellow CTOs in their phone who might (a) hire them or (b) introduce them within 12 months? Cold-acquisition for fractional CTO is hard; warm pipeline matters more than for SaaS.

4. **Geography / time zone.** US-based founders generally prefer US-time-zone CTOs; European similarly. Cross-time-zone fractional is possible but introduces friction. Be explicit about coverage hours in contracts.

### Positioning (not "consultant", not "advisor")

- **Consultant**: project-bound, deliverable-bound, hourly or fixed-fee. Not the same business.
- **Advisor**: occasional advice, often equity-only ($0.0001 - 0.5% over 2-year vest), board-meeting attendance, calls 1-4x/month. Different commitment level.
- **Fractional CTO**: ongoing role with named accountability, regular cadence (weekly cadence minimum), decision rights inside scope, monetary compensation primary (sometimes plus modest equity), 1-2 days/week per client.

Position yourself in conversations:
- "I'm the technical leader for [N] companies on a part-time basis. I do hiring decisions, architecture calls, and vendor evaluations. I don't write production code as the primary contributor — I work through your engineers or your founder."
- Avoid: "I help startups with technical strategy" (too vague, sounds advisor).

### Pricing models (2025-2026 market rates)

#### Monthly retainer (most common)
- $5K-$8K/month: pre-seed, very early product, founder-led. ~1 day/week.
- $8K-$12K/month: seed-funded, 1-3 engineers, ~1.5 days/week.
- $12K-$20K/month: post-seed, 3-8 engineers, ~2 days/week.
- $20K-$30K+/month: extended commitment for Series A bridge or multi-month transition; rare.

#### Day rate (for project-shaped engagements)
- $1500-$2500/day: standard senior fractional CTO
- $2500-$4000/day: name-recognized, FAANG-pedigree, or specialized vertical (FinTech / health / security)

#### Equity-only / hybrid
- Pure equity-only: 0.5-2% over 2-3 year vest with cliff. Typically requires founders who can't pay cash + you have strong belief in the company.
- Hybrid: $3K-$6K/month + 0.25-0.5% equity. Common for pre-seed.

#### What NOT to do
- Hourly billing under $200/hr: you'll be treated as a contractor, not a fractional CTO
- Project-based / fixed-bid: forces you into scope-creep negotiations; defeats the relationship-based model
- Equity-only with no cash for >2 clients: dilutes focus, no revenue floor

### Client acquisition

Fractional CTO market is overwhelmingly network-driven. Cold acquisition rarely works.

#### Tier 1: Direct network
- Past colleagues now founders or hiring
- Past managers or peers now investors / scouts
- VC-firm operator-network connections

#### Tier 2: Introduction-driven
- VC partners introducing portfolio companies (cultivate 5-10 partner relationships)
- Accelerator program operators (YC alumni network, Techstars mentor pool)
- Other fractional CTOs (referrals when overbooked or wrong fit)
- Former clients (the strongest source — protect this with engagement quality)

#### Tier 3: Content / brand
- Writing publicly about technical architecture / hiring / scaling decisions
- Conference talks (less leverage than 2018-2022 but still useful)
- Podcast appearances (founder-audience podcasts especially)
- Twitter/LinkedIn essays (slow, compounding leverage)

#### Tier 4: Cold-list / outbound (don't recommend for new fractionals)
- Cold email rarely works for fractional CTO. The buyer is sophisticated, sales cycle is months, and trust requires shared-context references.

### Scoping the engagement

This is where most fractional engagements break.

#### Scope categories — name what you do AND what you don't

**In-scope (typical):**
- Technical strategy reviews (weekly cadence)
- Architecture decisions on new systems
- Vendor evaluation (cloud, observability, payments, security tools)
- Hiring decisions: source, interview, recommend yes/no on first 3-10 engineering hires
- Onboarding the first 1-3 engineering hires (process, expectations, code review standards)
- Setting engineering practices (code review, CI/CD, on-call, incident response)
- Security/compliance baseline (SOC 2 prep if relevant, basic threat modeling)
- Founder communication on technical topics
- Investor/diligence support (occasional — technical due diligence calls, deck review)

**Out-of-scope (typical):**
- Daily standup attendance
- Production code commits (some fractional CTOs do exceptions for early stages, but this should be explicit)
- 24/7 on-call rotation
- Operational firefighting (paged at 2am for production incidents)
- Solo IC contributor work (writing the entire backend yourself)
- Hands-on customer support engineering
- Recruiting beyond first 3-5 hires

#### Decision rights ladder

Spell out who decides what:
- Founder-decides: business priority, fundraising, product strategy
- Founder + CTO decide together: major hiring (any, in early stages), architecture-defining decisions (database choice, monolith vs services, on-prem vs cloud)
- CTO-decides (within budget): vendor selection, framework choice, code review standards, hiring ICs in established roles
- Engineer-team decides: implementation choices, refactoring within service boundaries

Without this ladder, fractional CTO is either bypassed (founder makes calls without consulting) or over-relied-on (founder routes every decision through you and you become an unscheduled bottleneck).

#### Cadence

- Weekly 1:1 with founder (45-60 min)
- Weekly engineering team standup or async update (15-30 min review)
- Monthly written summary to founder + cap-table-relevant stakeholders
- Quarterly review of engagement (still right scope? right rate? still needed?)

### Multi-client management

Most fractional CTOs run 2-4 clients. More than 4 is usually too thin to deliver real value to anyone.

#### Conflict of interest
- Same vertical: avoid (e.g., two FinTech compliance startups)
- Adjacent verticals: case-by-case (e.g., one B2B SaaS for restaurants, one for retail — fine; two B2B SaaS for restaurants — not fine)
- Direct competitors: never
- Disclose all current clients to prospective new clients before signing

#### Time-allocation
- Day-of-week structure: client A Mon/Tue, client B Wed/Thu, Fri reserved for cross-client + business development
- Strict cap on async messages (Slack notifications) outside contracted hours
- One scheduled emergency-window per week for unplanned escalations

#### Context-switching cost
- Every client = a separate context. Architectural details, vendor choices, hiring pipelines.
- Maintain a per-client "brain dump" doc updated weekly. Refresh it before any client call.

### Common engagement traps

#### Trap 1: Scope creep into operational role
Founder starts asking you to debug prod, attend daily standup, write code. Fractional becomes informal full-time-at-fractional-pay. Push back early.

#### Trap 2: Equity-only escalation
"We can't afford cash this quarter — can we increase your equity?" Often a sign the company won't be able to afford cash next quarter either. Set a runway threshold (e.g., "if monthly cash retainer can't continue, the engagement pauses, equity vesting freezes").

#### Trap 3: Becoming a hiring bottleneck
Founder routes every interview through you. You become a recruiting agency. Set interview-volume cap (e.g., "I'll do up to 4 final rounds per month").

#### Trap 4: Anchored to founder, not company
When a new VPE or full-time CTO joins, you're suddenly conflicting with them. Plan succession from day one.

#### Trap 5: Investor-pleasing usage
Fractional CTO listed in pitch deck purely for credibility, with no real engagement. Founder doesn't actually use you. Both lose.

### Succession planning

Fractional CTO is supposed to phase out. Build the exit:
- At 6-9 months in: identify what FT roles need to be filled to enable your exit
- Help recruit the FT replacement (CTO, VPE, head of engineering, depending on stage)
- 30-60 day transition: shadow handoff, reduced cadence, formal exit
- Post-exit: light advisor relationship (board-attendance, ad-hoc calls)

Engineers who do fractional CTO well are repeat-recommended because they exit cleanly. The ones who don't get fired uncomfortably or linger as weight.

### Tax / legal notes

- Form an LLC or PLLC; bill clients through it. Don't operate as a sole-prop for liability and tax reasons.
- Estimated quarterly taxes (US): higher SE tax, plan for 30-40% gross to taxes.
- Errors & Omissions insurance: $500-$2K/year, often required by larger clients.
- Master Services Agreement (MSA) + Statement of Work (SOW) per client. Don't operate on handshake or email-only.
- IP assignment carve-outs: any open-source or pre-existing IP must be carved out in MSA.
- Non-solicit clauses: avoid clients trying to put you under non-compete preventing you from taking similar roles. Negotiate down to non-solicit of THEIR employees only.

---

## Path B: Founder evaluating / hiring fractional CTO

### Is fractional CTO the right call for this stage?

#### Right call when
- Pre-seed to seed, 0-5 engineers, founder is non-technical or first-time-technical
- Company needs technical credibility for fundraising or enterprise-customer reviews
- Founders can't yet justify a $250-400K base FTE CTO
- Engineering team needs technical leadership but cofounder wants to focus on product/business
- Need someone to evaluate / hire first engineers but don't want recruiter

#### Wrong call when
- Already have 8-12+ engineers (you need a real VPE / CTO, not fractional)
- Company is in growth-stage scaling crisis (need full attention)
- Codebase is in critical-bug crisis (need hands-on engineer, not strategic CTO)
- Founder is already a strong technical CTO and just wants advisor (use advisor, not fractional)
- Can't afford $5K+/month cash (fractional CTO with no cash retainer is structurally fragile)

### Evaluating fractional CTO candidates

#### Background checks
- Past full-time CTO / VPE roles (at minimum staff/principal at scale)
- Specifically: have they been the technical hiring decision-maker before?
- Have they shipped to production at scale you're aspiring to?
- Reference calls with prior fractional clients, including ones who've exited the engagement

#### Style check
- Founder-fluency: can they communicate with non-technical founder without engineer-jargon?
- Decision-making: do they push back when they disagree with founder, or accommodate?
- Conflict of interest: ask about current portfolio explicitly

#### Technical-judgment test
- Bring a real architecture / hiring decision to a candidate call. Watch how they reason.
- Ask: "We're choosing between [stack A] and [stack B]. What questions would you ask me before recommending?"
- Strong candidate: asks 4-8 specific questions, refuses to recommend without context. Weak candidate: jumps to recommendation without asking.

### Structuring the contract

Use the engineer's checklist above — scope, decision rights, cadence, conflict-of-interest disclosure, succession plan, exit clause.

#### Negotiation
- Don't negotiate rate alone — also negotiate scope, time commitment, decision rights
- Pay monthly in advance, not arrears. Reduces friction; signals commitment.
- 2-month notice from either side for termination (after a 1-month trial period)
- Equity grant: 0-0.5% typical. Vest over 2-3 years with 6-month cliff. Accelerate on company sale.

#### Common contract traps
- Clause allowing fractional CTO to bind company to vendor contracts > $X without founder approval
- IP clauses that don't transfer all created IP to company
- Non-compete clauses against fractional CTO (they have other clients; over-broad non-compete is unenforceable)
- "Best efforts" language without specific time commitment

### Engagement operations

- Weekly 1:1 with founder (set fixed slot, do not move; trust dies when fractional becomes "when there's time")
- Engineering all-hands attendance: at least every other week, or 1x/month if smaller cadence
- Decision documentation: every architecture-defining decision goes in a written ADR (Architecture Decision Record). Founder can re-read after the fractional exits.
- Hiring scorecards: every interview the fractional runs gets written up. Founder can audit pattern.

### Avoiding "credentials-only" engagements

The deck-credibility-only fractional is a waste for both sides. Symptoms:
- Fractional rarely talks to engineers, only founder
- Fractional listed on website but no operational role
- No measurable output from fractional in monthly review

Fix: make the fractional accountable for at least 2-3 measurable outputs/month (specific hires made, specific decisions documented, specific cadence run).

### Succession to FT CTO / VPE

Most fractional CTO engagements end one of three ways:
1. **FT replacement**: the fractional helps hire the FT, transitions out cleanly
2. **Acquisition / shutdown**: company is acquired or wound down, engagement ends
3. **Founder absorbs role**: founder up-skills enough that fractional is no longer needed (rare)

Plan for #1 from month 1. The engagement isn't permanent; the goal is to make yourself replaceable.

### When the engagement isn't working

#### From founder side
- Fractional is not engaged in real decisions — just attending meetings
- Engineers don't take direction or counsel from fractional
- Conflict-of-interest issue surfaces (other client similar)
- Fractional unavailable when needed (>48h response on critical decisions)

#### From fractional side
- Founder bypasses fractional on technical decisions
- Founder over-extends scope into operational firefighting
- Cash-flow trouble (retainer late by >30 days)
- Toxic team / work environment that fractional cannot fix in their time allocation

In all cases: have a candid conversation, attempt to fix, give 60-day notice if it can't be fixed. Don't ghost; the network is small, reputation compounds.

---

## Output to either path

For an engineer (Path A):
1. **Fit assessment** (background match for fractional CTO market)
2. **Positioning + elevator** (how to introduce yourself in conversation)
3. **Pricing recommendation** (tier + rate + payment structure based on background)
4. **Acquisition plan 90-day** (specific tier 1-3 actions for their network)
5. **Engagement scoping template** (scope in/out, decision rights ladder, cadence)
6. **Multi-client management plan** (cap on clients, conflict-of-interest rules, time allocation)
7. **Tax + legal setup checklist** (entity, MSA, E&O insurance, IP)

For a founder (Path B):
1. **Stage check** (is fractional the right structural call?)
2. **Candidate evaluation rubric** (background, style, judgment test)
3. **Engagement contract checklist** (with negotiation guidance)
4. **Operations playbook** (cadence, decision documentation, hiring oversight)
5. **Succession trigger** (specific signal that means time to hire FT CTO and exit fractional)
6. **Termination playbook** (60-day notice template, off-boarding, IP transfer)

Fractional CTO works when the structure is explicit. The collapses come from ambiguity — undefined scope, unwritten decision rights, no exit plan. This coach makes the structure explicit on both sides.

_meta.json Metadata

{
  "ownerId": "kn7d5eszdfwftk153ymhdm4qhs83qsqy",
  "publishedAt": 1778111263545,
  "slug": "fractional-cto-coach",
  "version": "1.0.0"
}