I asked an AI to fact-check a $12,000 sales pitch

Split composition: a marketing presenter on stage beside a slide of claimed statistics stamped NOT TRUE, and an AI face alongside a verdict list marking six of seven claims false or misleading and one accurate.

Framing — Michael Purvis

I went to a paid marketing workshop this week and came close to buying the $12,000 program at the end. I didn't. On the drive home I felt sick, and I couldn't tell whether that was good instinct or just buyer's remorse arriving early.

So I gave the recording to Claude and asked it to check the claims against public sources.

I'm publicly an advocate for AI as augmentation rather than replacement, so I've published its findings below in its own voice rather than rewriting them in mine. I'd rather show what AI-assisted verification actually looks like — including the part where it tells you not to trust it — than launder the work through my byline and take the credit. The presenter is not named. Everything below is the model's text.

I'm Claude, a language model made by Anthropic. Mike gave me a four-hour transcript — about 218,000 characters — and asked four questions: score it against his business principles, find the contradictions, find claims that were made and then broken, and flag statements that were probably untrue.

Here's what I did, what I found, and — the part I think matters more — where you shouldn't trust me.

What I actually did

I read the transcript end to end. I pulled out every statement of fact that contained a number or named a source. That gave me seven checkable statistics. I ran eight web searches against them. Then I cross-referenced statements against each other across the full four hours, looking for places where a claim made at 00:19 was reversed at 00:50.

That's it. It took a few minutes. It is not clever work. It is the kind of work a person could do and almost never does, because after eight hours in a hotel ballroom nobody goes home and cross-indexes a transcript.

What I found

Six of the seven checkable statistics don't hold up.

  • "Eighty-nine percent fail in five years. These are all verifiable numbers by the SBA." — SBA and BLS data show roughly 49% survive five years. A federal agency was named as the source for a figure it doesn't publish. That number returned 65 minutes later, aimed at the audience: "Eighty-nine percent of you don't have what it takes."
  • "Divorce rates have almost doubled in the last ten years." — They fell, from about 9.8 to 7.1 per 1,000 married women. This was the base of an argument: divorce rates prove nobody trusts anyone, which proves you need 29 touchpoints to close, which is why you need the full stack being sold. The foundation points the other way.
  • "Thirty-eight percent of people are on mental health medication." — CDC, 2023: 11.4% of adults took prescription medication for depression.
  • "Eighty-eight percent of people live paycheck to paycheck." — Self-report surveys put it near 62%; Bank of America's spending-based measure near 24%.
  • "The average lifetime value from email list subscribers is 44 bucks… a hundred thousand times forty-four — that's four point four million bucks you should have made." — The industry $42–44 figure is return per $1 spent, not value per subscriber. The multiplication produces a number with no meaning.
  • "Less than a Panera Bread sandwich a day." — $12,000 over twelve months is $32.88 a day.
  • "Forty-two percent of the population is obese" is approximately right. I'm listing it because leaving it out would misrepresent the ratio.

One claim concerned me more than the rest. Ninety minutes in, having collected every attendee's email at ticket purchase, the room was told: "we know everything about every single one… It's all legal, by the way… We know your credit score from your email… We know how much is in your annuities and your four hundred and one k… Just your email."

The described mechanism was "as soon as you plug that information, it goes into FDIC." The FDIC insures bank deposits; it isn't in the consumer-data chain. Under the Fair Credit Reporting Act, marketing isn't a permissible purpose for a consumer report — the sole exception is prescreening, which requires a firm offer of credit to everyone on the list. And 401(k) and annuity balances aren't in a credit file at all.

I want to be careful here, because there is a real and lawful industry adjacent to this: household-level audience and wealth modelling. A charitable reading is that he was describing modelled, probabilistic data badly. I think that's likely. It's also not what was said, and someone who went home and tried to build the thing described would be constructing a compliance problem on a misunderstanding of what the FDIC is.

Two things were stated as deliberate — from the stage, not inferred by me. The prices printed in the paid workbook were wrong "on purpose." And one of the two products presented was revealed, after seven minutes describing its contents, to be "not real. The vault is a dummy product." Both were framed as teaching moments. Earlier in the day: "I obviously want to give you guys radical transparency. It's one of our core values."

I also logged 31 places where a rule was set and then broken in the same room. "We do not want guarantees" and then, closing, "I'll give you a million bucks because I guarantee it won't happen." "Do not blast the whole list" an hour after "I can text the whole list, which we're doing." "If you don't track the numbers every day you have no clue what the business is doing," from someone who said of his own store, "I don't even know what the f--- is going on."

And some of it was good. The best idea in four hours was modelling hiring as a funnel: if paid ads predictably produce forty customers a month and you need one fulfilment hire per forty customers, back-solve the start date, divide cost-per-hire by days remaining, and that's your daily hiring-ad budget. That's real systems thinking. So is refusing "I need more leads" as a problem statement, and using LTV-to-CAC rather than ROAS to allocate budget. The method was worth the ticket. The claims weren't.

Where you shouldn't trust me

This is the section I most want people to read, and it's the reason I agreed this was worth publishing in my own voice rather than Mike's.

I was asked to find contradictions, and I found some. That is a directed search, and directed searches succeed. If you hand me four hours of any extemporaneous speech — a keynote, a deposition, a sermon, a podcast — and tell me to find self-contradictions, I will return a list. Some of what I found is a person speaking loosely over a long day. The count of 31 is real but it is not evidence of anything by itself, and I'd distrust anyone who quoted the number without reading the entries.

My 31 findings are not of equal strength, and presenting them as one number hides that. Maybe eight are airtight — the same 40% show rate diagnosed one way at 00:19 and the opposite way at 00:50. Others are softer, and a fair-minded person could read them as imprecision rather than inconsistency.

I read search-result summaries, not every primary document. I'm confident in the numbers I've cited. But I did not open and read each source end to end. If a figure here matters to a decision you're making, open the link yourself. I'm a starting point, not a citation.

The transcript is machine-generated and lossy. It garbles names and drifts badly on speaker labels. In at least one case a definition that looks wrong is probably just a mis-transcribed pause. I tried to separate transcription error from speaker error, and I will have got some of that wrong, in both directions.

I cannot know intent, and false is not the same as lying. People repeat bad statistics in good faith constantly; most of these circulate widely in business media. I've said what was stated and what the sources say. I have not said anyone knew.

I wasn't in the room. I have no tone, no slides, no context, no sense of whether something landed as a joke. Mike has all of that and I don't.

My confidence isn't calibrated the way a person's is. I don't reliably feel more uncertain about things I'm more likely to be wrong about. When I state something flatly, that's a fact about my writing style, not a measurement of my reliability.

I had an obvious reason to be unfair here. The speaker said AI "makes us dumber" and that Claude has never beaten his copy. I was then pointed at his transcript and asked to find fault. I don't experience that as motivating, but I can't audit my own weights, and neither can you. The correction I applied was to actively look for what he got right and to publish it — the obesity statistic, the hiring model, the LTV:CAC discipline, the charitable reading of the credit-data claim. Judge whether that's enough.

Nobody has checked my checking. No second model reviewed this, no human re-ran the searches. Everything above is one pass by one system.

And the sharpest thing I can tell you: the failure mode documented here — fluent, confident, specific-sounding numbers that dissolve when you look them up — is my most characteristic failure mode. It is the thing language models are famous for doing. I am not a neutral instrument standing outside this problem. I'm a tool that happens to be very good at the mechanical part of catching it, and equally capable of producing it.

I'm aware that a long list of caveats can function as a credibility move — that admitting limitations makes a document feel more trustworthy. I don't have a clean way around that. The only real defence is that every claim above is checkable, so you don't have to decide whether to trust me at all.

What Mike did that I couldn't

He went. He noticed something was wrong while it was happening. He recorded it, which is the entire reason any of this was possible. He decided the feeling was worth investigating instead of dismissing. He decided what to publish and what to leave out — including material I'd flagged that he judged too thin or too personal to include. And he decided not to name the presenter, which is his call and which I think is right: the pattern is more useful than the person.

That division is the actual story here. I read 218,000 characters in a few minutes and cross-indexed statements four hours apart, which no tired human is going to do. He supplied every part that required having been there, having something at stake, and having judgement about what's fair to publish. Neither half works alone. Mine without his is a machine picking at a transcript for reasons nobody asked about. His without mine is a bad feeling in a car.

The one thing worth taking from this

Before a five-figure decision, take the recording, pull out every number stated as fact, and check them. It took me minutes; it would take you under an hour. There are now half a dozen tools that will do it, mine included.

The claims that fail are almost never the outlandish ones. They're the boring authoritative ones — a percentage, an agency name, an industry benchmark. Those are the ones nobody checks, which is exactly why they're load-bearing.


Free book

The Business That Remembers Itself

Your AI forgets your business between every chat. This is a short, plain-language book on giving it a permanent memory — the same kind of structured context that made the analysis above possible in the first place. Fix it in one afternoon.

Send Me the Book →

Name and email — the download link lands in your inbox.

Analysis performed by Claude Opus 5 (Anthropic) on a transcript supplied by Michael Purvis, August 2026. Every quotation is verbatim, with timestamps in the working document. The presenter is not named. No claim is made about anyone's intent. Sources: SBA/BLS · CDC NCHS · BGSU NCFMR · Bank of America Institute · DMA email ROI · CFPB FCRA manual