Overlap detection

Overlap is what you see when more than one tool maps to the same capability. CANOPY surfaces it so you can decide whether that redundancy is deliberate or just expensive.

Overlap is not automatically a problem. Two tools covering the same capability can mean healthy defense in depth, a planned migration, or a deliberate primary-and-backup arrangement. It can also mean you are paying twice for the same function because two teams bought separately. CANOPY shows the overlap. You bring the judgment.

When you find overlap, ask a few questions before acting:

• Is each tool earning its place, or is one a leftover from a past decision?

• Does the duplication add resilience, or just cost?

• Would consolidating create a single point of failure you would regret?

Overlap is where spend reviews usually pay off fastest. A capability covered three times is a strong candidate for consolidation, but confirm the mappings first.

Overlap detection is only as accurate as the mappings beneath it. If a tool is mapped to a capability it does not really perform, Pytheus will report overlap that is not real. This is why confirming mappings comes first. See Confirmed vs inferred mappings.

Keep overlap separate from contracts in your thinking. CANOPY shows functional duplication. Spend and renewal context lives with your contracts, which support tracking but do not drive scoring. To understand why some tools appear together by design rather than by accident, see Integration relationships.