Expected impact
Impact estimates how much a recommendation moves your scores if you act on it, computed deterministically.
Last updated September 22, 2026
Expected impact answers the question every security leader asks before committing budget: what does this actually get me?
Pytheus estimates impact by projecting the score change if you close the gap a recommendation addresses. Because scoring is deterministic, this projection is exact, not a hopeful forecast. If a capability moves from maturity 2 to its target of 4, Pytheus Intelligence recalculates the affected domain score and the headline Pytheus Score using the same formulas it always uses, and shows you the difference. Modeled figures are labeled as modeled.
Impact reflects criticality and weighting. A compliance-required capability with a wide gap moves your scores more than a nice-to-have with the same gap, because it carries more weight in the Org Score. Because the Pytheus Score blends maturity with goal alignment, coverage and execution discipline, closing a coverage gap can lift more than one component at once.
Impact is a recalculation, not a promise about the real world. It tells you what your scores become if the maturity change you describe actually happens.
Use impact to sequence work. Recommendations with high impact and reasonable effort are the obvious early wins. High impact paired with high effort belongs on the roadmap with proper planning.
Impact pairs with effort to give you the full picture before you decide whether to approve it.