How to Spot an AI Vendor Overselling Their Tool
Six oversold-claim patterns AI vendors use on small businesses, and the exact test to run in a sales demo to check each one before you buy.
Most AI vendors selling into small businesses are not lying to you. They are marketing a real product with claims stretched past what a live demo can actually survive. The tell is rarely in the slide deck. It shows up the moment you push past the scripted flow: a vendor overselling their tool dodges a specific request, gets vague about what happens when the system fails, or points to a customer reference that turns out not to exist at your scale. That is a different problem from an outright scam, and a narrower one than a full vendor security review. This is about legitimate products with inflated pitches, and the specific tests that expose the gap in a single sales call.
This is one piece of a bigger picture: our guide to using AI in a small business covers the full adoption landscape, from picking tools to avoiding the traps that waste a small budget.
Overselling is not the same as lying
A scam vendor invents a product, a client list, or a company. An overselling vendor has a real tool that does something useful, wrapped in claims nobody on the sales side has bothered to qualify. A separate pattern covers the outright fraud cases, the fake case studies and pressure tactics that mean the product does not exist at all. What follows here assumes the vendor is real and the tool works, at least somewhat. The question is whether it works the way the pitch says it does, for a business your size, on your actual workflow.
Six claims that mean an AI vendor is overselling their tool
These are the phrases that show up in almost every AI sales deck aimed at small business owners, and the specific test that separates a legitimate feature from a rounding-up of what the product actually does.
The claim | What it's papering over | The test to run in the demo |
|---|---|---|
"Fully autonomous" | Someone is still reviewing or correcting outputs behind the scenes | Ask them to run it live, unscripted, on a task you supply on the spot |
"99% accuracy" | Accuracy on what, measured how, on whose data | Ask for the denominator: 99% of what population, tested against what ground truth |
"Replaces your whole team" | It replaces the easy 80% and leaves the hard 20% to a human anyway | Ask what happens on the failure case, in front of you, not in the FAQ |
"Works out of the box" | Setup, integration, and tuning that happened before the demo, not before your launch | Ask a reference customer how many weeks it took them to get real value, not a headline |
"We work with [big brand]" | One logo customer using one feature, not proof the tool fits a business your size | Ask for a reference call with a customer at your scale, not the flagship name |
"No hallucinations" | A model that is confidently wrong less often, not one that is never wrong | Ask what the tool does when it does not know, and who sees that moment |
Three questions that do most of the work
You do not need a checklist of forty questions. Three do most of the work, and they are the same three underneath every row in that table above.
Ask for a live, unscripted example using a task or a document you bring, not the one built into the demo script.
Ask what happens on the failure case, specifically, and watch whether the answer is a real workflow or a shrug.
Ask for a reference customer at a size and industry close to yours, not the largest logo on the website.
A vendor with a solid product answers all three without flinching, often by showing you the failure case themselves because they already know where it is. A vendor overselling the tool will steer around at least one of them, usually the failure case, because admitting the tool needs a human backstop undercuts the pitch that just replaced one.
Where this fits next to vetting and scam checks
Once a tool passes these tests on its merits, the job is not finished. A full vendor vetting pass covers the parts a good demo cannot show you: how the vendor handles your data, what the contract actually commits them to, and what happens if they get acquired or shut down. That is a broader, later stage check. What sits above is earlier and narrower: does the product do what the pitch claims, at all, before you get anywhere near a contract. Whether the honest answer is to build the thing yourself instead of buying it is a separate decision worth making before you sit through any demo.
The "replaces your whole team" claim deserves its own gut check, since it is the one most small business owners actually have to act on. Whether to hire a person or lean on AI first is a real tradeoff with a real answer for most roles, and it is rarely the clean swap the pitch describes.
Frequently asked questions
How do I know if an AI vendor is lying to me or just overselling?
A vendor overselling a real tool will still show you something working when pushed, even if it is weaker than the pitch. A vendor running an outright scam will stall, dodge a live demo entirely, or produce references that do not check out when you actually call them. See the patterns specific to outright scams here if the stalling looks total rather than partial.
What questions should I ask an AI vendor before buying their tool?
Ask for a live unscripted demo on a task you bring, ask exactly what happens on the failure case, and ask for a reference customer at your scale, not their biggest logo. Those three questions surface most inflated claims faster than any written checklist.
Is a claimed 99% accuracy rate a red flag for an AI tool?
Not by itself, but an unqualified one is. Ask what population that 99% covers, how it was measured, and against what ground truth. A vendor who can answer precisely usually has a real number. A vendor who repeats the figure without specifics is usually rounding up.
Should I ask an AI vendor for a reference customer before signing?
Yes, and specifically one close to your size and industry. A reference from a much larger company tells you the tool works for their budget, their integration team, and their volume, not necessarily for yours.
What is the difference between spotting an oversold AI tool and vetting an AI vendor?
Spotting overselling happens in the demo, before a contract exists, and asks whether the product does what the pitch claims. Vetting a vendor happens after that, and covers data handling, security, and contract terms for a product you have already confirmed actually works.
How did this land?
About the author

Senior Editor, AI & Product
Cecilia leads the Swarmz editorial desk. She has spent a decade turning complex AI and product topics into writing people actually finish, and she owns the blog's quality bar.


