The Twenty Minute VCChad Peets: Why Most Sales Reps Underperform & Remote Reps Ignore Development | E1193
CHAPTERS
- 0:00 – 4:15
Chad’s unconventional path into software sales recruiting
Chad explains how an early ambition to be a stockbroker turned into a pivot away from Merrill Lynch and into software sales recruiting. He shares the moment a client reframed his view of “real money,” and how that led to joining (and quickly leading) a top recruiting firm before founding Pietzen Associates.
- •Early inspiration from the film Wall Street and studying finance at USC
- •Why stockbroking felt like product-pushing and relationship monetization
- •A client encounter that redirected him into software sales recruiting
- •High-risk move: commission-only recruiting role while newly married
- •Becoming #1 at the firm and founding Pietzen Associates after partner conflict
- 4:15 – 7:15
Are great sellers born or made? The traits Chad says you can’t teach
Chad argues that selling ability is largely innate: you can improve someone, but you can’t create a seller from scratch. He emphasizes comfort with the phone, anticipating objections, and the willingness to outwork others.
- •Sales as an innate skill: coaching helps, but fundamentals can’t be taught
- •Comfort with direct outreach (especially phone) as a differentiator
- •Thinking “three steps ahead” and pre-handling objections
- •Work ethic as a compounding advantage in any sales role
- 7:15 – 9:07
Focus beats verticals: succeeding with a horizontal customer base
Harry challenges how to know customers deeply when your market is horizontal. Chad claims horizontal selling works fine—and is often better—so long as you develop tight audience understanding and targeted outreach instead of spraying across segments.
- •Chad’s view: vertical-only focus can cap TAM and company potential
- •Horizontal companies still require precision in targeting and ICP clarity
- •Avoid generic discovery questions; learn the buyer’s motivations first
- •Reps often default to “money” as motivation—Chad looks for development drive
- 9:07 – 11:47
Detecting “career growth” BS: resume pattern-matching and references
Chad details how he screens for authenticity by analyzing a candidate’s career moves and their underlying motivations. He also explains why references matter more as roles become more senior, and addresses concerns about hiring from a known ecosystem vs. diversity.
- •Resume forensics: moves for base pay/quota relief are red flags
- •Validating development motivation via leaders/companies chosen (e.g., AppDynamics, MongoDB, Snowflake)
- •References become increasingly important for CRO-level hires
- •Ecosystem hiring can limit diversity, but ecosystems can expand with intentional next-gen search
- •Med(d)ic/Medpick-style playbooks spreading beyond one network
- 11:47 – 15:51
Why Sutter Hill hires CROs pre-product (and why founders shouldn’t write the playbook)
Chad explains Sutter Hill’s atypical model: bringing in a CRO before the product exists to drive discovery and shape what gets built. He argues founders (often engineers) lack the time and repetition needed to run thousands of market conversations and translate that into a sales playbook and roadmap inputs.
- •Traditional sequence: build product → raise → build GTM; Chad says discovery must be deeper earlier
- •CROs can run thousands of calls to validate value, needs, and roadmap priorities
- •Founders should participate, but shouldn’t own the discovery workload
- •Sales leaders create sales playbooks; asking founders to do it is ‘backwards’
- •This approach often requires larger early capital (not a $2–3M seed) and fits Sutter Hill’s incubation model
- 15:51 – 21:06
What the “right sales org” means: CRO–Product alignment and roadmap-driven hiring
Chad defines a strong sales org as one where sales and product jointly own the roadmap and ICP expansion plan. He warns that boards/CEOs often push hiring ahead of product readiness, setting reps up to fail when the roadmap doesn’t deliver.
- •Roadmap must reflect customer reality gathered by the CRO, not siloed product guesses
- •ICP expansion requires explicit feature/security commitments and timelines
- •Hiring should map to addressable ICP capacity; otherwise reps have nothing real to sell
- •Common failure mode: pressure to double headcount without product enabling broader selling
- •Reps chasing big logos can distort roadmap and distract engineering with one-off demands
- 21:06 – 23:00
Fixing broken Product–Sales culture (and why CEO leadership is the lever)
Chad describes how mistrust forms when product and sales operate in silos and blame each other for missed revenue. His prescription is straightforward: CEO-led alignment, shared accountability, and explicit linkage between delivery commitments and forecast outcomes.
- •Silo dynamics: product says ‘sales can’t sell’; sales says ‘product built the wrong thing’
- •CEO must actively lead collaboration; it won’t self-correct
- •Tie roadmap delivery to revenue forecasting so product understands revenue impact
- •Use structured feedback loops from sales to product with plans and timelines
- 23:00 – 24:22
Comp, incentives, and attribution: pay for the behavior you want
Chad argues there’s no universal comp plan—only desired behaviors in a specific business context. He illustrates how comp can re-balance focus between land and expand when expansion cycles are too long or expansion size is too small.
- •Attribution is secondary to behavior design: comp plans create predictability
- •Example lever: higher commission rate on expansion to shift rep focus
- •Diagnose land vs. expand motion with cycle time and dollar outcomes
- •Revenue matters, but levers should match the constraint in the funnel
- 24:22 – 26:14
ACV thresholds, inside vs. field sales, and the 3× OTE productivity rule
Chad lays out how ACV and unit economics determine whether you run inside sales, field sales, or both. He uses a simple productivity heuristic—3× OTE—and warns against scaling headcount before productivity is proven or clearly trending upward.
- •$10K ACV requires a low-cost inside-sales model; field sales won’t pencil
- •Healthy model often combines velocity (inside) and enterprise (field) motions
- •Rule of thumb: reps should produce ~3× OTE (e.g., $300K OTE → $900K productivity)
- •Don’t add reps if productivity is weak—fix the system first
- •Hiring ahead of productivity is possible only if the data is trustworthy
- 26:14 – 27:59
Ramp time and when to invest in enablement and onboarding
Chad outlines ramp expectations (inside ~90 days; enterprise ideally ~6 months, often ~9) and how to diagnose why ramp is long. He argues enablement should start as CRO-led but must become programmatic as headcount scales, and onboarding should never be shortcut.
- •Enterprise ramp target: 6 months; reality can drift to 9—diagnose why
- •Ramp issues can stem from enablement gaps, product limitations, or cycle length
- •Enablement hiring is CRO-led; becomes necessary around ~30–40 reps
- •Standardize messaging/programs; don’t let managers improvise enablement
- •Onboarding at scale requires dedicated resources, classes, and multi-month programs
- 27:59 – 31:32
Sales and Customer Success: why expansion is still sales (and how churn gets created)
Chad critiques the ‘rep lands and leaves’ model and insists sales must stay engaged through the customer journey. He explains how misaligned incentives (bookings vs. consumption) can create overbooking, poor outcomes, and churn—making tight AE–CS partnership essential.
- •CS is difficult to “nail”; Snowflake historically minimized formal CS due to product-led expansion
- •CS should ensure implementation, adoption, utilization, and champion health
- •Expansion is a sales activity; CS supports outcomes and value realization
- •Misalignment risk: bookings-based comp encourages overbooking vs. real consumption/value
- •Customer journey ownership reduces churn and increases sustainable expansion
- 31:32 – 34:46
Snowflake hiring machine: process discipline, speed, and message consistency
Chad shares what enabled Snowflake’s rapid scaling: a strict, non-negotiable interview process, binary decisions, and uniform company messaging. He warns that extra interviewers (like engineers) slow hiring, introduce risk, and create internal friction without improving selection quality.
- •World-class scaling requires a standardized hiring process with no deviations
- •Binary decisions at each stage; indecision signals a weak hiring manager
- •Limit interviewers to those uniquely qualified to ‘sell’ or ‘qualify’ candidates
- •Avoid ‘culture fit by committee’—adds delay, risk, and post-decision resentment
- •Uniform recruiting pitch (especially equity story) preserves credibility across interview loops
- 34:46 – 51:43
Hire fast, fire thoughtfully: mis-hires, rep fatigue, and what makes great reps now
Chad defends ‘hire fast’ for scaling but urges rigor on profile adherence and accountability for rep success. He explains how reps can burn out from the grind (pipeline generation) and how today’s talent market makes it harder to find people willing to sacrifice for excellence—especially in inside sales and in-office development.
- •Speed matters, but only with a clear profile and front-end gatekeeping
- •Don’t fire in weeks unless it’s a major conduct/HR issue; managers must coach first
- •Separate ‘bad rep’ from ‘bad patch’ (territory/account quality)
- •Top-performer decline often stems from burnout and aversion to startup grind
- •Non-negotiables: work ethic, development mindset; inside sales should be in-office for faster growth
- 51:43 – 56:41
Enterprise vs. PLG expansion: timing, starting in mid-market, and retention metrics
Chad argues PLG-to-enterprise is a different motion that often requires a separate enterprise sales org and value proposition. He recommends starting in mid-market to learn and build, moving upstream only when product readiness is proven, and using GRR vs. NRR to distinguish product problems from GTM/CS expansion problems.
- •PLG users don’t automatically unlock enterprise buyers; value props differ (developer vs. CTO)
- •Chad’s preference: start with direct sales, then add PLG when product is ready
- •Go enterprise too early and you’ll get pulled into one-off requirements and long cycles
- •Start mid-market intentionally to learn and mature product for enterprise demands
- •GRR signals product satisfaction; slipping GRR is urgent; NRR reflects expansion execution too
- 56:41 – 1:02:14
Keeping teams together in bad patches: churn, product delivery, and forecast integrity
Chad explains that churn and product misses quickly undermine morale and retention—often first visible in sales engineer attrition. He also criticizes CEO-driven forecasts designed to raise funding rather than reflect business reality, warning CROs must push back or accept they’ll be blamed and fired.
- •SE attrition is an early warning; reps follow because SEs see product truth first
- •Churn drivers include missed commitments, product failures, and weak realized value
- •Sales stays if product listens, commits to fixes, and reliably delivers on timelines
- •Common dysfunction: CEO sets forecast to justify a raise; CRO is forced to accept unrealistic numbers
- •Best CROs confront the mismatch early; otherwise they’re set up to fail
- 1:02:14 – 1:07:53
Quick-fire: mindset shifts, best advice, biggest founder mistake, and Chad’s weakness
In closing, Chad reflects on how the world is changing and his limited willingness to compromise on core values. He shares tactical advice for new reps and leaders, rejects the ‘coin-operated mercenary’ stereotype, and identifies impatience as his biggest personal weakness.
- •Mindset shift: accept changing norms, but keep core principles; consider retirement over full value change
- •Advice to new reps: invest in learning, seek mentorship, outwork peers
- •Advice to new leaders: learn the business fast by getting close to customers and reps
- •Biggest founder mistake to $10M ARR: hiring the wrong CRO without knowing the required profile
- •Personal weakness: impatience and overreacting to too many ‘fires’ at once
