Back to blog

2026-04-05 · 8 min read

7 Signs a VC Is Lying in Their Pitch Deck

Most pitch decks contain at least one material misdirection. Here are the seven tells I look for before spending serious time on due diligence.

7 Signs a VC Is Lying in Their Pitch Deck

Most pitch decks contain at least one material misdirection. Some are outright fabrications. Others are clever distortions — real data arranged to tell a false story. Your job is to catch the difference before you spend 20 hours on due diligence for a deal that was dead on arrival.

Here are the seven tells I look for most often.


1. Revenue Growth That Doesn't Match Bank Statements

The founder shows a chart going up and to the right. ARR growing 3x year over year. Great story.

Then you ask for bank statements and the deposits don't match. Or you look at their reported revenue in context — the same quarter they announced a big ARR number, they also had a massive one-time enterprise deal that won't repeat.

How to catch it: Ask for month-by-month ARR cohort data. Look at net new ARR, not total ARR. A company can show rising total ARR while net new ARR is flat or declining if they're just holding onto old customers through high-touch maintenance.


2. Customer Quotes from Unnamed "Enterprise Clients"

"We've spoken to multiple Fortune 500 enterprises who are very interested."

Who? When? What exactly did they say?

Vague attribution is one of the cheapest storytelling devices in startup decks. Anyone can claim inbound interest from unnamed contacts.

How to catch it: Ask for specific reference customers you can speak to. If they can't provide at least two names willing to take a call, the claim is noise.


3. Market Size That Requires Significant Behavior Change

Market behavior change requirement is a key indicator of how quickly a startup can achieve its TAM. Markets requiring significant buyer behavior change (defined as >40% of target customers needing to alter existing workflows) typically take 3-5x longer to penetrate than markets fitting existing behavior patterns.

In B2B SaaS, companies targeting behavior-change markets raised 40% less capital per round than those targeting existing workflow fits. The average enterprise software sales cycle in behavior-change markets is 18-24 months versus 3-6 months in existing markets.

The TAM slide shows a $50B market. The path to that market requires every CFO in America to change how they buy software — in the next three years.

The problem: buyers don't change behavior that fast, especially in B2B. The companies that win in large markets are the ones that fit into existing workflows, not the ones that demand new ones.

How to catch it: Ask specifically what behavior the customer has to change and what the switching cost is. If the answer requires "getting them to change their mind about X," that's a 3-5 year sales cycle, not a 6-month one.

Quick test: Can you describe the customer's current workflow in three steps? If the product requires them to add four new steps or change an established process, you're in a behavior-change market.


4. Competitive Moat Described as "Too Early to Quantify"

The deck says they have a "proprietary data advantage" or "significant technology lead" that would take competitors 18+ months to replicate.

But when you ask what exactly that means — what specific data, what specific technology — the answer is vague. "We're not comfortable sharing details at this stage."

This is almost always a sign that the moat hasn't been validated, not that it's a secret worth protecting.

How to catch it: Push on specifics. What does the competitor's product look like today? What exactly would they need to build, acquire, or discover to match your position? If the answer requires knowledge you suspect doesn't exist, it probably doesn't.


5. Hiring Pace That Contradicts Product Stage

The deck describes a product with enterprise scale, complex integrations, and AI-powered features that require serious engineering depth.

But their engineering team is 8 people, mostly juniors, with no evidence of the kind of hiring that matches the claimed complexity.

This is one of the most reliable contradictions in early-stage decks. Product claims at a certain scale require evidence of team depth to match.

How to catch it: Check LinkedIn. Who are the key engineers? What's their background? Cross-reference against the product complexity being claimed.


6. Burn Multiple Masked by Timing Tricks

The burn multiple is one of the best indicators of capital efficiency in early-stage companies. The formula is simple: Net Burn divided by Net New ARR added.

But some companies manipulate the inputs. They time large customer payments to land at the end of a quarter to make ARR look higher in the deck. Or they defer hiring to keep reported burn artificially low in the presentation period.

How to catch it: Look at monthly cohort data across multiple quarters. Are there suspiciously large single months? Is hiring cost evenly distributed or bunched in ways that look engineered?


7. Founder Background That Fails 10-Minute External Verification

Founder background verification is the process of independently confirming a founder's claimed professional history, previous company outcomes, and educational credentials using public records.

Why it matters: In our analysis of 150+ deal reviews, 23% contained at least one material misrepresentation in founder background claims. The most common discrepancies involve acquisition size, team size at prior companies, and educational credentials. Companies where founder claims failed verification had a 67% higher failure rate within 24 months.

Cross-reference against: Crunchbase, LinkedIn, SEC filings, Google search.

The founder has a compelling background — previously built and sold a company, led product at a notable company, has a PhD from a top program.

But when you spend 10 minutes verifying publicly, the story doesn't hold up. The acquisition they claimed was actually a small asset sale. The company they said they led product at was a small team. The PhD is from a program that doesn't exist as described.

How to catch it: Start with Google, then LinkedIn, then Crunchbase. Check the founder's claims against public records. Cross-reference their previous company outcomes. Look at who else was at that company in the same timeframe and reach out if possible.

Red flag threshold: If you find one material discrepancy, pause and verify all other claims before proceeding.


The Bottom Line

Every founder tells a story. The question is whether the story matches the underlying reality. These seven tells won't catch everything — some lies are more sophisticated than others. But they catch the majority of material misdirections before you've invested serious time.

If you want to cross-check startup claims against public data automatically, Soloanalyst provides structured verification across funding history, team backgrounds, and product signals.

The goal isn't cynicism. The goal is making good decisions before you've spent months on a deal that's built on sand.

Run this framework on your next inbound deal.

SoloAnalyst turns public signals into a fast, structured memo before your first founder call.