Why every CEO needs a trusted second in command

Executive overview

Most CEOs hit a ceiling not because they lack vision, but because they have no one to run the business while they think. A COO gives the CEO breathing room to be strategic instead of reactive.

The right second in command isn't a clone — it's a yin/yang complement. The hire timing, the fit, and the onboarding all determine whether the relationship compounds or collapses.

The CEO's job is to grow the business; the COO's job is to run it — and the two roles only work when trust is total and the skills are genuinely complementary.

When to hire your second in command

• At 30 employees you have your first true candidate: someone who could run the company if you were sick for six months
• Before that, hire an executive assistant first — most "COO needs" at 10–30 staff are actually EA-level tasks
• The first real COO arrives when you have a full VP/C-level leadership team (~100 employees) who need someone to run them
• Headcount and revenue scale together: $10M is when you can start buying talent; $30M is when you can talent stack
• One A-player replaces three C-players — smaller, better-paid teams outperform larger cheap ones

Finding the right fit

• Start with a self-assessment: what fills you with energy vs. drains you? What functional areas do you own vs. want to shed?
• The COO should be strong where the CEO is weak — not competing for the same work
• Example: Shopify's Harley Finkelstein handles outward-facing sales and biz dev; Tobi Lütke owns engineering
• Great people aren't job-hunting — go where they congregate (e.g. veteran transition networks, executive communities)
• Treat the job description as a marketing asset: hire a copywriter to make it polarising and specific, not generic
• Culture specificity in the job post attracts the right person and repels the wrong one

The 90-day onboarding framework

• Month 1: observe only — sit in on every meeting, ride shotgun, read emails, take notes, act on nothing
• Month 2: stress-test hypotheses — dig into the things you wrote down, ask questions, validate or discard
• Month 3: execute in priority order, starting with easy wins — quick changes that pay dividends long-term
• Easy wins build trust with the team before tackling big disruptive projects (e.g. ERP integrations)
• Watch for ripple effects: resentment from staff who wanted the role, clashes in reporting lines, premature decisions

What makes the CEO-COO relationship work

• Treat it like a marriage: absolute trust, complementary strengths, ability to finish each other's sentences
• The CEO should praise publicly, give candid feedback privately, and ask the COO where they could improve
• Vulnerability runs both ways — the CEO asking for feedback models the behaviour they want in the organisation
• The right COO at one stage of growth may be wrong for the next: skills that work at $2M–$100M break at $100M+
• A pre-existing relationship (mastermind group, friendship) compresses the trust-building timeline dramatically

Common CEO mistakes that stall growth

• Seagull management: swooping in, making a mess, then leaving
• Interfering when things are running well — sometimes the job is to step back and let it operate
• Praising too rarely; defaulting to "what's broken" instead of "what's working"
• Bringing negative energy into the organisation — energy transfers, positive or negative
• Ignoring the CFO or VP of Finance on cash flow concerns (this caused Cameron's team to nearly miss payroll at 1-800-GOT-JUNK)
• Measuring too many KPIs; focus on the few that actually drive decisions

The employee net promoter score

• The single most important metric: how happy are your employees?
• Happy employees drive customer satisfaction, reduce turnover, lower training costs, and enable premium pricing
• Survey twice a year (January and July); ask one open question in July: "What's one free thing we could do to make this the best place to work?"
• Can be as simple as a post-it note with a 1–10 rating — tool doesn't matter, habit does

COO Alliance

• A peer community exclusively for second-in-commands — no entrepreneur groups, no functional silos
• $8,900/year: monthly 3-hour sessions, private Slack group, accountability groups of six, two optional in-person events
• In-person events held in Scottsdale and at MIT; topics include AI tools, culture, hiring, meeting rhythms, and KPIs
• ~200 members across 17 countries, ages 22–62, ~40% women
• Content is practitioner-level: members spend hours debating interview questions, onboarding software, and conflict resolution