Lenny's Podcast
Lenny's Podcast

What world-class GTM looks like in 2026 | Jeanne DeWitt Grosser (Vercel, Stripe, Google)

Jeanne DeWitt Grosser built world-class GTM teams at Stripe, Google, and, most recently, Vercel, where she serves as COO and oversees marketing, sales, customer success, revenue operations, and field engineering. She transformed Stripe’s early sales organization from the ground up and advises founde

Featured Speakers

Lenny Rachitsky HostJean Grosser Guest

Topics Discussed

Episode Summary

Executive Summary: Jean Grosser argues that go-to-market is now a full customer lifecycle, not just sales, and AI is collapsing many GTM tasks into agent-driven workflows. She shows how segmentation, pricing, and customer experience should be treated like product decisions, and how GTM engineers can automate repetitive work, increase seller leverage, and surface insights from customer data faster than humans alone.

Main Topics: What go-to-market really includes (Priority: 5/5): GTM spans every function that touches customers or revenue: marketing, sales, sales engineering, customer success, support, and partnerships. Jean argues these functions should operate as one integrated lifecycle rather than siloed teams. AI and the rise of the GTM engineer (Priority: 5/5): A new technical role is emerging to build agents and automate GTM workflows. Jean explains how her team uses GTM engineers to encode human sales motions into AI-powered systems for inbound, outbound, research, and follow-up. GTM as a product and customer experience (Priority: 5/5): Jean frames sales motion as a designed experience, similar to product design. The buying journey should feel collaborative, personalized, and differentiated, not transactional or generic. Segmentation and targeting strategy (Priority: 4/5): She explains segmentation as a way to predict buying behavior using attributes like company size, growth, business model, traffic, and workload type. Good segmentation informs both product strategy and GTM execution. Pricing, PLG, and sales motion evolution (Priority: 4/5): Jean argues pricing must align with value and customer segment, PLG has a ceiling, and most companies eventually need a sales motion. She also says comp plans need flexibility to keep up with shifting product strategy. How GTM should work with product and engineering (Priority: 4/5): The best GTM orgs provide product feedback, speak the language of engineers, and act like a research and commercialization arm of the company. Sales should feel like a partner to product, not an external force. Tools, build-vs-buy, and internal agent platforms (Priority: 4/5): Jean highlights Gong plus internal agents like deal bots and lead bots. She argues the workflow-specific context inside companies often makes it worth building custom agents rather than relying only on off-the-shelf tools.

Key Arguments: GTM is broader than sales; it includes any function that touches customers or revenue, and these functions should be orchestrated as a single lifecycle. AI is making GTM more consultative and embedded, because customers need help figuring out what to change, not just what to buy. The GTM engineer is emerging as a key role because agents can automate repetitive tasks and free sellers to spend more time with customers. Sales processes should be treated like products: map the journey, design every touchpoint, and optimize for a differentiated experience. Segmentation should be based on the attributes that actually correlate with value and buying behavior, not just company size. Customers usually buy to avoid pain or reduce risk, so messaging should emphasize competitive advantage and de-risking rather than only upside. PLG is still valuable, but it usually reaches a ceiling, so companies must add sales motion to sustain growth. The best sales teams feel like product managers to engineers because they have deep product knowledge and can translate customer feedback into roadmap signal. Pricing should be treated like a product decision, with value, cost, and packaging aligned to customer segments and willingness to pay. Building custom agents can be faster and cheaper than expected, and the value is often in encoding your company’s unique workflow and context.

Data Points: Customer buying motivation: 80% - Jean cites a rule of thumb that most customers buy to avoid pain or reduce risk rather than to increase upside. Time sellers spend with customers: 30% to 40% - Jean says sales reps historically spend only a minority of their time in front of customers. Target time with customers after AI: 70% - She says agents should eventually let sellers spend most of their time with humans instead of on rote work. SDRs before automation at Stripe: 4 - Stripe’s lean operating model meant Jean had only four SDRs where other companies might have had 30. Typical SDR team comparison: 30 SDRs - Jean contrasts Stripe’s lean setup with a typical larger-company SDR pod. Time to build lead agent: 6 weeks - At Vercel, one GTM engineer built the lead agent in about six weeks. Time spent by builder on lead agent: 25% to 30% - Jean says the GTM engineer spent roughly a quarter to a third of their time on the lead agent project. Time to build deal bot: 2 days - She says the lost-opportunity review bot was prototyped in about 40 hours. Annual cost of lead agent: about $1,000 - Jean estimates the lead agent costs around one thousand dollars per year to run on Vercel. SDR headcount replaced in inbound workflow: 10 to 1 - Jean describes moving from 10 SDRs doing inbound qualification to one human QAing the agent. Cost reduction: 90%+ - She compares the roughly $1M salary cost of a 10-person SDR team to a ~$1,000 agent cost. Growth-driven segment priority: 200% vs 8% - At Stripe, she used growth rate as a segmentation axis and prioritized fast-growing companies over slower-growing ones. Website traffic example: OpenAI is top 25 traffic site - Jean uses OpenAI to show how traffic can move a company into a higher-priority segment even if headcount is mid-market. Buying complexity threshold: about 10 people - She suggests around 10 employees is a reasonable scale to have enough process to begin GTM engineering. Revenue adoption benchmark: around $1M ARR - Jean agrees that many founders should wait until roughly this scale before hiring their first salesperson.

Pivotal Quotes: "If you are an account executive in my org and I put you in front of 10 engineers at our company, it should take them 10 minutes to figure out you aren’t a product manager." — Jean Grosser: Explaining why elite GTM teams need deep product fluency and credibility with engineering "We buy a lot of things because of how we feel about them." — Jean Grosser: Describing why the buying experience itself can become a competitive differentiator "When the going gets tough, the tough get going." — Jean Grosser: Her life motto and mindset for handling difficult quarters and setbacks

Implications: GTM is becoming more technical, more data-driven, and more product-like. Teams that combine segmentation, AI agents, strong discovery, and customer-centered experiences will likely outpace those relying on generic sales motions.

🔓 Sign Up for Unlimited Episode Search

About Lenny's Podcast

Lenny Rachitsky interviews world-class product leaders and growth experts about building products and growing careers.

View all episodes from Lenny's Podcast