By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

The Twenty Minute VC

Mire CRO Zhenya Loginov: Hiring Tips for Sales; Why Dropbox Lost Enterprise | 20VC #900

Zhenya Loginov is the CRO @ Miro, the leading visual collaboration platform that helps bring teams together and meaningfully improves the way people work. At Miro, he runs the go-to-market team of 700+ people across 11 global offices.

Harry StebbingshostZhenya Loginovguest

Jun 22, 20221h 0mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

CHAPTERS

Jump to publisher timestamps

Chapter summaries

From programming competitions to CRO: Zhenya’s path into tech and revenue leadership
Zhenya shares how a technical upbringing (competitive programming) led him to business roles in consulting/finance, then to founding an e-commerce company. He traces the subsequent career arc through eBay, Dropbox, Segment, and ultimately Miro.
- •Early technical foundation and decision to move to the business side
- •First startup experience as the entry point into tech
- •Transition from founder to operator at large tech companies
- •Progression into senior revenue and go-to-market leadership roles
Dropbox vs. Segment: the enterprise lesson and avoiding missed market windows
Zhenya’s biggest Dropbox takeaway is stark: if your market includes enterprise, you must commit to winning it. He explains how that lesson directly shaped his priorities at Segment—making it a serious enterprise player.
- •Enterprise is non-optional when it’s part of your addressable market
- •Dropbox had the chance to own enterprise file collaboration and didn’t
- •Enterprise success requires multi-year investment and focus
- •Segment role selection was influenced by the desire to ‘win enterprise’
When to move upmarket: timing, competition, and the multi-year enterprise build
Harry challenges the reflex to ‘move to enterprise too early,’ and Zhenya frames the answer as market-dependent. He emphasizes that enterprise capability takes years to build, so companies must plan far ahead even if they delay execution.
- •Move timing depends on competition and market dynamics
- •If competitors will jump upmarket, you can’t miss the boat
- •PLG/SMB depth can sustain big businesses, but enterprise takes 3–4+ years to mature
- •Strategic planning horizon matters more than short-term pull
Can early-stage teams run PLG and enterprise together? Focus, sequencing, and the ‘free money’ trap
Zhenya argues the best long-term model is PLG plus enterprise, but early-stage resource constraints usually force focus. He also explains how ‘pulled in’ enterprise deals can help (marquee logos, requirements learning) or harm (roadmap derailment).
- •PLG + enterprise is ideal long-term; early-stage often must pick one
- •If PLG is possible, prioritize it—hard to rebuild later if missed
- •Beware enterprise deals that require heavy off-roadmap engineering
- •Early enterprise adopters can become crucial lighthouse customers
Why Dropbox didn’t win enterprise: company-wide commitment and cultural beliefs
Zhenya attributes Dropbox’s enterprise shortfall to insufficient, sustained CEO-led commitment and incomplete cultural alignment. Winning enterprise requires the entire company—product, engineering, marketing, and leadership—to believe in the motion and support it.
- •Enterprise motion must be owned top-down, starting with the CEO
- •Culture must value enterprise customers and sales as customer-enabling
- •GTM leaders cycling through without full backing undermines momentum
- •Enterprise success isn’t just sales; it’s product/engineering/marketing alignment
Segment’s impact: learning sales as a deep discipline (from outsider to sales leader)
Zhenya describes being asked to run sales at Segment despite not coming from a sales background. He explains how that experience reshaped his view of sales from ‘relationships + product knowledge’ to a sophisticated, multi-disciplinary craft.
- •Moved from Head of CS to leading Sales at CEO’s request
- •Iterative trust-building: ‘try for six months’ cycles
- •Sales is a deep field with multiple sub-disciplines to master
- •Increased respect for sales through hands-on leadership experience
What a Sales Playbook really is: customer, team, and market levels
Zhenya defines a sales playbook across three layers: customer-level problem/solution, team-level operating model, and market-level long-term strategy. He also maps each layer to a distinct time horizon from single meetings to multi-year market shifts.
- •Customer-level: problem, persona, solution; spans meeting-to-deal cycle
- •Team-level: hiring profiles, ramp/training, coverage model; spans 6–12 months
- •Market-level: segmentation shifts, buyer shifts, geographies, competitor set; spans 5+ years
- •Playbook is not a doc—it’s an operating system across horizons
Who should build the playbook—and why hiring a Head of Sales can come before reps
Zhenya challenges the idea that founders should ‘write the playbook’ alone; he prefers founders deeply involved but guided by sales professionals. He argues that once early PMF/revenue traction exists, hiring a Head of Sales creates founder bandwidth versus consuming it like early reps can.
- •Founder is often first seller, but shouldn’t be sole author/operator of the playbook
- •Sales expertise is underestimated; playbook must resonate with reps
- •Enablement/empowerment: reps execute better when they own the system
- •Don’t hire sales before PMF; after several deals/$1M-ish revenue, hire Head of Sales
- •Head of Sales creates bandwidth; junior reps often consume founder time
PLG failure modes and internal conflict: sequencing, over-rotating to sales-led, and incentive design
Zhenya outlines common PLG pitfalls: adding enterprise too late, adding it too early (thereby killing PLG), and structuring teams to fight each other. He explains how misaligned ownership of ‘self-serve vs high-touch’ revenue creates cannibalization battles and bad resource use.
- •Too late to enterprise enablement can cause missed market opportunity
- •Too early to enterprise can prevent PLG engine formation and lock in sales-led behavior
- •Bad org design creates self-serve vs high-touch infighting
- •Incentives/ownership must optimize for company + customer, not sub-team revenue
How Miro reduces PLG vs enterprise friction: revenue alignment and product-led enterprise growth
Harry probes for resource conflicts at Miro, and Zhenya reframes the risk as ‘alignment conflicts.’ He explains Miro’s approach: CRO accountable for all revenue while self-serve stays within product, plus an enterprise growth product team that supports enterprise expansion through PLG principles.
- •CRO accountability across all revenue reduces internal cannibalization incentives
- •Self-serve/PLG team sits in product engineering (not under CRO) to protect UX quality
- •Enterprise growth can be a product team inside the PLG org
- •Connecting PLG and enterprise everywhere improves overall motion
Hiring sales leaders: the 70/30 rule, must-have criteria, and learning roles you don’t understand
Zhenya’s hiring philosophy favors candidates who know ~70% of the job but are hungry to grow into the remaining 30%. He stresses the need to research roles, define 3–5 resume-screen ‘must-haves,’ and build personal understanding via conversations and reading—especially when hiring outside your expertise.
- •Prefer ‘growth candidates’ over exact-repeat experience in many high-growth roles
- •Define non-negotiable experiences (the critical 70%) and screen ruthlessly
- •If you don’t understand the role, don’t open it—research first
- •Founders must become multi-discipline learners (books + expert conversations)
Designing a rigorous hiring process: pre-panel deep interviews, tailored panels, and avoiding common mistakes
Zhenya details an unorthodox process: heavy hiring-manager time (multiple one-hour interviews) before involving the broader panel, ensuring high confidence in both success and offer acceptance. He explains how to build role-specific panels, make them meaningfully ‘hard,’ and shares mistakes like ignoring criteria or over-trusting resumes/panels.
- •Use 3–5 must-have resume criteria; no ‘nice-to-haves’ at screening stage
- •Hiring manager spends ~4–5 hours in structured interviews before panel
- •Goal: ~70% confidence they’ll pass panel; ~90% confidence they’ll accept offer
- •Panels are role-specific; include internal stakeholders and sometimes board/advisors
- •Make panels hard by using calibrated interviewers who disagree thoughtfully
- •Common mistakes: ignoring your own criteria; over-trusting resume/panel; insufficient depth interviews
Onboarding and early warning signs: freeing the first month, building cross-functional ties, and radical candor
Zhenya advocates protecting a new leader’s first month for learning and relationship-building, especially with product/engineering peers they’ll need long-term. He gives early red flags (no shipped value, ‘strategy charts,’ team rejection) and explains how to address underperformance with direct, caring clarity about consequences.
- •Protect month one: learning, meeting key cross-functional partners, product immersion
- •Start with relationships needed 6–12 months out (e.g., engineering/product), not just direct reports
- •Create a small ‘low-hanging fruit’ project to build credibility
- •Red flags: no value by months 2–3; avoiding customers; team signals rejection
- •CEO should proactively solicit feedback about the new leader’s impact
- •Use radical candor: immediate, explicit feedback and consequences while showing support
Running deal reviews as team clinics: cadence, ownership, and avoiding defensiveness
Zhenya explains deal reviews as a learning mechanism for the entire sales org, not a performance trial for the rep. He outlines a weekly cadence, ~60-minute depth per deal, rep ownership of the content, and leader ownership of the framework—plus pitfalls when reps become defensive and hide reality.
- •Primary audience is the broader team; goal is shared learning and repeatability
- •Weekly deal reviews; ~60 minutes per deal can be effective
- •Review can be mid-flight or opportunity-creation, not only closed/won/lost
- •Senior sales leader sets the framework; rep running the deal owns the meeting content
- •Avoid making it a personal judgment forum; defensiveness reduces truth and learning
CRO vs Head of Sales, adding structure without killing agility, and closing quick-fire insights
Zhenya clarifies that CRO can mean different scopes; at Miro it includes CS and other ops-like functions, with a Head of Sales complementing his non-sales background. He shares his model for preserving agility through delegation (‘villages’), lightweight processes with frontline buy-in, then ends with quick-fire lessons on scaling, remote morale, international expansion, and admired PLG companies.
- •CRO often overlaps with Head of Sales; separation depends on scope and skill complementarity
- •Split responsibilities: CRO drives structure/process/strategy; Head of Sales drives sales execution and talent profiles
- •Agility comes from pushing authority down; leaders should ‘own the franchise’ locally
- •Process should be lightweight and originate from/bought into by frontline teams
- •Scaling breakpoint around ~150 people (Dunbar number)
- •International expansion requires whole-company support and should start earlier than many think
- •Remote work most harms morale/camaraderie; discovery remains timeless in sales

Publisher timestamps

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.