Spend benchmarks

The Pytheus Index becomes available to your organization once your cohort has enough participants for the comparison to be anonymous. Until then the surface may not appear in your dock. Your Pytheus contact can tell you where your cohort stands.

Knowing what you spend is useful. Knowing whether that spend is reasonable is what changes decisions. The Index spend benchmark places your costs next to a pooled cohort of peers in your sector and size band.

What it compares

• Per tool. Your annualized spend on a tool against the cohort median, 25th, and 75th percentiles for that product, with the percentage difference.

• Per domain. Your spend rolled up by security domain against the cohort's typical spend for that domain, including domains where you spend nothing but peers do.

Products are attributed to their dominant security domain through their capability mappings, so the domain view lines up with the rest of Pytheus.

Reading it honestly

The output is a difference, not a verdict. Spending above the cohort is not automatically wrong, and spending below it is not automatically safe. A higher figure may reflect a deliberate investment in a compliance-required capability; a lower figure may mean you are underinvesting where it counts.

The Index flags a domain as worth a closer look when your maturity there is low relative to peers and your spend is high relative to peers. That pairing, paying more while achieving less, is the clearest signal to investigate.

A spend benchmark is peer intelligence, not a price list. It reflects what comparable organizations actually record paying, pooled and anonymized.

Pair this with your own spend allocation to decide where to focus, and act before a renewal.