Fractional CTO vs. fractional engineering team

“Fractional” got popular enough that two very different services now share the adjective, and founders regularly buy the wrong one. A fractional CTO is senior technical judgment, a few hours a week. A fractional engineering team is capacity: people who build the product. Confuse them and you either hire an advisor and wonder why nothing ships, or hire builders and wonder why nobody stopped you from the wrong architecture.

We run the capacity kind, so mind the incentive as you read. The distinction itself, though, isn’t controversial; it’s mostly definitional, and getting it right is worth real money.

What a fractional CTO does

A fractional CTO is an experienced technical executive who gives your company a slice of their week: commonly four to ten hours across a couple of standing calls plus async availability. Market pricing varies a lot; think somewhere in the $200 to $400 an hour range, or $3k to $10k a month on retainer.

What that buys, when it’s good:

• Architecture decisions with scar tissue behind them. Build vs. buy, monolith vs. services, which database, which corners are safe to cut. Wrong answers here cost quarters; a few hours of the right person is cheap insurance.
• Translation. Between you and investors (“is our tech story credible?”), you and vendors (“is this quote sane?”), you and your own team (“is what they’re telling me true?”).
• Hiring judgment. Writing the job spec for the first engineer, interviewing finalists, designing the work-sample. Arguably the highest-leverage few hours they’ll give you, per the stakes of the first hire.
• Vendor and codebase audits. Reading an agency’s proposal or an inherited codebase and telling you what’s real.

What it doesn’t buy: software. A fractional CTO reviewing four hours a week produces zero features. That sounds obvious written down. It stops being obvious in sales calls where “technical leadership” is pitched as the missing piece of a company whose actual missing piece is a working product.

What a fractional engineering team does

Builds the thing. Specialties booked by the week (mechanics here), shipping working software on a weekly cadence: the full-stack build, the design pass, the deploy pipeline, the QA sweep. Costs scale with booked days; a one-engineer steady week runs about $1,750 at our from-rates, and a launch-push month with three seats runs low five figures.

What capacity doesn’t buy: a standing executive whose job is to tell you the roadmap is wrong. A good crew will flag bad ideas in their lane (“this schema will hurt in six months”) and a good provider’s senior people carry real judgment. But nobody on a day rate owns your three-year technical strategy, and pretending otherwise is how the two services get confused from the other direction.

The 2×2 that sorts it

Two questions: do you have technical judgment in the founding team, and do you have building capacity?

	Have capacity	Lack capacity
Have judgment (technical founder)	You’re fine. Ship.	Fractional or in-house team
Lack judgment (non-technical founders)	Fractional CTO to steer what you have	Usually both, sized to stage

Three of the quadrants are straightforward. The interesting one is bottom-right: non-technical founders with nothing built yet, which describes a lot of pre-seed companies. The failure pattern there is buying only one:

• Only a CTO: beautifully architected plans, no product. Twelve advisory hours a month can’t build an MVP.
• Only a team: product ships, but nobody with scar tissue owned the “should we?” questions, and some of them compound. (A candid crew mitigates this. It doesn’t replace it.)

The working pattern we see: a light CTO engagement (even four hours a month) setting direction and reviewing the big calls, plus a build crew doing the actual weeks. On MVP-stage budgets that combination often costs less than one senior full-time salary, and each half checks the other: the CTO audits the crew’s output, the crew reality-tests the CTO’s architecture against a codebase that exists.

Cost sanity-check, side by side

For a company heading into an eight-week MVP build:

	Fractional CTO only	Team only	Both
Monthly cost	~$5,000	~$9,000 (1 FS + burst design)	~$13,000
What exists after 2 months	A plan, specs, maybe a hire pipeline	A shipped MVP	A shipped MVP someone senior signed off on
Biggest risk	Nothing shipped	Confident wrong turns	Paying for redundancy you may not need

That last cell is honest: if your product is technically ordinary (a CRUD app with payments is technically ordinary, which is a compliment; boring technology ships), a good crew plus a written brief may not need the CTO layer. Spend the $5k on customer discovery instead.

Signals you specifically need the CTO half

• You’re about to sign a five-figure agency contract you can’t evaluate
• Investors keep probing the tech story and your answers are vibes
• You’ve been told “it has to be rebuilt” and can’t tell if that’s true or a sales pitch
• The product involves genuinely hard calls: regulated data, unusual scale, ML at the core
• You’re about to make the first full-time hire and can’t interview for what you can’t do

Signals you specifically need the team half

• The plan is solid and the product is still a Figma file
• Your technical founder is doing five jobs and the bottleneck is hands, not judgment
• There’s a dated deliverable (pilot, demo day, contract) that current capacity won’t hit
• The roadmap is spiky: pushes and quiets, not a steady line

One closing honesty: at very small scale the line blurs. A senior solutions architect booked one day a week functions a lot like a light fractional CTO, and several of our engagements run exactly that shape, an architect day plus build days (both are on the rate card). Buy the function, not the title: judgment where judgment’s missing, hands where hands are. Just don’t buy one and expect the other.