PM Scenario - #2: Legacy Sensor Fleet Sunset

A situational PM question. You’re in the PM’s seat, and there’s a call to make.

The situation: You’re the PM for an industrial IoT monitoring platform used by commercial greenhouse operators. Your engineering lead warns you that supporting the first-generation wireless soil sensors is consuming 35% of the platform team’s sprint capacity due to an outdated radio protocol.

What you know:

  • Of your 820 total customer accounts, 95 still run exclusively on the Gen-1 sensors, representing $640,000 in annual recurring revenue.
  • A full hardware upgrade kit costs $4,200 per facility, and the sales team reports these 95 accounts are operating on thin margins with no planned capital expenditure.
  • The platform team has a six-month backlog of critical security updates and automated alerting improvements requested by the remaining 725 customers.

Your call: How do you handle the Gen-1 sensor support over the next two quarters?

There’s no single right answer. Reply with what you’d do and why, and I’ll follow up with a question or two.

I wouldn’t cut them off cold, and I wouldn’t keep burning 35% of the team’s time on them either. That’s the worst of both worlds: the 725 other customers wait on security work, and the 95 Gen-1 customers still get a worse product.

I’d announce a real sunset with a long runway instead. No new Gen-1 features, security and critical fixes only, and a firm end-of-support date at the end of those two quarters. That frees up capacity gradually without leaving anyone’s greenhouse blind overnight.

The $4,200 kit is the sticking point, though. For accounts on thin margins with no capex planned, a forced upgrade is basically a churn notice. So I’d pair the date with something actually workable - a phased rollout, a discount or payment plan, and a cheaper bridge option if engineering can swing it - and I’d talk to the biggest of those 95 directly first, not just send a mass email.

If some still won’t move after that, that’s a clearer decision to make. At that point you’ve given them time, a path, and a price they could plan around, instead of just quietly letting the old protocol eat the roadmap.

I appreciate the nuance of not cutting them off cold while still setting a firm sunset. The idea of a phased rollout or payment plan for the upgrade kit is a good one to address the $4,200 sticking point. You also mentioned talking to the biggest of the 95 accounts directly. How would you prioritize those conversations, and what would be your goal for those initial discussions?

I’d start with the biggest revenue accounts and the ones with the most facilities, then the ones whose renewals or growing seasons are coming up soonest. Those are the conversations where a surprise $4,200 bill per facility hurts the most, and where losing the account stings the most.

The goal for those first talks wouldn’t be to close the upgrade on the spot. I’d want to find out what actually blocks them — is it cash flow, timing, install downtime, or just not trusting that the new kit is worth it? If I know that, I can offer the right version of the deal: a phased rollout, a payment plan, or a pilot on one facility first. And honestly, I’d also want a couple of them to become the early examples I can point the other 90 to.