May 25, 2022 · 54m · news
Oliver Jay: How To Create and Execute a World-Class Sales Playbook | 20VC #889 · 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 episode of 20VC, tech operating veteran Oliver Jay shares high-growth sales strategies, detailing how early-stage founders can successfully build agile sales playbooks, align hiring and onboarding with product mastery, and navigate the transition from PLG to enterprise and outbound sales.
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.7% of the talking time here. How this is scored →
speaking balance: gold is Harry, purple is the guest (3 minute bins)
When Harry cites Jason Lemkin's tactic of pitting two reps against each other Hunger Games style, Oliver directly rejects the framing, stating that if you rely on cohort competition you hired the wrong people.
Hardest push from Harry ▶ 9:46 Harry pushes Oliver on VC playbook adviceHarry directly challenges Oliver's dynamic playbook concept by citing VC advice and pointing out that reps churn and morale suffers when founders fail to provide a structured playbook early on.
Biggest teaching moment ▶ 7:07 Oliver redefines the 20-AE playbook thresholdOliver dismantles the standard industry usage of the word playbook, educating Harry that a repeatable sales playbook cannot be formally declared until a company has at least 20 ramped AEs.
Harry holds his own ▶ 9:46 Harry articulates rep failure modes from a VC perspectiveHarry demonstrates domain knowledge by detailing the exact mechanics of rep churn and toxic team dynamics that occur when junior hires lack a structured sales process.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Oliver Jay's Path from Finance to Scaling Sales | 2 | 3 | 1 | 2 | Harry sets up the interview asking about Oliver's career path from finance to sales at Dropbox and Asana. Oliver explains the evolution from BYOD to BYOA and product-led growth dynamics. The dynamic is polite and conversational with minimal friction. | |
| Demystifying and Structuring the Sales Playbook | 5 | 6 | 4 | 5 | Oliver immediately pushes back on the common definition of a sales playbook, reframing it around persona discovery rather than scalable processes. Harry presses back with VC perspective, asking how his usual advice to founders is wrong when lack of a playbook leads to rep churn. Oliver explains that repeatable playbooks shouldn't be locked down until a company has at least 20 ramped AEs. | |
| Deciding When and Whom to Hire First | 4 | 5 | 4 | 3 | Harry quotes Jason Lemkin's advice to hire two sales reps simultaneously and pit them against each other 'Hunger Games style.' Oliver explicitly disagrees with this premise, arguing that early stage reps need a culture of collaboration rather than manufactured internal competition. | |
| Designing the Interview Process and Compensation for Early Sales | 3 | 5 | 2 | 2 | Oliver breaks down hiring traits like reverence for product and making others better, sharing concrete interviewing techniques. He also warns against setting up traditional commission plans too early before target metrics are validated. | |
| Structuring an Effective Sales Onboarding Program | 2 | 5 | 1 | 2 | Oliver outlines a three-step onboarding framework starting with support and product exposure, followed by market knowledge, and ending with sales tactics. Harry acts as an active listener, asking tactical follow-up questions to clarify timelines and customer touchpoints. | |
| Transitioning to Outbound Sales and the CRO-CEO Partnership | 3 | 5 | 2 | 3 | Oliver warns against treating outbound cold emailing as a quick fix for plateauing PLG metrics. Harry asks how CEOs should manage CRO partnerships and handle rep excuses like bad timing using Toyota's Five Whys framework. |