
Hire a fractional CTO when you need senior technical judgment 5 to 15 hours a week and don't yet own a roadmap that justifies a full-time hire. Hire a full-time CTO when you've crossed product-market fit, plan to grow the engineering team past five people in the next year, or have raised a Series A where the board expects a named technical leader. Below $1M ARR or pre-seed, fractional almost always wins on cost and speed. Above $3M ARR with a hiring plan, full-time becomes the obvious answer.
Every non-technical founder hits this wall around the same point: the MVP is shipped, two engineers are contracting on Upwork, and an investor asks "who owns your technical roadmap?" There is no good answer. The founder isn't qualified to answer it, the contractors don't have the context, and hiring a full-time CTO at $250k base plus 1-3% equity feels insane for a company that just crossed $400k ARR.
The fractional CTO market exists because that gap is huge and growing. In 2026, the cost of a US-based senior engineer with leadership experience has settled around $220k-$320k base, and equity grants for first technical hires routinely run 1.5%-3%. That's a one-million-dollar four-year decision being made by a founder who has never managed an engineer.
Fractional is a way to buy senior judgment in hourly slices while you figure out if you even need the full role. It is also the default move once founders read about how to find a technical advisor for your startup and realize an advisor is too light-touch for what they actually need.
The terms get used loosely. Here is what the market actually means in 2026:
Fractional CTO. A senior engineer (usually 12+ years experience, often ex-VPE or ex-founding-engineer) who works 5 to 20 hours per week across one or more startups. Billed hourly ($150-$400/hr) or weekly ($1,500-$8,000/wk). Their job is technical strategy, hiring decisions, architecture review, vendor selection, due diligence prep, and being the technical voice in board meetings. They do not write production code at scale. They sometimes write spike code or kick off a greenfield repo.
Full-time CTO. A salaried employee with equity, owning the engineering org end to end. They hire the team, set the roadmap, run sprint cadence, manage performance, and answer to the board for technical execution. Base in 2026 runs $220k-$350k for an early-stage technical leader in the US, with equity grants of 0.5%-3% depending on stage and stack-rank.
Technical advisor. A 1-3 hour/month relationship, usually unpaid or paid in 0.1%-0.5% equity. Useful for periodic gut-checks, useless for execution.
Founding engineer. Not a CTO. A heads-down builder taking 1%-2% equity who reports to the CEO. Many founders confuse this with a CTO and end up paying CTO-tier equity for an IC role.
These are different jobs. A fractional CTO running due diligence for your Series A is not the same person who should be building your auth system.
This is the matrix we hand to founders who ask. It is opinionated.
| Stage | Symptoms | Right answer | Wrong answer |
|---|---|---|---|
| Idea / pre-MVP | No code yet, validating with mockups | Skip both. Use no-code or book a mid engineer for the build | Hiring a full-time CTO before there's a product to build |
| Pre-PMF, post-MVP | $0-$500k ARR, shipping but not retaining | Fractional CTO 5-10 hrs/wk, plus 1-2 booked engineers | Full-time CTO. You'll burn $300k while pivoting |
| Approaching PMF | $500k-$2M ARR, retention improving, raising seed | Fractional CTO 10-15 hrs/wk, start fielding full-time candidates passively | Hiring a full-time CTO under deadline pressure |
| Post-PMF, Series A | $2M-$10M ARR, board seat filled, hiring plan for 5+ engineers | Full-time CTO. Hire them before the round closes if possible | Continuing fractional past 12 months post-Series-A. Board will lose patience |
| Scale | $10M+ ARR, multiple product lines | Full-time CTO with a fractional advisor on the side | Trying to run engineering through a fractional. Coverage breaks |
| Acquisition prep | Any stage facing due diligence | Fractional CTO with M&A experience, 20-40 hrs over 6 weeks | Hiring a full-time the week before the data room opens |
The pattern: fractional is the answer when the question is "do I need a CTO yet?" Full-time is the answer when the question is "who is leading my engineering org?"
You are pre-PMF. You will pivot. A fractional CTO who has watched twenty startups pivot will protect you from over-architecting. A full-time CTO with two years of stock vesting will not.
You need technical due diligence prep. Acquirers and Series B investors will tear into your codebase, your security posture, your data handling, and your dependency graph. A fractional CTO who has been on the other side of these audits (often as the technical buyer at an acquirer) compresses six weeks of pain into two. We wrote a longer guide on how to prepare for technical due diligence as a founder, and the pattern is the same: bring in a fractional, scope the work to six weeks, ship.
You need a board-ready technical voice for one quarter. Some boards demand to hear from "the technical lead" before approving a budget or a pivot. A fractional with credibility (ex-Stripe, ex-Shopify, ex-Anthropic) lands better than a junior full-time CTO you hired in a panic.
You're the technical founder but you've never managed engineers. A fractional CTO is functionally an executive coach plus an architecture reviewer. You stay in the code, they unblock you on hiring, vendor calls, and the parts of the role you've never done. This is the most underused mode.
Your runway can't absorb $300k of fully-loaded cost. Fully-loaded cost of a US-based full-time CTO at $260k base, plus benefits, taxes, equipment, and recruiter fees, lands around $340k-$380k in year one. A fractional CTO at $300/hr for 10 hours a week is $156k annualized, with no recruiter fee, no severance risk, no equity dilution.
You are hiring 5+ engineers in the next 12 months. A fractional cannot run that hiring loop. You need someone in the building, in every onsite, owning the bar.
Your product has cross-cutting technical bets. A migration from a Rails monolith to a Go services backend. A model-routing layer for an AI product. A multi-region data architecture for an enterprise sale. These require continuous ownership across calendar quarters. A 10-hour-per-week fractional will drop context every week.
Your board has explicit expectations. A16z, Sequoia, and most tier-one funds want to see a named technical leader by Series A. Showing up with a fractional after a $15M round signals that you couldn't close one. (This is a vibes thing, not a logic thing, but it is real.)
Your company sells to enterprise security teams. Vendor security questionnaires routinely ask for the name and title of the head of engineering or CTO. A fractional listed there reads as a red flag during procurement.
You are scaling past 20 engineers. Engineering management is a real job. A fractional cannot run quarterly performance reviews, calibrate compensation, or own retention. Past about 15-20 engineers, the absence of a full-time technical leader becomes the company's biggest scaling risk.
The cost gap is wider than founders assume because they compare base salary to fractional weekly, not fully-loaded cost to total spend.
| Line item | Fractional CTO (10 hrs/wk @ $300/hr) | Full-time CTO ($260k base, 1.5% equity) |
|---|---|---|
| Annual cash cost | $156,000 | $260,000 |
| Benefits + payroll taxes (~25%) | $0 | $65,000 |
| Equipment, software, ops overhead | ~$2,000 | ~$8,000 |
| Recruiter fee (one-time, 25% of base) | $0 | $65,000 (amortized year one: $65k) |
| Equity cost (4-year vest, $20M post valuation) | $0 | $75,000/yr non-cash |
| Severance / mis-hire risk | $0 (cancel anytime) | $50k-$100k expected value |
| Year one fully-loaded | $158,000 | ~$523,000 (incl. equity) |
| Year one cash burn | $158,000 | ~$398,000 |
Two caveats on the table above. First, a full-time CTO will hire and ship more than a fractional, so the cost-per-output can be lower at scale. Second, the equity line is non-cash but dilutes future rounds; if your next round is at a 5x markup, that 1.5% costs your existing investors and you about $1.5M of paper value per round.
The crossover point in our experience: when your engineering team passes four and your annualized revenue passes $2M, full-time becomes cheaper per unit of shipped roadmap. Below that, fractional is cheaper and more flexible.
Cadence's pricing tiers are flat weekly numbers, no recruiter fees, no equity, cancel any week:
The Lead tier ($2,000/week or roughly $104k annualized for full-time-equivalent hours) is positioned as the fractional CTO option. A typical Lead engagement on Cadence is 10-20 hours a week, which lands at $1,000-$2,000/week depending on scope. There are 12,800 engineers in our pool and every one is AI-native by default (vetted on Cursor, Claude Code, and Copilot fluency through a voice interview before they unlock the platform).
The honest framing: a Cadence Lead is a strong fit if you want fractional CTO coverage without the $300/hr hourly billing that gets adversarial fast. If you specifically need a name-brand ex-Stripe CTO for a board meeting next week, a boutique fractional firm with that exact relationship will serve you better. If you need senior technical judgment, architecture review, hiring rubrics, and someone to run technical due diligence prep, the Lead tier at flat weekly billing is usually the better economics.
We've seen the same pattern repeat: founders book a Lead for 4-6 weeks to handle a specific scope (Series A diligence prep, an architecture migration plan, the first three engineering hires), then drop back to a Senior or Mid for execution. Booking weekly with a 48-hour free trial means you can test fit without a recruiter call.
If you want to compare this to running a hiring loop yourself, we wrote about how to interview a developer when you can't code, and the math on time-to-hire alone is brutal.
If you're reading this at 11pm because the question is live for you, the next step is not "post a job on AngelList for a CTO." It's:
If you want a faster fractional path with weekly billing and no equity, book a Lead engineer on Cadence and use the 48-hour free trial to test fit. Worst case you spend two days finding out it's not the right shape and walk away with a written scope you can hand to the next candidate.
Most fractional CTO engagements run 5 to 20 hours per week, with 10 being the median. Below 5 hours you're effectively buying advisor time, not fractional time. Above 20 hours you're inside one or two days of a full-time hire and should evaluate whether the relationship should convert.
Some do, most don't at scale. The good ones write spike code, kick off a greenfield repo, or pair with an engineer to unblock a hard problem. Expecting a fractional CTO to ship production features at full velocity defeats the purpose of paying $200-$400 per hour. Pair fractional leadership with a Mid or Senior engineer (on Cadence or elsewhere) for shipping.
Most fractional CTO engagements are cash only. If equity is part of the deal it usually lands at 0.1%-0.5% with a 1-year cliff and a clause that converts to cash if the founder takes on a full-time CTO. Avoid giving fractional CTOs the same equity grants you'd give a full-time hire; the alignment is wrong and you'll regret it at the next round.
If the fractional is doing 15+ hours a week, has been with you for six months, knows the codebase, and the company is post-PMF, have the conversation. About 1 in 4 fractional engagements convert. Be honest about whether they want full-time work; many fractional CTOs deliberately chose the model and won't take a salaried role.
Pre-Series A, yes. Most seed investors are comfortable with a fractional CTO if the relationship is documented and the person is credible. Post-Series A, no; boards expect a named full-time technical leader within 6-9 months of close, and a strong fractional CTO will often help you hire your replacement before they roll off.
Ask for two reference calls with founders they've worked with for at least six months. Ask each reference: "What did they do that another senior engineer wouldn't have done?" If the answer is vague, the fractional is probably an IC in disguise. If the answer is specific (hiring rubrics, architecture trade-offs avoided, vendor selection saved, diligence prep), that's a real fractional CTO.