Technology Refresh Cycle Revenue
Exploit mandatory product replacement cycles to generate project revenue from existing accounts
In physical security, the average product replacement cycle across cameras, access control, and burglar alarm is approximately 3.5 years. A commercial account with three or four distinct security product categories is therefore replacing one category roughly every 12 to 18 months, creating a near-constant pipeline of project revenue from accounts that are already paying RMR. This is structurally different from HVAC, where equipment replacement is driven primarily by failure or regulatory change (refrigerant transitions), not by technology advancement the customer proactively wants. The framework involves mapping the installed base by product category and estimated install date, projecting a rolling refresh pipeline, and proactively presenting upgrade proposals before customers seek outside bids.
- Technology obsolescence creates predictable project revenue from customers who are already paying recurring fees.
- A 3.5-year average replacement cycle across multiple product categories means one category is cycling roughly every 12-18 months per account.
- Proactive upgrade proposals from the incumbent vendor win more often than reactive bids because the relationship and site knowledge are already in place.
- AI-driven capability upgrades (hotspot analysis, license plate recognition) give customers a business ROI reason to replace equipment early, compressing the natural cycle.
- The refresh pipeline is a function of installed base size and age, making it a manageable, forecastable revenue line.
- Build an installed-base registerFor every active commercial account, record each product category installed (cameras, access control, burglar alarm, fire), the install date, and the product generation. This is the foundation of the refresh pipeline.Pro tipSegment by product category, not just by account. One account with four categories is four independent refresh opportunities.
- Project the rolling 18-month refresh pipelineApply the 3.5-year average replacement cycle to each product-category row in the register. Any install date older than 3 years is a near-term opportunity. Sum the estimated project values to forecast refresh revenue independently of new-logo acquisition.Pro tipThis pipeline number is defensible to investors and acquirers as organic growth that does not require new customer acquisition cost.WarningDo not assume every account will refresh on cycle. Apply a conversion rate based on historical upgrade close rates to arrive at a realistic pipeline.
- Proactively present upgrade proposals before the customer seeks bidsContact accounts 6-9 months before their estimated replacement window with a proposal that leads on capability (AI analytics, new access standards) rather than just replacement. The incumbent has a structural advantage: no site survey needed, existing relationship, and known system architecture.Pro tipFrame upgrades around customer-side ROI (the hotspot analysis example: retail customers replacing 2-year-old cameras to gain AI business intelligence). When the ROI story is strong, price is secondary.WarningIf the outreach is purely 'your system is old,' customers will put it out to bid. Lead with what the new technology does for their business.
- Track early-cycle upgrades driven by AI or regulatory changeSome accounts will want to upgrade before the natural 3.5-year cycle because a new AI capability creates a business-decision ROI (retail hotspot analysis, license plate recognition). Flag these accounts and accelerate the proposal timeline.
The Entry and Exit hosts described retail customers who had installed camera systems 2 years prior but were replacing them entirely to gain AI hotspot analysis, which tracks where customers linger in a store and informs merchandising decisions. The replacement was economically justified by the business intelligence value, not by equipment failure or the natural replacement cycle. The incumbent security company captured the project because they already held the monitoring contract and the customer relationship.
A commercial account with cameras, access control, and a burglar alarm, each installed in different years, cycles one product category every roughly 12-18 months on a 3.5-year average replacement schedule. The incumbent security company generates project revenue from this account every year without acquiring a new customer, simply by managing the installation dates and proactively proposing upgrades.
Extracted from Owned and Operated (HVAC vs Security episode). The Entry and Exit hosts cited the 3.5-year average replacement cycle and the AI-driven camera upgrade example to explain why their installed base generates recurring project revenue without requiring new-logo acquisition.