The other might help get you a renewal after the initial contract is up, but on the other hand, once something is in the budget and established, it has to be really, really awful to get kicked out and go through the process of finding a replacement. Voila, enterprise software!
Slack, for example, a lot of the requests came from engineers to work with it.
The product has to be REALLY good though, for most, this is a very hard sell
So you end up talking on Slack about an issue someone's noticed, and then trying to decide whether it's "worth" the bother of creating a ticket for, or if someone's aware of a ticket already for it, or or or.
storytime:
We had a demo scheduled with a company. We were shopping for a security auditing system for dependencies across all GitHub repositories.
The person going through the demo did an absolutely terrible job at reading the room and understanding who they sell to (right now). Focused a lot on reporting, compliance while we cared more about the mechanics.
If so, I’d love to hear you feedback on our demo, if not I’d love to offer you a demo.
But the funny thing is that a slightly different pronunciation of "Xi Zhao" changes the meaning from (roughly) "western prosperity" to "morning bath".
But I am now actively looking at it.
That is just not true in most cases.
We all know these products with elaborate dashboards, too much reporting, too many data points. Those are created simply to appeal for the decision makers.
You sell to developers by a better UX/UI and workflow, you sell to decision makers by telling them how they will get a better view of things and manage teams better.
You have to build both ends, and you have to sell the decision making end much better and much more aggressively.
Edit: typos