What does fractional CTO look like for early-stage startups?

Fractional CTO is one of those titles that means six different things depending on who you ask. Here is what it actually looks like in practice for an early-stage startup, and when it is the right move. What it is not: A coder you have hired part-time. That is a contract engineer. A strategic advisor who shows up to board meetings. That is an advisor. A recruiter helping you fill roles. That is a technical recruiter. What it is: A fractional CTO is a senior technical person, usually 10+ years deep in the stack, who owns the strategic technical decisions on your team for a few days a month. They translate between you (the non-technical founder, in most cases) and the people building the product. They make the calls you do not have the expertise to make. Typical scope for early-stage: Architecture review and sign-off. Not writing code, but saying yes or no to direction. Hiring. Writing job specs, doing the first technical interview round, deciding who to extend offers to. Vendor selection. Should we use Clerk or NextAuth? Supabase or Neon? Stripe or Paddle? They have an opinion and have shipped with all of them. Code review at the milestone level. Not line-by-line, but "is this codebase going to scale to 10x users". Talking to your investors when they ask technical due diligence questions. Saying no to engineering work that will not move the business. Helping you fire someone who is not working out. When you need one: You are a non-technical founder with one or more engineers and you cannot tell if they are doing a good job. You are about to make a significant architecture decision (build vs. buy, monolith vs. microservices, hosted vs. self-hosted). You are raising and investors want to see a technical leader on the team. You have hit a quality cliff: bugs are increasing, deploys are scary, the engineer is overwhelmed. You are considering hiring a full-time VP Engineering or CTO and want to test the role before committing. When you do not need one: You have a senior technical co-founder. You already have a CTO. You do not need a second one. The product has not shipped yet. You need a builder, not a strategist. You are already past Series A. You need full-time leadership, not fractional. Typical engagement: Four to eight hours per week, three to six month minimum. $4K to $8K per month for a real one (not a junior pretending). Should include async availability for emergencies, not just scheduled meetings. Should produce written artifacts: hiring rubrics, architecture decision records, vendor evaluations. What to watch for: Someone who only shows up to scheduled calls and never reads the code is not engaged enough. Pass. Someone who wants to write code is overstepping. They are moonlighting, not leading. Someone who cannot articulate trade-offs in writing is not senior enough. Pass. Someone who wants equity instead of cash early is a yellow flag. They might be more interested in the upside than the work. Honest take: fractional CTO is the most overrated category in early-stage hiring. Most founders who think they need one actually need a senior engineer doing the build, plus an honest technical friend they can call. But for the specific case where you are non-technical, you have engineers, and you need someone who can say "this architecture will not scale", it is the highest-leverage hire you can make. A good fractional CTO saves you from the build-the-wrong-thing mistake, which is the most expensive mistake any startup makes.