Post-webinar playbook · RevGenius × Lusha · June 2026
Four GTM operators walked through what’s actually working in their stack. This is the playbook
— each workflow written up to run, with a ready prompt you can open in Claude today.
5 KEY takeaways
Lucy Alexander · HubSpotLindsay Rothlisberger · ZapierDavide Grieco · ClayElad Uzan · Lusha
01. The teams pulling ahead aren’t running more AI.
They got their data clean enough to act on it, then removed manual steps, then automated. In that order.
02. Every panelist moved from volume KPIs to signal quality.
Meetings weighted by account fit (HubSpot). Time with customers (Zapier). Data-to-pipeline time (Lusha). Activity isn’t the metric anymore.
03. Lucy (HubSpot): data quality beats prompt sophistication.
The biggest CVR lifts came from better inputs — chat transcripts as an AI input drove +200% CVR. Expect three iterations before results turn positive.
04. Lindsay (Zapier): if it needs a new tab, it doesn’t ship.
Standalone AI apps got abandoned. The workflows that stuck were already embedded in the tools reps use every day.
05. Davide (Clay): don’t hand AI the creative decisions.
Every campaign that worked started with a human-designed message. AI scaled the distribution. Taste is what nobody can copy
Topic 1 — The KPIs that actually matter
What everyone is measuring now
Before they walked through workflows, each panelist named the one KPI their team runs against today — and what they stopped tracking to get there. The thread underneath: every operator moved away from volume metrics and toward signal quality. Activity isn’t the KPI anymore. Outcomes per unit of rep time are.
Lucy · HubSpot
Meetings booked,weighted
by account quality
Moved from raw volume to conversion quality. +45% YoY CVR across 1M+ emails. The top 30% of accounts drive 95% of revenue, surfaced by signal weighting — not by funnel position.
Lindsay · Zapier
Time with customers
Currently 50%. Target is 75%. Stopped measuring raw pipeline volume. The math behind the shift: $1.7M–$2.6M of recovered selling capacity per 100 reps annually.
Davide · Clay
Pipeline and revenue,
with a brand multiplier
Scaled back mass cold outbound. Not because it stopped working — the opportunity cost and brand drag outweighed the return.
Elad · Lusha
Contact-to-meeting rate
+ data-to-pipeline time
Stopped counting contacts. Started counting conversations. ICP got more fluid — semantic, not hard-coded geo and headcount.
Workflow 01
Lucy Alexander · Director of Agentic Prospecting, HubSpot
Turn inbound signals into personalized meetings — automatically
HubSpot stopped sending the same email to every inbound lead. Every conversion now triggers a workflow that pulls the prospect’s website, CRM history, and behavioral signals — then generates copy section by section before the rep touches it. The result: 10,000+ qualified meetings per quarter, +45% YoY CVR across more than a million emails.
The biggest unlock wasn’t the prompt. It was the inputs. Behavioral signals — recent page visits, and especially chat transcripts — drove the largest CVR lifts. Chat transcripts alone produced +200% CVR in one test. Personalized copy on its own wasn’t enough either; content recommendations had to be personalized alongside it, which doubled CVR again.
Tools in this workflow
Key learning
Data quality matters more than prompt sophistication. The biggest CVR lifts came from unstructured behavioral inputs — chat transcripts as an AI input produced +200% CVR in one test. Expect three or more prompt iterations before results turn positive.
— Lucy Alexander, Director of Agentic Prospecting · HubSpot
Lucy’s second workflow — worth knowing about
Across 800+ reps, HubSpot also runs an AI agent that ranks each rep’s book in a four-quadrant fit/intent model. Accounts re-rank dynamically as new signals fire, and accountability mechanisms attach to each quadrant. The system surfaces the top 30% of accounts that drive 95% of revenue — which is what makes the signal-weighted KPI above mean anything in practice.
Inbound lead enrolled
HubSpot Workflow triggers on conversion event — form fill, chat, demo request.
Context pulled automatically
Website scraper hits the company page. CRM surfaces job title, recent page visits, industry, company size, and the conversion event itself.
Copy generated in sections
LLM writes opening, pain point, and close as separate calls — tighter quality control than a single-pass prompt.
Email rendered and sent
Dynamic template populated. HubSpot Sequences delivers. No human review — quality governed upstream through prompt design and a style guide.
Rep picks up a warm lead
Rep sees a prospect who’s already opened a personalized email — not a cold name on a list.
Workflow 02
Lindsay Rothlisberger · Director of Revenue Operations, Zapier
Signal found → email drafted → CRM updated, without the rep touching a spreadsheet
Zapier treats GTM as infrastructure, not a stack of tools. When a buying signal fires, the workflow generates the outreach, drops a draft in the rep’s outbox, runs pre-call prep, and writes MEDDPIC notes back to the CRM — all before the rep opens their laptop.
The number Lindsay’s team runs against: time with customers. Currently 50%, targeting 75%. The math: ~5 hours per rep per week recovered, which works out to $1.7M–$2.6M of recovered selling capacity per 100 reps annually.
The architectural commitment underneath: centrally managed context, reusable skills, agents embedded in the tools reps already use. Not a new app. Not a new login. The signal triggers something that’s already where the rep is.
Tools in this workflow
Key learning
Standalone tools that needed a new login got abandoned. The workflows that stuck were already inside reps’ tools — signal fires, draft lands in the outbox, MEDDPIC writes back to CRM. No new tab. Context is the whole game: good context creates trust instantly, bad context destroys it faster than no outreach at all.
— Lindsay Rothlisberger, Director of Revenue Operations · Zapier
Buying signal fires
Job change, funding event, tech install, or intent signal detected via Lusha or the connected data layer.
Outreach draft generated
AI step in Zapier writes a signal-specific email referencing the trigger. Drops directly into the rep’s outbox as a draft — not a notification.
Pre-call prep delivered
Account brief, contact context, and signal summary sent to the rep before the scheduled call.
MEDDPIC notes written back
Post-call, AI writes structured MEDDPIC fields back to CRM — rep reviews and edits, doesn’t rebuild from scratch.
Rep spends time selling
Every manual step between signal and conversation has been removed from the rep’s day.
Workflow 03
Davide Grieco · Head of Growth, Clay
Don’t build workflows. Build campaigns. Then engineer the distribution.
Davide doesn’t think in workflows — he thinks in campaigns. Content is engineered, not generated. Distribution runs across five to six channels orchestrated by Clay. Sellers get tooling, built in Claude on top of Clay, to follow up at the right moment with context already loaded — instead of switching tabs to look things up.
The underlying bet: AI-generated content is saturating the market. The durable edge that’s left is taste — knowing what to say and to whom. Teams that delegate creative decisions to AI will get beaten by teams that use AI to scale what they already know works.
Davide’s growth motion has four legs running in parallel: content engineering with multi-channel distribution; PLG-to-SLG conversion paths driven by product signals; executive thought leadership with built-in monetization levers; and programmatic SEO automated against a human-designed framework.
Tools in this workflow
Key learning
Don’t defer creative decisions to AI. Every campaign that worked started with a human-designed message. AI scaled the distribution. The other shift: mass cold outbound got scaled back — not killed, but deprioritized against the opportunity cost and the brand cost of being one more cold email in a crowded inbox.
— Davide Grieco, Head of Growth · Clay
Campaign designed by a human
Content angle, audience definition, and core message set before any automation touches it.
Account list built with signals
Clay pulls target accounts filtered by fit signals — hiring surge, tech install, funding, or ICP criteria.
Multi-channel distribution
Campaign runs across 5–6 channels orchestrated through Clay — sequence, LinkedIn, content syndication, and internal seller alerts.
Seller tooling activated in Claude
Reps get signal-triggered prompts with context pre-loaded — not a notification, a ready action.
Pipeline and brand move together
Revenue motion and brand build run from the same campaign — not siloed by team or channel.
Workflow 04
Elad Uzan · VP of Product, Lusha
Signal spotted → sequence live →
rep contacts in hours, not days
Lusha customers were rebuilding their targeting inside every tool — exporting a list, re-importing it somewhere else, building sequences by hand on top of data they’d already sorted. The same work, three times.
Signal-to-Sequence connects the buying signal directly to the outreach sequence. When the signal fires, the right sequence is already there. The contact has been verified — title, email, direct dial — before the first email goes out. Time from signal to first contact dropped from days to hours.
The thing that’s easy to get wrong: AI wasn’t what made this work. Removing the manual step between data and action was. AI came after the process was clean. Layer AI on top of a broken workflow and you get the broken workflow, faster.
Tools in this workflow
Key learning
The teams moving fastest didn’t add AI first — they removed the manual step sitting between data and action. AI came after the process was clean. Get that backwards and you’ve automated a broken workflow.
— Elad Uzan, VP of Product · Lusha
Signal detected by Lusha
Job change, funding round, tech install, or intent signal fires on a target account.
Contact verified in one call
Lusha validates the right person at the account — title, email, direct dial — before any outreach goes out.
Sequence populated automatically
Signal routes to the pre-built sequence matching that trigger type. No manual enrollment, no list export, no re-targeting.
Rep reviews, not rebuilds
Rep gets a warm context card — signal, contact, draft first touch — and approves or edits. Not a blank page.
Outreach live within hours
What used to take a day of list work and manual enrollment happens the same morning as the signal.
Topic 3 — From the session
What didn’t work
Every panelist was asked to name a bet that quietly got shelved. The honest answers were the most useful part of the session.
Lucy Alexander · HubSpot
Overweighted prompt sophistication, underweighted data quality. Early prompt iterations all failed — it took three or more rounds before results turned positive. The biggest lift came from unstructured inputs like chat transcripts, but that insight came late.
The lesson: better inputs beat better prompts. If results aren’t moving, the question is what you’re feeding the model — not how cleverly you’re asking.
Lindsay Rothlisberger · Zapier
Built standalone AI apps outside of where people already work. The tools required a separate login and created silos instead of integration. Without managed context shared across the GTM, AI amplified fragmentation instead of reducing it.
The lesson: AI embedded in existing tools beats a new tool that does one thing well. If it needs a new tab, it probably doesn’t ship.
Davide Grieco · Clay
Two misfires. First: vibe-coding custom solutions for problems that were already solved — wasted engineering time and opportunity cost. Second: deferring campaign ideation and creative decisions to AI. Campaigns without a human point of view produced content that didn’t convert.
The lesson: AI can’t replace taste. Use it to scale what works, not to figure out what works.
Elad Uzan · Lusha
The black-box failure. The team built a ready-to-go list that landed in front of reps with no rationale attached — the logic was that reps wanted the work done for them. Reps rejected it. They didn’t want a black box. They wanted to understand why these people were in front of them, and they wanted to be the ones deciding what the machine was optimizing for. Nobody asked to train a model. Everyone wanted to say “these are the signals that matter to me.”
The lesson: technology has to adapt to how each team works, not the other way around. Do the heavy lifting, but leave the controls in the seller’s hands.
Topic 4 — Where the edge comes from
What stays, what fades
The forward-looking question Elad pressed on: in a market where everyone has access to the same tools and workflows, where does the edge actually come from?
Here to stay
Lucy
The IC career path. The deep specialist who owns a workflow end-to-end will be rewarded over the generalist manager. Expect more compensation flowing toward IC excellence and fewer people climbing the management ladder just because that’s the way up.
Lindsay
Shared context and reusable skills. GTM treated as infrastructure. Centrally managed context, reusable skills, agents embedded where the rep already works. The hard-to-build layer underneath stays.
Davide
AEO — AI Engine Optimization. AI as a buyer is coming. Teams need to think about how AI systems discover and evaluate vendors, not just humans. Underneath all of it: taste and trust are what’s left to compete on.
Elad
Hard-to-build infrastructure. The data layer, the signal engine, the connectivity — that’s what stays. Everything built on top of it is replaceable. The real question isn’t how to replace it; it’s how to get more out of it.
Already fading
Lucy
100% AI SDRs. Helpful at the margins. Not viable for hitting a real revenue number. Decision-makers in companies over 50 people don’t buy that way.
Lindsay
One-off prompts and standalone point solutions. A clever prompt in a separate app doesn’t beat a mediocre prompt embedded in the rep’s existing flow. Point solutions are getting consolidated or ignored.
Davide
Vibe-coded bespoke solutions and AI-led campaign ideation. Both produce slop at scale. Use AI to scale what works — not to figure out what works.
Elad
Full automation, no human in the loop. AI does the heavy lifting but the judgment stays with the seller. Black-box workflows lose trust, fast.
The thread underneath
An agent is only as good as the data underneath it
Point automation at stale records and you just make the wrong calls faster. Infrastructure stays. Tools on top of it don’t. If you’re sitting on something that’s hard to build, stop asking how you’re going to replace it — start asking how you’re going to get more out of it.
The teams pulling ahead in 2026 aren’t running more AI. They got their data clean enough to act on it. Then they removed the manual steps. Then they automated. In that order.
Prompts in this playbook use the Lusha connector for Claude. Data returned is subject to Lusha’s privacy policy and terms of use. Example outputs in this playbook are illustrative — run the prompts with your own data and connectors to see live results.