I Review Lead Data for a Living. Here’s What I Checked Before Approving Lusha for Our Sales Team

2026-08-18 · Julian Hartwell

It was a Tuesday afternoon when a lead list I’d approved came back to haunt me. One of our SDRs had spent two hours calling an ‘IT Director’ at a company that, according to the database, had 500 employees. The company actually had 12. And the IT Director hadn’t worked there for seven months.

The list had passed our standard checks. The emails were formatted correctly. The phone numbers looked like real phone numbers. The titles matched our buyer persona. But the data didn’t reflect reality. That’s worse than empty data, because it burns trust.

I’m the quality and compliance manager for a B2B SaaS team. I review every contact dataset and data integration before it reaches sales—roughly 200 unique deliverables a year. In 2024, I rejected 14% of first deliveries due to verification gaps.

That Tuesday changed how I evaluate lead generation tools. At least, that’s been my experience working with small, focused sales teams. It’s also why, months later, when our RevOps team started evaluating Lusha, I didn’t just ask ‘is the data good?’ I asked ‘what could make this data fail in our workflow?’

When I First Started Reviewing Data Vendors, I Assumed More Contacts Meant Better Options

My initial approach to lead data was completely wrong. I thought a bigger B2B contact database meant more opportunities. But 10 million records from a company that never updates them isn’t an opportunity. It’s an audit problem.

We learned that the hard way. A data quality issue cost us around $22,000 in wasted SDR hours and delayed a product launch sequence by a week. The vendor kept saying their match rate was ‘within industry standard.’ I kept asking which standard they were using. That was the moment I started designing our own verification protocol.

Now, every contract for data includes requirements around freshness, verification, duplicate handling, and API response quality. But before any contract, I check three things:

  • How the data is verified, not just where it comes from.
  • How it behaves when it enters our tools, not just how it looks in a CSV export.
  • How tracking and reporting reflect reality, not vendor-defined ‘success.’

That last one is the one most RevOps teams miss.

What I Actually Looked At for Lusha

Let me walk through the evaluation, because it wasn’t magic. We used Lusha’s official pricing page, their public developer docs, and a 500-contact pilot against our own ICP.

Lusha Pricing Official: Start With the Source, Not a Blog

When someone searches ‘lusha pricing official,’ they should land on lusha.com/pricing. That’s what I did. I didn’t start with a third-party blog or a forum comment from two years ago.

I was looking for a few things on the official page:

  • Is the plan structure clear—credits, exports, API access, seats?
  • Are there separate add-ons for API company data or email verification?
  • Is there enough detail to compare our current tool without requesting a 30-minute demo?

I won’t quote the exact numbers here because we negotiated an annual plan, and prices change (which, honestly, is the norm for B2B tools). Honestly, the exact price matters less than whether the pricing model matches your usage pattern. Our team needed API company data for enrichment and email verification for outbound. If the page hadn’t been transparent about those, I would have flagged it. I also use the same logic from FTC business guidance: when a vendor says a record is ‘verified,’ I want to know what substantiates that claim. Vague verification language isn’t data.

The Lusha B2B Contact Database: Sample the Data, Then Write an Audit Checklist

Next, we pulled 250 contacts from Lusha’s B2B contact database—or rather, we pulled a sample of about 400 potential matches and narrowed it to 250 that fit our strict ICP: U.S.-based B2B services companies with 50 to 500 employees, a specific persona, and a confirmed work email or direct dial.

Then we cross-checked each record for domain validity, employee count consistency, and email bounce behavior in a test send. Some records failed. That’s normal. But the failure rate was substantially lower than our current provider, and the failures were easy to spot. That’s the thing I care about most: predictable weaknesses. A database that fails predictably lets us build safeguards. A database that fails randomly is chaos.

API Company Data: Check the Schema, Not Just the Endpoint

We also connected to Lusha’s API for company data. I checked the API response schema, rate limits, and how often the data is refreshed. This matters for automation workflows because they inherit whatever the API returns. For example, if the employee count field is a range rather than a number, your segmentation logic needs to handle that. If the API returns duplicate records under different legal entity names, you need deduplication rules. The public developer docs answered these questions before the pilot.

Seeing what the API returned made me realize something: a lot of API company data tools document beautifully but return messy fields. Lusha’s response structure was clean enough for our analytics pipeline. But we still built validations on top—no single source gets a free pass.

The Email Tracking Disconnect That Almost Broke the Rollout

Here’s where the story takes a turn. After three weeks, I approved Lusha for a controlled rollout. The data looked good, the API behaved, and our SDRs liked the interface. I sent a Slack message saying ‘green light.’

The next morning, our RevOps analyst flagged a strange bounce report. Emails to some of the new contacts were bouncing with ‘invalid domain.’ But our email tracking tool was still recording them as ‘opened.’ Not just ‘sent’—opened.

I pulled the logs. We found 41 contacts where the email bounced but the tracking pixel fired anyway. The sequence tool was probably counting a cached message or an automatic state change as an open. Whatever the cause, the result was a false positive. A human would read that report and believe those prospects were engaged. They weren’t.

At first, I thought it was Lusha’s problem. It wasn’t. The data was accurate—the verification result was there, and the API flagged the invalid domains. The problem was the handoff between Lusha, our sending tool, and our email tracking configuration.

Basically, the data was fine. The process wasn’t.

What Should Revenue Operations Teams Evaluate in Email Tracking?

This is the question I wish we had asked on day one.

Most buyers focus on whether the contact database has a good match rate. They completely miss how tracking handles hard bounces. But for RevOps, the more important question is: what happens to a contact after a tool says the email is ‘valid’?

Here’s what I now check with any email tracking setup:

  • Bounce syncing. Does a hard bounce automatically suppress that contact from future sequences, or does it stay in the ‘open’ list and distort your reporting?
  • Open vs. delivered. Does the tool distinguish between ‘delivered’ and ‘opened’? If it doesn’t, an invalid address can falsely look like engagement.
  • Verification handoff. Is email verification run at the moment of export, or only when the record is added? We needed real-time verification before sending, not a one-time check.
  • Consent and suppression. Can you sync opt-outs and unsubscribes back to the database? Otherwise, you’re multiplying bad touches.

When I compared our pilot data—valid emails that were sent, valid emails that were opened, and invalid emails that should have never hit the send queue—the difference was stark. The tracking tool had been giving us a ‘healthy’ deliverability rate that did not match reality. That contrast insight is the reason I no longer approve a lead gen tool without checking the tracking layer.

The Outcome, and the Lesson

We didn’t cancel the rollout. We paused it—or rather, we slowed it down enough to fix the integration. We added a rule: no email goes out until the address passes both Lusha’s verification and our own sending platform’s validation. It added a few seconds per lead, but it saved us from another round of phantom opens.

The upside of moving forward was cleaner data and a faster list-building workflow. The risk was that we’d lose confidence if tracking kept lying to us. I kept asking myself: is faster lead gen worth another reporting cleanup? Eventually, the answer was yes—because the root cause wasn’t the database. It was our workflow.

Here’s what I want you to take from this:

A contact database is only as valuable as the process around it. The best lead gen data in the world won’t help you if your email tracking counts bounces as opens.

If you’re evaluating a tool like Lusha—or any B2B contact database—use their official pricing page and API documentation. Run a pilot. Check the data. But don’t stop there. Test the full path from database to email click. That’s where quality is really decided.

Trust me on this one. I’ve been burned by the part of the process nobody checks.