Disclosure: we build Prospectio, a competing product.
What Dux-Soup is
A Chrome extension that automates LinkedIn actions: visiting profiles, sending connection requests, messaging, endorsing. Turbo adds drip campaigns. Cloud runs the whole thing on their servers so it doesn’t depend on your browser being open.
What it does well
Longevity and stability. Nearly a decade in a category where tools disappear. It does what it says.
Profile visiting at scale. The original use case and still a decent one. Visiting a few hundred relevant profiles a week generates real inbound profile views and occasional inbound messages, at almost no risk.
Price. Cheap across all tiers.
Simplicity. Small feature set, easy to understand.
Where it’s behind
Personalisation. Basic merge fields. Nothing reads the prospect.
Architecture. The extension version has all the detection and availability problems extensions have. The cloud version fixes availability but the product wasn’t designed cloud-first.
Reply handling. None to speak of. Replies go to your LinkedIn inbox.
Interface. Functional and dated. Not a dealbreaker, but you notice it next to newer tools.
Who should use Dux-Soup
- Anyone who mainly wants automated profile visiting as a soft-touch inbound tactic.
- Very low-volume users who want the cheapest thing that works.
Who shouldn’t
- Teams running outbound as a primary pipeline source.
- Anyone who needs personalisation beyond a first name.
The verdict
Fine for what it is, which is a light-touch activity tool. If outbound is how you generate pipeline, this isn’t the system to build it on.