Lusha Setup Guide for Outbound Sales Teams (2026)

Most teams install Lusha in an afternoon, burn through a month of credits in the first week, and conclude the data is bad. This Lusha setup guide for outbound teams exists to prevent exactly that, because the problem is almost never the data. It is the missing setup around it.

Lusha is a B2B contact and company data platform: a browser extension that pulls contacts from LinkedIn, a prospecting platform for building lists, an API, and native CRM integrations, with notably strong direct-dial coverage and European data. Pricing is credit-based, every revealed contact spends from a pool, and that one design choice is why setup discipline matters more here than with flat-rate tools.

The eight steps below are the same configuration we use when we wire Lusha into the outbound systems we build for clients: plan selection, the extension workflow, ICP filters, CRM wiring, enrichment routines, credit governance, verification, and the push into your sequencer.

Step 1: Pick the right plan and seat count

Lusha's tiers break down like this, as of this writing:

Two decisions matter more than the tier itself. First, test before you buy: run the free tier against 50 contacts you already know in your exact market and count how many emails and direct dials come back accurate, because coverage varies by geography and industry. Second, buy seats only for people who actually prospect. Credits pool across the team on paid plans, so three active seats sharing a healthy pool beat eight seats bought just in case.

Pricing shifts, so verify current numbers before committing; our Lusha pricing guide keeps a tier-by-tier breakdown.

Step 2: Install the extension and set the LinkedIn workflow

The Chrome extension is where most Lusha usage happens: open a LinkedIn profile or a Sales Navigator search, and it reveals emails and direct dials for the person on screen, then saves them to a list.

Install it from the Chrome Web Store, sign in, and set one team rule immediately: reveal only contacts that pass your ICP definition. The extension makes spending credits feel free, one click per contact, and a rep browsing loosely can spend fifty credits in an afternoon on companies you will never sequence. The habit that protects the pool: qualify the company first, then reveal the person.

Step 3: Build ICP filters in the prospecting platform

The prospecting platform is Lusha's searchable database, and it is where list building should happen, not through ad hoc profile visits. Translate your ICP into saved filters: industry, company headcount, geography, and seniority or job title.

Build one saved search per segment and name it plainly, something like "US manufacturing, 50 to 500 employees, operations leaders," so every export inherits a segment identity. That naming discipline pays off in Step 8, when you measure which segments actually produce buyer conversations.

Step 4: Connect your CRM with field mapping and dedupe rules

Lusha integrates natively with HubSpot, Salesforce, and Pipedrive. Connect it before the first export, then make two configuration decisions.

Field mapping: decide where each Lusha attribute lands, direct dials into the mobile field rather than the company line, and add a source field stamped "Lusha" with the enrichment date, so you can audit data quality by source later.

Dedupe rules: match on email address before creating any record, and set the overwrite policy deliberately. Our default: Lusha fills empty fields but never overwrites a value a rep entered by hand. Without that rule, one bulk enrichment can silently replace fresh, human-verified data with older vendor data.

The Salesforce wiring has its own quirks around flows, duplicate rules, and permission sets, covered step by step in our Lusha Salesforce integration guide.

Step 5: Configure enrichment workflows

Beyond one-at-a-time reveals, Lusha's bulk enrichment fills gaps in lists you already own. Two routines earn a permanent spot on the calendar.

Enrich inbound and event lists as they arrive: upload the CSV, map the columns, and let Lusha append direct dials and verified emails before the list ever reaches a rep. A form fill with a phone number attached gets called; one without usually gets a single email and dies.

Refresh stale records quarterly. Contact data decays as people change roles, and the oldest segment of your CRM is quietly rotting. A quarterly re-enrichment pass on active target accounts catches job changes, and a job change is more than hygiene: a champion who moved is a warm door into a brand new account.

Step 6: Set credit rules and usage governance

On team plans, admins can set credit limits per user and review usage analytics. Use both from day one.

Set monthly per-seat limits that sum to less than the full pool, holding back a reserve of roughly 20 percent for bulk enrichment runs and end-of-quarter pushes. Then review the usage report monthly: who is spending, on which segments, and with what reply rate downstream. Governance sounds bureaucratic until the alternative arrives.

Step 7: Verify every email before it reaches the sequencer

No data vendor is perfect, and even accurate data ages between the reveal and the send. Run every Lusha export through an independent email verification layer before it touches your sequencer, and sort the results into three buckets: verified addresses go to sequencing, catch-all and risky addresses go to a low-volume segment or LinkedIn-first outreach, and invalid addresses get deleted, not tried anyway.

The target is hard bounces under 2 percent. Above that line, mailbox providers start reading you as a mass sender, and the damage lands on your sending domains, which take weeks to recover. Verification costs a fraction of what a burned domain costs.

Step 8: Push to the sequencer and measure quality by segment

Push verified contacts into your sequencing tool, Smartlead, Instantly, or whatever runs your sending, with the segment name from Step 3 riding along as a tag.

Then close the loop monthly. For each segment, read three numbers: hard bounce rate, which reflects data quality; reply rate, which reflects targeting, with 1 to 5 percent as the healthy cold email band; and positive reply share, which reflects the message, at 15 to 50 percent of total replies on a well-matched list. We do not track open rates at all, because the tracking pixel hurts deliverability and tells you nothing a reply does not.

Segments that hold up on all three earn more credits next month. Segments that bounce or go silent get rebuilt before they get re-exported. The day-to-day operating rhythm on top of this setup is in our guide on how to use Lusha for lead generation.

A note on GDPR for EU prospecting

Lusha's European coverage is a real strength, and prospecting into the EU carries real obligations. Cold B2B outreach in most EU markets rests on the legitimate interest basis, which in practice means: contact people whose role plainly relates to your offer, say who you are and why you are writing, include a working opt-out in every message, and honor removals across the whole stack, the CRM, the sequencer, and your Lusha lists alike. Rules differ by country, so have counsel sanity-check your approach before scaling EU volume.

Where Lusha fits in the bigger machine

Set up this way, Lusha becomes one strong source inside an enrichment waterfall: ICP filters feed it, verification guards its output, the CRM stays clean, and the sequencer receives only contacts worth a send. That surrounding system is what we build. We orchestrate 20-plus tools, Lusha among them when it fits the market, into one outbound machine the client owns outright.

Work through the eight steps before the first export, and the credit pool starts behaving like a budget with a return, not a meter that runs out mid-quarter.

Ready to turn verified data into booked meetings?

A well-configured Lusha stack gives you accurate contacts; the system around it turns them into qualified meetings. We orchestrate the full machine, enrichment, verification, sending infrastructure you own, and reply handling, with results guaranteed from a free pilot onward.

Book your free pilot →