Why Your B2B Intent Data and AI SDR Aren't Producing Meetings (It's a Workflow Problem)

2026-08-26 · Julian Hartwell

I run RevOps for a B2B SaaS company. For the last six years, I've handled data enrichment contracts, intent data subscriptions, and prospecting tooling for our sales team. I've also made about a dozen significant mistakes in that time—totaling somewhere around $38,000 in wasted budget. Maybe $35,000. I'd need to pull the invoices. The point is: I've felt the sting of a full pipeline that produces nothing.

In January 2025, our CRM looked healthy. We had 1,200 enriched accounts, 79 active conversations, and 11 demos booked from a campaign we had labeled 'agent-native.' We closed zero. Not because the SDRs were lazy. The workflow was broken in ways that the tools hid.

The surface problem: a full pipeline that produces no revenue

If you're reading this because your pipeline looks full but your calendar doesn't, I get it. You're probably chasing one of three things: a data enrichment company that promises more leads, a B2B intent data platform that scores every account, or an AI SDR that writes follow-ups for you. I've tried all three. The problem isn't any single tool. It's that data, intent, and AI are being sold as outcomes when they're actually raw material.

Let's talk about why that matters, and what I wish someone had told me before I spent the first $18,000.

What I was missing: three uncomfortable causes

Cause 1: Data freshness is not data accuracy

I once agreed to use a new data enrichment company for field data. The vendor said their records were 90% accurate. They were right—if you measured accuracy against their own sample. When we matched the file against our CRM, the match rate was closer to 68%, and 11% of the 'verified' emails bounced.

The uncomfortable truth: a data enrichment company can give you an email address that existed yesterday, but the decision-maker you need may have changed roles. The record is still in their database. It's just not your customer anymore. That's not just a data quality problem. It's a freshness problem.

When I check tools now, I ask when the record was last verified, not whether the vendor claims a high accuracy score. If you're looking at Lusha pricing credits per month in 2025, don't stop at the number of credits. Ask whether the credits can be consumed by an API and whether the data behind them is refreshed on a recurring basis.

Cause 2: Intent data is a timing signal, not a purchase order

The most expensive mistake I made was treating a B2B intent data platform like a lead qualification tool. We saw a spike of companies researching 'sales data tools.' Great. So we bypassed our own qualification process and pushed every spike into the top of the funnel. The result: SDRs were chasing accounts that had zero buying appetite, and the accounts that were actually looking at us got the same generic template as everyone else.

Here's the counterintuitive part. Adding more intent sources made the problem worse. Our own paid ads created intent signals. The platform couldn't distinguish between a person searching for a solution because they need it, and a person searching because they're a competitor, a student, or—and this one was fun—our own marketing team checking our landing page.

Intent data is useful when it's used as a trigger to start research, not as a verdict to launch outreach. An intent score is not an order. It's a question.

Cause 3: An agent-native workflow is about the data path, not the chatbot

Now the question everyone asks: how does AI SDR fit into an agent-native prospecting workflow? I've learned to split that question into two.

First, can the AI SDR act? Yes—it can draft email, handle objections, and book meetings. Second, can it act on the data connected to your stack? That's where most workflows fall apart.

Agent-native, for me, means the AI SDR calls an API, triggers a data enrichment company, receives an intent event, fetches a verified contact, writes a CRM task, and sends a personalized sequence—without a human copy-pasting from a browser tab. If the AI SDR requires a CSV export, or a manual phone number lookup, or a modal to confirm an email address, it isn't agent-native. It's a content machine with extra steps.

This is where Lusha's agent-native API is worth a deeper look. Not because the AI SDR is smarter, but because the data can be consumed as an API response instead of a spreadsheet. That may sound technical, but it changes everything. A spreadsheet needs a human. An API call doesn't.

The real cost of a data stack that doesn't connect

Let's get specific. In September 2024, our team renewed a data contract with an enrichment vendor for $4,200. We were promised 9,000 contacts with intent flags. What we got was a CSV with columns we didn't use and an intent score that meant nothing to our sales process. We spent two weeks trying to clean it. Forty hours of manual work. If you value an SDR hour at $75, that's another $3,000. And the delay pushed our Q4 campaign into November.

That's the hidden cost. Not the subscription. The reinvention of a workflow around a tool that was never designed to fit one.

This is also why I'm wary when people search for AppSumo alternatives to Lusha. AppSumo deals can be great for small businesses. I've bought them. But if the deal gives you credits and no API, no SLA, and no path to connect the data to your AI SDR, then you're buying a cheaper version of the same spreadsheet problem. The 60% discount isn't a saving. It's a new tax on your team's time.

That's why I've changed my stance on pricing. When a deadline matters, I'll pay for certainty. In March 2024, a vendor offered us a rush data integration for an extra $400. We paid it because the alternative was a $15,000 campaign slipping to May. The campaign launched on time. The extra $400 felt painful, but it bought something more expensive than speed: it bought the lack of a panic.

What I do now: a short checklist

I keep this simple because the problem is already complicated enough.

  1. Ask for match rate on our CRM, not on the vendor's sample. If they can't run a match against a 500-account sample, that's a red flag.
  2. Ask for a verification timestamp. If a field says 'verified,' verify when. A phone number verified in 2022 is usually a wrong number.
  3. Set a credit budget for the AI SDR. If you use Lusha's pricing credits per month 2025 as a baseline, make sure the AI SDR can't spend more than X credits per day on a batch. Automation with no limits is a debt machine.
  4. Define an intent trigger you can explain in one sentence. For example, 'contact them if they've viewed our pricing page or searched for our category in the last seven days.' If you can't explain it, your SDRs won't trust it.
  5. Test the full agent-native flow before you scale. Enrich a lead, fetch intent, send an email, log the reply. If you can't do that without a person opening a CSV, fix that first.

The fix is a workflow, not a vendor

Looking back, my biggest mistake wasn't buying the wrong tool. It was expecting a tool to replace a workflow. Data enrichment, intent data, and AI SDRs are all useful. But they only create value when they're connected to the decisions your team actually makes.

So if you're starting this process today, don't begin with a price comparison or another AppSumo search. Begin by writing down how a lead moves from raw signal to outreach event. Who triggers it? When does the data get verified? What happens when the intent score is high but the contact is stale? That's the workflow. The platform comes after.

And when you do get to pricing, remember that certainty has value. As of January 2025, Lusha's pricing page is credit-based with monthly credits per user—you're paying for access to a stream, not a one-time pool. The best deal is the one you can actually operate under pressure. Not the one that looks good on paper.