4 ms·
> cut costs, jack up prices, and milk remaining users for as much cash as possible for as long as possible. Don't forget "slash the workforce, ensuring that th
by apparent 3mo ago
> cut costs, jack up prices, and milk remaining users for as much cash as possible for as long as possible.
Don't forget "slash the workforce, ensuring that the product will get worse over time".
- quickthrowman 3mo agoThat’s what “cut costs” means for SaaS, firing people.
- apparent 3mo agoYes, it is part of cutting costs, but there are other ways to cut costs ("synergies" from merging back office functions) that don't necessarily affect the product.
- deleted 3mo ago[deleted]
- JumpCrisscross 3mo ago> Don't forget "slash the workforce, ensuring that the product will get worse over time" Not commenting on Bending Spoons. But in general, a company built to grow is overprovisioned for one being put into maintenance mode. If you're growing, sure, let the designers change the UI every release. If you're trying not to lose customers, don't do that. Which means you don't need a crack team of in-house designers.
- apparent 3mo agoI agree that a company in growth mode needs more employees than one in maintenance mode. But wouldn't the owners already have cut unnecessary employees before selling out to PE or similar?
- JumpCrisscross 3mo ago> wouldn't the owners already have cut unnecessary employees before selling out to PE or similar? Usually not. It's emotionally difficult. And knowing what you need and don't need to cut (versus transition or aggregate with your conglomerate's administrative layer) is its own expertise. If you had that, you wouldn't need Bending Spoons or whomever.