Oct 25, 2023 · 1h 1m · news
Ely Lerner: Should Startups Hire Advisors & How much should they be paid? | E1075 · 20VC with Harry Stebbings
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, startup advisor Ely Lerner shares actionable frameworks for scaling startups, explaining how to effectively hire and compensate advisors, implement an "Offense vs. Defense" engineering framework, and optimize user activation aligned with an Ideal Customer Profile (ICP).
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 18.2% of the talking time here. How this is scored →
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Ely directly tells Harry 'You are [wrong]' when Harry forcefully insists that advisors should work with functional heads rather than guiding the CEO on primary growth strategy.
Hardest push from Harry ▶ 20:35 Harry aggressively challenging advisor access boundariesHarry forcefully rejects Ely's boundary that advisors must work through the CEO, using colorful language ('just fuck off... talk to my head of product') to challenge the premise.
Biggest teaching moment ▶ 36:00 Ely explaining diminishing returns on defensive tech investmentsEly educates Harry on how over-investing in defensive engineering like security and scaling past the point of diminishing returns creates a massive hidden opportunity cost against compounding offensive growth.
Harry holds his own ▶ 29:36 Harry calling out elite advisor compensation realitiesHarry demonstrates sharp domain knowledge by naming top advisors Elena Verna and Casey Winters, bluntly pressing Ely on market expectations by stating 'you gotta pay the fuck up'.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Ely's Entry Into Product, Growth, and Yelp | 1 | 2 | 0 | 0 | Harry opens with a warm welcome and asks Ely about his career transition into product across Yelp and Chime. Ely delivers a detailed background monologue about his experience with 0-to-1 internal incubations and the Eat24 acquisition. | |
| Zero-to-One Internal Startups vs. Corporate AI Hype | 4 | 3 | 1 | 4 | Harry challenges why top talent would build zero-to-one products inside incumbents without equity. Ely explains the unique leverage of corporate assets, and Harry adds that speed to distribution is a major motivator. | |
| Incentive Alignment: Product Lessons from Yelp and Chime | 3 | 3 | 0 | 0 | Ely explains incentive alignment as his key takeaway from Yelp and Chime. Harry links this to Brian Balfour's Reforge episode on business model fit before asking Ely to define modern advisory roles. | |
| Startup Timing: When to Bring in Functional Advisors | 2 | 4 | 1 | 3 | Ely advises founders never to delegate strategy for their primary growth lever. Harry probes whether that strategy can be delegated even if the company hires a full-time functional executive. | |
| Advisors vs. Hires: Navigating the Startup Gap | 3 | 2 | 0 | 1 | Harry asks how startups decide between hiring an advisor versus a full-time Head of Growth. Ely outlines the startup growth gap, and Harry offers a practical scenario involving an out-of-home marketing expert. | |
| Hands-On vs. Traditional Company-Level Advisory | 2 | 4 | 0 | 1 | Ely breaks down the distinction between traditional high-level monthly advising and his hands-on weekly model. Harry guides the explanation with direct questions on advisor evaluation criteria. | |
| The Limits of Advising: Teach to Fish | 5 | 5 | 6 | 8 | Harry forcefully challenges Ely's premise that advisors should only work with founders rather than functional heads, using colorful language ('just fuck off'). Ely directly rejects Harry's framing and insists founders must own primary growth levers. | |
| Evaluating Advisor Fit by Stage, Playbook, and Geography | 3 | 3 | 0 | 2 | Harry questions whether seed stage is too early for growth advisors given the lack of initial flywheels. Ely clarifies that seed advisors should help founders discover their growth model rather than scale an existing playbook. | |
| The 'Freemium Trial' Approach to Advisor Fit | 4 | 2 | 0 | 1 | Harry asks how founders can verify an advisor's true attribution claims. Ely explains his model of offering free help first, which Harry aptly re-frames as a 'freemium trial' for advisory services. | |
| Advisory Compensation: Structuring Equity and Cash | 6 | 3 | 1 | 5 | Harry injects real-world market context by citing top-tier advisors like Elena Verna and Casey Winters, bluntly stating founders 'gotta pay the fuck up'. Ely agrees and explains how cash-equity splits are structured. | |
| Ensuring Success: Overcoming Engineering Bottlenecks | 2 | 3 | 0 | 2 | Harry interrupts Ely's overview of first-month success signals to ask why engineering teams struggle to ship fast. Harry forces Ely to precisely define output versus outcome-driven engineering. | |
| The Offense vs. Defense Engineering Framework | 5 | 4 | 0 | 2 | Ely presents his Offense vs. Defense framework for engineering focus. Harry demonstrates strong product grasp by offering Figma's co-pilot as an offensive example and correctly summarizing the opportunity cost of chasing 100% reliability. | |
| Transitioning Growth Loops from Offense to Defense | 3 | 4 | 0 | 1 | Harry asks if offensive bets can transition into defensive ones and vice versa. Ely details S-curve growth loop decay and cites Airbnb's trust and safety as a defensive initiative that became offensive. | |
| Coordination and Conflicts in Outcome-Aligned Teams | 2 | 3 | 0 | 1 | Harry asks about potential org conflicts between offensive and defensive teams. Ely explains codebase coordination taxes and common founder mistakes like setting too many top-level OKRs. | |
| Managing Failed Bets and Validating Key Assumptions | 5 | 4 | 1 | 3 | Harry references Meta's Alex Schultz to argue that retention is king in growth prioritization. Ely agrees but reframes retention focus around activation and proper ICP tracking rather than churn reduction. | |
| Why Advisor Relationships Fail | 3 | 3 | 0 | 1 | Harry asks why advisor relationships fail and equates knowing when to end an advisory contract to changing therapists. Ely outlines capacity limits and alignment criteria. | |
| The Loneliness of the Solopreneur Advisor | 2 | 3 | 0 | 1 | Ely discusses the loneliness of solopreneur advising. Harry pivots quickly to ask whether growth teams should operate independently or embedded within core product teams. | |
| Avoiding Activation Pitfalls by Tracking the ICP | 4 | 4 | 1 | 2 | Harry points out that horizontal product founders frequently fail to understand their ICP. Ely builds on this by explaining that horizontal ICPs must be defined by shared user attributes rather than demographic personas. | |
| Staying Narrow in Horizontal Product Positioning | 3 | 3 | 1 | 4 | Harry pushes back on horizontal positioning, arguing that overly broad messaging fails to resonate with specific verticals like dentists or product orgs. Ely explains staying narrow horizontally. | |
| Quick Fire: The Death of Broad Growth Hacks | 2 | 2 | 0 | 1 | Harry initiates the quick-fire round. Ely asserts that the entire paradigm of broad 'growth hacks' has died, and Harry asks about data cleanliness requirements for growth hires. | |
| Quick Fire: Impressive Growth Strategies and Real Estate Network Effects | 3 | 2 | 0 | 0 | Harry asks for recent impressive growth strategies, citing Canva's TikTok and Notion's YouTube channels. Ely praises network effect models and highlights early-stage Cashflow Portal. |