ZoomInfo on X

K

kamil ali rextin@kamilrextin

A lot of people don’t know what ZoomInfo shipping and at insane speeds for a public company You all need to check out link We’ve been building data infrastructure and consistently find zoominfo / link quality higher and it has better coverage even in niche obscure industries. Hats off to @HenryLSchuck Dennis Sevilla and my slack friend Hannah Telegen This isn’t paid for btw (though I wouldn’t mind affiliate commissions) I was a zoominfo hater I’ve been public about getting slammed with auto renew an arrogant AM/AE. Henry and the team shipped and won me over and that’s incredibly hard to pull off so now I am cheerleader Discolure Yes I own $GTM via public markets

F

Fivos Aresti@fivosaresti

Old school GTM is BROKEN. • Hire a bunch of reps • Get legacy category-leading tools (e.g. 6Sense, Demandbase, ZoomInfo) • Have sales and marketing work in silos The NEW-school GTM playbook is run by RevOps + GTM Engineers. Here's how the top teams are doing it: 1️⃣ ICP Analysis • Export Closed Won + Closed Lost from the CRM • Feed both into Claude Code to find the patterns • Build the ICP model on 3 layers: firmographics, account signals, technographics 2️⃣ TAM Map Map the entire market that fits the ICP: • Apollo(.)io's company database • Ocean(.)io for lookalikes companies • AI Ark for keyword search • Clay's database for extra companies 3️⃣ AI Account Research Enrich every account at scale: • Apollo(.)io for firmographics • Claygent + Claude for account-fit signals • Exa for deep web research • Sumble for technographics • Findymail for social signals 4️⃣ Tier + Score • Split accounts into Tier 1, 2, 3 • Score each one by awareness stage: • Identified → Aware → Interested → Considering → Selecting 5️⃣ Contact Sourcing Find and validate the buying committee: • Combination of Clay + AI Ark to source contacts • Findymail to find and verify emails • BetterContact for phone numbers 6️⃣ Demand Generation Only now do you turn on the channels, and all three run together on the same RevOps foundation: • Content: LinkedIn, X, Website • Outbound: LinkedIn, Calls, Email • Ads: LinkedIn, Meta, Google 7️⃣ Meeting Booked • Clay routes the lead to HubSpot • Cal(.)com books the call 8️⃣ Sales Process • Ergo for account intel before every call • Nooks for dialing • Apollo(.)io + HubSpot to run the pipeline • Qwilr for proposals • Claude as the copilot through all of it 9️⃣ Closed Won Every closed won account feeds the engine to find more lookalike companies. Bookmark this for your next GTM build.

T

Ticker Mavericks@TickerMavericks

ZoomInfo ($GTM) sells the database sales teams use to find who to call: names, job titles, emails, phone numbers. Its existing customers now spend about 11% less with it each year. That’s the number the whole company turns on. Here’s the machine. A subscription business starts each year with last year’s customers, and some cancel or cut back. ZoomInfo reports this as net revenue retention: 89% last quarter, down from 90%. For every $100 those customers spent a year ago, they now spend $89. So before it can grow at all, ZoomInfo has to win about $11 of new business for every $100 it already has. Last quarter its revenue grew 1.2% from a year earlier, to $310.4M. The bucket is leaking almost as fast as it’s being filled. And the leak has a name people fear: AI. If an AI tool can dig up a contact, fewer companies want to pay per seat to look one up. In May ZoomInfo cut its yearly forecast, cut about 600 jobs, and began moving customers from per-seat pricing to paying for the data they use. ZoomInfo’s own forecast now points down: it expects $298M to $301M of revenue this quarter, below last quarter’s $310.4M. Growing on paper last quarter, shrinking on its own numbers this one. So for any subscription company, find net revenue retention before the growth rate. Above 100%, existing customers grow the business on their own. Below it, new sales are refilling a leak, and the growth rate only tells you how fast they’re bailing. What it comes down to: does charging for the data customers use, instead of per seat, slow the leak or speed it up? Retention is the number that will answer it. We may hold positions in names we cover. Not advice. DYOR.

A

Alex Lindahl@gtm_engineer

GTM Engineering : What’s going on here? Reddit: GTM Engineers are going extinct! GTMEs only do the plumbing Claude is killing @clay Claude is killing the GTME VCs: Tier 1 VCs have the most hiring a GTME @sequoia has the most of all VCs 100+ companies every month hiring GTME 74% of the jobs mention Clay Only 12% mention ZoomInfo 63% of those jobs mention Clay

J

Juan José Zevallos@chinozc

Según ZoomInfo, los sectores regulados necesitan entre 7 y 12 aprobadores para una compra, software necesita bastantes menos. Si tu ciclo de venta en LATAM tiene 10 firmantes, ¿el problema real es el precio o el proceso de decisión?

C

CG@cgtwts

the lead gen industry is cooked zoominfo charges $600/mo. lusha charges $449. treg charges $0 in subscriptions and just $0.0089 per lead. the pricing-to-value ratio is actually insane.

A

Alex Vacca@itsalexvacca

AI was supposed to kill agencies. Then YC asked founders to build service companies where AI does most of the work. That's how we run @Frontal_AI. So every core tool we keep has to pass one test: Can Claude run it from one instruction? In 2021 you'd pay ZoomInfo $30K a year and still check half the data by hand. We replaced all of that with Clay. Copy our GTM stack, all 8 layers: 1/ Sourcing. Build one list per pain you solve, in Clay. → A title-and-industry filter says almost nothing about the buyer's problem. → We still check titles and accounts by eye in Sales Navigator. 2/ Enrichment. Find 2 to 3 people per company and run the email waterfall in Clay. → Keep each provider's result in its own column and pick one final email from them. → On Clay's Launch plan, upload the emails to MillionVerifier as a CSV. Running it inside Clay needs the Growth plan. 3/ Sending. We run 2 sequencers on purpose. Tier 1 goes to lemlist, email and LinkedIn in one sequence. Tier 2 goes to Instantly, email only. → Instantly pauses a campaign at 5% bounces by default. Set it to 2%. 4/ Signals. RB2B catches the site visit, PredictLeads the job post or funding round, UserGems the champion who just moved. → Each event goes on the account's row in Clay, with the date and a link to check it. → Keep the n8n workflow in between dumb, it just passes the event along. The scoring happens in Clay, where the whole team can read it. 5/ Ads. The same Tier 1 and 2 accounts go to LinkedIn as a company list. 6/ AI. Claude Code runs from each client's folder and reads their rules file first, so nobody re-explains a client. → One API key per person, with spend alerts. → We're rolling that out after my team burned $8,000 in AI credits on one task. An intern could've done it with a browser, and nobody noticed. 7/ RevOps. One reply stops every sequence for that lead, on every channel. → Positive replies post to one Slack channel, and a morning digest covers yesterday's replies, bounces and anything waiting on a person. → Claude suggests CRM updates in Slack. Someone on the team applies them. 8/ Delivery. One team runs all of it for many clients at once. → Every new client gets a copy of the same template folder, so their first campaign starts from what already worked. → Once a week we review every tool like it's a teammate. What did it actually do, where did someone copy and paste anyway, what broke without anyone seeing an error? Starting from zero? Clay, Prospeo, MillionVerifier, Instantly, HubSpot's free CRM and Claude Code. Add the rest later. Pick the layer your team still runs by hand and fix that one first. The settings are in the article.

M

Marketful@marketful_

ZoomInfo publishes no platform price, locks most contracts for 1-3 years, and auto-renews at +10%. Apollo, Cognism, and Lusha exist for specific reasons. Know your exit before picking a tool. link

A

Ankit GTM@ankit_saas

if you’re using Apollo or Zoominfo for list building, you’re not gonna make it

D

Dalton@dcmvlt

if you're mass pulling from zoominfo or apollo, you're dialing the same list as every other agency. here's how to fix it: stop pulling by industry and headcount and instead pull by buying signals for example if you're selling fractional sdr work, pull companies hiring sdrs. they already WANT what you sell if you're selling marketing, pull companies already running ads. they believe in the power of marketing. you can enrich with tools like: clay builtwith sales nav google ads transparency center which will allow you to cross reference the data to make sure what you're calling about is RELEVANT to their situation. I swear to you the list decides what the call sounds like 99% of the time before you pick up the phone.

A

Alex Vacca@itsalexvacca

AI was supposed to kill agencies. Then YC asked founders to build service companies where AI does most of the work. That's how we run @Frontal_AI. So every core tool we keep has to pass one test: Can Claude run it from one instruction? In 2021 you'd pay ZoomInfo $30K a year and still check half the data by hand. We replaced all of that with Clay. Copy our GTM stack, all 8 layers: 1/ Sourcing. Build one list per pain you solve, in Clay. → A title-and-industry filter says almost nothing about the buyer's problem. → We still check titles and accounts by eye in Sales Navigator. 2/ Enrichment. Find 2 to 3 people per company and run the email waterfall in Clay. → Keep each provider's result in its own column and pick one final email from them. → On Clay's Launch plan, upload the emails to MillionVerifier as a CSV. Running it inside Clay needs the Growth plan. 3/ Sending. We run 2 sequencers on purpose. Tier 1 goes to lemlist, email and LinkedIn in one sequence. Tier 2 goes to Instantly, email only. → Instantly pauses a campaign at 5% bounces by default. Set it to 2%. 4/ Signals. RB2B catches the site visit, PredictLeads the job post or funding round, UserGems the champion who just moved. → Each event goes on the account's row in Clay, with the date and a link to check it. → Keep the n8n workflow in between dumb, it just passes the event along. The scoring happens in Clay, where the whole team can read it. 5/ Ads. The same Tier 1 and 2 accounts go to LinkedIn as a company list. 6/ AI. Claude Code runs from each client's folder and reads their rules file first, so nobody re-explains a client. → One API key per person, with spend alerts. → We're rolling that out after my team burned $8,000 in AI credits on one task. An intern could've done it with a browser, and nobody noticed. 7/ RevOps. One reply stops every sequence for that lead, on every channel. → Positive replies post to one Slack channel, and a morning digest covers yesterday's replies, bounces and anything waiting on a person. → Claude suggests CRM updates in Slack. Someone on the team applies them. 8/ Delivery. One team runs all of it for many clients at once. → Every new client gets a copy of the same template folder, so their first campaign starts from what already worked. → Once a week we review every tool like it's a teammate. What did it actually do, where did someone copy and paste anyway, what broke without anyone seeing an error? Starting from zero? Clay, Prospeo, MillionVerifier, Instantly, HubSpot's free CRM and Claude Code. Add the rest later. Pick the layer your team still runs by hand and fix that one first. The settings are in the article.

A

Ankit GTM@ankit_saas

if you’re using Apollo or Zoominfo for list building, you’re not gonna make it

C

Cody Schneider@codyschneider

stop paying $15k a year for zoominfo seats you can build your whole tam map in claude code and pay per contact instead 1. have claude write your icp. industry, headcount, titles, tech stack, geo 2. pull every matching company and the decision makers from the getleads api 3. waterfall the emails. getleads first, then apollo, then leadmagic for anyone still missing 4. verify every email with million verifier. keep the ok ones, not catch all 5. find personal emails and mobiles for the top accounts so you can run customer match ads to them 6. write it all to one postgres table so your team queries one list, not 5 csvs 7. rerun weekly on a cron and add net new people and job changes getleads is a fraction of a cent per contact the seat model made sense when a human had to click export. claude doesn't need a seat get started for free - link

F

Fernando Cao@thefernandocz

2024 outbound ran on ZoomInfo, Outreach and Zapier. Ours runs on none of them. Here's what replaced each one, job by job: Lead data 2024: ZoomInfo, Apollo Now: Prospeo, Blitz and GetLeads on every build, DiscoLike for company discovery Email finding 2024: Hunter Now: a waterfall. GetLeads, then Blitz, then Prospeo, then Findymail Verification 2024: NeverBounce Now: MillionVerifier on every address, LeadMagic on the catch-alls Inboxes 2024: Workspace seats on the company domain Now: generic domains from Porkbun, Google inboxes from ScaledMail Sequencing 2024: Outreach, Salesloft Now: Email Bison, one plain-text email per campaign LinkedIn 2024: Sales Navigator and PhantomBuster Now: our own LinkedIn tool on Unipile, HeyReach for older campaigns Replies 2024: an SDR in Gmail Now: an AI agent on Claude that answers, flags or closes every reply. Slack holds the few a person needs to see. Meetings 2024: Calendly, Gong Now: link Grain Automation 2024: Zapier and a spreadsheet Now: Claude Code routines on our servers, Supabase underneath The tools aren't the biggest shift. Who does the work is. In 2024 most of these jobs had a person attached. Now they run on timers and agents, and people take the exceptions. What I'd take from this: The stack doesn't sit still. Three rows changed in the last three weeks: Blitz joined on Oct 1, our own LinkedIn tool became the default on Oct 8, Porkbun took over domains on Oct 12. Test the swap before you make it. Blitz only got in after a head-to-head against Prospeo on six ICPs. The glue is code now. Zapier and a spreadsheet became routines we can read, test and fix. Which job in your stack still looks like 2024? -- We build and run AI-native outbound systems on a pay-per-qualified-meeting model. You only pay when a qualified meeting actually lands on your calendar. See if you qualify: link

C

Cooper@cooperaiq

Best · Sales Intelligence Top 3 1. @useapolloio: AIQ 78 2. @zoominfo: AIQ 45 3. Cognism: AIQ 42 AIQ: recommendation strength within this ranking.

A

Apple Radar@appleradartwt

Pay-as-you-go instead of ZoomInfo's $600/month is a big shift. But cost per lead only matters if the data is good. How do email accuracy and data freshness compare to ZoomInfo or Apollo?

J

Jason@jnoble100

Good that someone's testing this. The real question is how many of those contacts are right and still in the job. Would love to see the error rate next to the speed.

S

SrinivasanSS@SrinivasanSS52

What is this zoominfo @grok

C

cena@cenaydebtsfree

Zoominfo ya kak ?

C

Cody Schneider@codyschneider

stop paying $15k a year for zoominfo seats you can build your whole tam map in claude code and pay per contact instead 1. have claude write your icp. industry, headcount, titles, tech stack, geo 2. pull every matching company and the decision makers from the getleads api 3. waterfall the emails. getleads first, then apollo, then leadmagic for anyone still missing 4. verify every email with million verifier. keep the ok ones, not catch all 5. find personal emails and mobiles for the top accounts so you can run customer match ads to them 6. write it all to one postgres table so your team queries one list, not 5 csvs 7. rerun weekly on a cron and add net new people and job changes getleads is a fraction of a cent per contact the seat model made sense when a human had to click export. claude doesn't need a seat get started for free - link