How to hire your first CTO: checklist for non-technical founders

To hire your first CTO as a non-technical founder, work a 14-item checklist: validate the business, write a one-page spec, source through warm intros, vet on communication first and code second, run two third-party technical reference calls, then end with a paid four-week trial before any equity grant. If you're pre-product or under 18 months of runway, hire a fractional CTO or book a Cadence Lead by the week instead of giving anyone the title.

This post is for the founder who can sell, recruit, and raise, but cannot personally tell whether the candidate's code is good. That gap is the entire problem. The fix is structured process, not gut feel. Below is the framework, the literal checklist, the trial spec, and the decision rules for when a first CTO is the wrong move entirely.

The non-technical founder problem in one sentence

You're hiring for skills you can't directly evaluate, and you're handing the keys to the most expensive function in the company.

Roughly half of first technical hires at startups get replaced inside 18 months. The replacement is rarely about raw talent. It's about a mismatch between what the founder thought they were buying (a co-pilot) and what they bought (a builder who couldn't recruit, or a recruiter who couldn't ship, or a senior engineer who quietly hated the title).

If you're technical, you can catch that mismatch in the first sprint. If you're non-technical, you find out at month nine, when the burn caught up and the product slipped two quarters. So the cost of a bad first technical hire is asymmetric for you. The fix is to spend the front-loaded effort that a technical founder would skip.

Before the search: do these three things

1. Validate the business with revenue or pre-orders. A real CTO candidate will ask why this company should exist before they ask about equity. If your answer is "I think it's a great idea," you're recruiting on vision alone, which means you'll over-grant equity and attract the wrong profile. Get to $5k-50k MRR, signed letters of intent, or a 500-name waitlist with paid pre-orders before you start the CTO search. The same logic applies if you're validating a B2B SaaS idea pre-launch: proof first, then hire.

2. Write a one-page spec describing the first six months of work. Not "build the product." Specifically: which three features ship by which dates, which integrations matter, which customers will use them, which infra decisions are reversible vs locked. If you can't write this page, you're not ready to hire a CTO; you're ready to hire a consultant or book a senior engineer to help you write it.

3. Decide if you actually need a CTO, or a senior engineer with a title path. Most pre-Series A startups don't need a CTO. They need a Senior Engineer or Lead Engineer who ships and recruits, with a written path to the CTO title at Series A. Over-titling the first hire wastes 5-10% equity and locks you into a title you can't take back without a messy renegotiation.

The 14-item checklist

Paste this into Notion. Tick each before moving to the next stage.

Pre-interview gates

Business has revenue, signed LOIs, or a paying waitlist
One-page six-month spec is written and dated
Equity band decided in writing (with your lawyer)
Decision made: full-time CTO, fractional CTO, or senior engineer with title path

Search 5. Three warm-intro candidates from your investor and operator network 6. Three platform-sourced candidates (AngelList, Y Combinator Work at a Startup, technical Slack groups) 7. Public work reviewed: shipped products, not GitHub stars

Interview 8. 60-minute founder fit call: vision, communication, working style 9. 90-minute technical walkthrough: candidate explains a past architectural decision and the trade-offs they rejected 10. Hiring sample: 4-hour paid take-home where they spec a feature from your roadmap (not write code, spec it)

References 11. Three reference calls completed: two former peers, one former direct report or manager 12. Independent technical reference call by a paid third-party CTO advisor (90 minutes, $300-500)

Trial 13. Four-week paid trial at the offered weekly rate, scoped to ship one real feature 14. Offer extended only after trial week 4 retro, with equity vest starting from trial day 1

If you skip even three of these steps, you're hiring on hope. The whole point is that a non-technical founder cannot catch problems mid-sprint, so the checklist front-loads the catching.

How to evaluate technical work when you can't read code

This is the hardest part of the framework, and it's the one every other guide skips.

Look at shipped products, not code samples. Ask the candidate for three products they shipped that real customers paid for. Use the products. Talk to one customer of each (the candidate can intro you). A pretty GitHub means nothing if nothing in it ever shipped to a paying user.

Get a code review walkthrough. Ask the candidate to walk you through a pull request they're proud of, and a pull request they regret. The PR they regret is more diagnostic than the one they're proud of. Strong engineers can articulate the trade-off they made, why it was wrong in retrospect, and what they'd do differently. Weak candidates blame the codebase or the deadline.

Run third-party technical references. This is the move non-technical founders miss. Hire an independent CTO or senior engineer for 90 minutes (rates run $250-500/hour) and have them call two of the candidate's references with a technical script. The script asks about: how the candidate handles ambiguous requirements, how they make architectural decisions, how they recruit, how they handle being wrong. You'll get a half-page memo back with a clear "yes, no, or maybe" and the reasoning.

If you don't know an independent CTO advisor, your investors do. Ask. The $400 spend caps a $300k+ mistake.

Check decisions, not output. A CTO's job is mostly making good decisions about what not to build. In the interview, give the candidate a real spec from your roadmap and ask: which 30% of this would you cut? If they cut nothing, they're a builder, not a CTO. If they cut everything, they're an advisor, not a CTO. You want someone who cuts the 30% with a clear reason that maps to your business model.

When to hire fractional or skip the CTO title

Here's an honest decision table. Most first-time founders pick the wrong column.

Path	Cost	Timeline	When it wins	When it loses
Full-time CTO hire	$200k-300k salary + 5-15% equity	3-6 month search	Post-Series A, multi-year scope, you've raised enough to support payroll	Pre-product, unvalidated, runway under 18 months
Fractional CTO	$5k-15k/month, 10-20 hrs/week	2-4 weeks to start	Advisory plus light shipping, you need a sounding board	If you need full-time shipping velocity
Cadence Lead (booked weekly)	$2,000/week, full-time	48-hour free trial	Validated product, need ship velocity, want no equity dilution	If you need a true co-founder commitment
Senior Engineer (no CTO title)	$150k-200k + 1-3% equity	2-3 month search	Post-product, pre-Series A, clear roadmap	If your board expects a named CTO

For most pre-Series A founders, the right move is column three or four, not column one. A build vs buy framework applies to roles too: don't full-time-hire what you can rent by the week.

A Cadence Lead is full-time at $2,000/week, with weekly billing, no equity grant, and a 48-hour free trial. Every engineer on the platform is AI-native by default, vetted on Cursor and Claude Code fluency before they unlock bookings. The pool is roughly 12,800 engineers. For a non-technical founder pre-Series A, the math is: ten weeks of a Cadence Lead costs $20k, no equity. Ten weeks of full-time CTO search costs your time, $25k recruiter fees, and a 6-15% equity grant before they ship a line of code.

That said, a Cadence Lead is not a co-founder substitute. If you genuinely need someone whose name goes on the cap table and whose career is bet on this company, hire a CTO. The booking path is for the months between "I have a product" and "I have a Series A," when you need ship velocity but a named CTO would be premature.

The 4-week paid trial spec

If you're going to hire full-time, the trial is the single most important thing you do. Skip it and you're guessing. Run it well and you'll see exactly what you're buying before you sign the offer.

Pay the candidate at the full offered weekly rate ($1,500-2,000/week is standard). Four weeks at $2,000/week is $8,000 to derisk a $300k+ commitment.

Week 1: scope a feature. Pick one feature from your six-month spec. Have the candidate write the technical spec, the rollout plan, and the success metrics. Their spec quality is the entire signal. A real CTO writes a spec a junior could ship; a weak candidate writes a spec only they can ship.

Week 2: ship the feature. They write the code, deploy it, and run the rollout. Watch how they communicate during this week. Do they over-communicate trade-offs and blockers, or do they go silent? A non-technical founder cannot afford a silent CTO.

Week 3: hire a junior under them. Have them run a hiring loop for a junior engineer (Cadence, Upwork, or your network). They write the JD, screen candidates, and run interviews. Their hiring instinct is at least as important as their coding ability. The CTOs who fail are usually the ones who can't recruit.

Week 4: present to the team. Have them present the feature, the spec for next quarter, and one architecture decision they want to make. Invite an investor or advisor. The presentation is the cultural fit signal.

Decision criteria, in order: did they ship? did they communicate proactively? did they identify a real hiring candidate? could they explain a technical decision to a non-technical audience without condescension? If any answer is no, do not extend the offer. The trial is the catch; respect what it caught.

Founder mistakes that burn equity and runway

Over-titling the first hire. The single most expensive mistake. Senior Engineer with a documented path to CTO is almost always the right starting title. You can promote later; you cannot un-grant CTO equity.

Skipping references because you liked them in person. Charm is the cheapest skill on the planet. References are the only proof of pattern. Always do three. Always include the third-party technical reference call.

Trial-by-side-project. Asking a candidate to "do a small project on the weekend" tells you nothing about whether they ship under real pressure. Pay them for four real weeks on real work. The cost is trivial against the asymmetric risk.

Hiring before the spec exists. If you can't write a one-page six-month plan, hire a consultant for two weeks to help you write it before you start the CTO search. Hiring a CTO to write your spec means they'll write the spec they want to build, not the one your business needs.

Skipping daily check-ins during the trial. Daily ratings during the four weeks catch communication drift early. If you're booking a Cadence engineer instead, the platform handles daily ratings and weekly retros automatically. If you're running the trial yourself, set a 15-minute daily standup; do not skip it.

If you'd rather skip the four-week trial entirely and try a full-time engineer with a 48-hour free window first, that's exactly what a Cadence booking is built for. Cadence's hiring flow shortlists vetted engineers in two minutes, with weekly billing and no notice period. Trial 48 hours free; book by the week if it works; cancel any week if it doesn't.

Steps

The literal sequence to follow, end to end. Each step is sequential; don't skip ahead.

Validate the business. Hit $5k+ MRR, signed LOIs, or a paying waitlist before opening the search.
Write the spec. One page, six months, three named features with dates and success metrics.
Decide the title. Default to Senior Engineer with a written path to CTO at Series A unless your board explicitly requires the title now.
Set the equity band. Pre-product 5-15%, post-product pre-Series A 1-5%, post-Series A 0.5-2%, all with 4-year vest and 1-year cliff. Confirm with your lawyer.
Source candidates. Three from warm intros, three from AngelList or Y Combinator Work at a Startup. Six is the minimum top of funnel.
Review public work. Shipped products only. Use them. Talk to one customer per product if you can.
Run the founder fit call. Sixty minutes. Vision, working style, communication. No code in this call.
Run the technical walkthrough. Ninety minutes. Candidate walks through one PR they're proud of and one they regret.
Run the paid spec exercise. Four hours, paid at the offered weekly rate. Candidate scopes a feature from your roadmap.
Run three reference calls. Two peers, one manager or report. Use a written script; document answers.
Commission a third-party technical reference. Hire an independent CTO advisor for 90 minutes ($300-500). Have them call two references with a technical script.
Run the four-week paid trial. Spec week, ship week, hire week, present week. Daily 15-minute standup.
Run the trial retro on day 28. Score against the four criteria: shipped, communicated, recruited, presented. Any "no" ends the process.
Extend the offer. Equity vest starts retroactively from trial day 1. Document the title-up path if you started with Senior Engineer.

When the right answer isn't a CTO at all

Sometimes the honest answer for a non-technical founder is: don't hire a CTO right now. Book a Cadence Lead at $2,000/week for the next twelve weeks, ship the next product milestone, then revisit. You'll have learned what work actually needs doing, what kind of person you actually need, and you'll have twelve weeks of revenue or learning to show the next hire. If you're earlier than that, a fractional CTO at 10-20 hours per week is a smaller bet that buys you advisory plus a few hours of shipping.

Skip-the-CTO is also the right call if you're a solo founder still defining MVP scope. Hiring a CTO before you've validated the wedge is the most common way founders give away their company on the way to discovering they were building the wrong thing.

FAQ

Should a non-technical founder give the first hire the CTO title?

Usually no. Default to Senior Engineer or Lead Engineer with a written path to CTO at Series A. Over-titling the first hire wastes 5-10% equity and locks you into a title you can't take back without a renegotiation that often ends with the person leaving anyway.

How much equity does a first CTO get?

Pre-product CTOs at company formation get 5-15%. Post-product, pre-Series A first CTOs get 1-5%. Post-Series A first CTOs get 0.5-2%. Always vest over four years with a one-year cliff. Confirm bands with your lawyer before opening the search; never negotiate equity in the offer call.

Can you hire a CTO without being technical yourself?

Yes, with structured process. The four catches are: a written one-page spec before the search, three reference calls including one third-party technical reference, a paid four-week trial on real work, and a documented title path if you start with Senior Engineer. Skip any one and you're effectively hiring blind.

What's the difference between a fractional CTO and a Cadence Lead?

A fractional CTO works 10-20 hours per week on advisory plus light shipping, costs $5k-15k per month, and usually expects a 0.5-2% equity grant. A Cadence Lead is a full-time engineer at $2,000 per week with no equity grant, weekly billing, a 48-hour free trial, and no notice period. Use a fractional CTO for advisory at the seed stage; book a Cadence Lead when you need full-time shipping but full-time hiring is premature.

How do I know if my first technical hire is failing before it's too late?

Run a 30-day check on three signals: are they communicating proactively (or going silent under pressure), are they recruiting (or have they refused to start), and are they writing specs that a junior could pick up (or specs only they can ship). Two reds at 30 days means the trial period was too short. Cut early; the cost of waiting is a quarter of runway.

All posts