Part-Time vs Fractional vs Interim vs Advisor

These terms are used interchangeably in marketing copy, but the engagements differ in scope, time commitment, and authority. Founders who hire the wrong shape for their problem usually end up paying for hours they cannot use.

• Part-time CTO: ongoing retainer, 1-3 days per week, executive authority, multi-month engagement, typically serves 2-4 clients in parallel
• Fractional CTO: umbrella marketing term that includes part-time CTOs, advisory CTOs, project CTOs. Most providers use it to mean 5-20 hours per week on retainer
• Interim CTO: full-time or near-full-time, fixed 3-9 month window, covering a departure, turnaround, or M&A integration. Day rates run higher than part-time
• Advisory CTO: 2-8 hours per month, no decision rights, paid mostly in equity (0.25-1%), used as sounding board not operator
• CTO-as-a-service from an agency: a named senior plus a bench of engineers. Strategic input bundled with delivery hours, which can mask whether strategy is actually independent
• Co-founder CTO: full-time, 10-50% equity, on cap table, no monthly cash
• Rule of thumb: need someone to own technology end-to-end but cannot afford an executive salary, part-time CTO is right. Need a coach, hire an advisor

What Two Days a Week Actually Looks Like

A two-day-per-week engagement is roughly 16 hours of focused time plus async availability the rest of the week. Most part-time CTOs structure those days as one heavier in-person or video block and one operational block, with Slack and email coverage throughout the week for urgent decisions.

• Day 1 (typically Monday or Tuesday): founder one-on-one, engineering standup, architecture and roadmap review, technical interviews if hiring is open
• Day 2 (typically Thursday): vendor calls, code review of high-risk changes, hiring pipeline review, board or investor prep when relevant
• Async between days: Slack response on technical decisions within hours, PR review on critical paths, on-call escalation for production incidents needing executive input
• Monthly: written technical update for board or investors, vendor and cost review, hiring forecast against runway
• Quarterly: architecture review, security and compliance posture check, roadmap reset against company OKRs
• Coverage gaps: a part-time CTO is not a duty officer. Pager rotation, incident commander duties, daily code shipping stay with the engineering team
• Flex up: most retainers allow temporary bump to 3-4 days during fundraising, technical due diligence, key hires, or product launches at same blended day rate

When an Early-Stage Startup Actually Needs One

The model is wasted on companies that need code shipped and oversold to companies that just need an advisor. The signal is not stage alone but the gap between technical decisions being made and the seniority available to make them.

• Pre-product, non-technical founder: about to pick a stack, hire an offshore agency, or sign a build contract. A part-time CTO at 1 day per week prevents $50K-$200K of rework
• Post-product, pre-seed: MVP from contractors or junior team, need to decide what to throw away before raising
• Post-seed, pre-Series A: 4-10 engineers, no senior leader, founder is de facto CTO and it is becoming the bottleneck. Most common entry point
• Pre-fundraise: investors will run technical due diligence and the founder cannot answer architecture, security, or scaling questions credibly
• Post-acquisition or post-pivot: existing CTO has left, full-time search will take 4-6 months, the company cannot stall
• Regulated domain entry (fintech, health, defense): need a named accountable technical executive for compliance documents
• Skip if: pre-idea, need pure execution and have a strong tech lead, or runway under 4 months (use the cash for engineers)

What a Part-Time CTO Owns

The point of the role is judgment, not throughput. The deliverables are decisions and hires, not pull requests. A good part-time CTO writes very little production code on purpose.

• Architecture and stack decisions: database, hosting model, framework, boundaries between services. Documenting tradeoffs for the next CTO
• Engineering hiring: job descriptions, sourcing through their network, running technical interviews, calibrating offers, negotiating start dates
• Vendor and contractor selection: evaluating agencies, choosing infra and SaaS vendors, negotiating contracts, killing underperforming relationships
• Investor and board conversations: technical sections of deck, due diligence Q&A, board updates on engineering progress and risk
• Security, compliance, IP basics: clean code ownership, secrets management, SOC2 or GDPR prep, founder not personally exposed
• Engineering process: standups, sprint cadence, on-call, postmortems, code review standards, calibrated to team size
• Budget and runway: cloud spend, headcount plan, build vs buy decisions tied to next 12-18 months of cash
• NOT owned: daily ticket execution, line management of every engineer once team passes 6-8, design or product roadmap ownership

Engagement Structure, Cash, and Equity

Most engagements are month-to-month retainers with a 30-day notice clause on either side. Long fixed terms are a warning sign. Equity is optional and almost always small.

• Contract: monthly retainer, 30-day rolling notice, defined hour band (e.g. 50-70 hours/month) with flex clause for bursts
• Cash retainer: paid monthly in advance, not arrears. Late payment is the leading cause of part-time CTOs disengaging quietly
• Equity when granted: typically 0.25-1.0% for a 12-24 month engagement, 4-year vesting with 3-12 month cliff. Some part-time CTOs decline equity to stay independent
• Hybrid structures: at pre-seed, 50/50 cash and equity common (e.g. $2,500/month cash + 0.75% equity). At seed and later, equity drops or disappears as cash retainer rises
• IP and confidentiality: standard work-for-hire assignment, mutual NDA, conflict-of-interest clause naming direct competitors they cannot take on
• Expenses: pass-through for travel, conferences attended on behalf of company, tools bought in company name
• Exit clause: written handoff scope (documentation, hiring pipeline transferred, vendor relationships introduced) triggered when a full-time CTO is hired

Pricing Benchmarks (US, UK, EU, 2026)

Rates have hardened over the last two years as senior engineering leaders moved into fractional work full-time. The numbers below are the realistic range for an operator with 10+ years experience and at least one previous CTO role.

• US hourly: $200-$500/hr, with $600+ for specialist domains (AI infra, payments, regulated health)
• US day rate: $1,500-$4,000/day. New York and Bay Area cluster at the top
• US monthly retainer (2 days/week): $8,000-$15,000. Executive tier at 3-4 days reaches $15,000-$25,000
• UK day rate: £1,000-£1,600/day. London at top, Manchester/Leeds £800-£1,100
• UK monthly retainer: seed-stage 1 day/week £1,500-£3,000, growth-stage 2-3 days £4,500-£7,000, Series A 3-4 days £6,000-£10,000
• EU monthly retainer: €4,000-€10,000 for 1-2 days/week, €10,000-€20,000 for heavier engagements
• Full-time comparison: US Series A CTO package totals $280K-$450K all-in; UK equivalent £180K-£280K. Part-time at 2 days/week typically lands at 35-45% of those figures
• Red flag: anyone quoting under $100/hr is a senior engineer renaming themselves. Anyone quoting over $1,000/hr without specific specialism is selling brand, not time

The Handoff to a Full-Time CTO

The most underrated part of the engagement is the exit. A part-time CTO who cannot describe how they will be replaced is selling indefinite dependence. The trigger is usually the team reaching 8-15 engineers, a Series A close, or the founder needing a full-time technical co-pilot for the next 5 years.

• Decide the trigger up front: team size, fundraise milestone, or revenue threshold. Write it into the engagement letter
• Outgoing CTO writes the job spec, comp band, and target archetype for the full-time hire
• They run the search alongside the founder, using their network as first pass, then external recruiters
• 30-60 day overlap with the new full-time CTO: weekly transition meetings, vendor and engineer introductions, transfer of documentation
• Architecture decision log, hiring pipeline, vendor contracts, and credentials transferred in writing
• Optional advisory tail: many part-time CTOs continue at 2-4 hours/month as advisors for 6-12 months post-handoff
• Equity: vesting continues through overlap period, then stops at the agreed end date. Unvested equity returns to option pool

Common Failure Modes

Most failed engagements are diagnosable in the first 60 days. The patterns repeat across founder communities.

• Hired an advisor when you needed an operator: opinions on weekly calls but never a decision, no hires, owns nothing. Wasted retainer
• Hired a coder when you needed a CTO: senior engineer at part-time rates ships features but cannot run vendor negotiations, board updates, or executive hiring
• Too many concurrent clients: part-time CTO running 5-6 clients in parallel is structurally unavailable. Cap them at 3-4 for a 2-day/week slot
• Domain mismatch: B2B SaaS veteran on a consumer hardware company, web generalist on a payments startup. Domain transfer time eats the retainer
• No written scope: drifts into ad-hoc Slack, founders feel they are paying for nothing, CTO feels constantly interrupted
• Founder will not delegate: founder approves every technical decision anyway, CTO is a paid spectator
• Equity-only at pre-seed: usually under-deliver because cash-paying clients get priority. Pay something, even $1,500/month
• No handoff plan: 18 months in, company scaled, CTO still part-time, knowledge locked in their head, founder cannot afford to lose them or replace them

How to Interview a Part-Time CTO

The interview should test for operating judgment, not technical trivia. A 60-90 minute first call plus one reference check from a previous founder client is usually enough.

• Ask for two specific previous engagements, what they owned, and what the founder would say if you called them. Then call those founders
• Ask how they would spend the first 30 days at your company. A vague "audit and listen" is weak; specifics about your stack and team are strong
• Ask for an example of a vendor or hire they fired, and how they handled it. Tests executive willingness to make unpopular calls
• Ask what they would NOT do for you. If answer is "anything you need," they do not understand the model
• Ask how many other clients they currently have and on what days. Confirm capacity for your 2-day slot
• Ask for a written technical assessment of your current product or plan, paid as a one-week trial at their day rate. The output tells you more than any interview
• Reference the handoff explicitly: "How and when will you make yourself unnecessary?" A good answer includes a team size or fundraise trigger
• Confirm domain depth on at least one of your hard problems (scaling, compliance, AI, payments, mobile). General CTO experience not enough on specialist problem

FAQ