The Revenue AI Report

AI Tech Landscape · Social Media & Outreach Automation

Dux-Soup

LinkedIn Automation

Visit Dux-Soupdux-soup.com

LinkedIn automation tool for lead generation, outreach, and relationship building with AI-powered personalization.

Journey stage
Prospecting
Ambition level
Optimize
Owning seat
Sales

What it claims to do

  • Connection Messages
  • Content Strategy
  • Profile Auto-Visiting
  • Data Export
  • Drip Campaigns

Claimed benefit. Scaled outreach capabilities, consistent pipeline generation, time efficiency

Reported use case. SDR teams automating initial outreach to targeted account lists

Source: the vendor and the capability mapping work behind this map. The Revenue AI Report has not independently verified these figures. Verified findings live in Research, with method, sample, and field date attached. Unfamiliar terms are defined in the AI and Revenue Dictionary.

Published case studies

We found a minimum of 3 published case studies here. There may be more we have not found. Case studies are published by the vendor. Customer names, figures, and outcomes are the vendor's claims. The Revenue AI Report has not audited them. Independently checked findings live in Research, with method, sample, and field date attached.

How to read these claims

The sample is chosen by the seller
A case study is the best result the vendor is allowed to publish. It is not a sample of all customers. The accounts that churned do not get a page.
There is no control group
Almost no vendor study compares the team using the tool against a matched team that did not. Without that comparison, the lift reported cannot be separated from headcount changes, pricing changes, seasonality, or a good quarter.
The baseline is usually missing
A percentage gain means nothing without the starting number. A 300% increase in meetings from two meetings a week is eight. Ask for the absolute figures and the time window.
Activity is not revenue
Most published gains are activity metrics: emails sent, replies, hours saved, meetings booked. Closed revenue, win rate, and retention are the metrics that survive a board meeting. Ask which one the study actually measured.
Named logos are not always customers
Logos and case studies have been published for accounts that had already churned or had only run a pilot. Ask the reference directly, by name, and ask how long they have been live.

Field notes: what users say in public

Independent feedback from review sites and practitioner forums, not vendor marketing. This is what a buyer would hear from a peer who has already run the tool.

4.7trustpilot.com, 42 reviews, observed 2026Check the live score ↗

What holds up

  • No repeated praise found in independent sources.

What people complain about

  • No repeated complaint found in independent sources.

Trustpilot rating is solid but review volume is small; verify current LinkedIn compliance risk directly before relying on it for outreach at scale.

Ask these on the call

  1. 01Ask about current LinkedIn ban risk and how the tool paces activity to stay within limits.
  2. 02Ask about support responsiveness, since automation tools often need quick fixes when LinkedIn changes its UI.
  3. 03Ask how pricing compares across the browser extension versus cloud-based plans.

How to read review evidence

Review sites are a biased sample
Most reviews are collected by the vendor, often with an incentive attached. Scores cluster high across the whole category, so a 4.6 average is closer to par than to proof. Read the one and two star reviews first, and read the most recent ones, because product and pricing change faster than the average score does.
Forums show the failure modes, not the base rate
Reddit and Hacker News threads surface what breaks, which is exactly what a business case needs. They do not tell you how common the problem is. Treat a repeated complaint as a question for the vendor, not as a verdict.
Complaints about price are usually complaints about structure
Seat minimums, credit packs that expire, annual lock-in, and per-action pricing produce most of the pricing anger in public reviews. Get the structure in writing, not the headline number.
Ratings are a snapshot
Every score here is dated. Check the live page before you cite it in a board deck.

The friction above is the tool level version of a pattern the Report has already measured. See The proof gap for the method, sample, and field date behind it.

Claims versus the record

No citable discrepancy between this vendor's public claims and independent reporting was found at the time of the last check. That is not verification. It means nothing has been published either way, so the claims above still rest on the vendor's own account.

What has to be true before you buy

The Report does not review tools in isolation. Every tool on this map is connected to three things we publish elsewhere on the site: a decision framework that tells you how to evaluate it, a research theme that shows what we have measured in the market around it, and an essay that applies both to a real case. Those links appear at the bottom of this section so you can verify our reasoning instead of taking this page at face value.

Ambition level: Optimize

Same process, less time. Judge it on hours returned and data hygiene, not revenue.

Get accepted and qualified rates, not meetings booked, before the contract is signed.

Friction at this stage

  • Dirty lists and stale contact data
  • Generic personalization
  • Manual account research

The framework to apply

BUILD / BUY / THREAD is the decision framework the Report uses for tools at this stage. Decides whether an agent is bought, built, or threaded into what you already run.

The research behind it

The proof gap is the market evidence we have published for this category, with method, sample, and field date attached. How thin the published evidence is behind autonomous prospecting claims.

The essay that applies it

AI SDR unit economics shows this framework and this evidence applied to a real situation, so you can see the reasoning end to end.

Common questions about Dux-Soup

What does Dux-Soup do?
LinkedIn automation tool for lead generation, outreach, and relationship building with AI-powered personalization. It sits in the Social Media & Outreach Automation category and maps to the Prospecting stage of the revenue journey.
Where does Dux-Soup fit in a revenue team?
Dux-Soup maps to the Prospecting stage at the Optimize level of ambition, and is usually owned by the Sales seat. Reported use: SDR teams automating initial outreach to targeted account lists
Does Dux-Soup publish customer case studies?
Yes. 3 named customer stories are published, including Target Connect, Client Matchmaking, HG Insights. These are vendor claims, not figures verified by The Revenue AI Report. A case study is the best result a vendor is allowed to publish, not a sample of all customers.
What do buyers say about Dux-Soup?
Public score 4.7 on trustpilot.com from 42 reviews, observed 2026. Trustpilot rating is solid but review volume is small; verify current LinkedIn compliance risk directly before relying on it for outreach at scale.
What should we ask Dux-Soup before buying?
Ask about current LinkedIn ban risk and how the tool paces activity to stay within limits. Ask about support responsiveness, since automation tools often need quick fixes when LinkedIn changes its UI. Ask how pricing compares across the browser extension versus cloud-based plans.

Answers are assembled from the vendor material, published case studies, and independent evidence shown on this page. Terms are defined in the AI and Revenue Dictionary.