The bill you see is not the bill you pay
Most teams can name their monthly extension spend. Very few can name the second cost: every plugin is a dependency that must be updated, tested, occasionally debugged and eventually replaced. That work is real, it is recurring, and it usually lands on whoever is closest to the site—often the founder or a single developer with no time budgeted for it.
Overlap is the expensive pattern, not volume
A store with forty well-chosen extensions can be cheaper to run than one with fifteen that overlap. Overlap appears when two plugins both claim bundles, or discounts, or reviews, or subscription logic. Nobody remembers which one is authoritative, so every change requires investigation before it requires work. That investigation time is the constraint, and it grows with the catalog.
How to price it honestly
Take one month and record three numbers: hours spent on updates and breakage, hours spent working out which tool owns a behaviour, and the number of changes that were delayed because nobody was confident about the blast radius. Multiply by a loaded hourly cost. That figure is usually larger than the licence total, and unlike the licence total it scales with growth.
Simplify before adding
The default fix is to add a tool that manages the other tools. The better first move is removal: identify overlapping responsibilities, decide which system is authoritative for each behaviour, and retire the rest under a tested rollback plan. Removal lowers cost and risk at the same time, which almost no purchase does.
Key takeaways
- Licence spend is the visible cost; maintenance surface and investigation time are the expensive ones.
- Overlapping responsibility between plugins slows every future change, regardless of plugin count.
- Decide what is authoritative for each behaviour, then remove the rest before adding anything new.