Back to rankings

MMR v3 · USD

How startups are ranked by verified MRR

How StartupsMRR verifies startup revenue from payment providers and turns verified MRR, growth and consistency into a transparent, versioned Market Momentum Rating (MMR). The score ranges from 0 to 1000.

Why new companies start provisional

New companies begin with a provisional MMR because growth and consistency require observed history. Missing history receives no estimated points, so a score early on reflects how much has been measured, not how the business is performing. A company is on the board from its first verified reading, marked provisional: its MRR is a fact the moment the payment provider reports it. Because unmeasured history earns nothing, a provisional Momentum score understates a business rather than overstating it, and it rises as readings accumulate. The score stops being provisional after three verified readings, thirty days of history, and a 30-day comparison; the Fastest growing board waits for that comparison. Nothing is backdated to reach it sooner.

Verified revenue, not only MRR

MRR describes what recurs; a business selling one-time packages has little of it and real revenue. For Stripe, StartupsMRR also reads every payment the account has settled: revenue is what was paid, less refunds and lost disputes, in USD. It is shown for the last 30 days, all time once the whole history has been read, and month by month, with buyers counted as distinct paying customers. It is published only when every revenue source of the company reports it and the 30 days are read in full, and the company chooses how it is shown: exact, a range, or hidden, which by default matches its MRR visibility. Only daily totals and a buyer count are stored, never a customer or a payment. Momentum scores still use MRR.

Component weights

Missing signals reduce coverage and remain unawarded.

Revenue strength

30%

Log-normalized verified MRR; verified 30-day revenue joins when available.

Growth

30%

30- and 90-day change. Positive growth is capped at 300%, with a lower cap for bases below $100.

Consistency

20%

Repeated daily snapshots and MRR stability. One snapshot cannot receive full points.

Recurring quality

10%

Verified recurring subscriptions and expansion across customers.

Confidence

10%

Ownership, provider quality, freshness, and depth of verification history.

Efficiency

0%

Reserved for revenue per verified visitor. It carries no weight until that signal is verified, rather than holding points nothing can earn.

Eligibility

  • A live listing with a working read-only key from its payment provider. Control of the domain is verified separately (a DNS record, the provider's own check of the merchant's website, or the App Store page of an app connected through RevenueCat), and each Trust Page says whether it is
  • Healthy live provider connection and fresh publishable snapshot
  • MRR counts active subscriptions only: past-due ones (a failed payment being retried), trials, paused and usage-based subscriptions are left out
  • USD-only in v3; no silent currency conversion
  • Test-mode data can never create a score
  • Provisional scores are ranked and labelled provisional; the Trust Page shows the number only once it is final
  • A company with a working key and nothing sold yet has a public page marked Pre-revenue, with no figures and no rank, and joins the board with its first verified revenue

Provisional and stale

A score remains provisional until it has at least three daily snapshots, 30 days of history, and 70% input coverage. A snapshot expires after 26 hours; stale scores are excluded from verified ranking until the next successful sync.

Trust Page disclosure and continuity

Founders choose MRR as an exact figure, a published range, or hidden; customers as an exact count, a range, or hidden; trend as a percentage, direction only, or hidden; and verification continuity as public or hidden. Hidden signals are removed at the database read boundary, including from cards, badges, structured data, and ranking modes that would reveal an ordering.

A trend is stable when its absolute 30-day change is below 2% (200 basis points). Exact growth ranking requires an exact published percentage.

Continuously verified means every interval since the stated start has an accepted, publishable live-provider reading with no gap longer than 72 hours. A gap over 72 hours, a different provider account, or lapsed domain ownership resets the start. Reconnecting the same account inside the window and changing listing visibility do not.

During a provider or pipeline interruption, the Trust Page labels verification as pending and may retain the last disclosed values with a visible timestamp for up to 72 hours. After that it withholds those values until a fresh reading succeeds.

What source verification does not prove

Provider data raises the cost of fabrication and makes readings auditable, but it does not prevent wash transactions such as a founder charging their own cards. Private reconciliation uses reversal, concentration, pause, and collected-to-run-rate signals; these are not published because exposing them would disclose additional business data and teach manipulation strategies.

Integrity boundary

Every calculation stores its version, source snapshot, baseline snapshots, exact components, input hash, confidence, coverage, and evaluation time. Identical inputs are idempotent. Spotlight purchases, balances, and clicks are outside the scoring schema and never affect MMR.