Lusha's Waterfall U-turn, Outreach's Claude Play, and the Data Trust Gap

Lusha is now selling waterfall enrichment. The product update adds a Data Waterfall section that checks additional sources when Lusha lacks a work email or phone, billed per successful match and available on Pro plans and above. The important detail for your next call: earlier copy had marketed 'no waterfalls'. That is a direct reversal, and it lands in the same week two one-star Capterra reviews hit Seamless.AI. Buyers are already wary of enrichment vendors that promise complete coverage and then charge per match.

One-line talk track: 'Waterfall is a coverage tactic, not a data-quality guarantee. The question is not how many sources you cascade through; it is who owns the match, how you audit accuracy, and what happens when the first source is wrong.'

When a prospect says Lusha now does waterfall, do not argue coverage. Move the conversation to provenance, match rates by segment, and billing predictability. Ask how they will measure false positives, not just fill rates. If your team sells a data or enrichment product, this is your week to lead with validation and auditability.

1. Lusha adds waterfall enrichment When you hear: 'Lusha added waterfall enrichment, so they can fill more fields.' Say: 'Waterfall helps with fill rate, but it can also hide where a record came from. If your team is paid on connect rates, you need to know which source produced the match and how it is validated. Ask Lusha for match accuracy by job function and country, plus the per-match billing rules. Then compare that to the cost of bad data in your sequences.'

2. Outreach integrates with Claude and lists on Salesforce AgentExchange When you hear: 'Outreach is embedding into Claude and Salesforce AgentExchange.' Say: 'That is useful for teams already living in Claude or Salesforce. The real question is governance: what deal data leaves your CRM, how are permissions enforced, and can you audit the answers Claude gives? If your reps are asking an AI assistant for forecast and account answers, you need a clean data model underneath. Otherwise you are automating guesswork.'

3. Apollo becomes Salesforce Hunter's flagship data partner and launches Agents When you hear: 'Apollo is the flagship data partner for Salesforce's Hunter Agent, so we get Apollo data without a separate contract.' Say: 'Distribution is not the same as fit. Embedded data is convenient, but you still need to control which contacts enter your CRM, how consent is managed, and how you prevent duplicates. Ask how the Salesforce agent handles exclusions, opt-outs, and territory rules. If it cannot respect your RevOps logic, free data becomes expensive cleanup.'

Also watch: Gong has stood up an Industry Expansion team targeting Financial Services, with healthcare, consulting, manufacturing, and energy as secondary verticals. Verticalised GTM means your financial services deals will face a competitor with a tailored story. Prepare a regulated-industry proof point before your next enterprise deal review.

Two fresh 1.0-star Capterra reviews landed for Seamless.AI this week. Even with no long-form text, a one-star rating is a loud buying signal. It usually means the buyer felt misled on deliverable quality, not that a feature was missing. Pair that with Lusha's waterfall reversal and you have a clear theme: data vendors are under pressure on trust.

Buyers are asking harder questions about enrichment: - 'How do you stop false positives?' - 'What happens when a match is wrong — do I get a credit?' - 'Can I see the source of every field?' - 'Will this create duplicates or compliance risk in my CRM?'

Your job is not to defend your data. It is to make the evaluation concrete. Offer a sample audit: take 200 records the buyer already knows, run them through your process, and score accuracy by segment. Do it before pricing. When a competitor leads with coverage volume, you lead with verified outcomes. That is how you turn a one-star category problem into a trust advantage.

Objection-handling line: 'If the first source is wrong, a waterfall just makes the wrong answer arrive faster.'

This week, update one battlecard. Add a 'data provenance and billing' module for any competitor now selling waterfall or embedded data. Include three questions your reps must ask: 1. How is match accuracy measured, and by whom? 2. What are the per-match billing rules when a field is wrong or unusable? 3. How does the vendor prevent duplicates, opt-outs, and CRM permission conflicts?

Then run a 15-minute deal review on your open enrichment and sales-data deals. Ask each rep: 'What does the buyer believe about waterfall, and have we shown them an audit?' If the answer is no, book the audit before the next pricing conversation. For sales leaders, add this to your Monday pipeline call. RevOps should own the questions; reps should own the sample audit request. Do it once this week, and you will expose the gap between coverage claims and pipeline-ready data.

Competitive moves land fast. Your team does not need more noise; it needs the three signals that change a deal. IndustryLens tracks your competitors, pairs every move with a talk track, and sends a 90-day brief to your inbox. Pick three competitors, drop your email, and see what your next call should sound like. Track your own competitors — free. Pick 3, drop your email, get a 90-day brief back in your inbox → https://industry-lens.com/free-competitor-radar