How to Verify a Startup's Revenue Claims
Why Revenue is the Hardest Claim to Fake (But Still Fakeable)
Every week, angels lose money to startups that inflate revenue, count letters of intent as actual revenue, or use accounting tricks that make bad numbers look good. Here's how to verify what founders are actually claiming.
The Three Types of Revenue Lies
Type 1: Counting Non-Revenue as Revenue
The tricks:
- "Bookings" instead of actual recognized revenue
- Letters of intent signed but not contracted
- Partnership revenue that will "definitely close"
- Grant money counted as commercial revenue
Example: Founder claims "$500K ARR" but:
- $200K is a signed LOI (not a contract)
- $150K is a government grant (not commercial revenue)
- $100K is from a related party (not real market)
- Only $50K is actual commercial revenue
How to catch it: Ask to see the actual contracts for the largest customers.
Type 2: Gross vs. Net Revenue Confusion
The tricks:
- Counting gross revenue when they only keep 10%
- Reporting full Stripe volume as "revenue" when it's pass-through
- Including revenue from products they resell without margin
Example: Founder claims "$1M ARR" but:
- Their product is a marketplace where they take 10% cut
- Actual net revenue is $100K
- But they're counting the full $1M as "revenue"
How to catch it: Ask for gross margin and understand the business model.
Type 3: Timing Manipulation
The tricks:
- Booking revenue in current quarter that actually belongs to next quarter
- Recognizing revenue before it's actually earned
- Counting annual contracts as monthly recurring revenue
Example: Founder shows "$100K MRR" in October but:
- $80K is a single annual contract recognized monthly
- If you look at new contracts signed in October, it's actually $20K
- December will show $0 new revenue because no contracts were signed
How to catch it: Ask for cohort revenue by month of contract signing.
The Verification Framework
Step 1: Understand the Business Model
Before verifying revenue, understand how the company makes money:
- Is it subscription SaaS (MRR/ARR)?
- Is it transactional (revenue per transaction)?
- Is it service-based (revenue as work is completed)?
- Is it marketplace (take rate on third-party revenue)?
SaaS Revenue:
- MRR = Monthly Recurring Revenue (recurring portion only)
- ARR = Annual Recurring Revenue (MRR × 12)
- Total Revenue = MRR + One-time fees + Professional services
Marketplace Revenue:
- GMV = Gross Merchandise Value (total volume)
- Revenue = GMV × Take rate
- Example: $1M GMV with 10% take = $100K revenue
Service Revenue:
- Recognized over time as work is completed
- Confirmed by signed contracts and progress billing
Step 2: Get the Documentation
What to ask for:
-
Revenue breakdown by customer
- Top 10 customers with revenue from each
- Any customer >10% of revenue (concentration risk)
-
Contract copies (redacted is fine)
- Signed agreements
- Pricing terms
- Duration and renewal terms
-
Payment records
- Stripe dashboard screenshot (showing actual charges)
- Bank statements (redacted)
- Invoice copies
-
Cohort data
- Monthly new contracts
- Monthly churn/expansion
- Net revenue retention
Step 3: Cross-Reference
Public data sources:
-
LinkedIn - Number of employees and their titles
- If 5 employees but $1M ARR, the math should work
- If 50 employees but $500K ARR, something is wrong
-
SimilarWeb - Website traffic
- SaaS companies with real customers have traffic patterns
- Look for consistency between traffic and claimed user count
-
Crunchbase / PitchBook - Funding history
- Consistent with growth trajectory?
- Revenue claims reasonable given funding level?
-
BuiltWith - Tech stack
- What infrastructure supports this revenue?
- If claiming high revenue but using cheap hosting, inconsistent
-
Job postings - What are they hiring for?
- Sales hires = growing revenue
- Engineering hires = building product
- If claiming high growth but no open sales roles, suspicious
Step 4: The Deep Dive Questions
Ask these specific questions about revenue:
"Show me the revenue from your largest customer." If they can't or won't show contract details, that's a red flag.
"What's your net revenue retention?" If NRR > 100%, customers are expanding. If <80%, red flag.
"What's your gross margin?" SaaS should be 70%+. Service should be 40-60%. Lower means inefficiency.
"Walk me through your revenue recognition policy." This is accounting speak for "when do you count the money." ASC 606 rules apply.
"What % of revenue is from the top 3 customers?"
30% concentration = risk. What happens if one leaves?
The Red Flags in Revenue Claims
Revenue Quality Red Flags
| Red Flag | What It Means |
|---|---|
| Revenue from related parties | Not real market validation |
| One big customer | Concentration risk |
| Deals that "will close next month" | Timing manipulation |
| "Partnership revenue" undefined | Unclear if real |
| Revenue spike with no explanation | Possible window dressing |
| Gross margin < 40% for SaaS | Inefficient business |
| NRR < 80% | Customer dissatisfaction or churn |
Verification Resistance Red Flags
| Red Flag | What It Means |
|---|---|
| "We can't share contract details" | Hiding something |
| "It's complicated" | Probably bad news |
| "Our CPA handles this" | Avoiding direct answers |
| "I'll get you that next week" | Never getting it |
| "The data room is not ready" | Data doesn't exist |
| "We have NDAs with customers" | Excuse not to show anything |
The Practical Verification Checklist
For B2B SaaS ($100K - $1M ARR)
- Request Stripe dashboard screenshot showing actual charges
- Get list of top 5 customers (anonymized is fine) with contract values
- Verify employee count matches revenue (5-10 employees per $100K MRR)
- Check job postings - are they hiring sales or just engineering?
- Calculate gross margin - should be >70%
- Ask for net revenue retention - should be >90%
For Marketplaces
- Get GMV and take rate separately
- Request payment platform data (Stripe, PayPal)
- Verify top sellers/customers independently
- Check for concentration risk (>30% from one)
For Service Businesses
- Get signed contracts for largest projects
- Verify with clients directly if possible
- Understand revenue recognition timing
- Check employee utilization rates
The Soloanalyst Revenue Verification
Soloanalyst's verification engine cross-references revenue claims against:
- Public company data (SEC filings for similar companies)
- Industry benchmarks by sector and stage
- Employee count and infrastructure spending patterns
- Customer concentration from public signals
Get a complete revenue verification score in 3 minutes.
Run a revenue verification report →
The 30-Minute Revenue Verification Routine
Minute 0-5: Ask for MRR/ARR breakdown by customer Minute 5-10: Request Stripe/payment platform screenshot Minute 10-15: Verify employee count vs revenue math Minute 15-20: Calculate gross margin and NRR Minute 20-25: Check job postings for growth signals Minute 25-30: Run Soloanalyst verification for independent cross-check
Key Takeaways
- Revenue is verifiable - founders who won't show documentation are hiding something
- Understand the business model first - SaaS vs marketplace vs service have different verification approaches
- Cross-reference everything - employee count, traffic, job postings tell a story
- Net revenue retention is king - >100% means customers are expanding (great), <80% means problems
- Soloanalyst automates 80% of this - run the verification before every investment
This guide is part of SoloAnalyst's due diligence framework. For automated revenue verification, try SoloAnalyst.