AJ Tennant on Enterprise Sales, Customer Success and Hiring

Glean vice president of sales and success AJ Tennant speaks with Harry Stebbings about enterprise sales, customer success and hiring. His examples and claims about Glean reflect his position at the company.

Tennant believes sales skills can be learned rather than being reserved for naturally outgoing people. He has seen quieter colleagues succeed through effort and willingness to learn.

The hardest skill for him was accepting rejection. Selling print advertisements to small businesses early in his career felt intrusive, and hearing repeated refusals was uncomfortable.

He sees junior representatives struggle to listen and adapt in live conversations. Rather than follow a rigid script after a prospect shows interest, strong sellers adjust to the person and situation.

For outbound selling, he favors research and a specific point of view over mass generic messages. Account executives should expect to do some of their own prospecting, even when marketing and sales-development teams provide support.

Tennant is wary of turning a sales playbook into unnecessary complexity. For him the fundamentals are a target customer, a good product and message, new meetings, conversion to opportunities and progress through the funnel.

Founders should stay closely involved in finding early customers and product-market fit, he says, citing leaders at Slack and Glean. As the organization matures, the CEO can support the team without personally deciding every message and sales tactic.

A young company cannot effectively pursue every segment at once. He suggests starting with a defined middle market, where more sales cycles can generate learning before expanding into the largest enterprises.

At Glean, he describes an early focus on technology companies with roughly 500 to several thousand employees, with annual contract values a little above $100,000. He estimates average sales cycles at roughly four to five months, shorter for some smaller accounts; these are his examples, not universal benchmarks.

His main Slack lesson was the need for productive tension between go-to-market and product teams. Sales wanted to support large customers while parts of engineering questioned whether the product could yet serve organizations with more than 5,000 users.

Bringing engineers and product leaders onto customer calls helped them hear the problems directly. Tennant also learned that, once a horizontal product has repeatable success, delaying the move upmarket can leave opportunities behind.

He says the trigger to move upmarket is repeatable customer value in the middle market plus successful experiments with larger accounts. A company should build on evidence that it can deliver value, rather than pursue enterprise deals solely because they are large.

Sales segmentation can move quickly, but security, permissions, legal review, pilots and deployment require work. At Slack he separated smaller and enterprise accounts; at Glean the team made a similar distinction and chose a few strategic large accounts.

T-Mobile became one such company-wide bet at Glean. Tennant says the team focused on proving success with a Fortune 100 customer before broadening the enterprise push. The experience is his account of one company’s approach.

Enterprise security discussions can consume many hours, he says. He recommends learning from the first difficult deals and phasing the move: give representatives one or two large targets while they continue selling to customers with clearer product-market fit.

Moving every seller to Fortune 50 or 100 accounts too early could leave the company without revenue for nine to twelve months. Existing business must sustain the team while the longer enterprise motion develops.

Tennant is open to a small initial contract with a very large customer if both sides agree on measurable success criteria and a route to expansion. He describes a paid test comparing call-resolution time that, in his account, led to a seven-figure contract.

He considers many AI budgets experimental because companies may be responding to board pressure before defining defensible return on investment. His goal is to translate interest in AI into specific business outcomes that can support renewal.

Stebbings suggests specializing sellers by vertical once a reference customer is established. Tennant prefers generalists until a larger scale, supplemented by industry-specific training, because maintaining coverage across verticals and regions requires substantial headcount.

Terms such as “generative AI” and “AI-enabled workforce” may attract attention, Tennant says, but customer examples and measurable value matter more. He warns that an AI project disconnected from business results may be vulnerable at renewal.

He says some large enterprises are willing to spend millions annually on AI initiatives and that Glean had a contract well above $5 million. Those are his contemporaneous claims about particular accounts, not a measure of the entire market.

Tennant argues that implementation, security and change management often lag the sales promise. Some projects can take months or require costly services; he says adoption and usage may disappoint when buyers assume deployment will be easy.

At Glean, he says account executives must have an approved deployment success plan to be paid on a deal. He owns both pre- and post-sales and wants the plan in place before the team assumes implementation will take care of itself.

He avoids a clean handoff in enterprise accounts: the account executive stays involved alongside the customer success manager because expansion depends on successful adoption. Customer success is measured on retention and active use, while the AE has an explicit upsell incentive.

He describes a healthcare account that grew from a $60,000 initial deal to more than $500,000 over nine months, crediting the AE, sales engineer and customer success manager. It is one company example, not a guaranteed expansion rate.

Customer-success staffing should reflect both current contract value and the customer’s potential size. A small first deal at a very large enterprise may warrant a more experienced manager if the future opportunity and deployment complexity justify it.

Tennant favors clear customer-success metrics and places particular weight on gross revenue retention because losing enterprise accounts can damage reputation. He reports Glean gross revenue retention of 97–98% at the time; the interview does not independently verify the figure.

He also tracks leading indicators: time from signature to launch and the share of paid seats actively using the product. He expects rapid deployment and sustained usage to support retention, though usage alone does not guarantee renewal.

He expects some experimental AI products to churn when they fail to show value, and says Glean has seen customers move from other tools. This is a vendor’s market observation and forecast, not an independently measured churn rate.

Customer-success managers can receive an upsell bonus, but he would not make it their primary measure. He describes occasional spot bonuses for large expansions and says the company could make the approach more systematic.

For sales compensation, he would add stronger accelerators for performance above quota. The aim is to reward exceptional results, including across account executives, sales development and customer success.

In hiring, Tennant uses a chronological interview: school, career decisions, achievements and reasons for each transition. He says the pattern can reveal motivations that a polished answer about one job might conceal.

He asks who candidates worked for, including difficult managers, and what those people would say in a reference. He also asks for examples of prior work, such as a deck or email, to see how candidates actually think and communicate.

Candidates then present to a panel about their experience, a challenge, a win and how they would prepare to approach an account. He cares less about polished slides than the quality of preparation and ability to read a room.

During the presentation he asks candidates to name and rank ten data points they would use to prioritize a book of 100 accounts. The surprise question tests creative problem solving and strategic thinking under pressure, skills he considers relevant to the job.

Stebbings questions whether the strongest graduates want sales careers. Tennant argues enterprise technology sales can attract thoughtful people because it combines learning about businesses with helping customers implement change. He says talent is not confined to elite universities.

He rejects the stereotype that the best salespeople are motivated only by commissions. In his experience they also want development, coaching and demanding problems; compensation still matters but is not the whole story.

He defends panel interviews because sellers routinely present to groups of stakeholders. Glean does not use a conventional take-home assignment, he says, but may ask candidates to share a suitable artifact showing work they have already done.

Before joining Glean, Tennant spoke to customers through existing relationships to understand their experience. He values similar curiosity in candidates, while the host notes that approaching a prospective employer’s customers requires care.

With hindsight, he wishes his own Glean interview had included a request to propose solutions to several company problems. He thinks such a discussion helps assess a senior leader’s thinking and can generate useful ideas for the team.

He estimates that poor enterprise sales hires can become apparent within about 90 days, and smaller-business hires sooner. He looks for whether people bring potential solutions to problems and can work constructively through disagreement.

He calls the latter “collaborative tension”: advocating a point of view directly without steamrolling colleagues. A culture of disagreement can be productive, he says, but only if people still want to work together.

His largest hiring mistake was moving too fast to fill a role and overlooking warning signs or references. He would rather take another few weeks to complete the process than make a rushed hire that later becomes difficult to unwind.

He once believed great representatives needed no enablement and would figure everything out. His experience at Slack and Glean changed his mind: founders and sales leaders who fail to invest in onboarding and training can hurt performance over time.

On discounting, he is more flexible early to win important deals, but recommends a tighter discount framework once revenue reaches roughly $10–20 million. He values a reference customer’s actual success and willingness to help others more than a logo alone.

For a new head of sales, his advice is to work directly on deals, learn the product, understand the people and assess the position. He uses those three Ps—product, people and position—as a simple career and operating framework.

To win T-Mobile at Slack, Tennant says he learned about the customer’s daily work by speaking with retail and support staff. He also sought a conversation with the CEO before a meeting; he offers the story as an example of proactive account research.

When goals are missed, he recommends returning to the mission and recognizing small wins. He distinguishes achievable goals that can be exceeded from stretch targets that may only be partly reached.

Tennant wants sales to be recognized as a path to senior leadership and hopes one day to become a CEO. He points to Wiz’s use of channel partners as an effective distribution strategy, while discussing his view of the challenges Slack faced in competing with Microsoft.

Tennant asks Stebbings about his own career. The host describes repeated skepticism as he moved from podcasting into investing and fund management, and the emotional difficulty of criticism as his public profile grew.

Stebbings says persistence and sustained work helped him keep the podcast going when its early audience was small. The two return to their opening theme: most skills improve with practice, even if exceptional performance can also involve innate advantages.