How to Hire Your First Leadership Team: A Founder's Guide

Somewhere between your fifteenth and thirtieth hire, the job changes. You stop being the person who does everything and become the person who decides who does everything. That transition is where most founders quietly fall apart. Not because they can't attract talent, but because they hire their first leadership team the way they hired their first employees: fast, by instinct, filling gaps as they appear.

It works for a while. Then it doesn't. I watched a founder friend spend eleven months building a management layer that imploded in a single quarter because two of her three directors had overlapping strengths and a shared blind spot. Nobody owned the thing that actually broke. That's not bad luck. That's a hiring process that never asked what the company needed versus what the founder was tired of doing.

You don't need a perfect org chart. You need a sequence, a few decision rules, and the discipline to resist the urge to clone yourself.

How to hire your first leadership team without cloning yourself

Most founders I've talked to over the years made the same mistake at the start: they wrote a job description from the title outward. "We need a CTO." "We need a Head of Sales." Then they interviewed for competence in the abstract—impressive résumés, confident answers, a vague sense that this person could "take things off my plate."

That framing is the problem. A title describes a function. A leadership hire has to solve a bottleneck. If you can't name the bottleneck in a single sentence, with a number attached, you're not ready to hire.

Start from the outcome, not the role

Before I write a single line of a spec, I ask one question: what breaks in the next two quarters if nobody owns this? If the answer is vague, so is the hire. If it's "our churn climbs because nobody is talking to customers after onboarding," you've found your role. It's probably customer success, but the title matters less than the outcome.

Concretely, a useful spec looks like this:

• One sentence naming the outcome. Not "lead marketing" but "build a repeatable acquisition engine that gets us from 40 to 120 qualified leads a month."
• The three or four metrics this person owns and reports on weekly.
• The constraints: budget, team size, and—critically—what they can't touch in the first six months.
• What success looks like at day 90 versus day 180.

That last point is where most founders shortchange themselves. Look, if you can't articulate what a person must deliver in the first three months, you're not hiring a leader. You're hiring a presence.

The bottleneck sequencing framework

Which role comes first? Almost every early-stage company I've seen converges on a similar order, regardless of sector. Not because there's a sacred sequence, but because the bottlenecks tend to arrive in the same order as you grow.

Stage	Typical bottleneck	First leadership hire
~10–15 people	Founder is the sales team, the support desk, and the product roadmap	Revenue owner (Head of Sales or a commercial lead who can still sell)
~20–30 people	Engineering has no counterweight; product decisions are made in the founder's head	Technical or product lead who can delegate without losing the plot
~40–60 people	No one is watching the numbers; processes are ad hoc	Operations or finance lead who owns the operating rhythm

B2B SaaS companies often need a revenue lead first. Marketplaces usually need someone to own supply before demand. Services businesses live or die by a delivery lead. The pattern shifts, but the principle holds: hire against the bottleneck, not against the org chart your board sent you.

What is the 70/30 rule in hiring?

The 70/30 rule says you should hire someone who already has roughly 70% of the skills and experience the role requires, leaving 30% to be learned on the job. The logic is that a candidate at 100% has nowhere to grow and will likely be bored within a year, while a candidate at 40% will drown before they figure things out.

In leadership hiring, it's a useful guardrail, but I'd argue it needs a twist. The 70% shouldn't be skill-based as much as context-based: Have they operated at a scale similar to yours? Have they managed a team the size you're building? Have they seen the problem you're facing? The 30% they learn is your specific market, your product, your way of working—things only your company can teach. Get the ratio wrong in the other direction and you'll hire a specialist who can't generalize under pressure.

My honest take? The rule is more helpful as a rejection filter than as a target. If someone is at 100%, ask why they want a role they're already overqualified for. If they're at 40%, ask who'll be carrying them for the first six months. That person is usually you.

The five C's of leadership and why they matter more than skills

Skills can be taught. Composition can't. When you're building your first leadership layer, you're not just filling seats—you're assembling a group of people who will have to make decisions together under pressure, in rooms you aren't in. That requires a shared vocabulary.

I've used a rough framework for years, adapted from a few sources but mostly from watching teams succeed and fail:

• Character — how they behave when the numbers are bad and nobody's watching. This is the non-negotiable one.
• Competence — the track record, but specifically: have they done this exact thing at this exact scale?
• Communication — can they explain a complex decision to a junior without condescension? Watch for this in interviews; it reveals a lot.
• Composure — what they do when a project blows up at 11pm. Not whether they panic, but how quickly they recover.
• Curiosity — do they read, ask questions, change their mind? Leaders who stop learning become bottlenecks within eighteen months.

Notice what's missing: charisma, pedigree, eloquence on stage. Those are nice. They're not what makes a leadership team cohere.

The diagnostic interview

A standard interview tests whether someone can talk about leadership. A diagnostic one tests whether they actually lead. I've found three question types far more useful than any competency matrix:

1. "Walk me through the last decision you made that you'd reverse if you could." Then listen for the mechanism: how did they notice? Who did they consult? What would they do differently?
2. "Tell me about a hire you made that didn't work out. Who was responsible, and why?" Listen for whether they own it or blame the person.
3. "Here's a real problem we have. How would you spend your first two weeks?" You're not looking for the right answer. You're looking for whether they ask questions before proposing a solution.

The third question is where most candidates fail. The good ones ask what data exists, who owns adjacent decisions, what's already been tried. The weak ones start proposing fixes before they even understand the constraints.

What is the 70-20-10 rule for leadership?

The 70-20-10 model describes how leaders actually develop: roughly 70% of a leader's growth comes from challenging on-the-job experience, 20% from relationships (mentors, peers, feedback), and only 10% from formal training courses. It's widely used in leadership development programs, and it has a direct implication for hiring.

Stop over-indexing on credentials. If 90% of leadership capability is built through doing and through relationships, then a candidate with a prestigious MBA and no track record of owning things is a worse bet than someone who has run a smaller team through a hard year. The MBA is 10%. The scar tissue is 70%.

This is why I've grown skeptical of "executive presence" as a hiring criterion. Presence is a proxy for polish, and polish is a proxy for exposure to polished environments. What you actually need is someone who has been through the meat grinder of building something and can talk about it honestly. Ask about the mistakes. The 70% shows up there.

Applying the rule when you hire

In practice, this means weighting your evaluation toward demonstrated experience over education and over interview performance. Concretely:

• Ask for a specific story, not a philosophy. "Tell me about the pivot you led" beats "What's your view on pivots?"
• Score references honestly. I started doing structured reference calls after I realized I was only asking for confirmation of my own impression. Ask about failures. Ask what they'd change.
• Value the candidate who has run a smaller thing well over the one who has run a bigger thing badly. Scale of responsibility is not the same as intensity of it.

The 70-20-10 model isn't a hiring rule—but it tells you which signals to trust. Trust hands-on experience. Discount polish. The gap between the two is where bad leadership hires live.

What is the 30-60-90 rule for a new manager?

The 30-60-90 framework splits a new leader's first quarter into three phases: 30 days of learning and observation, 60 days of forming and testing hypotheses, and 90 days of executing against a plan. It's used widely for onboarding, but in leadership hiring it's also a design tool—it forces you to write down, before you hire, what this person must accomplish and by when.

Most founders skip this. They write a job spec, run interviews, hire, and then... hope. The 30-60-90 plan turns hope into a contract. It gives the new leader a map, the founder a scorecard, and both parties a shared language for the hard conversations that follow.

The 30-60-90 plan that actually works

Here's the structure I've settled on after several rounds of trial and error, including one hire where I didn't write the plan and it went badly within ten weeks:

1. Days 1–30: learn. Meet every team they'll touch. Read the last six months of internal docs. Sit in on customer calls. The only deliverable is a written assessment of what they found—what's working, what isn't, and where they disagree with the current plan. No decisions yet.
2. Days 31–60: hypothesize and test. Propose two or three changes against the assessment. Run small experiments. Present findings to you and peers. The deliverable is a prioritized list of interventions, each with a hypothesis and a metric.
3. Days 61–90: execute. Ship the first version of their plan. Own the metrics. Report on progress weekly. By the end of the quarter, they should be able to say what they got wrong and what they'll adjust.

That last part matters more than it sounds. The 90-day review isn't a performance evaluation—it's a calibration. If the new leader can't articulate what they'd change about their own plan, you've hired someone who executes but doesn't learn. That's a slow-burn problem, and you'd rather find out at day 90 than at month 14.

The honest failure mode too many leadership teams make

The biggest mistake I see isn't hiring the wrong person. It's hiring the right people in the wrong order and then wondering why the team doesn't work. A strong VP Sales and a strong VP Ops can be individually excellent and collectively awful if they don't agree on what "winning" means. The team has to be designed, not just assembled.

Practically, that means one thing: before your first leadership team has its first meeting, someone—probably you—writes down what the group is accountable for as a group, and what each individual is accountable for alone. Not an org chart. A shared scorecard. If the group doesn't have a shared scorecard, they'll each optimize for their own function and the company will lose on the seams between them.

I've seen teams where the shared scorecard was literally a single spreadsheet on a Monday morning call: three numbers, each owned by one person, with the whole group on the hook for all three. It sounded too simple to work. It worked better than any of the elaborate OKR systems I watched get ignored.

Here's the thought I'd leave you with. You can't outsource the composition of your first leadership team to a recruiter, a board member, or a framework. You can borrow the tools—70/30 as a filter, 30-60-90 as a contract, the C's as a shared vocabulary—but the judgment about who belongs in the room is yours. And the room you build in year one is the room your company will make decisions in for years. Choose the seats carefully, and don't let anyone tell you the order doesn't matter. It's the order that determines whether they become a team or just a collection of talented people sharing a meeting invite.