Julian Teixeira on Hiring Sales Teams and Building a Repeatable Process

1Password chief revenue officer Julian Teixeira joins Harry Stebbings to discuss early sales hires, quotas, prospecting and managing a growing team. His examples and metrics come from his experience at 1Password and Lightspeed, and reflect his role selling 1Password's products. The interview does not independently verify company figures or show that the same sales practices work everywhere.

Teixeira began in marketing and says good marketing provides guardrails for repeatable sales by aligning the external perception of a brand with what salespeople present. At Lightspeed, he learned that connecting personally with employees and understanding their motivations matters during rapid change, when a process established only months earlier may already be outdated.

He recalls feeling impostor syndrome while taking responsibility for sales and go-to-market before Lightspeed's IPO. He says comparing himself with people who have achieved more pushes him to improve. This is his personal experience, not a general claim that insecurity benefits every leader.

Teixeira dislikes a sales playbook that becomes a document nobody uses. Instead he describes breaking down the anatomy of a win: the repeatable steps that improve the odds of closing a deal. The document alone is not enough; hiring curious, disciplined people and developing their selling skills and industry knowledge is essential.

He strongly favors founders doing early sales themselves so they hear customers' reactions firsthand, even though a capable first go-to-market hire can also help build the process. For that first hire he looks for humility, patience, curiosity and motivation to build, rather than relying on an impressive résumé from a larger company.

Asked whether to hire two salespeople at once, he says yes: competition can motivate them, and two observations can help distinguish individual difficulties from systemic problems. It remains a very small sample, and he presents the approach as a practical heuristic rather than a reliable experiment.

At both Lightspeed and 1Password, he says, the early sales team initially worked toward a common company goal while management learned what individual capacity looked like. Individual performance was still measured, with additional incentives. He says this can work for a few months, sometimes six or seven, before individual targets become necessary; it may not work everywhere.

He recommends simple compensation plans that allow representatives to understand what they will earn, and changing incentives when company priorities change. If the business needs multi-product or multi-year deals, he says, compensation should reinforce that goal rather than remain disconnected from it.

Teixeira says plans are typically designed so roughly 70% of representatives can achieve their targets, with strong rewards for exceeding them. He recalls stretch targets 20% to 30% above his estimate producing around 10% more than the initially realistic goal, even when the stretch target was missed. These are his experience and planning assumptions, not controlled evidence of causation.

He argues technology sales have become harder after years in which buyers were more willing to spend. Stebbings questions the quality of many salespeople and leaders, and Teixeira agrees that rapid scaling and easy conditions could produce mediocre performance. Their assessment is opinion, not a measured judgment of the profession.

Asked whether to fire everyone who misses a target, Teixeira distinguishes skills from willingness to improve. Someone adapting to a new product or motion may need coaching; he is less patient with people who blame everything else and do not improve. He also says laid-off workers should be evaluated individually, while Stebbings notes that a whole product division can close for reasons unrelated to an individual's performance.

Teixeira says he looks for signs of a poor fit within the first three months, using behavior and leading indicators alongside ramp targets. The first two weeks should cover the product, systems and team, but he also looks for questions and active curiosity. After training, he expects new representatives to begin developing pipeline and join customer conversations, initially with support.

Listening to strong colleagues' calls, seeking coaching and additional training are signs of engagement in his view. He cites approximately 29% to 30% 'non-regretted' attrition for the year, and says the company is putting more emphasis on screening during hiring. The interview does not define the population, exact period or classification of that attrition, so it should not be treated as an overall turnover rate.

He expects account executives to research companies and individuals that fit the ideal customer profile and conduct their own outreach, even before receiving paid leads. Personal relevance matters more than sending the same template to a thousand people. He believes the experience strengthens the skills needed to capture interest in an inbound discovery call as well.

Stebbings asks whether outbound prospecting is viable amid a flood of AI-generated messages. Teixeira says it is harder but still viable: AI may speed up research, but he does not expect it simply to run on autopilot and fill a pipeline. Business development representatives should generate most pipeline in his model, while account executives continue practicing outreach.

1Password initially separated hunters, who pursue new business, from farmers, who expand existing accounts. Teixeira says the company already had 50,000 business customers when his team started, but penetration within those businesses was below 2%. He attributes that to enthusiastic users bringing the product to work; the interview does not fully define the penetration denominator or reporting period.

He says 1Password is moving toward a hybrid sales model as its product portfolio expands and customers land and expand. In his account, pushing for too much in an initial sale was costing new deals. Hunters and farmers have different strengths, so he argues the structure should follow how customers buy rather than a universal rule.

He favors compensating customer success on net dollar retention, with overlap between its incentives and those of account executives. In his description, customer success acts as an adviser and coordinator while account executives focus on revenue. He notes that assigning all work to one person reduces the number of accounts that person can cover.

Teixeira says 1Password had not yet specialized sales teams by industry because the company saw little difference across verticals in win rates, contract values and time to close. It instead organized by customer segment and territory, while expecting industry specialization later. These are management observations without detailed comparative data.

He describes enterprise deals as typically six figures and says the company had just landed its first seven-figure customer. Midmarket values vary around $50,000 to $100,000 or into six figures, while small-business deals range from a few thousand to $25,000 or $30,000. These are his approximate segment figures, not audited averages; the interview does not define the precise contract-value period for every example.

For smaller deals, he says a full outbound, account-executive and customer-success motion is often uneconomic. 1Password concentrates outbound spending on midmarket and enterprise, while small-business sales rely on high-volume inbound demand and lower-touch onboarding. His claim that most of the small-business team pays for itself four times over is a company measure without a full calculation.

Stebbings asks why the company does not simply multiply a team with that payback. Teixeira says inbound demand and unit economics can impose a ceiling and describes exploring managed-service providers and distributors for smaller customers. He believes companies should build an upmarket motion early, though the optimal mix depends on their economics.

He reports a 54% outbound and 46% inbound split on converted deals, compared with approximately 99% inbound a year earlier. Enterprise deals average roughly two quarters to close, he says, while outbound pipeline can take three to four quarters. His approximate comparisons describe his business at the time, not a market benchmark.

Teixeira says outbound deals typically close at half the rate of inbound deals but at twice the value. He argues outbound allows the seller to help define the purchase before the customer settles on a specific solution. The interview does not specify matched cohorts or full calculation methods for these comparisons.

Stebbings questions whether sellers should spend time educating customers who do not already believe they have a problem. Teixeira agrees it is an uphill battle if the buyer does not recognize the problem, but recommends leading with the customer's existing priorities rather than a product pitch. In security, he tries to connect credential management to concerns such as employee safety and reducing threats.

For pipeline reviews, Teixeira recommends weekly inspection in every segment. Small-business teams can compare daily pacing and aggregate trends, while large enterprise deals merit more account-level scrutiny and weekly milestones, even when a sale takes months. He wants teams to examine what must happen to win and what progress occurred that week.

He describes a cadence in which account executives review their pipelines, frontline managers challenge assumptions and leaders aggregate forecasts for a meeting with sales, marketing and finance. Stebbings asks whether those layers waste time and whether representatives could report directly. Teixeira argues that scale makes individual presentations unwieldy and that managers can challenge optimistic impressions.

He says 1Password uses Momentum for call notes, follow-ups, sentiment and suggested improvements, and discusses Gong as a coaching tool. He would prefer insights delivered through tools employees already use rather than yet another interface. These descriptions are his experience and preferences, not independently tested assessments of the products.

For a sales stack he recommends a CRM, outreach and call-coaching tools, and sales enablement that surfaces relevant material at the right deal stage. He says he implemented Salesforce, Outreach and Gong at 1Password. His suggested stack reflects that company's needs and is not a requirement for every sales team.

When results disappoint, he recommends recognizing what has gone well while being honest about failures, addressing the problem rather than attacking the person. He says missed procurement steps and undiscovered budget holders frequently cause deals to slip. A seller should help an internal champion prepare answers to the CFO's questions, not simply supply technical jargon.

Teixeira says buyers are scrutinizing software costs more closely and that CFOs increasingly want to understand spending. Even at 1Password, which he describes as growing and profitable, teams regularly rationalize tools and check for overlap. He regrets not pushing harder for product and engineering investment when the company had cash, but acknowledges that the outcome of that alternative is unknowable.

He leads a remote sales team but values gathering people in person, including annual meetings and smaller groups at month- or quarter-end. He misses the informal coaching and signals available when colleagues share a room, and says remote leadership requires more deliberate effort to understand how people are doing.

His advice to a sales leader taking a new role is to choose a company whose principal challenge they want to solve and where they believe they can help realize its potential. He expects artificial end-of-month discount pressure to become less effective as buyers learn the tactic.

Teixeira praises Wiz's rapid growth and, especially, the hiring and change management needed to reach what he describes as $500 million in revenue. The interview does not specify the metric, period or independently verify the figure. His broader point is that executing familiar expansion steps on a compressed timeline is difficult.