The Dux-Soup Data Enrichment Checklist I Wish I Had: Bulk Email, Intent Data, and Free Version Features

Start with data enrichment, not automation speed. If you're looking at Dux-Soup because you want to automate LinkedIn prospecting and then send bulk email to the contacts you collect, the first question isn't how many profile visits you can automate. It's whether the data you're about to put into that workflow is worth using. I ran Dux-Soup for about two years, and the mistake I remember most clearly was a 1,412-recipient bulk email campaign with a 9% bounce rate and a three-week recovery delay. The tool wasn't the problem. My checklist was. Start with data enrichment, not automation speed.

I should mention: that lesson cost me about $2,600 in rework, lost time, and a bruised sender reputation. Since 2021, I've run prospecting operations for two SaaS teams, and I've personally made and documented four significant data mistakes. None of them came from a dramatic platform failure. They came from moving too fast on details that felt minor at the time.

Why I'm Not a Neutral Observer

First, let's clear up the search phrase: the official name is Dux-Soup, but many people type Dux Soup Chrome extension, and the correct tool still shows up. The Dux-Soup Chrome extension sits on top of LinkedIn. It can visit profiles, send connection requests, and export the public data you see on a profile into a CSV or a CRM. For me, it turned the boring part of prospecting into something I could delegate to a tool.

But Dux-Soup is not a replacement for data enrichment. It's an automation layer—which, honestly, should have been obvious to me. It handles a specific part of the workflow. It doesn't decide whether the rest of your data is good enough to send.

What the Dux-Soup Free Version Features Do (and Don't Do)

Here's the honest summary of the Dux-Soup free version features I tested: the free tier is a test drive, not a full pipeline. It includes enough daily LinkedIn actions to learn how automated connection requests feel to you and to the person receiving them. For a small team, the free tier is a no-brainer as a testing tool. As of January 2026, Dux-Soup's pricing page still shows a free plan. The exact daily limits change, so check the page before you build a budget.

On my team, I ran a 50-profile test on the free plan before recommending a paid plan. That test exposed a bigger problem: our targeting list was full of titles that didn't match the profile data we actually wanted. If you're just starting out, the free version can teach you a lot about your own targeting. But if you're hoping the free tier will quietly produce a list of 5,000 verified contacts, you'll be disappointed. That's not what it's for.

Bulk Email: Where Good Data Goes to Die

Bulk email is the part where I failed. I built a list of 1,412 contacts from three sources: a Dux-Soup export, an enrichment API, and a CRM pull. I merged them by looking for a non-empty email field and called it clean. I should have filtered by verified date and role-based address rules. But I was in a hurry and thought, what are the odds? The odds caught up with me.

We sent the campaign and saw a 9% bounce rate. That number doesn't sound catastrophic until you realize it triggers spam complaints and hurts your sending domain. The next campaign went into inboxes at a noticeably lower rate. The recovery took about three weeks. The total cost was roughly $2,600 when I added up SDR time, the redesign of the sequence, and the lost momentum from a quieter inbox.

I also cut one corner on purpose: I skipped a higher-accuracy enrichment pass because it would have cost about $60. That decision made the story worse. Saving $60 on the front end created a $2,600 problem on the back end. Now I say plainly: 5 minutes of verification beats 5 days of correction.

Intent Data: How It Works (and Doesn't)

Every RevOps conversation eventually reaches intent data. If you've ever searched for intent data how it works, you've probably seen the same generic definition I did. Here's the practical version: an intent data provider tracks content consumption, searches, and form fills across a network of websites. It groups those signals by company or IP address, then assigns a score. A high score means that company is researching a topic in your space. It does not mean the right buyer is ready to talk.

What most people don't realize is that intent data is a research signal, not a buying signal. The person reading a comparison page for LinkedIn automation tools could be a sales manager, a consultant, or a competitor doing research. Intent data tells you where to look, not who to call. Vendors won't usually say that loud.

In a Dux-Soup workflow, intent data should come before the connection request. Use it to decide which companies to target. Then use Dux-Soup to find the right people at those companies. If you do it in the opposite order, you end up with a pile of LinkedIn connections to companies that haven't shown any interest.

What Should Revenue Operations Teams Evaluate in Data Enrichment Features?

After my mistakes, I built a framework for evaluating data enrichment features. If you're a RevOps lead, these are the five questions that matter most to me now.

• Last verified date. A field that says verified means nothing without a date. An email verified fourteen months ago is a guess. Ask the provider for the date and treat anything older than six months as a risk.
• Verification method. Did the tool check the actual mailbox, or did it just look at the format? A syntax check will happily accept [email protected] and [email protected]. Those are role-based addresses, not personal contacts, and they cause problems in bulk email campaigns.
• Coverage vs. match rate. Coverage is the percentage of records that have an email address. Match rate is the percentage that are actually correct. A provider with 90% coverage and 70% match rate is worse for outreach than one with 60% coverage and 95% match rate. I learned this after seeing we had 1,412 emails and maybe 1,100 were safe to send to.
• Source and compliance. Where did the data come from? If a provider can't describe its sourcing in a way that passes a basic privacy review, that's a red flag. Under GDPR and other privacy laws, you need a legal basis for storing and contacting people. Get the documentation before you buy, not after.
• Export and field mapping. Can the enriched data flow cleanly into your CRM or sequencing tool? If your SDRs have to fix fields manually, those manual fixes will create the next mistake. I prefer tools that let me define which fields are required before a record is marked complete.

The best enrichment feature I could ask for is not a bigger database. It's an honest last-verified timestamp and a verification method I can trust. If a vendor gets vague on those, I move on.

When This Advice Doesn't Apply

If you're sending fewer than 500 emails a month, you probably don't need a heavy enrichment stack. The Dux-Soup free version plus a spreadsheet and a manual review of 50 records can be enough for a side project or a small team. If you're in a regulated sector like finance or healthcare, get legal review before you build any data sourcing into a workflow. And check LinkedIn's current terms around automation; platform rules change, and I don't pretend to know every one of them.

Bottom line: Dux-Soup is a useful tool, but it won't fix bad data. Use the free version features to test your targeting. Use bulk email only after you've verified the list. Use intent data to prioritize companies, not to predict the next purchase. And build the checklist before you hit send. Prevention is cheaper than recovery.