That's a bit oversimplified. Surely a bug that could lead to data loss needs to be fixed ASAP regardless of whether a customer complains about it or not.
The thing about bugs is their subtle influence on overall product quality.
It's like building a wall; if one layer of bricks is laid unevenly, at least a number of layers built on top of it will have to compensate. Usually, this compensation takes form in increased development times or increased complexity / convolution of new features.
Furthermore, it lowers end users' overall trust in the platform.
Both of these two effects will have at least some negative impact on profitability, though it may be lower than the increased profitability gained by adding new features.
I'm not saying all bugs should be fixed immediately at the expense of new features, but I've rarely been in a situation, where it felt "right" to ignore a bug indefinitely.
That's risk management. If the risk of losing the customers' (or future prospects') revenue is big enough, you should fix the bug. There might also be the risk of fines.
It's like building a wall; if one layer of bricks is laid unevenly, at least a number of layers built on top of it will have to compensate. Usually, this compensation takes form in increased development times or increased complexity / convolution of new features.
Furthermore, it lowers end users' overall trust in the platform.
Both of these two effects will have at least some negative impact on profitability, though it may be lower than the increased profitability gained by adding new features.
I'm not saying all bugs should be fixed immediately at the expense of new features, but I've rarely been in a situation, where it felt "right" to ignore a bug indefinitely.