I don't want whatever dark patterns and bonus features ( https://devblogs.microsoft.com/oldnewthing/20061101-03/?p=29... ) marketing came up with this year. I want the basic functionality you had at 1.0, with all the bugfixes since.
At that point, it is absolutely the best thing to get rid of everyone and just keep selling the product you have. Too often a company tries to hold on to long, adding new features that don't actually improve anything.
I wish more companies were willing to admit when they reached that point.
Gen. Maximus: "Would you, Quintus? Would I?"
- Gladiator, 2000
But, yes your right at some point you have to admit your product is mature, and cut the engineering effort on that product, hopefully before you start driving customers away.
For products used by big enterprises its pretty amazing how long a product can go without meaningful updates and still have companies paying for maintenance. I've seen it a few times now, the engineering/testing is basically cut to one developer who's job is basically to fix bugs and nothing else. For many enterprises this is a pretty decent model. In many cases they don't need or want new features, and the IT guys are very happy if they just get a point release once or twice a year that is a 100% drop in replacement with some bugs fixed.
For a large conglomerate that can sell new licenses as part of a bundle deal, its a good plan to, the customer base grows at about the same rate as people drop the products. The result is just a constant cash flow with basically no overhead.