Lusha: Trading Depth for Distribution

Lusha is spending its product effort on reach rather than depth. In July it shipped a natural-language prompt interface that builds prospecting lists from a plain-English description of an ideal account profile, explicitly positioned for AI agents through Model Context Protocol as well as human users. That follows a Scalestack partnership for agentic revenue operations and a Claude connector, and an Albato integration extending Lusha into over 1,000 applications including Airtable, WhatsApp for Business and ActiveCampaign.

Commercially, the entry tier got quietly more expensive. Lusha's Summer Sale discount on the Starter tier was logged moving from 35% to 25%, an effective change from $32.45 to $37.45 per month billed annually, while deeper 35% discounts held on Pro and Premium. We could not re-verify these figures: lusha.com/pricing returned HTTP 403 to our check on 5 August 2026. Treat the prices as logged in July, not as confirmed today.

The counter-signal is depth. Mid-market reviewers describe a threshold where teams outgrow Lusha and move to ZoomInfo or Apollo for firmographic detail and organisational mapping.

Lusha has read the direction of the category correctly. If buying decisions increasingly happen inside AI assistants and orchestration layers rather than inside a vendor's own UI, then being reachable from Claude, from Scalestack, and from a thousand no-code apps matters more than winning a feature comparison. Distribution into workflows is a genuine moat and it is harder to copy than a data field.

But it is a moat around a known limitation. The mid-market review pattern is consistent: Lusha is valued for speed and simplicity on one-off lookups, and abandoned when a team needs to map an organisation properly. Distribution makes Lusha present in more places; it does not make the underlying record deeper.

The pricing move is small but directionally interesting. Reducing the entry discount while protecting Pro and Premium discounts optimises for value per acquired account rather than volume of accounts — consistent with the Glassdoor signal describing a self-service pivot that reduces inbound volume to direct sales. Both readings are emerging-tier and one is single-source, so hold them loosely.

Do not lead with data depth alone, even though it is your strongest argument. A buyer evaluating Lusha at the entry tier has already decided that simplicity and speed matter more than completeness; telling them your database is bigger confirms their concern about complexity.

Lead instead with the migration story. The review evidence says Lusha customers leave when they grow, which means the competitive event is not the initial purchase but the moment a team starts mapping buying committees. Position for that moment: show what organisational mapping looks like, and make the switching path from Lusha explicit and cheap.

Where you do need to match Lusha is placement. A Claude connector, MCP support, Scalestack and 1,000-plus apps through Albato mean Lusha shows up inside workflows where your product may not appear at all. If a prospect's agent can call Lusha and cannot call you, depth is irrelevant because you are not in the conversation.

Their content programme is also worth answering. The talent-mobility and job-change reports are effective lead magnets built on a real buying trigger, and the Agentforce and Breeze playbooks stake a claim to being the default data layer inside two large CRM ecosystems.

• Can I build a list by describing my ICP in plain English, the way Lusha now allows?
• Can my AI agent reach your data directly through MCP, or do I have to use your UI?
• Lusha starts around $37 a month. Why is your entry price different?
• We are outgrowing simple contact lookups. Can you map a full buying committee and org structure?
• Do you integrate with Agentforce and HubSpot Breeze the way Lusha's playbooks describe?

1. This week: Audit your presence in the surfaces Lusha now occupies — MCP, Claude, Scalestack, Albato. Absence there is a bigger competitive gap than any data-coverage difference.
2. This month: Build an outgrowing-Lusha migration play aimed at teams moving from one-off lookups to org mapping. That is the documented churn moment.
3. This month: Answer the job-change signal content. Talent mobility is a real buying trigger and Lusha currently owns the benchmark asset.
4. Next quarter: Re-check Lusha's published pricing directly. Our automated check was blocked, and entry-tier pricing is moving.

Lusha is making a coherent bet that the interface layer is where sales-intelligence gets decided, and that being callable beats being comprehensive. Shipping natural-language list building with MCP support, a Claude connector and a Scalestack partnership inside a single quarter is real execution, not a positioning exercise.

The bet has an obvious flaw and Lusha appears to know it. Distribution does not fix depth, and the mid-market review pattern — teams leaving for ZoomInfo and Apollo once they need organisational mapping — has been consistent for months. Being present in a thousand applications matters less if the record returned is thin at the moment a deal gets serious.

Our read is that Lusha is optimising for a specific customer: the small or mid-sized team that wants fast, adequate data inside tools they already use, at a price point it is now nudging upward. That is a defensible position and a real business. It is not a position from which to win enterprise evaluations, and rivals should compete for the graduating customer rather than the first one. We would revisit if Lusha ships genuine org-hierarchy mapping; nothing in this quarter's signals suggests that is imminent.

• Lusha homepage — Lusha
• Lusha deepens AI-driven GTM role with Scalestack tie-up — TipRanks
• Lusha deepens AI and no-code integrations — TipRanks
• Lusha integrations — Lusha
• Push verified contacts straight into Capsule — Lusha
• Lusha pricing — Lusha (could not verify, HTTP 403 on 5 Aug 2026)
• G2 review: mid-market data depth — G2
• Lusha for HubSpot Breeze playbook — Lusha
• H1 2026 Talent Mobility Report — Lusha