Every "Best of" page on Revuo is ordered by one deterministic formula over data anyone can inspect:
crawler-verified capability claims, evidence freshness, agent readiness, and profile completeness.
Same stored inputs, same score — an outsider with this page and the public data recomputes the ranking.
Positions are never sold, and there is no manual override in the codebase.
[ the dimensions and their weights ]
45%
Verified capability coverage
The core buying question is 'does it actually do X'. Coverage counts a capability claim only when the weekly crawler validated its evidence URL on the vendor's own site — an unvalidated checkbox is worth zero. Weighted per category via the capability-group blueprint (compliance weighs more in Billing than in PIM). Non-verifiable kinds (workflow) earn at most half credit.
15%
Evidence verification rate
Of the claims that can be checked, how many passed the last crawl. Rewards vendors whose documentation actually supports what their listing says.
10%
Evidence freshness
Full credit when the last verification pass is 30 days old or less, decaying to zero at 180 days (where the eligibility gate takes over). Software changes; stale evidence is weaker evidence.
15%
Agent readiness
Buyers increasingly integrate software with AI agents. This is the existing deterministic 0-100 composite over API surface, protocol support (incl. probed MCP servers), SDKs, integration ecosystem, and developer experience.
15%
Data completeness & pricing transparency
A complete profile and public pricing are what buyers ask for first. 'Contact us'-only pricing scores this dimension's pricing half at zero — that is an editorial position, and a published one.
Every product's per-dimension breakdown is public — on its listing, on every ranked entry
("why #4?"), and in the rankings.get MCP
tool. The weighted total is exactly Σ weight × dimension score; nothing else enters.
[ deliberately excluded — and why ]
Paid tier / any payment
Positions are never sold. Tier buys labeled placement strips and vendor services only.
AI web sentiment
Non-deterministic, unauditable, and astroturfable — two runs differ, so nobody could recompute the ranking. Display-only.
Review ratings
At current review volume a handful of reviews would swing positions. Display-only until a category has meaningful volume; any future inclusion will be Bayesian-smoothed and version-bumped.
Popularity / telemetry
Views and MCP appearances create rich-get-richer loops and are farmable. Vendor analytics only.
Editorial badges
Editor's Choice and Top Rated are labeled overlays, never score inputs — and never assigned to house products.
[ eligibility gates — binary, never blended ]
A product is either rankable or it isn't; gates never leak into the score. Products that fail a gate
appear on the ranking page by name under "Not yet ranked", with the reason shown publicly — silent
exclusion is an operator lever this system refuses to have. Payment is deliberately not a gate:
a free listing with complete, crawler-validated data is fully rankable.
Published, and the website reachable on recent checks.
Claim verification fresh: stale beyond 180 days drops a listing out of the ranking; beyond 365 days it is flagged for removal per the listing policy.
At least 50% of the category's core capability groups carry a verified claim.
Listing copy passes the genericity gate (no marketing slop on ranked pages).
A ranked page publishes only with ≥ 8 eligible products — no "Top 10" over a handful of listings.
Verified and Featured tiers buy vendor services (analytics, sentiment drill-down, a CTA button) and
clearly-labeled placement strips on browse pages. They contribute zero to
rankings, to MCP result ordering, and to the "verified data" trust flag — which is earned via an approved
vendor claim (crawl freshness is a separate signal, exposed as verifiedAt), and is free on every tier. Where something IS paid, it carries
a label at the point of display, including machine-readable
tier and
sponsored fields
in agent-callable responses.
[ house products — the conflict of interest, handled structurally ]
Revuo is operated by the maker of FacetFlux (PIM),
TenderStrike (tender management),
Monego (e-invoicing) and
Optivise. They appear in their own categories' rankings — excluded
rankings would misrepresent the market, and self-inclusion is the forcing function that keeps this
methodology honest. The rules that make that defensible are structural, not editorial:
Same formula, same gates, no editorial adjustment — the per-dimension breakdown on every house entry is publicly auditable.
House products can never hold Featured placement or editorial badges — enforced by build-failing tests, not policy.
Every API and MCP payload carries houseProduct: true, so the disclosure survives AI-mediated consumption.
Reviews of house products are never solicited or incentivized.
The honest pitch to competitors: outrank the founder by verifying your data — the formula rewards exactly that.
[ how this methodology changes ]
Weights change only at quarterly methodology reviews, decided by editorial alone — never in response to a
vendor request, and never in a sales conversation. Vendors (and anyone) can propose criteria the
whole category is judged on; accepted criteria enter at their group's default weight and take effect at the
next quarterly revision. Every change bumps the version, ships with a public changelog entry and ≥15 days
notice to claimed vendors, and ranking deltas are never compared across versions. Off-schedule ranking
recomputes are marked as such on the page.