Hiring a second-in-command: when, who, and how to get it right

Executive overview

Most entrepreneurs are not strong operators, yet they try to run everything themselves. The result: overwhelm, stalled growth, and a business that owns them rather than the other way around. Hiring a second-in-command — whether titled COO, VP Operations, or President — is the structural fix.

The right hire frees the CEO to work on high-energy activities, enables a self-managing leadership team, and typically returns 3–4x their cost in revenue. The critical window is the $10M–$30M revenue mark.

The core insight: hiring someone who has done the job beats hiring someone who knows how to do it — every time.

When to hire and what it costs

• The org evolves at revenue inflection points: $300K (first hire), $1M (first manager), $3M (a few managers), $10M (a management team), $30M (a true leadership team).
• The $10M–$30M mark is when functional heads become seasoned enough that they don't need managing — only direction.
• Justify the COO hire when the return is 3–4x their compensation: a $250K–$300K hire should unlock ~$1M–$2M in incremental gross margin.
• A second justification is personal: the cost of burnout, relationship damage, and lost health often exceeds the salary of a hire.

Internal vs. external candidates

• Promote internally only if the person is a self-driven learner who will actively grow their own skills.
• Internal candidates bring IP, relationships, and systems knowledge — a meaningful advantage.
• The risk of always hiring externally: eroding internal DNA and culture continuity.
• Screen for industry IP requirements honestly. A manufacturing background transfers across products; a restaurant operator probably shouldn't run a retail chain.
• The decisive filter: have they done the four or five core things this role requires over the next 12 months? Not "do they know how" — have they actually done it?

Writing the job posting

• Treat every job posting as a sales letter: it should magnetize 50% of readers and actively repel the other 50%.
• Have the functional head draft it, then pass it to a copywriter to make it pop.
• Include only three things: core responsibilities, required behavioral traits, and non-negotiable core values.
• Omit any criteria that isn't truly required — long lists of requirements disproportionately deter qualified women from applying.
• Don't hide the hard parts of the role. Describing difficulty attracts the right candidates and filters out the wrong ones.
• Skip tool-specific requirements (e.g., HubSpot vs. Salesforce) — capable hires will learn.

Rating candidates consistently

• Define each behavioral trait in precise, shared language before interviewing begins. Example: tenacity = "the doglike work ethic to get over, under, or around any obstacle put in one's path."
• Build a one-page scorecard; grade candidates on a 1–5 scale per trait.
• Only advance candidates scoring 4 or 5 on every required trait — meeting the middle is not sufficient.
• Train every interviewer on definitions before they interview anyone. Shared definitions prevent wildly divergent ratings.

Red flags in candidates

• Culture misfit — skills don't matter if alignment is absent.
• No track record of growing people. A senior leader's core job is developing others.
• Job-hopping: repeated 12–18 month stints signal someone who leaves rather than solves.

Recruiting and compensation

• A-players have jobs. They won't apply cold — they need to be poached.
• Use a polarizing job posting plus an executive recruiting firm with a track record in C-suite placements.
• Set the title accurately before setting the salary. Title inflation (calling someone a COO when they're a VP Ops) distorts benchmarks.
• Compensation should reflect: title, scope of responsibilities, P&L ownership, strategic contribution, and how much leadership time they require from the CEO.
• Equity is not standard practice outside high-growth tech. Offer strong base pay, great culture, development programs, and generous time off instead.