Rating Methodology

    Product Strength is the unweighted geometric mean of Product Value, Adoption and Durability, with explicit uncertainty and evidence.

    strength-v9 · Adoption calibration 2026-10-27

    Strength = ∛(Product Value × Adoption × Durability)

    Three equal inputs. Unweighted geometric mean. Every score stays on 0–100; uncertainty ranges use the same formula.

    01

    Product Value

    How well does it do the job?

    Compare task success, corrections and workflow completeness with a named alternative, including a general model configured for the same work.

    02

    Adoption

    How much real use has it earned?

    Use dated, product-specific active users or annual revenue / ARR. Enterprise products prioritize revenue; documented paying customers or production deployments are fallbacks.

    03

    Durability

    Can it defend and renew its advantage?

    Assess a three-year horizon: credible rivals, bundling pressure, defensible assets and demonstrated expansion. Size, specialization and ordinary integrations alone earn no premium.

    One adoption scale

    $25 per active user, per year.

    1 million monthly active users and $25 million annual product revenue / ARR receive the same Adoption score: 63.

    MAU × $25 is a comparison assumption, not reported revenue or estimated ARPU. Both inputs follow the same fixed curve, with smaller gains at larger scale. Never add the two.

    Active users
    Require a dated MAU, WAU or DAU observation for this product. Weekly and daily counts retain their cadence and serve only as monthly lower bounds, with no multiplier.
    Registered users ≠ active users
    Sign-ups, downloads, website visits and parent-platform audiences earn no active-user count credit. A registered account may never return.
    Enterprise revenue
    Use scoped annual product revenue, ARR or a labeled run rate. Keep its metric, period and currency. Exclude parent revenue, forecasts, bookings, GMV and funding.
    Equivalent scale · USD per year
    Monthly active usersRevenue / ARRAdoption
    4K$100K20
    40K$1M35
    400K$10M55
    1M$25M63
    4M$100M75
    40M$1B90
    400M$10B97
    4B$100B100

    Fixed anchors with logarithmic interpolation; linear below $100K. The dollar column is observed revenue for revenue-based ratings and only a scoring equivalent for user-based ratings.

    HBM: compare the same market and quarter

    For SK hynix, Samsung and Micron HBM only, matched global revenue shares replace mixed historical revenue and deployment estimates. Fixed editorial anchors: 10% share → 85; 50% → 95, capped at 95. Logarithmic interpolation makes gains taper. This is not a dollar conversion or a general rule for niche markets.

    min(95, 85 + 10 × ln(share% / 10) / ln(5))

    Applies to reviewed major suppliers with at least 10% share. Scores round to one decimal with ±10-point editorial ranges, clipped to 0–100; decimals do not imply measurement precision. Revenue share does not measure units, product quality or durability. Original rounded shares stay visible.

    Compare the three suppliers and sources →

    Read the evidence with the score

    ≈ means an estimateScores are editorial judgments. Disclosed observations keep their source and date; ranges express uncertainty. Ratings older than 90 days are flagged for review.

    25 can mean adoption is unverifiedAvailability-only entries currently use an estimated 25. This identifies an evidence gap, not measured low demand. Registrations alone cannot establish active use.

    Compare the same workflowOverlapping ranges and small point differences do not establish a clear winner. Check the named alternative, deployment conditions and total cost.

    Calculation notes & company scores

    Normalize each fixed 0–100 component by dividing by 100, multiply, take the cube root and return to 0–100. Example: 90 / 90 / 30 gives 62.4. Missing evidence is not a genuine zero.

    Company components = 82% of the strongest product + 18% of the top-three mean. Apply the same geometric mean to those components. Deduplicate product families; never allocate company value or revenue to product scores.

    Pricing, inference costs and profitability are supporting information. Economics is excluded from the score and cannot be derived from the three criteria. Open models and frameworks can use documented ecosystem deployment without sales.

    Compare products