When to hire a COO and how to make the partnership work

Executive overview

Most entrepreneurs reach a point where being self-reliant becomes a ceiling, not a strength. The business stalls because the founder is working outside their zone of genius — covering areas they dislike or do poorly.

The fix is hiring a second-in-command who is excellent at exactly what the CEO is not. This isn't delegation — it's a divide-and-conquer partnership built on deep trust, clear role boundaries, and mutual reinforcement.

The right COO doesn't just free the CEO — it makes the whole greater than the sum of its parts.

Recognising the inflection point

• Businesses hit natural thresholds: 1, 3, 10, 30, 100, 300 employees — each requiring a different operating model.
• At the 30-to-100 employee transition, founders typically lack the skills to manage everything and get stretched thin.
• Being busy on high-impact work isn't enough — if it drains you, someone else should own it.
• The COO role exists to carry the areas the CEO either can't do well or doesn't want to do.

Titles, trust, and hiring right

• Don't rush to give C-level titles at small companies — it causes salary creep and inflated expectations.
• At 20-30 people, "director of operations" or "general manager" is often the right fit.
• Interview primarily for trust: if you wouldn't hand them your banking login on day one, keep looking.
• Hire for proven execution, not theoretical knowledge — someone who has actually done the work, not just read about it.
• Cultural fit and core values alignment matter as much as skill set.

The yin-and-yang structure

• Every COO role is different — no fixed template. Finance may or may not report to them; sales, IT, and operations vary by company.
• The COO should own what the CEO avoids. Shopify's Harley Finkelstein (outward-facing) complements Tobias Lütke (inward, engineering). Howard Schultz's outward energy was balanced by operationally focused COOs.
• Common universal COO strengths: systems, leadership development, recruiting, conflict resolution, consensus building, project planning.

Onboarding and the first 90 days

• The "dating period" — cultural vetting, trust-building, reference checks — must happen before the hire, not after.
• CEOs often make the mistake of abdicating rather than delegating once a COO arrives.
• Give too much rope too fast, and the COO takes the company in a direction you didn't intend.
• The 1-800-GOT-JUNK example: Brian hired the former president of Starbucks to replace Cameron Herold, immediately handed her everything, and had to let her go 12 months later — cultural disconnection, too much autonomy too fast.

The CEO-COO relationship

• Schedule dedicated relationship time: weekly runs, off-site working sessions, recurring check-ins — not just operational meetings.
• The COO is often the only person who will tell the CEO hard truths. Never shoot the messenger.
• Disagree privately; present as a united front publicly — like co-parents.
• The COO's role is to make the CEO look iconic externally. The CEO's role is to protect the COO's credibility internally.
• Misaligned reference frames cause most breakdowns — two people in the same conversation rarely share the same definitions, assumptions, or context. Work to understand each other's perspective before assuming alignment.

What great coaching looks like

• Cameron Herold positions himself between coach (Socratic questions) and consultant (does the work) — closer to a mentor who provides shortcuts from lived experience.
• For the COO Alliance: peer learning, not expert delivery. Masterminds, Slack channels, peer presentations, occasional outside speakers. He presents for roughly 30 minutes of a two-day event.
• Momentum compounds: get enough small things into orbit and they stay there. Don't wait for perfection.

Before hiring a COO, hire an EA

• Many entrepreneurs say they need a COO but don't yet have an executive assistant.
• If you don't have an EA, you are one.
• Hire the EA first — it frees the CEO for higher-leverage work and clarifies what a true second-in-command would actually own.