Zhenya Loginov on Enterprise Sales, Product-Led Growth and Hiring

Zhenya Loginov studied programming and competed in programming contests, but entered business through consulting and finance. After starting and closing an e-commerce company, he worked at eBay, Dropbox and Segment before joining Miro.

His retrospective lesson from Dropbox is that a company whose market includes large enterprises must decide how to compete there. He believes Dropbox had an opportunity to become an enterprise platform but lost ground to other companies; that is his interpretation, not a comprehensive market finding.

Stebbings cautions that startups may underestimate the size of the small-business market and enter enterprise too soon. Loginov says the decision depends on competition and available time: if competitors may occupy the enterprise segment, a company must plan early, because building that motion can take years.

For a resource-constrained early company, he would generally establish product-led growth first if the market permits it. He believes a combination of product-led adoption and enterprise selling can be powerful later, while acknowledging that doing both early requires investment.

An early large customer can become a valuable reference and teach a startup about enterprise requirements. But Loginov warns against taking the deal if the custom work would divert engineering and product resources from the core roadmap; attractive revenue is not free of opportunity cost.

He attributes Dropbox's enterprise difficulties partly to insufficient company-wide commitment, not simply the quality of its sales leaders. In his view, leadership, product, engineering and marketing all need to support the enterprise strategy; this is a former employee's account.

At Segment, Loginov began in customer success and was asked to run sales after roughly a month. He recalls telling the CEO that more experienced sales leaders existed, and learning the role through a series of opportunities to prove himself.

That experience changed his view of sales from relationship building and product knowledge to a deeper discipline with many skills. The more he learned about the work, he says, the more he respected the people who do it well.

Loginov describes a sales playbook at three levels. The customer level addresses the buyer's problem and solution over a meeting or deal cycle; the team level covers hiring, training, coverage and leadership over roughly six to twelve months.

The market level concerns the longer-term plan: moving between customer segments, reaching different decision-makers, expanding internationally and responding to larger competitors. He uses roughly five years or more as an illustrative horizon.

Stebbings believes founders should create the first playbook. Loginov disagrees: founders must connect sales to the company's vision and remain involved, but he favors a sales professional leading the process and having ownership of what the team will execute.

He would generally hire a head of sales rather than only junior reps once the company has some initial product-market fit and customer evidence. Before that, he says, sales hires will not discover product-market fit for the founder; a junior rep also needs substantial founder support.

In his view, starting enterprise too late can leave a market open to competitors, while starting too early can prevent a company from establishing a product-led engine. The right sequence depends on the business, and he acknowledges some markets are best served by sales-led models.

A further risk is misaligned incentives between self-service and high-touch teams. If each owns only its own revenue, sellers might pursue small customers who would otherwise grow through self-service, causing internal conflict and unnecessary expense.

At Miro, Loginov says he is responsible for overall revenue, while the self-service team sits within product. He argues that shared outcomes reduce his incentive to favor one channel at the customer's expense; this is his description of the arrangement in 2022.

He says Miro also has an enterprise growth product team within the self-service organization to help larger customers mature and expand. His stated goal is to connect the product-led and enterprise motions, not treat one as merely a small-customer channel.

For leadership hiring, Loginov often looks for someone who knows about 70% of a role and is motivated to learn the remainder. He stresses that the hiring manager must first identify the experiences that cannot be missing; the percentages describe his heuristic, not a measured rule.

A founder unfamiliar with a role should learn it before opening the search. Loginov suggests speaking with experienced leaders, reading and continuing to study unfamiliar disciplines, because hiring a specialist does not eliminate a founder's responsibility to understand the work.

His process begins with three to five concrete, non-negotiable criteria. He screens résumés against what they can actually show, such as managing a particular scale, working in an international business or selling large enterprise contracts, depending on the role.

The hiring manager then spends four to five hours in structured conversations with promising candidates before a panel. He starts with areas likely to be most challenging and may stop earlier when a candidate does not meet the bar.

He wants a tailored panel of roughly three to five people who understand the job or will work closely with the hire. A board member or external adviser can fill a gap; he prefers interviewers who can disagree with him and explain their reasoning.

In a product-led company, he says a strong enterprise seller needs the same sales fundamentals as elsewhere plus respect for end-user experience and other functions. He does not believe there is a separate, fixed breed of product-led salesperson.

Loginov now uses case studies less often for leadership roles. He prefers asking about real experiences and following up on decisions, collaboration and reasoning, because performance on an artificial puzzle can depend heavily on prior exposure.

His own hiring mistakes include ignoring criteria he knew mattered and trusting a résumé and an enthusiastic panel without digging deeply enough. He recalls one candidate who lacked relevant international experience and another whose issues he believes more interviewing might have exposed.

Asked about compensation, he declines to offer a general answer because he does not believe he has a useful insight to add. Instead the conversation moves to onboarding a first head of sales.

He tries to free a new leader's first month for learning: understanding the product, meeting colleagues and observing customer calls. He encourages early relationships with engineering and product leaders, including people the hire may need to work with later.

Alongside that foundation, he wants the new leader to deliver one small, useful project, such as helping the existing sales team or closing a deal. An early contribution can build credibility and make later, larger changes easier.

Stebbings asks whether the CEO should make introductions and suggest an early project or leave the new hire to figure everything out. Loginov says onboarding is a shared responsibility: after the interview, the hiring manager should actively help the person succeed.

He sees no delivered value or customer contact by months two or three as a warning sign. He also asks existing teammates whether the leader is helping them; their concerns deserve investigation rather than an automatic conclusion that the person must leave.

He recalls a hire who initially met resistance but became well regarded after the leader and team addressed their relationship. If concerns persist, he favors direct, caring feedback that explains both the issue and the consequences of failing to improve.

Deal reviews, in his view, are primarily a learning clinic for the whole sales team. At Segment he recalls weekly reviews; a detailed discussion of one deal might take an hour and could concern an active opportunity rather than a closed sale.

The senior sales leader should establish the format, while the person running the deal supplies the details and leads the discussion. A review fails when it feels like a personal trial and makes a seller defensive; it should help the individual and others improve.

The CRO and head of sales can be one role or separate roles depending on the company. At Miro, Loginov says his remit also includes customer success, operations and other functions, so he works with a head of sales who brings complementary sales experience.

He describes his contribution as structure, process and strategy, while the sales leader manages large deals, the broader sales organization and hiring profiles. He deliberately sought someone strong in areas where he felt less experienced.

To retain agility, Loginov favors delegating authority to local and functional leaders. He wants a large organization to operate more like multiple small teams, with enough autonomy for leaders in markets such as Japan or France to move quickly.

Processes should be as light as possible and have buy-in from the teams closest to customers. If a team does not support a proposed process, the leader must either earn that support or change the process rather than imposing bureaucracy for its own sake.

Customer discovery remains essential in sales, he says. He also observes that closing deals through old-style social settings such as golf may be less common, though he recalls closing one on a bike ride; this is an observation rather than a quantified trend.

He sees a challenge when a team grows beyond roughly 150 people and a leader can no longer know everyone personally. He invokes that number as an operating heuristic, not a proven threshold for every organization.

International expansion needs support across legal, finance, operations and product, including local entities, contracts and localization. Based on his experience, he favors starting earlier than Dropbox did, but the revenue levels he mentions are personal rules of thumb rather than universal triggers.

Hiring regional leaders far from headquarters deserves particular care, he says: problems can take longer to notice and replacing someone at a distance is costly. He has become more cautious after difficult transitions in previous roles.

His advice to founders is to invest time learning how sales works instead of delegating it entirely. For a new revenue leader, he recommends a plan for personal learning over the next few years as the company itself changes.

He would like more movement between sales and other functions to build empathy in both directions. He also says remote work can make team camaraderie harder to sustain, even when experienced salespeople can operate effectively from a distance.

Loginov admires unconventional go-to-market approaches at companies such as Atlassian and Coda and sees potential in product-led companies including Canva and Notion. These are his assessments in 2022; Stebbings thanks him and closes the interview.