This seems really flawed. Let's plug in numbers. This says that if a service costs 125$/month/employee and I have 1000 employees ($125000/month) I will save ~5 million a year. However a service costing 1.5 million at such a company has other costs. Namely that a product that costs that much almost always needs an in house support team. I have never seen the case where an expensive product also didn't need 2-3 people…
This complaint seems really flawed. > PagerDuty for example doesn't save people any time, it just sends alerts. Have you tried building a pagerduty in house? That is literally the time save. The "value of pagerduty" is still measured the same way as any other tool. Do I build it custom in house? Do I pay someone else a modest amount? That is what this tool is doing and is geared towards startups who make this decisio…
Half the products we have bought have had full internal teams to support. And many don't suite our needs, so we have enitre development teams building abstractions that are more complex than the product we bought so we can use the product we bought. And some of those abstractions have been in development for 2 years so no one can use the product yet.
My only point is that buying vs building is complex. When you boil that down to a tool that essentially says always buy, it causes a bit of PTSD for me.