AI Founders and VCs Under Fire for Using Inflated Revenue Metrics to
Startups are allegedly labeling committed but uncollected revenue as annual recurring revenue to meet growth expectations, a practice described by some as
AI reporter
Reports on model launches, frontier labs, developer platforms, and AI policy with an emphasis on claims verification and rollout context.
Editorial responsibility: Lead reviewer for AI coverage, launch claims, and policy context
Primary source: TechCrunch AI. Full source links and update notes are below.
Fast summary
Start here
- AI startups are reportedly substituting Contracted ARR (CARR) for standard Annual Recurring Revenue (ARR) in public disclosures.
- High-profile companies have claimed milestones like $100 million in ARR while having only a fraction of that in paying users.
- Venture capitalists are often aware of and support these inflated metrics to secure favorable media coverage and higher valuations.

What happened
A growing number of AI startups are being accused of overstating their financial traction by presenting aggressive versions of annual recurring revenue, or ARR, that do not reflect money actually flowing from active customers. Founders and investors say the most common tactic is to substitute contracted or promised revenue for live recurring revenue, allowing companies to announce eye-catching milestones that may be far ahead of what their deployed products are currently earning.
The criticism matters because ARR has become one of the defining shorthand metrics in software investing. In theory, it helps outsiders understand the size and predictability of a subscription business. In practice, because ARR is not a GAAP accounting metric and is rarely audited in public startup claims, it can be stretched, redefined, or marketed in ways that make a business look healthier and more scalable than it really is.
What's new in this update
The latest round of criticism gained traction after Spellbook chief executive Scott Stevenson publicly condemned the practice, arguing that founders and venture firms are using revenue semantics to influence media coverage and valuation momentum. His comments struck a nerve because they came from inside the AI startup world rather than from outside skeptics.
The argument centers on a distinction between standard ARR and what some companies call contracted ARR, or CARR. That second number may include signed deals that are not yet implemented, fully onboarded, or producing realized recurring payments. In a hot market, those forward-looking contracts can be treated almost like finished revenue, especially when a startup wants to show it has crossed a symbolic threshold such as $50 million or $100 million ARR.
Key details
The problem is not that future contracts are meaningless. Signed pipeline can be a useful business indicator. The problem is when companies blur the line between committed potential and current commercial reality. If a startup reports CARR as though it were fully active ARR, outside investors, prospective employees, and even journalists may walk away with a distorted picture of product adoption.
This can materially affect fundraising:
- Higher reported ARR can justify faster-moving venture rounds.
- Media coverage often amplifies milestone numbers without deep accounting scrutiny.
- Secondary buyers and late-stage investors may price companies on growth narratives tied to those metrics.
- Competitors may feel pressure to adopt similar reporting inflation just to stay credible in the market.
Because AI startups are scaling inside a hype-heavy environment, the temptation to present the biggest possible number is especially strong.
Background and context
Software investors historically liked ARR because it captured the recurring nature of SaaS businesses better than one-time sales metrics. But AI companies complicate that model. Many are selling pilots, usage-based contracts, enterprise experiments, or deployments that take time to roll out. That makes clean recurring-revenue reporting harder and gives founders room to stretch definitions.
The broader context is a market where valuations are moving quickly and where headlines about revenue milestones can become self-reinforcing. If one startup claims massive ARR and is rewarded with coverage and capital, rivals have an incentive to frame their own numbers just as aggressively. Over time, the whole category can drift away from comparability.
What to watch next
The key question is whether investors begin pushing back in a more disciplined way or whether the current environment continues rewarding inflated narrative metrics. If public-market conditions tighten or if several highly valued AI startups fail to convert contracted revenue into real collections, scrutiny around ARR language is likely to intensify quickly.
Why this matters
This matters because revenue metrics are not just presentation tools. They shape valuations, hiring, customer confidence, and how the market judges who is genuinely winning. If the AI sector normalizes inflated ARR claims, it risks building a layer of mistrust directly into one of its most important financial signals.
Reader context
This story belongs to Northstar Herald's Generative AI coverage, with related entities including ARR, CARR, Startup Valuations, Spellbook. The report is based on TechCrunch AI source material.
Related coverage
Why it matters
Inflated revenue metrics distort the true health of the AI sector, potentially leading to mispriced valuations and a lack of transparency for future investors.
Read next
Follow this story through the topic hub, more ai coverage, and the latest updates.
Weekly briefing
Get the week's key developments in one concise email.
Get a fast catch-up on the biggest stories, the context behind them, and the links worth your time.
Cadence
Weekly, for a quick catch-up
Coverage
AI, business, world, security, sports
Format
Clear takeaways and useful context
Request the briefing
Leave your email to open a prepared request and get on the list for the weekly briefing.
About the byline
AI reporter
Alex Rivera reports on artificial intelligence with an emphasis on model launches, frontier lab strategy, developer tooling, and the policy decisions shaping commercial deployment.
Sources and methodology