The Fractional Advantage

You've just closed your seed. The deck said "technical hire within 90 days." Your lead investor introduced you to three CTO candidates over the weekend. You have a board meeting in six weeks and you'd like to walk in with a name.

Here's what nobody puts on the slide. You're not hiring a CTO. You're betting on which of three people will make the handful of decisions that determine whether your architecture survives the next growth phase -- and you're making that bet before you know what those decisions are. The candidate with the cleanest resume has never operated at your stage. The cheapest one will be learning on your cap table. The third has two other offers.

The Education You're Paying For

Michael Watkins, in The First 90 Days, puts a number on what it costs a company to onboard a senior executive: roughly 6.2 months before they're generating more value than they consume. That's the baseline for a leader stepping into a role they've done before. For a first-time CTO stepping into a first-time company, the curve is longer and the mistakes are more expensive, because early-stage architecture decisions have a long blast radius.

Picture your own numbers. You're considering a full-time CTO at, say, $350K plus two percent of the company. Over the first year, most of their working hours go to recruiting, onboarding themselves, learning your stack, and running the standups that nobody else will run. Some fraction of their time -- you pick the fraction honestly -- goes to the decisions that actually shape the company. If that fraction is a quarter, you're paying full executive comp for the quarter you needed and carrying the rest.

This isn't a failure of the individual. It's what happens when a company needs decisions informed by experience it can't yet afford, and hires availability instead. Will Larson has written extensively on the gap between engineering management as a role and engineering leadership as a craft. The role is easy to fill. The craft is not.

What the First 18 Months Actually Demand

Strip the title off and look at the work. In the first 18 months of a company, the technical leader has to make a small number of decisions that compound for years: the foundational architecture, the first five engineering hires, the vendor contracts that will either constrain or liberate the product, and the cultural pattern that determines how the team handles its first real incident. These are not forty-hour-a-week problems. They are high-stakes, low-volume problems that reward pattern recognition and punish improvisation.

When Founding Partner B built ToolWatch -- which grew through acquisition into AlignOps -- the architecture calls made in the first year were the ones that determined whether the product could survive the integration years later. At GigSmart, Founding Partner A's early decisions about marketplace infrastructure are what let the platform now operate across all 50 states. At Oxen.ai, Founding Partner C is making choices right now whose consequences will be visible in 2028. None of this work required forty hours a week. All of it required having made the same class of call, badly, somewhere else first.

Camille Fournier makes this point cleanly in The Manager's Path: the further up the leadership stack you go, the more the job compresses into a smaller number of decisions with larger consequences. Hours stop being the unit. Judgment becomes the unit.

The Reflex Nobody Examines

There's a reflex in early-stage companies -- we'll call it the full-time reflex -- where the board, the founder, and the candidate all quietly agree that a serious company must have a serious person in the chair forty hours a week. It shows up in pattern-matching from investors. It shows up in the founder's own insecurity about whether the company is "real." It shows up in the candidate's compensation requirements, which are calibrated to a full-time role because that's what the market pays.

The reflex is doing work. It's resolving an anxiety about legitimacy. It's signaling commitment to the next round. What it isn't doing is matching the shape of the hire to the shape of the work.

Harvard Business Review's coverage of fractional executive roles tracks the same phenomenon from the C-suite side: companies bring in full-time leaders for workloads that don't justify the headcount, then either burn them out on the wrong work or ask them to manufacture busyness to fill the role. Neither outcome is what the company needed.

Reframing the Hire

Here's the actual question underneath the CTO decision. You're not choosing between "fractional" and "full-time." You're choosing between buying hours and buying judgment. A full-time hire is the right answer when the work is continuous and the judgment load is distributed across many small decisions per day. A fractional hire is the right answer when the work is episodic and the judgment load concentrates in a smaller number of high-stakes calls.

Most early-stage companies are in the second category and talk themselves into the first one, because the first one feels safer to explain to a board. This is the judgment-hours confusion -- and once you see it, the hiring decision stops being a tradeoff and starts being a diagnostic.

An experienced fractional leader working across several early-stage companies is running a pattern-recognition loop. When the migration you're struggling with is the third variant of one they've watched play out this year, diagnosis gets faster and expensive experiments don't need to happen a fourth time. Gergely Orosz's Pragmatic Engineer reporting on engineering leadership compensation shows how uneven the market is for this kind of experience; the people who have it are rarely available full-time at the comp an early-stage company can sustain. So the real choice isn't "best fractional vs. best full-time." It's "best fractional vs. the full-time you can actually hire."

When Full-Time Is The Right Call

We're not arguing fractional is always better. Once the engineering team crosses roughly ten to fifteen people, once daily architectural decisions require continuous oversight, or once the product itself is the technical innovation rather than a wrapper around one, the company has outgrown episodic leadership. At that point a fractional partner's highest-leverage move is to recognize the transition, help recruit the full-time hire, transfer the context and relationships, and step out cleanly. Lara Hogan's writing on leadership transitions treats the handoff as its own craft, and it is.

The best fractional engagement ends with the company hiring a full-time CTO on strong footing: architecture sound, team built, processes working, incident patterns established. The new hire inherits a functioning technical organization instead of a pile of decisions to unwind. Our success is measured by how well the organization functions after we leave, which is the opposite of the consulting incentive to extend the engagement -- and it's the clearest proof that the model works.

So before you sign an offer letter for the CTO candidate your investor introduced you to last weekend, ask yourself: do I need someone making twenty-five decisions this year or two thousand? Am I buying hours or judgment? If the honest answer is the former of each, we should probably talk before you commit the cap table to the latter.