BlitzAPI

How would you find every company currently running Google Ads? Probably not with an industry filter. That’s exactly why TAM by Jobs is one of the most exciting things we’ve built at BlitzAPI ⚡ Second episode of our motion explainer series. The idea is pretty simple: job postings tell you much more than “this company is hiring.” They already tell you the company is active. They usually mean there’s budget. And inside the description, you can often find the real signals: tools, vendors, projects, expansion, infrastructure, new teams, new priorities. Once you start combining multiple job signals together, you can build completely different ways of defining a market. Not just: “show me companies in this industry” but: “show me companies where there’s actual evidence that this use case exists” That’s basically the whole idea behind TAM by Jobs. And honestly, this is exactly the kind of thing we want to keep building at BlitzAPI. Not just more data. More ways to use it creatively. More ways to discover markets that normal filters would completely miss. That’s where the high-intent part gets really interesting. Hope you’ll enjoy this one 🙌 More motion explainers coming around the best GTM systems + use cases we see every day. Cheeeeerz ⚡

We ship, again and again and again 🔥 and today, we’re super happy to announce BlitzAPI x ZeroClick The last 5 weeks have been pretty intense at Blitz We’ve been pushing hard to make our product more powerful, more flexible, and much more AI-native. Our conviction is pretty simple: the next buyers of B2B data won’t only be humans. they’ll be AI agents too. We’ve always built Blitz with that in mind. API-first. MCP. Agent Skills. Machine-readable docs. An AI could already understand Blitz, call our APIs and use the data. There was just one annoying part left: payment. An agent could use the product… but still needed a human to buy it. Not very agentic 😅 That’s what we fixed with ZeroClick Now an agent can: - discover Blitz - understand what we offer - see the pricing - buy the data - and use it all in the same flow. Just $0.001 per record returned. The agent buys what it needs and keeps moving. What a world haha 😅 Blitz was already built for agents to use. Now it’s built for agents to buy too. Huge thanks to the ZeroClick team for building this with us. We still have a ridiculous amount shipping over the next few weeks. Apparently resting is not part of the roadmap !! Cheeeeeerzzz ⚡

BlitzAPI now starts at $99/month 🔥 And honestly, this changes a lot for us. Until now, Blitz was mostly built and priced for teams running serious data volumes. Today, we’re opening it to smaller teams, founders and builders too. Starting at $99/month, you get: → every BlitzAPI feature → 10 requests / second → 200,000 records / month → the same data as every other plan → the same products as every other plan No “starter version” of the product. No feature wall. The main difference between plans is basically how much speed + volume you need. And I really like that model. Because a founder building his first outbound system shouldn’t need a $1k/month data stack just to experiment. A small RevOps team should be able to build a TAM, find the right people, enrich profiles, pull job signals, find emails and actually run workflows in production. At $99 for 200k records, that’s roughly $0.0005 per record. Which gives you quite a lot of room to build things 😅 This is probably the first time BlitzAPI really becomes accessible to almost anyone who wants to build with B2B data. And that was important for us. - Same infrastructure. - Same data. - Same building blocks. Just a much easier place to start. Every account also starts with 1,000 free credits. No card. No sales call. Just build.

BlitzAPI is entering a new era ⚡ We get asked pretty often what actually makes BlitzAPI different. What are we trying to build that doesn’t already exist? It’s been almost 10 months now (crazy how fast this goes 😅), and step by step the product is starting to look a lot more like the vision we had from day one. And that vision starts with a pretty simple belief: access to B2B data is not really the problem anymore. How you use it is. The advantage is moving from having data to being able to build better systems with it. Better TAMs. Better targeting. Better signals. Better CRM infrastructure. Better software. And honestly, I think creativity + flexibility are becoming increasingly important for GTM Engineers, RevOps teams and Software Engineers. That’s why we made a few choices very early at BlitzAPI: API-first. High volume. Flexible primitives instead of rigid workflows. Basically, give people the building blocks and let them decide what to build. Because the same data can power an outbound workflow, a CRM, an internal tool, an AI agent or an entire SaaS product. We don’t want to tell you how you should use the data. We want to give you enough infrastructure to build whatever makes sense for you. I say this pretty often: we don’t sell you data. we rent you our infrastructure. And we design pretty much every feature with that idea in mind. Not only: how do we retrieve more data? But: what can someone build once they have it? This week is another good example with a lot of new updates coming 1. Past experiences + job descriptions as filters Useful for things like stack analysis, recruiting signals, career-based targeting and much more. 2. Catch-all + MX provider in filters and outputs Small detail, but super useful when you want proper routing and control over your email infrastructure. 3. 15M+ additional emails enriched More email coverage available across markets worldwide. Small blocks individually. A lot of new playbooks when you start combining them. That’s really where BlitzAPI is going: API-first. AI-native. High quality. Fully scalable. Whether you’re building outbound infrastructure, fixing a CRM, creating an agent or embedding B2B data into your own software. There’s still a loooot to build. But 10 months in, I’m pretty proud of what this thing is becoming and even more of what our customers are already building with it. The next few weeks should be pretty busy too 👀 Take care, Cheeeeerz ⚡

How do you build a high-intent contact list with BlitzAPI + Jev ? This is the first episode of a new video series we’ve been working on for a while ⚡ With the team, we had a pretty simple question: how do we share the GTM systems / playbooks we see working every day… without making another boring piece of B2B content? Few constraints on my side: I don’t really want to put my face everywhere on social media (and my english is sometimes a little… strange 😅) I don’t want someone else to become “the face” of Blitz atm And most importantly, I want to talk about fairly technical topics without making them painful to understand. So we decided to try something different. Short motion explainers. One problem. One concept. One real GTM system. The goal is to take the best use cases we see with our customers and explain why the system works, not just show you which buttons to click. First one today: how to scale decision-maker discovery with Waterfall ICP + Jev. The problem is pretty simple. Go too narrow in People Search → you miss companies. Go too broad → you get half the org chart. Waterfall ICP lets you search by priority instead of trying to squeeze your entire targeting strategy into one query. Then Jev can use the full profile context to recover the precision: buyer champion influencer noise That’s basically the whole system. Company TAM → Waterfall ICP → Jev → Routing → Activation. We’re aiming for around 3-5 videos / month, each one based on real GTM use cases and systems we see around BlitzAPI. And we’re using this to finally start building our YouTube channel too. Very curious to get your feedback on the format, the pacing, the topics, everything. Hope you’ll like this one 🙌 And for everyone heading to San Francisco this week… enjoy the trip !! 🔥

JEV knows your ICP by heart You shouldn't need to spend hours crafting the perfect query ❤️ Today, you need to find each word, each key that corresponds exactly to your ICP But an ICP is just a logical series of questions If you write them exactly as they should be, you get a TAM calculator Say your ICP is VPs of Sales at SaaS companies in the USA, 50 to 200 employees 🔍 But you can't just write that in a query Do you know what it maps to? That's why we built a small POC with JEV, just to see how it could work 🛠️ You describe your ICP in your own words, it writes the query and runs it 👀 It's still a POC, and we haven't decided if it should become a feature Is this something you'd want to see in BlitzAPI?