Martin Gontovnikas (Gonto): The Biggest Mistakes Startups Make When Scaling into Enterprises
- Aisha Washington
- 1 day ago
- 7 min read
Moving from self-service adoption to enterprise sales is rarely a simple change of customer segment. It affects product design, onboarding, pricing, marketing, sales, compliance, and even the way a company decides which promises it can safely make. In this episode of 20VC, host Harry Stebbings speaks with Martin Gontovnikas—widely known as Gonto—about the mistakes that appear during that transition.
Drawing on seven years at Auth0 and his experience applying engineering ideas to growth, Gonto argues that successful expansion requires more than adding an enterprise plan. Startups must preserve the experience that attracted their original users while building the capabilities, buying confidence, and organizational discipline larger customers expect.
Growth Begins with Psychology, Not a Dashboard
Gonto entered growth unexpectedly after being promoted to lead Auth0’s self-service business. Without a conventional marketing background, he approached the job like an engineer: define a problem, form a hypothesis, test an intervention, and study the result.
That analytical foundation mattered, but it did not make growth purely quantitative. Gonto emphasizes that branding, customer psychology, and first impressions remain crucial even when the audience consists of developers. Data can reveal where behavior changes, but it cannot automatically explain why people behave that way or produce the creative idea that changes the trajectory.
His definition of growth is therefore closer to applying the scientific method to a business KPI. Teams begin with a meaningful outcome, gather qualitative and quantitative evidence, propose an experience that might improve it, and test that proposal. The best insights often come from speaking directly with users before examining another dashboard.
This distinction also explains why conventional A/B testing has limits in business-to-business products. Consumer services may have enough traffic to identify small statistical differences quickly. A B2B startup often has fewer users, longer evaluation cycles, and more varied accounts. Experiments can still confirm that a change did not damage performance, but substantial gains may require a larger product or positioning bet.
Make Risk-Taking a Managed Practice
Exponential growth, in Gonto’s account, does not emerge from a perfectly orderly sequence of safe decisions. Significant outcomes generally involve uncertainty, operational problems, and experiments that may fail. Courage is not the absence of fear; it is a willingness to proceed after recognizing the risk.
Leaders can make this behavior practical by giving teams explicit room to experiment. That means allocating both time and people—not merely a discretionary cash budget—and accepting the opportunity cost. A major onboarding redesign, for example, may prevent the same engineers and designers from shipping other requested features.
Gonto suggests treating initiatives as a portfolio of differently sized bets. Small experiments might adjust a message or interface element. Medium bets could replace a page or change part of the activation journey. Large bets might rebuild onboarding or introduce a new product motion. Teams can continue running smaller tests while waiting for a more ambitious initiative to produce measurable results.
Failure should lead to a postmortem rather than punishment. A useful review records the original hypothesis, what happened, what interviews or behavioral evidence revealed, and which assumptions proved wrong. Those findings need to remain accessible so another team does not unknowingly repeat the same experiment.
Time limits are equally important. An experiment without a decision date can quietly become a permanent project. Defining the evaluation period in advance forces the team to decide whether to expand, modify, or stop the work.
Founders Must Find the Initial Product-Market Fit
Gonto cautions against hiring a growth leader to solve an unresolved product-market-fit problem. Before a repeatable growth system can amplify demand, founders must determine who urgently needs the product and why.
He recommends beginning with a small set of design partners—roughly six to eight customers—who can expose missing capabilities, confusing workflows, and differences between the founder’s assumptions and actual use. Growth professionals become more effective once there is enough reliable customer and behavioral information to guide their work.
A growth mindset, however, can exist before a formal team does. Founders can monitor activation and retention, interview users, maintain growth dashboards, and pair analytically minded employees with colleagues who deeply understand the target audience. When the company eventually hires specialists, they inherit a learning system rather than a vague instruction to “make the numbers go up.”
Product-Led Growth Depends on the First Experience
For a product-led company, onboarding is not a decorative tutorial. It is the moment when a user decides whether the product seems relevant, understandable, and worth returning to.
One avoidable mistake is placing a new user in an empty dashboard and expecting imagination to do the rest. Sample data, templates, and guided starting points can reveal value before the customer has completed a complex setup. Advanced functions should appear gradually, after users understand the core workflow.
Gonto also rejects a universal product tour. A junior developer may appreciate a detailed point-and-click walkthrough, while a senior practitioner may prefer a short explanation and immediate access to the product. Onboarding can adapt to role, experience, company profile, or stated use case.
This is particularly important for horizontal products that serve many jobs. A template library does more than accelerate setup: the template a user chooses provides information about intent. Combined with prior behavior, that signal can shape subsequent recommendations and reveal which capabilities are likely to matter.
Retention, in this framework, means repeatedly experiencing the product’s central value. A feature may appear sophisticated yet harm retention if it introduces complexity before the user needs it. Gonto also favors letting prospects experience valuable functionality before imposing a hard paywall. Once users understand what a capability does for them, an upgrade request—or the later removal of premium access—has far more context.
Combine Bottom-Up Adoption with Top-Down Selling
Enterprise expansion works best when product-led adoption and sales reinforce one another. Bottom-up usage can create internal advocates, while top-down selling addresses procurement, security, compliance, budgets, and cross-company deployment.
The challenge is recognizing when a self-service user is ready for a sales conversation. Gonto points to behavioral evidence of friction: a person repeatedly explores a restricted area, reaches a limit, or appears unable to complete an intended action. These moments can indicate genuine demand more accurately than a generic lead score.
Startups should also help internal champions sell. A developer who loves the product still needs language, evidence, and presentation material to persuade a manager. Demo resources, use-case playbooks, and architecture guidance can raise that champion’s credibility. During formal sales conversations, involving specialists such as enterprise architects can make discussions more relevant to the buyer’s environment.
Enterprise messaging must account for organizational risk. Security, privacy, compliance, and analyst recognition may look like checklist items, but buyers often use them to defend a decision internally. The startup must address those concerns without allowing procurement requirements to erase the product’s original usability.
Enterprise Growth Requires Active Expansion
Product-led growth does not mean waiting indefinitely for adoption to spread by itself. A company with expensive acquisition and support requirements cannot sustain low revenue merely by hoping accounts will mature over time.
Once a customer has found value, the startup can actively identify adjacent teams and business units. That may involve asking the champion to invite colleagues, conducting interviews across the organization, or finding other use cases where the product solves a related problem. Enterprise expansion is deliberate account development, not passive observation.
The sales motion also changes with market size. Advertising and broad content campaigns may efficiently reach small businesses but prove insufficient for a narrow group of large accounts. High-touch events and highly tailored engagement can make sense when each prospective relationship has substantial value. A focused offering for a few important companies may produce results comparable to serving a much larger population of small customers.
Do Not Turn an Enterprise Plan into Product Bloat
One of the most dangerous misconceptions is that a startup can become enterprise-ready by flipping a switch. Larger customers require real investments in administration, permissions, security, privacy, compliance, deployment, and support.
At the same time, chasing every enterprise checklist can damage the experience that built the company. Gonto uses New Relic as a cautionary example, arguing that an increased enterprise focus contributed to product complexity and a weaker experience for new users. His broader point is not that enterprise features are unnecessary, but that adding them without protecting the core workflow can undermine future acquisition.
The correct balance is difficult: satisfy legitimate organizational requirements while keeping everyday tasks coherent. Enterprise buyers may approve the purchase, but users determine whether the product becomes embedded in the company.
Above all, Gonto identifies overpromising and underdelivering as the biggest scaling mistake. A startup eager to win a major contract may imply that unfinished capabilities are already dependable. The resulting expectation gap damages trust, strains product teams, and creates dissatisfied customers precisely when references and reputation matter most.
Align Marketing, Product, and Growth
Gonto advocates close alignment between what marketing promises and what the product actually delivers. He describes the CTMO concept as a way to connect marketing and product responsibility rather than allowing each function to optimize independently.
One practical structure divides growth work between acquisition and activation on one side, and retention and conversion on the other. Marketing and product can then share ownership of onboarding instead of treating it as exclusively belonging to one department.
Healthy disagreement is useful when it produces a more precise experience. In one example, marketing wanted to introduce a “talk to sales” option during onboarding, while product leaders feared disrupting developers. The compromise was targeted exposure: show the option to appropriate non-developer, senior, or large-company users instead of presenting it to everyone.
Metrics require the same cross-functional discipline. Open rates, clicks, and sign-ups are easy to celebrate, but they become vanity indicators when they do not lead to activation, retention, or revenue. Paid acquisition is wasteful if the users it attracts never experience the product’s value.
Hire for Resourcefulness and Different Perspectives
For growth roles, Gonto values creativity, customer understanding, competitiveness, and resourcefulness—a combination he characterizes as a hunger to achieve something meaningful. Prestigious résumés are less revealing than the way candidates investigate an unfamiliar problem.
Case studies and practical exercises can expose how applicants ask questions, form hypotheses, and work with incomplete information. The goal is not to reward a predetermined answer. It is to discover whether someone can produce an original, defensible approach.
Teams also benefit from genuine differences in perspective. Hiring people who think like the leader may reduce friction, but it narrows the available ideas. Complementary strengths improve the odds that the organization will notice customer needs, risks, and opportunities that one kind of thinker would miss.
Marketing itself is becoming more technical. Automation, data analysis, web research, and AI-assisted personalization give modern teams new leverage. Yet the underlying principle remains unchanged: tools should improve relevant business outcomes, not simply generate more activity that looks impressive on a dashboard.
