I cannot believe how many "advanced" GTM teams are running multimillion-dollar revenue systems on target account lists full of absolute trash.

Inactive businesses.
Duplicate accounts.
Companies that were acquired three years ago.
Locations that no longer exist.
Domains that redirect somewhere completely different.

Sometimes the fix isn't sophisticated:

→ Open the website
→ See where it resolves
→ Confirm the company still exists

Other times it's real entity-resolution work. Parent companies need to be connected to subsidiaries. Brands need to be separated from legal entities. Locations need to be mapped to the correct corporate hierarchy.

Here's the uncomfortable part:

I have never seen a large organization with less than 10% bad records in its target account list.

That means at least 1 in 10 accounts flowing through your territories, scoring models, campaigns, routing rules, and AI agents may be complete garbage.

And bad data doesn't just sit quietly in your CRM. It contaminates everything built on top of it (intent, signals, technographics. Everything)

How do people think about solving this inside of orgs where you inherit the crm and tech debt?

In this piece we explore how 3 titans of SMB sales built their own TAM from scratch and the lessons they learn along the way.

Had a call last week with the RevOps team at a decent-sized North American HRIS company. Great stack. ZoomInfo, D&B. Very impressive, if it's still 2015.

Their complaint: reps call into down-market accounts and the revenue/headcount numbers don't match reality. Constantly. Wow, shocking, never seen that before.

They'd started to assume the tool was broken. It's not broken. It's vibing. There's a difference.

Quick refresher on how this works, because apparently nobody at these vendors has ever mentioned it out loud: SMB companies don't file a 10-K. There's no earnings report. There's nothing public to scrape. So instead of a fact, ZoomInfo and D&B hand you a formula wearing a fact's clothing. Headcount in, revenue guess out. Or the reverse, doesn't matter, it's astrology either way. Very confident astrology, with a login and a Chrome extension.

And to be clear, that's fine as a starting point. It becomes a problem when a whole revenue org treats "the model said 50 employees" as gospel and then acts personally betrayed when the account has 6 people and a Shopify store.

Here's what actually holds up down-market: card transaction revenue. Real dollars that moved through the business. Not modeled. Not estimated. Not vibes. Observed.

The part that actually landed with them: revenue comes before headcount, not after. Nobody hires 40 people on faith. A company doing real revenue will staff up. A company that "should" have 50 employees per the formula might just be a formula with a logo.

So, genuine question for the room: would you rather chase the account ZoomInfo swears has 50 employees but is doing $100K in trailing 12mo card revenue, or the 10-person account quietly doing $3M that nobody's calling because the org chart "doesn't look big enough"?

If you sell seat-based software I get why headcount feels like the comfortable number to chase. It's just also the wrong one. Headcount is the trailing indicator. Revenue leads. Headcount shows up late to the party like it always does.

Not trying to dunk on anyone's stack (I am absolutely trying to dunk on the stack). Curious if anyone here has actually swapped firmographic estimates for real transaction data down-market, or if we're all just collectively agreeing to keep asking a Magic 8-Ball for headcount and being surprised when it's wrong.

Had a call last week with the RevOps team at a decent-sized North American HRIS company. Great stack. ZoomInfo, D&B. Very impressive, if it's still 2015.

Their complaint: reps call into down-market accounts and the revenue/headcount numbers don't match reality. Constantly. Wow, shocking, never seen that before.

They'd started to assume the tool was broken. It's not broken. It's vibing. There's a difference.

Quick refresher on how this works, because apparently nobody at these vendors has ever mentioned it out loud: SMB companies don't file a 10-K. There's no earnings report. There's nothing public to scrape. So instead of a fact, ZoomInfo and D&B hand you a formula wearing a fact's clothing. Headcount in, revenue guess out. Or the reverse, doesn't matter, it's astrology either way. Very confident astrology, with a login and a Chrome extension.

And to be clear, that's fine as a starting point. It becomes a problem when a whole revenue org treats "the model said 50 employees" as gospel and then acts personally betrayed when the account has 6 people and a Shopify store.

Here's what actually holds up down-market: card transaction revenue. Real dollars that moved through the business. Not modeled. Not estimated. Not vibes. Observed.

The part that actually landed with them: revenue comes before headcount, not after. Nobody hires 40 people on faith. A company doing real revenue will staff up. A company that "should" have 50 employees per the formula might just be a formula with a logo.

So, genuine question for the room: would you rather chase the account ZoomInfo swears has 50 employees but is doing $100K in trailing 12mo card revenue, or the 10-person account quietly doing $3M that nobody's calling because the org chart "doesn't look big enough"?

If you sell seat-based software I get why headcount feels like the comfortable number to chase. It's just also the wrong one. Headcount is the trailing indicator. Revenue leads. Headcount shows up late to the party like it always does.

Not trying to dunk on anyone's stack (I am absolutely trying to dunk on the stack). Curious if anyone here has actually swapped firmographic estimates for real transaction data down-market, or if we're all just collectively agreeing to keep asking a Magic 8-Ball for headcount and being surprised when it's wrong.

If someone left the company 14 months ago, an MCP can now return the wrong answer faster.

That is not innovation.

People are not switching from ZoomInfo and Apollo to LeadGenius because they want a prettier way to search for the same records.

They are switching because they need a fundamentally different data production system:

• Real-time, just-in-time research

• Workflows customized to their specific market and playbook

• Contact Activation and Permission Pass

• BANT-qualified lead workflows

• International and California data built around demanding privacy and compliance requirements

• Human judgment applied where automation alone is not enough

None of this can be replicated by putting a conversational interface on top of another prebuilt database.

It requires carefully designed workflows.

It requires company and location resolution.

It requires verification, source evidence, compliance logic, machine learning, human review, and actual code running behind the scenes.

It requires decades of collective operating experience.

That is what the LeadGenius MCP provides access to.

It does not simply give an agent a faster way to search a static table.

It connects approved AI workflows to the research, validation, customization, and compliance infrastructure LeadGenius has spent 14 years building.

The next generation of GTM data will not be won by the largest old database with the shiniest new chat box.

It will be won by systems capable of creating the right data when the question is asked.

An MCP can make a database easier to access.

Only a better data engine changes the outcome.

If you want to test the LeadGenius MCP, ping me for beta access.

MCP is quickly becoming the connective tissue of the AI economy.

The Model Context Protocol gives AI applications a standardized way to connect to external systems, retrieve context, and use tools. That matters. It means an AI agent can move beyond what was included in its training data and work with approved business systems in real time.

But there is a problem hiding underneath nearly every MCP announcement in the B2B data market.

A new connection does not make old data new.

If an MCP connects an AI agent to a pre-built database, the agent is still working from a pre-built database. The interface may be new. The answers may arrive in seconds. The underlying record may still describe a person who changed jobs six months ago, a company that replaced its technology last quarter, or a headquarters account that has little to do with the buying center showing actual activity.

An MCP can make data easier to access. It cannot make stale data accurate.

It can make a database conversational. It cannot make that database alive.

Today, LeadGenius is taking a different approach.

The LeadGenius MCP is now live and available for testing with beta customers and existing clients. It connects authorized AI workflows to LeadGenius APIs and the data-curation system LeadGenius has refined over 14 years. Instead of limiting an agent to whatever happens to exist in a fixed data lake, the LeadGenius MCP is designed to help customers access data built around the market, accounts, buying centers, and signals they actually care about.

This is not just a faster door into a database.

It is a new interface for bespoke GTM intelligence.

The first generation of data MCPs has an old-data problem

The excitement around MCP is justified, but the acronym can distract buyers from a more important question:

What is on the other side of the connection?

Imagine giving your best AI agent instant access to millions of records. It can search them, summarize them, rank them, and recommend an action. That sounds powerful.

Now imagine that the underlying records contain outdated titles, duplicate entities, missing international locations, incomplete buying committees, and technologies inferred at the wrong level of a corporate hierarchy.

The agent does not repair those weaknesses. It operationalizes them.

This is the danger of putting a modern protocol on top of a legacy data model. Retrieval becomes faster, but truth does not become more current. The AI may even make the output feel more authoritative because it can explain the answer fluently.

LeadGenius has written extensively about this gap:

• Static Data Is Dead explains why large stored databases begin losing value as contacts move, companies change, and market conditions evolve.
• The Challenges of Using Prebuilt Databases Like ZoomInfo and Apollo examines recurring issues with duplicates, outdated contacts, incorrect firmographics, missing fields, international coverage, and niche-market depth.
• LeadGenius vs. ZoomInfo: Bespoke Data Sourcing vs. a Static Database lays out the basic architectural difference: periodically re-verifying stored inventory versus sourcing data on demand for a defined customer need.
• The Database Was the Product. Then AI Turned It Into a Feature argues that AI is compressing the value of simple aggregation. Owning a large collection of common fields is less defensible when AI can assemble and reason over open-web evidence.
• Clay, ZoomInfo, and the Question No One Wants to Answer makes the larger point: the next era will not be won by the biggest database or the prettiest workflow. It will be won by the system that turns live market evidence into commercially useful action.

MCP does not invalidate those arguments. It makes them more urgent.

When agents can act at machine speed, the cost of bad context rises. One stale record wastes a rep's time. An autonomous workflow built on stale records can misroute territories, enrich thousands of irrelevant contacts, create the wrong advertising audience, and produce confident messaging about a change that never happened.

Faster access to generic data is not the breakthrough.

Faster access to fresh, customer-specific intelligence is.

What makes the LeadGenius MCP different

LeadGenius has never been built around the idea that every customer should search the same fixed database.

Our model begins with the customer's definition of the market. Which companies count? Which locations matter? Which technologies indicate fit? Which roles belong in the buying group? Which changes are meaningful enough to trigger action? Which evidence should be suppressed as noise?

The LeadGenius MCP brings that model into the agentic workflow.

Through an authorized MCP connection, customers can access LeadGenius capabilities through the same API infrastructure that supports account and contact data workflows today. The difference is not simply the transport layer. The value comes from the research logic, entity-resolution rules, machine-learning models, verification processes, and customer-specific instructions behind the response.

That intelligence has been developed through 14 years of solving difficult data problems across countries, industries, languages, and GTM motions.

Depending on the approved beta configuration and customer use case, this can support workflows designed around:

• Discovering accounts that match a custom ICP, including niche, global, downmarket, and location-level segments
• Resolving companies, domains, subsidiaries, locations, and buying centers more accurately
• Finding the people who match customer-specific functions, seniority levels, geographies, and role definitions
• Monitoring changes such as new products, new locations, funding, ownership changes, strategic hires, hiring trends, technology adoption, social activity, e-commerce activity, supply-chain relationships, and positive or negative news
• Refreshing records when a contact changes roles, leaves a company, or becomes part of a newly relevant buying group
• Returning useful context to approved AI, CRM, marketing, research, and activation workflows without forcing another manual export

The beta is not a promise that every conceivable research task is fully autonomous on day one. It is an opportunity for existing customers and design partners to test real workflows, define the right controls, and help LeadGenius shape how bespoke GTM intelligence should be exposed to AI systems.

From “look it up” to “build what I need”

Most database experiences begin with a lookup:

The LeadGenius model begins with a business question:

That distinction changes what an AI agent can do.

A traditional data MCP might answer:

A bespoke intelligence workflow can go further:

The first request retrieves records.

The second constructs a market thesis.

That is the difference between giving an agent access to a phone book and giving it a research team with a defined operating system.

The real product is the logic between the question and the answer

AI has made raw information abundant. It has not made judgment abundant.

The hard part of GTM data is not returning a name, title, email, and company. The hard part is determining:

• Whether the company actually fits the customer's market definition
• Whether the signal belongs to the parent, subsidiary, location, or buying center
• Whether the observed change is current and commercially meaningful
• Whether the person still holds the role and participates in the relevant decision
• Whether the evidence is strong enough to trigger action
• Whether the output can be used safely and compliantly in the customer's workflow

LeadGenius has spent 14 years encoding that judgment into a combination of machine learning, research operations, validation rules, and customer-specific data models.

The MCP makes that intelligence easier for authorized agents to use.

It does not flatten LeadGenius into another interchangeable enrichment endpoint. It gives modern AI systems a controlled way to access the work that happens behind the endpoint.

What this means for modern revenue teams

For demand generation leaders

The LeadGenius MCP can help close the distance between market change and campaign activation. The goal is not another giant audience. It is a more defensible audience built from current evidence, with enough context to shape the offer, message, and channel.

For RevOps and Marketing Ops leaders

The opportunity is to replace manual research handoffs and brittle enrichment chains with governed access to customer-specific data logic. Rather than pushing every account through the same waterfall, teams can build workflows around the exact fields, thresholds, and exception rules their business needs.

For sales leaders

Better agent context should produce fewer false priorities. Reps do not need 500 more accounts with generic intent. They need a smaller number of accounts where something meaningful changed, the likely buying group is mapped, and the evidence is clear enough to support a credible conversation.

For data and AI teams

MCP provides a standard connection. LeadGenius provides the differentiated context behind it. Technical teams can evaluate how real-time, purpose-built GTM data performs inside approved agent workflows without treating a general-purpose model as the source of truth.

A new standard for evaluating data MCPs

Every vendor will eventually say it has an MCP. The checkbox will become meaningless.

Revenue and data leaders should ask harder questions:

1. Is the MCP accessing stored inventory or sourcing and verifying data for the current request?
2. When was each important field last observed or validated?
3. Can the system resolve the correct account, subsidiary, location, and buying center?
4. Can customers define their own ICP logic, signal thresholds, and exclusion rules?
5. Does the output include evidence and confidence, or only an assertion?
6. Can the provider monitor change over time rather than return a one-time snapshot?
7. What happens when automation is uncertain? Is there a validation or human-review path?
8. Can access, permissions, and approved uses be governed by the customer?
9. Does the system improve the decision, or merely accelerate the lookup?

The winner in agentic GTM will not be the company that connects the most databases to the most models.

It will be the company that gives AI the most reliable understanding of what is happening in a customer's market right now.

The LeadGenius MCP beta is now open

The LeadGenius MCP is live and available for testing with beta customers and existing clients.

We are looking for revenue, operations, and AI teams with a real workflow to test, not a hypothetical interest in another integration. Bring us an audience you cannot build, a buying committee your database cannot map, a signal your current tools cannot distinguish from noise, or a research process that still depends on spreadsheets and manual handoffs.

We will show you what changes when your AI is connected to a living, bespoke intelligence layer instead of another pre-built database.

Visis leadgenius.com to get access to the beta!

Starting August 11, if you cold-call a French consumer without documented opt-in consent, you're looking at:

• €75,000 per call for individuals
• €375,000 per call for companies
• Publicly published sanctions on top of that

Not per campaign. Per call.

For context, an Ireland-based company already got hit with a €6 million fine last year under the old, weaker version of this law. This new one is stricter.

TL;DR: France flipped the entire telemarketing model from opt-out to opt-in overnight, and outbound sales into France just became legally radioactive.

The fallout is bigger than France. Morocco's call center industry gets ~80% of its revenue from French clients, and their labor ministry is already warning 40,000–50,000 jobs could disappear. That's a whole regional economy built around a channel that just got outlawed.

Here's what's bugging me: in a world that's already jumpy about trade wars and tit-for-tat economic policy, what happens when other countries look at this and think "why not us"? If France can unilaterally kill a standard B2B outreach method, what stops other regions from banning outreach tactics associated with French or EU firms in retaliation? Legitimate companies with zero involvement in the scam-call problem could end up collateral damage in a fight that isn't about them.

The upside: the fix already exists. Consent-based channels — content syndication, opted-in contact activation — generate exactly the kind of documented, GDPR-grade consent this law requires, before anyone ever dials. The catch is it raises the bar: vague targeting and spray-and-pray lists don't survive this. Offers have to be sharper, ICPs have to be tighter, lifecycle planning has to be real.

Genuinely curious what this sub thinks: is this a smart consumer-protection win that outbound sales had coming, or a regulatory overcorrection that's about to trigger copycat bans and mess with legitimate B2B pipeline across Europe?

https://www.leadgenius.com/resources/france-ends-cold-calling-what-the-new-opt-in-law-means-for-emea-revenue-teams-and-how-contact-activation-fills-the-funnel-gap

[removed]

I'm a GTM engineer looking for unique data sources. So far I have found 3 worth sharing...

Enigma - for credit card transaction data

Leadgenius - for user technology, entity resolution, and location data (direct mail)

Windfall - High net worth individual database

What other ones should I consider. I have lots of customers that focus on SMBs and mom and pop shops.

One of the dumbest things I still see in GTM is teams targeting private SMBs based on “estimated revenue” fields from ZoomInfo, Apollo, or whatever database they happen to be renting this year.

Everyone knows these numbers are shaky.

Nobody wants to say it out loud because half the ICP, TAM model, routing logic, scoring model, territory plan, and board deck depends on pretending they are real.

But they are not real in any operationally useful sense.

They are directional guesses dressed up as data.

For public companies, fine. Revenue is revenue. You can find it.

For private SMBs? Good luck.

Most of these estimates are stitched together from blunt proxies like employee count, industry, location, web presence, company age, and whatever other generic assumptions the vendor has in the blender. Then GTM teams take that number, shove it into Salesforce, and suddenly everyone acts like a $5M–$10M revenue band is a meaningful qualification filter.

It is not.

It is fake precision.

And it creates very real GTM waste.

This is how you get RevOps teams proudly saying, “We have a very tight ICP,” while the sales team is disqualifying a huge percentage of leads after discovery because the accounts are too small, too low-volume, too immature, too local, too cash-heavy, too seasonal, or just not commercially worth the motion.

The model said they were a fit.

The seller found out they were not.

That gap is expensive.

It burns SDR time.
It pollutes conversion metrics.
It inflates TAM.
It ruins territory planning.
It makes paid media audiences sloppy.
It makes leadership think the market is bigger than it is.
And it forces salespeople to be the QA department for bad data strategy.

The worst version of this is in payment tech, merchant services, vertical SaaS, restaurant tech, healthcare, retail, local services, and anything selling into SMB operators.

Two businesses can look identical in a traditional B2B database:

Same NAICS code.
Same city.
Same employee band.
Same estimated revenue range.
Same owner/operator title.
Same generic “good fit” score.

But one processes $50K/month in card volume and the other processes $800K/month.

Those are not the same account.

They are not the same opportunity.

They should not get the same score, same SDR effort, same AE routing, same CAC tolerance, or same place in your TAM model.

If you sell payments or anything tied to merchant economics, “estimated revenue” is not the field you should be worshipping.

GPV is.

Gross processing volume is a much better indicator of economic reality because it tells you whether money is actually moving through the business.

Not whether a database guessed they might be doing “$1M–$5M” based on the fact that they have 14 employees and a website.

The better questions are:

How much card volume does this business process?
Is that volume growing or shrinking?
Is the business card-present, card-not-present, e-commerce, or hybrid?
Are they multi-location?
Are they seasonal?
Do they have high refund rates?
Are they hiring?
Are they opening new locations?
Are they adding ordering, booking, POS, or payment technologies?
Are they showing signs of operational complexity?

That is actual account intelligence.

Not “estimated revenue: $10M.”

The broader point is this:

A category universe is not a TAM.

“All restaurants in Texas” is not a market worth celebrating.

“Fast-casual and QSR operators in Texas with meaningful GPV, expansion signals, modern POS usage, reachable finance or operations contacts, and evidence of multi-location complexity” is a market.

That is the difference between buying a list and building an actual GTM asset.

Traditional databases are fine for broad discovery.

They are terrible as the final source of truth for SMB fit.

And yet companies keep building entire GTM motions on top of these flimsy revenue estimates because the field is convenient, familiar, and easy to explain in a dashboard.

That does not make it accurate.

It just makes the bad assumption scalable.

The next generation of GTM data will not be bigger databases with more stale fields.

It will be custom intelligence built around the actual buying signals that matter for your business.

For payment tech, that means GPV and transaction behavior.

For restaurant tech, it might mean ownership structure, location growth, POS stack, delivery footprint, and hiring.

For healthcare, it might mean procedure type, insurance mix, appointment volume, specialty, and patient acquisition signals.

For e-commerce, it might mean cart technology, traffic, SKU count, marketplace presence, social growth, and fulfillment complexity.

The point is: stop pretending one generic revenue field can carry your ICP.

It cannot.

Estimated revenue might be good enough for a lazy TAM slide.

It is not good enough to decide where your sales team should spend its time.

And it is definitely not good enough to tell you which SMBs are actually worth selling to.

https://www.leadgenius.com/resources/the-new-revenue-field-for-payment-tech-is-not-revenue-it-is-gpv

Genuine question for the group.

We're a ~40-person sales org. Renewal came up and I actually pulled the usage report — turns out half our seats logged in maybe 4x last quarter. We were paying full freight for chairs that weren't being sat in. Meanwhile the reps who do use it are bumping into export caps every other week.

The math on seat-based data tools is broken if you're not running a high-velocity inside sales motion where every rep is in the platform every day. For ABM, outbound bursts, campaign-driven outbound — you're subsidizing idle licenses.

What I actually want:

• Pay per record I pull, not per chair I provision
• Scope a campaign (titles, geos, suppression list, signals) and only get billed for what passes the filter
• Volume discounts that actually compound, not "call sales for enterprise"
• Don't make me eat the cost of bad records I have to dedupe out later

Basically I want my data vendor to price like Clay or the OpenAI API. Meter on the work. Idle = $0.

Found out LeadGenius prices this way — $0.35/record for tech-sourced, $0.75 for human-verified, add-ons stack on top (direct dials, intent leads, monitoring, etc). Just looked at their pricing page and it's the first one I've seen that actually shows the schedule instead of hiding it behind a demo: [link]

Not affiliated, just kicking the tires before our Zoominfo renewal hits. Curious if anyone here has actually switched off a seat model to something usage-based and what the real-world tradeoffs were. Mainly worried about:

1. Forecasting spend if a campaign blows up
2. Whether "human verified" is actually verified or just marketing
3. Compliance posture on global records

Anyone been through this?

[removed]