3 ms·
It's software that automates a lot of costly auditing and troubleshooting in complex systems, so the core value proposition is hours that humans don't spend (an
by beat 11y ago
It's software that automates a lot of costly auditing and troubleshooting in complex systems, so the core value proposition is hours that humans don't spend (and reduced downtime). If it can reduce the workload of senior/lead engineers by 5-10%, what's that worth? This sort of thing is really hard to quantify, although I'm sure we'll get more data as it grows.
Does per-seat licensing work best, or something modeling the amount of data being processed? Fixed or floating seats? We're definitely looking at higher pricing, from hundreds to a few thousand per seat annually (not unusual in the market). I'm not worried about whether the product will be loved - we're engineers ourselves, totally focused on the suckiest parts of working on enterprise systems. If our product isn't a pleasure to use, I'll take it as a personal failure. But then we have to sell it. And I'm an engineer solving my own pain points, not a sales guy. That part is new to me!
- dsr_ 11y agoEverybody prefers predictability. That shows up in the comments on this page about people who hate to see "Call for pricing" on the site: it means that the cost is extremely complex. Here's a question: will people want to use the software because it makes their lives easier, or will people want to have the software running because it makes their lives easier? That's the difference between a good per-seat plan (where customers want more seats because employees want to use it) or a good per-[quantity] plan, where nobody cares who is running it but the company does better as a result. Feel free to email me at the address in my profile if you want a deeper discussion.