The Twenty Minute VCJordan Van Horn: 3 Reasons Salespeople Fail; How to Make a Sales Playbook | 20VC #918
CHAPTERS
- 0:00 – 1:39
From winery sales to Dropbox & Monte Carlo: Jordan’s path into tech sales
Jordan shares how he accidentally found his way into sales, starting in the wine industry and later moving to San Francisco where he joined Dropbox. He also sets context for how those early experiences shaped his later leadership roles, culminating in Monte Carlo.
- •Started career in the wine industry via a Gallo Winery scholarship program
- •Moved to San Francisco and transitioned into tech at Dropbox
- •Sales as an “accidental” career path for many operators
- •How early roles created foundations for later go-to-market leadership
- 1:39 – 2:20
Lessons from selling wine: connecting with wildly different buyers
Jordan explains how winery work forced him to sell to a broad range of people—from grocery managers to senators. That range taught humility and the core sales skill of understanding what matters to different stakeholders.
- •Selling to diverse audiences builds adaptability
- •Learned empathy and how to connect across backgrounds
- •Sales effectiveness comes from understanding what’s important to others
- •Early perspective shaped his later enterprise selling approach
- 2:20 – 3:58
Dropbox vs. Segment: clarity of identity and the craft of hiring
Jordan contrasts Dropbox’s occasional lack of focus on identity (consumer vs. enterprise) with Segment’s intense discipline around hiring. He highlights that leadership leverage ultimately comes from bringing in great people and maintaining a high talent bar.
- •Startups succeed or fail on simplicity and clarity of thought
- •Dropbox’s identity ambiguity created missed opportunities
- •Segment experience emphasized hiring as the highest-leverage leadership skill
- •A company is people + how you do things (culture + execution)
- 3:58 – 5:16
What a “revenue leader” actually does (and why titles matter less)
Jordan demystifies his ‘revenue leader’ title, effectively describing a CRO-style remit across SDR, sales, CS, and partnerships. He also notes Monte Carlo’s informal approach to leveling/titling given rapid scaling.
- •Revenue leader role mirrors a CRO remit
- •Ownership spans multiple go-to-market functions
- •Monte Carlo scaled far without formal HR/titling infrastructure
- •Focus on impact over nomenclature
- 5:16 – 6:00
Sales playbook definition: five steps from understanding to customer success
Jordan defines a sales playbook as discrete steps that guide a customer from understanding the product through evaluation, consensus, and formal commitment. Importantly, he frames it as a blueprint for post-sale success—not just closing.
- •Playbook helps customer understand what you do
- •Evaluates whether solution drives a business outcome
- •Builds consensus among stakeholders
- •Formalizes the relationship and sets success blueprint
- 6:00 – 8:21
Who owns the playbook: founder-led V0 vs. prescriptive V20
Jordan argues founders must own the earliest version of the playbook, while later versions become more detailed to support scaling and onboarding. He outlines three foundational pillars founders must document continuously across company stages.
- •Playbooks evolve from V0 to highly prescriptive versions
- •Founder accountable for V0 foundations
- •Document: who you solve for (and who you don’t)
- •Document: wins/losses and customer resonance factors
- •Document: why buy now (the compelling event)
- 8:21 – 10:09
“Is our product for everyone?” How to define ‘who’ for horizontal tools
Jordan explains that ‘who’ in sales means the buyer and early-adopter companies, not all possible end users. Even horizontal products must focus sales time on the highest-value targets given limited bandwidth and product maturity constraints.
- •Separate end-user breadth from monetization buyer focus
- •Early adopters differ from eventual large-enterprise targets
- •Match sales motion to product readiness (e.g., SSO, enterprise needs)
- •Focus is a time-management and prioritization tool for sales teams
- 10:09 – 12:13
How founders should capture resonance: recorded calls, themes, and the rule of three
Jordan recommends recorded calls as the best artifact for new sales hires, with founder shadowing as a close second. He emphasizes systematically asking prospects why they took the call, then grouping answers into a few repeatable archetypes.
- •Recorded calls are the best onboarding gift to sales
- •Ask every prospect: ‘Why did you take this call?’
- •Look for consistent themes behind meetings and purchases
- •Use simple archetypes (rule of three) rather than dozens of categories
- 12:13 – 14:02
Quota misses and ‘no urgency’: diagnose pain, avoid bad pressure tactics
Jordan reframes urgency as a pain-understanding problem: if pain is real and consequences are clear, deals don’t endlessly slip. He critiques exploding discounts as a poor customer experience and notes that relationships can help—but shouldn’t replace value clarity.
- •Lack of urgency usually means insufficiently understood pain
- •Clarify consequences of inaction and why now matters
- •Exploding discounts create a bad customer experience
- •People buy from people, but value must still be anchored
- 14:02 – 16:10
Discounting strategy by stage: learning early, pricing discipline later
Jordan’s stance is that early-stage ARR and exact pricing matter less than learning with high-fit customers. As you scale, however, pricing discipline becomes crucial because customers compare notes and fairness perception impacts trust and retention.
- •Early-stage: optimize for learning and customer quality, not price
- •Communicate pricing will evolve; align price to value
- •Later-stage: discounting discipline improves customer trust
- •Packaging/price gaps shouldn’t be ‘solved’ by excessive discounting
- 16:10 – 17:58
When champions leave: multithreading vs. compressing deal cycles
Jordan explains that multithreading depends on deal size and complexity; for low ASP, speed matters more than stakeholder mapping. For enterprise, you must align champion, practitioner, and economic buyer—or risk churn even after signature.
- •Champion departure is brutal pre- and post-close
- •Low ASP: compress cycles to reduce ‘things go wrong’ window
- •Enterprise: must multithread across champion/practitioner/economic buyer
- •No champion post-close equals day-one churn risk
- 17:58 – 22:28
When to hire the first sales hire: what problem are you solving?
Jordan rejects a one-size-fits-all formula and instead pushes founders to articulate the purpose of the hire. He outlines scenarios where hiring makes sense—and warns that hiring won’t fix product-market fit or instantly remove the founder from sales.
- •First question: why hire a salesperson—what problem is being solved?
- •Don’t hire sales to solve PMF issues
- •Signals: repeatable lead generation and progression indicators
- •Expect founders to stay heavily involved with customers for months
- 22:28 – 26:26
Head of Sales vs. junior reps: complexity, confidence, and founder involvement
Jordan offers three variables for choosing seniority: sale complexity, confidence in the go-to-market motion, and desired founder involvement. He warns against over-hiring senior leaders too early, who may add process overhead instead of closing deals.
- •Decision variables: sale complexity, GTM confidence, founder involvement
- •Transactional motions can start with junior reps if volume supports it
- •Senior leaders help scale hiring and attract talent, not necessarily sell better
- •Avoid premature process/tooling overhead (e.g., Salesforce too early)
- 26:26 – 31:18
Designing the sales hiring process: 3 reasons salespeople fail and how to screen for them
Jordan structures hiring around failure modes: org fit, motivation, and skill alignment. He advocates ‘scaring candidates off’ with reality, then going deep on relevant past performance with layered questioning to uncover true attribution.
- •Salespeople fail due to: culture fit, motivation, or skill mismatch
- •Start by truth-telling about what’s hard so candidates self-select
- •Prefer deep dives into relevant past experience over forward case studies
- •Key diagnostic question: ‘What was hard about it?’
- 31:18 – 36:38
Interview loop mechanics and what great candidate presentations look like
Jordan breaks down his multi-step loop: motivation screen, deep track-record assessment, then competency-based interviews and a final presentation (even though he dislikes it). He values presentations that demonstrate discovery and curiosity, not polished ‘book reports.’
- •First screen tests motivation and startup reality tolerance
- •Manager deep-dives track record and attribution before broader loop
- •Onsite/loop assigns competencies to interviewers with scoring
- •Best presentations are interactive and discovery-driven; worst are scripted recitations
- 36:38 – 54:15
Jordan’s hiring mistakes and post-hire management: user guide, talent nurturing, and onboarding signals
Jordan shares his biggest hiring errors (skipping process, weak references, unclear role definition), then shifts to how he manages after hiring. He explains his personal ‘user guide,’ how he gives day-one feedback on strengths/failure risks, and what onboarding/red flags look like—especially in enterprise sales.
- •Mistakes: deviating from process, skipping references, unclear role conviction
- •User guide sets expectations, boundaries, and decision principles to build trust
- •Day-one: explain why hired + why they might fail; revisit regularly
- •Onboarding should match company maturity; managers own early enablement
- •Early red flag is lack of impact in first 30 days; focus on leading indicators over revenue
- 54:15 – 1:03:46
Deal reviews and the learning engine: postmortems, psychological safety, and scaling challenges
Jordan describes an aggressive postmortem culture—weekly forward-looking deal reviews plus retros on significant losses (and even messy wins). He also discusses creating safety by modeling vulnerability, then closes with what breaks during scaling and sales strategies he admires.
- •Early-stage success depends on learning speed, not just revenue
- •Weekly deep deal reviews plus retros for resource-heavy losses/slow POCs
- •Reps should lead postmortems; leaders must prevent blame dynamics
- •Safety comes from leaders sharing failures and normalizing imperfection
- •Scaling breaks communication and erodes ‘core nucleus’ practices; admired strategies: Retool and MongoDB transitions
