Self-assessment

What kind of founder are you?

Almost every early hiring mistake traces back to the same thing: a founder hiring for the work they enjoy instead of the work they avoid. Start by naming your archetype honestly, then use the flow chart to decide who comes next — and, just as importantly, when not to hire at all.

The quiz

Six questions

0 / 6

1.It's a blank Monday with no meetings. What do you actually do?
2.Where did the idea for the company come from?
3.Your first ten customers arrived mostly because…
4.Which board meeting slide do you dread preparing?
5.A great candidate says yes to only one role. Which do you take?
6.Which criticism has followed you across jobs?

Answer all six questions to see which archetype you lean toward. There is no good or bad result — only a different first hire.

The four archetypes

The Product Visionary

Product

You start from the user. You can describe the product a year out in vivid detail, you obsess over the flow, the copy, the edges — and customers feel it. Your unfair advantage is taste plus proximity to the problem.

Strengths

Sharp product judgement; you kill features other people would ship
Recruits designers and product-minded engineers who want to build something good
Tells a narrative story investors and early customers buy into
Fast qualitative learning loops — you talk to users constantly

Blind spots

Perfecting the product long past the point where distribution is the bottleneck
Under-investing in repeatable sales; every deal is founder-sold and unmodelled
Weak operating cadence — plans live in your head, not in a system
Hiring in your own image, ending up with a company that can build but not sell

Hire first

Technical co-founder or founding engineer (CTO track)
Pre-seed, before you write a line of production code
You need someone who owns architecture and velocity so your vision ships weekly, not quarterly.
First AE / founding account executive
Seed, after ~10 unaided customers you closed yourself
Prove the sale is transferable off the founder before you raise a Series A on it.

Hire later

VP Sales or CRO
Series A, at roughly $1.5–3M ARR
Turn the founder-led motion into quota, pipeline coverage, and a forecast.
Head of Finance / fractional CFO
Series A close
Board reporting, ARR bridge, and a model you did not build in a spreadsheet at 2am.
COO or Chief of Staff
Series B
Someone must own the operating cadence so you can stay on product and customers.

Should you be CEO?You should stay CEO if you can hold a number, run a weekly business review, and hire people who are better at go-to-market than you are. If board mechanics drain you, plan for a strong president/COO rather than a title change.

The Deep Technical Founder

Technical

You are solving something genuinely hard — infrastructure, ML, security, a real research edge. Your moat is what you can build that others cannot, and your credibility with engineers is your best recruiting asset.

Strengths

Genuine defensibility; the technology is the differentiation
Magnet for exceptional engineers who want a hard problem
Fast, cheap early builds — you don't need a large team to get to a demo
Credible with technical buyers and technical investors

Blind spots

Building for the problem you find interesting, not the one buyers fund
Treating go-to-market as a solved problem once the product works
Avoiding pricing conversations, so contracts are under-valued
Slow to hire non-engineers, which leaves the company voiceless in market

Hire first

Commercial co-founder or first sales hire
Pre-seed to seed, as soon as there is a demo
Someone must live in the buyer's world and translate the technology into a purchase order.
Design-minded product hire
Seed
Hard technology usually ships an unusable surface. A product/design owner fixes activation.

Hire later

VP Engineering (distinct from you as CTO)
Series A, ~15–20 engineers
You keep architecture and technical strategy; they own delivery, process, and managers.
Head of Marketing / demand gen
Series A–B
Category creation and pipeline; technical products die in silence more often than in failure.
CFO
Series B
Unit economics, cloud spend as COGS, and institutional board reporting.

Should you be CEO?Many deep technical founders are strongest as CTO with a partner as CEO. Test yourself honestly: do you enjoy selling, recruiting, and fundraising? If not, move to CTO early and deliberately — it is a promotion into your strength, not a demotion.

The Commercial Founder

Commercial

You sell. You had customers before you had a product, you know the buyer's budget cycle, and you can open doors most founders cannot. Your risk is building a company that can close deals it cannot deliver.

Strengths

Revenue from day one; pipeline is rarely the constraint
Deep, specific buyer knowledge — pain, budget, procurement, champions
Natural fundraiser; comfortable with narrative and objection handling
Recruits senior go-to-market talent through personal network

Blind spots

Over-promising roadmap to close, creating bespoke work that never scales
Under-valuing engineering leadership and shipping fragile systems
Confusing sold revenue with retained revenue; churn shows up at Series A diligence
Buying growth with headcount before the motion is efficient

Hire first

Technical co-founder / CTO
Before incorporation if possible; certainly pre-seed
Equity-level ownership of the product. Agencies and contractors will not survive Series A diligence.
Head of Product
Seed
A single owner who says no to one-off commitments and turns deals into a roadmap.

Hire later

Head of Customer Success
Seed to Series A, at ~15–25 paying accounts
Net revenue retention is the single number Series B investors underwrite.
VP Engineering
Series A
Delivery predictability so the sales promise and the ship date agree.
CFO
Series B
CAC payback, magic number, and a plan that survives a board's scrutiny.

Should you be CEO?You are usually the right CEO. Your job is to protect the product organisation from your own selling: put a strong CTO and Head of Product between the deal and the roadmap, and pay them in equity, not gratitude.

The Operator Founder

Operator

You have run things before — a P&L, a large team, a complex supply chain. You build systems, cadence, and clarity, and the company feels well-run from the first week. Your risk is running a tidy company that isn't taking enough risk.

Strengths

Excellent hiring, onboarding, and performance management from day one
Real financial literacy; the model is honest and the runway is known
Cross-functional execution; things you commit to actually happen
Boards trust you quickly, which makes fundraising smoother

Blind spots

Over-processing an eight-person company; structure before product-market fit
Preferring incremental optimisation to the risky bet the market rewards
Hiring senior managers too early — layers without leverage
Deferring to the loudest customer instead of holding a product point of view

Hire first

Product-obsessed co-founder or Head of Product
Pre-seed
Someone whose whole job is the opinionated bet, not the efficient execution of it.
Founding engineer
Pre-seed to seed
Speed of iteration matters more than organisational design at this stage.

Hire later

Demand generation lead
Seed to Series A
Operators tend to build the machine before there is fuel; buy the fuel.
CHRO / Head of People
Series B, around 100 people
Your instincts scale further than most founders'; a partner here compounds them.
CFO
Series B
You can carry finance longer than most, but institutional reporting eventually needs an owner.

Should you be CEO?You are a durable CEO through Series B and beyond. Guard against comfort: the operator failure mode is a well-run company with a mediocre product. Make sure someone in the room is allowed to be unreasonable.

The hiring flow chart

Work down the chart. At each stage there is one question that decides whether you hire or wait — answering it honestly is worth more than any org design exercise.

Day zero → Pre-seed
2–4 people
Can you build and sell the first version without hiring?
Yes
Hire nobody. Spend the money on customer discovery and a working prototype.
No
Hire the co-founder-grade complement to your archetype — equity, not salary.
Pre-seed → Seed
4–10 people
Do you have 5–10 customers who would be upset if you shut down?
Yes
Hire 2–3 founding engineers and one commercial or product complement.
No
Do not hire. Every hire before this point makes the pivot more expensive.
Seed → Series A
10–30 people
Has anyone other than a founder closed a full-price deal?
Yes
Hire the first sales manager, a Head of Product, and a Head of Finance.
No
Keep founder-selling. A VP Sales hired before a repeatable motion will fail in nine months.
Series A → Series B
30–120 people
Are two or more functions bottlenecked on your personal decisions?
Yes
Hire the executive layer: CRO or VP Sales, VP Engineering, CFO, Head of People.
No
Hire managers, not executives. Depth beats titles until the bottleneck is real.
Series B and beyond
120–250 people
Can each function commit to a number and hit it without you?
Yes
You have an executive team. Shift to capital, category, and succession.
No
Upgrade the weakest seat now. Series B boards forgive a miss, not a slow leadership call.

Four hiring principles

Hire against your blind spot, not your comfort

The first senior hire should be the person who does well what you avoid. Founders who hire mirrors build lopsided companies that stall exactly where the founder does.

Hire the stage, not the logo

A VP from a 5,000-person company usually needs a machine that does not exist yet. At Series A, hire people who have gone from 1 to 10; at Series B, from 10 to 50.

Do the job before you hire for it

You cannot evaluate a Head of Sales if you have never sold. Own the function long enough to know what good looks like and what the real bottleneck is.

Executives follow proof, not hope

Hire an executive to scale something that already works. Hiring one to discover it converts your problem into an expensive, slower version of the same problem.