The $500K Question

You've been heads-down on product for eighteen months. Four engineers, a prototype customers actually use, a runway number you've memorized to the dollar. You'd been planning to post the job that week anyway. The board's asking is permission. You nod and open a new tab to draft the role.

That tab is where a lot of startups quietly light half their seed money on fire.

The Decision Nobody Audits

What follows feels like momentum. You write the JD, talk to recruiters, take meetings. Months pass. You extend an offer, negotiate equity, wait out a notice period. A few more months while the new CTO ramps on codebase, team, customers, market. Look up and you've spent close to a year and a meaningful chunk of your round on a single hire.

The numbers aren't secret. Levels.fyi and the Pragmatic Engineer's annual compensation research both document that early-stage startup CTO packages, base plus equity at plan, routinely land in the mid-six figures all-in. The exact figure depends on your market and candidate. The shape is the same: it's the most expensive hire you'll make for a year, and the hardest to unwind.

The question nobody asks in the board meeting is whether you need forty hours a week of that person right now.

Across Brandfolder, ToolWatch/AlignOps, Oxen.ai, and a labor marketplace that grew to all 50 states, we've watched that question go unasked more times than we can count. At seed, the honest answer is almost always no. You don't hire a general contractor to live in the house while you're still surveying the lot. But that's what the reflex does. And the reflex has gotten more expensive now that every company, tech-first or not, has to modernize on purpose or watch a competitor who did eat its market: what you can't afford is buying the wrong shape of technology leadership for the phase you're in.

Three Jobs in One Title

The word "CTO" hides at least three jobs, and they don't all show up at once.

Pre-PMF, the critical work is architecture, stack choice, early hires, and the two or three calls that'll be expensive to reverse at Series B. High leverage, low volume. You need someone who's made these calls before, not someone sitting in your Slack all day.

With traction, the work shifts. Technical debt starts compounding. The first engineering manager needs hiring and coaching. The cloud bill becomes a topic. You need more hours, but the highest-value ones are still strategic. Execution can run on a strong EM and a handful of senior engineers.

Past fifteen engineers and multiple teams, the job changes again: people, culture, cross-functional alignment, board communication, recruiting at a scale where the CTO's personal brand affects candidate flow. This is where full-time stops being optional. Camille Fournier's The Manager's Path and Will Larson's staffeng.com both describe this as a real discontinuity, the person great at the first two jobs often isn't the one you want for the third.

Hire for the third when you still need the first, and you've bought capacity you won't use at the price of what you actually need.

The Premature-Hire Pattern

Call it the premature-hire pattern: matching an early-stage need for strategic direction with a late-stage operating model, because the title feels binary and the board pressure is real. It's the CTO version of hiring a VP of Sales before you have repeatable sales.

The pattern compounds for two reasons. First, executive hiring is hard. Michael Watkins' The First 90 Days and repeated HBR analyses put senior outside-hire failure rates in the 40% range within 18 months. The odds don't improve when the role is ambiguous and the company can't yet describe what success looks like. Second, the builder often isn't the scaler. The CTO who makes the right zero-to-one call on your data model is frequently not the person who runs a forty-person org two years later. Hire too early and you're buying a seat you'll likely re-hire anyway.

A Diagnostic You Can Run

If you want a sharper test than "the board asked," here are eight questions. More than half answered no means you probably don't need full-time yet.

1. Scale
   Do you have fifteen-plus engineers, or will you within six months?
2. Decision bottleneck
   Are technical decisions blocked at the top more than once a week?
3. Org complexity
   Do you have multiple engineering teams with different objectives and distinct tech stacks?
4. Recruiting drag
   Are you losing named candidates specifically because of the leadership gap?
5. Board agenda
   Is technical strategy a recurring agenda item at your board meetings?
6. Enterprise pull
   Is complex enterprise partnership work requiring a technical executive in the room?
7. Spend leverage
   Is your monthly engineering spend large enough that a ten-percent efficiency gain pays a full-time CTO salary?
8. Runway
   Is your runway eighteen months or longer at the post-hire burn?

Below four "yes" answers, fractional plus a strong engineering manager is almost always the better bet. Will Larson's writing at lethain.com makes the same point: match leadership to the work, not to the org chart you hope to have.

What the Money Actually Buys You

Here's the reframe. The $500K question was never about money, it was about what you're actually buying.

A full-time CTO buys dedicated judgment, but also a fixed cost, a long search, a real chance of a mis-hire, and a bet that today's right person will still be right when the job changes. A fractional engagement buys compressed experience at partial hours, room to layer in an engineering manager, and an off-ramp if the company shape changes. Neither is universally better, they solve different problems for different stages.

We're not dogmatic. If your product is the technology, deep ML infrastructure, regulated fintech, novel hardware, full-time from day one is usually right. If you've found a genuinely exceptional candidate with conviction about your problem and runway to absorb the bet, take them. But if what's driving the search is a board member's question, you're answering the wrong prompt.

The honest version of the conversation with your board isn't "we're hiring a CTO." It's: "Here's what the technical work actually looks like for this phase. Here's the shape of leadership that matches it. Here's what we'll change when it doesn't anymore." That doesn't make you look less ambitious, it makes you look like someone who's done this before.