> no revenue line to follow, and no market to lose

Two paragraphs later, the topic is:

> Cost

I mean this is just incredibly lazy thinking and writing. There's always a cost line to follow, just because there's "not a revenue line" means absolutely nothing it just sounds pithy.

And if you cut your cost hard enough, you will put platform stability in danger, or hamstring your engineering org's ability to test and iterate, which will make you lose your market.

Again, incredibly lazy thinking and writing.