The Twenty Minute VCMartin Gontovnikas (Gonto): The Biggest Mistakes Startups Make When Scaling into Enterprises | E1115
CHAPTERS
- 0:00 – 0:44
Psychology-first growth: why enterprise scaling isn’t a switch
Gonto opens by arguing that psychology underpins marketing—even in developer-first products. He warns that treating “scaling to enterprise” like a clean flip from bottoms-up to top-down causes startups to lose their original users and eventually stall.
- •Psychology drives decisions, including in technical/dev audiences
- •Enterprise is not an on/off switch from bottoms-up motions
- •Forgetting the original user base is a common path to failure
- •Product-led companies should protect early user experience
- •First impressions are one-time and hard to recover from
- 0:44 – 1:45
Accidental entry into growth: engineering mindset applied to self-serve
Harry asks how Gonto got into growth. Gonto explains he joined Auth0 for developer advocacy, discovered self-serve drove revenue, and used an engineering approach to improve metrics—before even realizing it was ‘growth.’
- •Joined Auth0 aiming for developer advocacy
- •Self-serve signups were the main revenue driver
- •Promoted into leading self-service without a marketing background
- •Applied engineering/scientific thinking to improve numbers
- •Growth work often starts before teams label it ‘growth’
- 1:45 – 3:48
Two Auth0 lessons: emotional decisions + exponential growth requires big bets
Reflecting on seven years at Auth0, Gonto shares two core learnings: emotional/psychological storytelling can outperform data-heavy messaging, and true exponential growth usually comes from risky, high-conviction moves during hard moments.
- •Even developer marketing is driven by emotion and narrative coherence
- •Reducing data in emails and improving story increased conversions
- •Exponential growth companies experience ‘crazy events’ and problems
- •Auth0 bet heavily on signups/activation to avoid missing ARR goals
- •Large risks and focused bets can be existentially important
- 3:48 – 6:52
Building a culture of risk-taking: budgets, autonomy, and postmortems
Gonto explains why most people avoid risk and how leaders can make risk-taking safe. He emphasizes small autonomy budgets, not punishing well-designed failures, and systematic postmortems fueled by qualitative learning.
- •Bravery = being scared and doing it anyway
- •Set an experimentation budget (e.g., < $10k) with no-approval execution
- •Failure is acceptable if learning occurs; punish only repeated non-learning
- •Run postmortems and prioritize qualitative understanding
- •Maintain searchable learning repositories (even GPT-augmented)
- 6:52 – 8:05
What ‘growth’ really means: scientific method on KPIs, not data worship
Gonto reframes growth as applying the scientific method to business KPIs. Data helps validate, but it doesn’t generate the best ideas—creativity and deep customer understanding create the step-changes that matter, especially in B2B.
- •Growth = experimentation discipline applied to KPIs
- •Data rarely tells you what to do; it validates hypotheses
- •B2B constraints make traditional A/B testing slower and less definitive
- •Creativity + persona empathy produce bigger outcomes than micro-tweaks
- •Qualitative interviews are central to finding meaningful levers
- 8:05 – 10:07
A/B testing in B2B: use it for big swings and guardrails, not tiny lifts
Harry challenges the ‘data doesn’t tell you’ stance with A/B testing examples. Gonto clarifies that in B2B, tests are often underpowered and miss ‘800% ideas,’ so he uses A/B mainly for large conceptual shifts and to prevent regressions.
- •B2C can iterate instantly at scale; B2B sample sizes are small
- •Teams (not individuals) make B2B decisions, complicating interpretation
- •A/B is best for radically different bets that yield faster signals
- •Use A/B as a guardrail: ship improvements and ensure metrics don’t drop
- •Avoid getting trapped optimizing what’s testable vs what’s valuable
- 10:07 – 14:45
Budgeting and timeboxing bets: portfolio planning + qualitative gut checks
Gonto outlines a portfolio approach: many small bets to ‘buy time,’ a few medium bets, and an occasional big swing that can create step-function growth. He advises timeboxing and using qualitative feedback to judge momentum early.
- •Big swings often cost people-time more than cash spend
- •Plan a mix: multiple small bets, a couple medium bets, one big bet
- •Small wins keep targets on track while big bets mature
- •Timebox initiatives and use interviews to sense traction early
- •Example: outbound failed until research revealed ‘initiative timing’ mattered
- 14:45 – 15:51
How growth teams fit in org design: interspersed ideally, siloed in reality
Harry asks whether growth should be centralized. Gonto says it should be embedded everywhere, but as companies scale, product teams get consumed by enterprise checklists, support, and maintenance—so separate innovation/growth teams often become necessary.
- •Best-case: growth mindset distributed across all teams
- •Scaling introduces enterprise feature requests, support burdens, and tech debt
- •Core product teams lose space for innovation over time
- •Separate growth/innovation teams become a practical workaround
- •Large companies that still win protect small teams to keep betting (Amazon example)
- 15:51 – 18:41
When to hire growth: never before PMF; founders must own the search
Gonto argues strongly against hiring growth pre–product-market fit. He believes finding PMF is the founder’s job, and even PLG companies should start closed with design partners to nail onboarding before opening the floodgates.
- •Don’t hire growth before PMF; it won’t fix a missing fit
- •Founder accountability: if founders can’t find PMF, the company won’t win
- •PLG should start closed with 6–8 design partners
- •Use early partners to refine onboarding and the first-time experience
- •Avoid burning first impressions by launching broadly too early
- 18:41 – 21:20
First impressions in PLG: onboarding pitfalls and segment-aware product tours
They dig into what makes a bad first impression—blank dashboards, pushing advanced features too early, and forcing the wrong use case. Gonto describes testing two onboarding styles and tailoring tours by user seniority to avoid alienating experts or novices.
- •Blank states and missing guided data are instant turn-offs
- •Don’t force advanced/paid-heavy features before users understand basics
- •Wrong use-case steering causes early churn
- •Test onboarding styles: step-by-step vs conceptual ‘big boxes’ overview
- •Segment onboarding by seniority/persona (junior wants guidance; senior wants autonomy)
- 21:20 – 22:41
Horizontal products: templates as personalization + intent signal
Harry asks about tools like Notion/Airtable used by many personas. Gonto proposes templates and use-case content as both a starting experience and a way for users to self-identify, enabling personalization based on what they viewed pre-signup.
- •Build robust templates for diverse use cases
- •Use content/templates to teach, not just to populate the workspace
- •Infer persona from pre-signup browsing behavior (templates/blog posts)
- •Personalize product ordering/options based on inferred use case
- •Templates double as an intent/segmentation data engine
- 22:41 – 25:35
Mastering bottoms-up: help when users are stuck, then route to sales
Gonto explains that bottoms-up users want to be left alone until they’re blocked or ready. He shares behavioral signals to detect friction and describes ‘product advocates’—technical-ish helpers who unblock users and only then connect them to sales.
- •Bottoms-up users resist sales until they hit friction or value moments
- •Detect ‘blocked’ behavior via click patterns, doc hopping, and inactivity
- •Proactive help builds reciprocity and increases willingness to engage
- •Use technical product advocates instead of SDRs for developer audiences
- •Hire product advocates from tech support/bootcamp backgrounds for fit and cost
- 25:35 – 32:04
Packaging, retention, and anti-retention patterns: monetize without killing activation
They cover how much to give away, how to structure plans via feature clusters, and how to identify behaviors that destroy retention early. Gonto emphasizes retention as repeated experience of the core value prop and warns against hard paywalls that prevent users from feeling value.
- •Use clustering on feature usage to design plan tiers
- •Move 1–2 ‘missing’ features to the next tier to drive upgrades
- •Identify anti-retention patterns—features that cause immediate drop-off if used too early
- •Example: MFA implemented in week one hurt retention; later adoption improved it
- •Avoid hard paywalls; prefer trials + quota limits or read-only after trial
- 32:04 – 37:03
Enterprise/top-down done right: combine with bottoms-up and sell to human incentives
Gonto argues top-down should be layered onto existing bottoms-up signals, not built as a separate cold outbound silo. He details tactics like account-based outreach triggered by internal usage, bias-driven brand familiarity, champion enablement kits, and messaging that starts with user-specific benefits and ladders up to exec outcomes.
- •Trigger top-down outreach from bottoms-up adoption inside target accounts
- •Outbound to leaders using ‘someone at your company is using us’ social proof
- •Run awareness ads for exec personas to exploit availability bias
- •Arm champions with internal sell kits, references, and ROI materials
- •Message: start with specific user benefit, then translate to leadership outcomes; adjust for enterprise vs startup buyers
- 37:03 – 39:55
Enterprise demos and ‘do things that don’t scale’: internal demos + whiteboarding
They discuss how to win enterprise evaluations through demos that match the prospect’s language. Gonto recommends enabling champions to demo internally, and when direct demos are needed, bringing specialized roles (e.g., enterprise architects) to run whiteboarding sessions and strategy mapping around core use cases.
- •Enable champions with self-serve demo assets to sell internally
- •Demos win when you speak the prospect’s functional language
- •Use enterprise architects to add strategic credibility beyond AEs/SEs
- •Whiteboard sessions create differentiated value and trust
- •Organize enablement around 4–5 core use cases rather than industries
- 39:55 – 44:35
When (and why) to move into enterprise: signals, economics, and common scaling myths
Harry questions whether startups should sell enterprise at all, given SMB depth. Gonto says most PLG companies end up with most revenue from mid-market/enterprise, and the right time is when larger accounts organically sign up—while warning about the trap of enterprise-level cost bases paired with SMB-level revenue and ‘expansion will happen’ fantasies.
- •Most PLG businesses skew revenue to mid-market/enterprise over time
- •Timing signal: enterprise accounts begin signing up and showing intent
- •SMB requires low-cost acquisition and nailing a broad need at scale
- •Avoid high-touch enterprise costs without enterprise revenue
- •Expansion isn’t automatic—teams must actively drive internal rollout workshops and multi-champion growth
- 44:35 – 50:00
Biggest enterprise scaling mistake: checklist bloat that destroys developer love (New Relic case)
Gonto explains the core misunderstanding: enterprise selling shifts from experience to checklists, which tempts companies to bloat products for RFQs. He uses New Relic as a cautionary tale—winning enterprise deals by adding features but losing the developers who originally created pipeline momentum.
- •Enterprise procurement rewards ‘checkbox coverage,’ not delight
- •Building for RFQ checklists adds bloat and degrades usability
- •Developers stop adopting, killing the bottoms-up pipeline source
- •You must add enterprise requirements without sacrificing experience
- •Enterprise buying is driven by fear of getting fired vs desire for promotion
- 50:00 – 55:18
CTMO and org alignment: merging product + marketing to match promises with reality
Gonto proposes a Chief Technology Marketing Officer (CTMO) concept to better align product-led companies. His argument: in PLG, marketing makes the promise and the product must prove it, so the critical interface is product–marketing (especially onboarding) rather than sales–marketing.
- •CTMO = Chief Technology Marketing Officer to bridge product and marketing
- •PLG success depends on product proving the marketing promise
- •Co-own onboarding/activation between product and marketing with healthy conflict
- •Split growth focus: marketing growth drives activated signups; product growth drives retention/conversion
- •Biggest failure mode: marketing overpromises; product teams lose touch with users
- 55:18 – 1:01:55
Hiring great growth people: ‘hunger for glory,’ exercises, and diversity of viewpoints
They shift to hiring: what profile makes a strong first growth hire and how to assess them. Gonto prioritizes intrinsic drive, creativity, scrappiness, and persona empathy over logos, using abstract exercises to evaluate process and questioning, and hiring for complementary perspectives rather than clones.
- •Look for ‘hunger for glory’—deep intrinsic motivation to prove themselves
- •Traits: creative, persona-aligned, competitive, scrappy execution
- •Beware resume/logo bias; it often leads to poor hires
- •Use abstract case exercises; evaluate questions and reasoning more than final answer
- •Hire for weaknesses and diverse viewpoints—even someone you don’t naturally like if they’re sharp
- 1:01:55 – 1:11:01
Growth mistakes and the future: vanity metrics, AI-enabled ops, intent data, and creator sponsorship
Gonto shares painful lessons: spending heavily to drive signups that never activate and celebrating email open rates that actually hurt retention. He closes with a view that marketing ops/engineering and intent-based data will matter more with AI automation, and a nuanced tactic on YouTuber sponsorships—integrating the product organically rather than making it the video’s headline.
- •Paid acquisition can create vanity signups without activation or revenue impact
- •Always tie KPIs to bottom-line outcomes, not surface metrics
- •Email opens/clicks can rise while retention falls—test against downstream outcomes
- •AI will amplify the need for marketing ops/engineering and intent-based outbound
- •Creator sponsorship works better when the product is used naturally inside builds, not over-featured as the main topic
