GTM 50 | The Next Buyer of Your Data Is Not a Person
Hi, it’s Rick Koleta. Welcome to GTM Vault, a breakdown of how high-growth companies design, test, and scale revenue architecture. Read inside OpenAI, Anthropic, Meta, and Google, and by 27,000+ operators across 150+ countries building GTM systems that compound.This episode in the Library: the written playbook, the stack and the full transcript, free and open. Open it at pro.gtmvault.co.The list was exported, the sequence was loaded, and the reps worked it for three weeks. By the time the last contact was touched, a third of the data was already wrong. That decay rate was tolerable when humans worked lists over weeks, because a rep sees the bounced email and flags it. It is fatal when agents work signals in seconds, because the agent does not know the data is wrong. It acts on it.The entire contact data industry was built for the tolerant version of that buyer: a person, in an interface, self-serving through a slick UI. Yoni Tserruya spent ten years winning that market. A few months ago he watched SDR and BDR agents go into production at customer accounts, doing certain work better than the humans they sit beside, and concluded the buyer of his data is about to stop being a person.This is not a data quality story. Quality was always the product. The hard part is that the customer consuming the data is losing the ability to notice when it is wrong, which changes what a data company has to be.Yoni Tserruya is the co-founder and CEO of Lusha, which he started as a side project in 2016 and bootstrapped for years before scaling it into one of the largest B2B contact data platforms in the market. Ten years in, he is rebuilding it as the layer AI agents query live: a verified provider in Clay’s ecosystem, waterfalls with Scale Stack, extensions inside Claude and ChatGPT, and a decision-makers API built for machine callers. He is explicit about the stakes: the agent is becoming the future persona of the data.In GTM 50, Yoni breaks down why the buyer of contact data is stopping being a person, what survives of a ten-year-old product when the interface stops mattering, how waterfalls reset vendor economics, what an agent needs from a data vendor that a human never did, the two-layer retrofit forcing a ten-year-old company into the AI era, and how Lusha’s own GTM went headless.This is not a conversation about data vendors. It is a conversation about which parts of your GTM system have to be true at the moment an agent acts.Inside this episodeThis episode maps what happens to the bottom layer of the GTM stack when the thing consuming it changes species.Yoni opens with the inflection. It was not a keynote, it was production: a few months ago, early-adopter customers started running SDR and BDR agents live, trusting them with work they used to give reps, and seeing results. The majority of the market is not there, but enough early adopters are that he treats the next one to two years as the window in which agents become the real persona of his data.We go deep on what breaks when the buyer is a machine. When a human worked the list, wrong data got caught: the rep knew it was wrong and flagged it. Put an agent on bad data and the damage is bigger and the detection is slower, because nothing in the loop knows to be suspicious. His conclusion runs against the commoditization story: inside a waterfall era, accuracy matters more, not less, and customers who need compliant, trusted data still pick their vendors carefully.We cover the rebuild. Lusha won its first decade on two things, data quality and a self-serve UX simple enough that any user could log in, start free, and buy alone. The second thing is now irrelevant. If customers consume the data through Clay, Claude, or their own agents, they may never see Lusha’s interface again, so the product is being rebuilt as API and MCP based, integrated everywhere, chosen by machines on quality rather than by users on feel. He calls it a different way of thinking about the whole business, and it is still in progress.We cover waterfall economics from the vendor’s side of the table. Waterfalls are the natural end state, one orchestrator stacking providers where customers used to buy three vendors and manage the mess themselves, and Yoni expects everyone to have one eventually. Lusha’s answer is to be agnostic and be everywhere: Clay, Claude, n8n, Make, Zapier. He is direct about the trade inside someone else’s waterfall: Lusha typically wins on quality and coverage, loses on price, and starts at forty-nine dollars a month, which he frames as quality any company can afford.We go into agent-to-agent selling. When a buyer agent meets a vendor agent, both arrive having read everything public, so the discovery call dies and the conversation goes straight to pricing, integrations, and the needs that are not on the open web. The spam-to-spam worry gets the same answer: detection improves in parallel with generation, phones already screen callers, and the thing that passes the filter is a relevant reason for the contact. Laser-focused targeting stops being best practice and becomes the only thing that works.We cover the retrofit, which he is honest about being harder than starting fresh. It runs on two layers, making the product AI-ready and making the organization AI-powered, and both are iterative and never finished. The mechanisms are concrete: every employee gets access to the AI tools they need, all-hands sessions share AI initiatives across divisions, and a team called Builders for Builders ships internal skills other teams adopt. The sharpest move is the constraint: where a team resists adoption, he shrinks the team while holding the workload constant, so AI becomes necessary rather than optional. There is no playbook and no expert to hire, because, as he puts it, eight months ago nobody was talking about Claude eating the world. The asset is a culture where trying and failing is cheap.We go into how Lusha runs Lusha. Everything dogfoods: lead scoring, enrichment, prioritization, outbound, and churn risk all run on Lusha’s own data. The stack is going headless. The AEs almost never open Salesforce anymore, working instead from a custom dashboard that aggregates Salesforce, Lusha, outreach, and back office data into one view that says who to target and why, with engagement and call transcripts summarized and written back automatically. He expects go-to-market to go headless at more companies for the least glamorous reason available: it is a simpler operation.We cover the pressure test. Operators are killing six-figure ZoomInfo contracts with Clay-native stacks, and Yoni’s answer is that Lusha was never the six-figure trap: it is usage-based, pay-as-you-go, bottom-up PLG. The position he claims against Apollo, Clay, and ZoomInfo simultaneously is the context layer feeding every agent in the market, including for SMBs. The LLM absorption question gets his most specific answer: a model can find five or ten contacts on the open web, it cannot return five thousand sorted, trusted results, because that requires a database designed for GTM. Claude and ChatGPT extensions already route those queries to Lusha. Compliance, he argues, is both moat and tax, and more moat, because very few companies can serve data compliantly at all.We close on 2028 and the rapid-fire section. Reps today spend twenty to thirty percent of their time with customers; two years out he expects fifty to sixty, with agents absorbing the research, sequencing, and admin, quotas rising as manual work falls. Rapid fire lands API adoption as the underrated metric, transcripts and call recordings as the most overrated capability in revenue AI, company data as the next commodity, start small and iterate fast as the habit, and one sentence completed without hesitation: in three years the static lead list is irrelevant.Watch or listen now across YouTube, Apple Podcasts, and SpotifyDiscussed in this episode(0:00) Cold Open: A Third of Your List Is Already Wrong(2:58) The Mom… This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.gtmvault.co/subscribe
