MMR v3 · USD

MMR scoring methodology

How verified business signals become a transparent, versioned Market Momentum Rating. 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. Provisional scores are visible to the founder but are not assigned a leaderboard rank: a company measured for one day cannot be honestly ordered against one measured for six months. A startup joins the ranking once it has three verified readings, thirty days of history, and a 30-day comparison. Nothing is backdated to reach that sooner.

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

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

Eligibility

Approved startup and verified DNS ownership
Healthy live provider connection and fresh publishable snapshot
USD-only in v3; no silent currency conversion
Test-mode data can never create a score
Provisional scores are not ranked and are not published

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 DNS 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.