Antoine Blitz

Founder @BlitzAPI ⚡️ Unlimited B2B Data APIs

[Antoine Blitz @AntoineBlitz]

new @blitzapi video series 🎥
short explainers around real GTM systems.

episode 1:
Waterfall ICP + Jev (@typesafeai)

go too narrow → lose TAM
go too broad → lose signal

Waterfall handles discovery.
Jev handles context + precision.

AI can recover precision. it can’t recover someone you never discovered.

so many things you can build with Blitz + Jev !!

next video week ⚡️

[Antoine Blitz @AntoineBlitz]

we need to prioritize our time. The choice was to be focus on Product, Support and Innovation rather than Sales / Outbound / Marketing

also, our offer helped us to get big customers fast and they become ambassador or our product because they like the project

and finally when we need to do something, we build an internal tool to make it repeatable :)

[Antoine Blitz @AntoineBlitz]

Great September for @blitzapi

+25% growth
-7pts churn
- new pricing model
- new website
- tracking server side
- ads platform and CAPI
- data improvements (92% quality and 40% more coverage)
- new email discovery technology
- new branding app
- new MCP and Dashboard
- 3 new features with Profile Enrichment
- 4 Motion explainers videos

Next target:
3M ARR
SOC II & GDPR certification
New features 👀
New data objects
Big partnerships

Team of 3, this AI world is crazy

[Oddon @ibadus_]

@BlitzAPI MCP is live ⚡️

Before that our MCP allowed only to read our docs...

NOW it can pull THOUSANDS of leads for you with their emails, write full script to pull MILLIONS of leads or just build anything you want on top of Blitz 🦾

We've spent some time optimizing everything for your agents like the context usage per tool calls and many small details

Happy building! 🙌

[Antoine Blitz @AntoineBlitz]

@ibadus_ @blitzapi I can’t follow on the marketing side 😭

[Antoine Blitz @AntoineBlitz]

Refreshed every 7 days 🥲

[Antoine Blitz @AntoineBlitz]

Please @prospeo_io, don't target my co-founders on @blitzapi .... 😂

The market is huge, and I love them

[Antoine Blitz @AntoineBlitz]

If your first provider is good, you will have much more noise and stale data than accurate records in your next steps

Indeed, adding coverage means adding people the first provider doesn’t have.
It works only if all the providers had 100% accuracy

You will waste time, energy, money for few accurate records and a lot of stale data

[Antoine Blitz @AntoineBlitz]

contacts data waterfall is the worst idea you can have to enhance your GTM.
you will lose time, money, and performance

except if you want other data sources (local businesses etc.) with some niche providers

[Antoine Blitz @AntoineBlitz]

i can even go deeper:
use the technology « linkedin to email » ONLY with your contact data provider

to increase your coverage, the next steps must be first / last / domain technology

[Antoine Blitz @AntoineBlitz]

we use Sales Nav exports as the reference dataset (5 files, different targeting)

then enrich every profile with each provider

not found = coverage miss
found = we compare it against the real Sales Nav data for accuracy

so:
Y = accuracy
X = coverage

the lines on the graph represent accurate coverage = accuracy × coverage

[Antoine Blitz @AntoineBlitz]

THREAD

everyone in B2B data says the same things:
“best coverage”, “freshest data”, “highest accuracy”

so we tested it.
Apollo, Prospeo, MoltSets, QuickEnrich, GetLeads + BlitzAPI.

Full benchmark

[Antoine Blitz @AntoineBlitz]

@THArrowOfApollo You have an LI internal ID, so could be a solution, but we never saw a tool provide this ID… so hard to maintain

[Antoine Blitz @AntoineBlitz]

i'm not alone apparently 😅

the hard part is: what matching key do you use to identify an Experience and reliably upsert it?

internal IDs have limits. you need some kind of public identifier if you want this to stay reliable over time.

we already built a system for this in Blitz, but it's internal and not flexible with every tools.

curious how you’d approach it on your side?

[Antoine Blitz @AntoineBlitz]

hot take: i’m convinced most CRMs still have the wrong data model

the People object is always messy because it tries to merge the person + their current experience into one record

People should be the identity
Experience should be a separate object linked to Accounts
would make CRM hygiene, job changes and signal tracking way easier

[Antoine Blitz @AntoineBlitz]

quick recap

you can find the full report here: https://t.co/rgaN5uD0na

[Antoine Blitz @AntoineBlitz]

waterfalls were interesting too.

the first fallback created most of the extra value.

after that, returns dropped very quickly.

more providers ≠ automatically a better waterfall.

measure incremental accurate records, not just extra hits. Again, truly think waterfall for contacts data is not valuable at all