There were three things I used to take a close look at. One was the head count and not just a simple how many people will it take to look after this. It's a case of the product being self-sustaining and low touch. You can take those people, say you had eight people looking after a legacy system, you now need two. I've got six more people that can actually work on developing innovative solutions for the business, adding business value and generating more revenues for the company.
That's very important to ensure that it is low touch and as self-maintaining as possible. The second piece is around APIs because if you don't have a consistent API with the massive volume of data you're collecting on some of these systems, people are going to want to consume it. You want to be able get that data to and from them as soon as possible.
If you don't have a consistent repeatable API you're basically, you're repeating the development cycle every time a new requirement comes in whereas these things should be pretty much cookie cutter. Once it's done once you can send the data to any other system that you might need to. The other thing that we would look at is solutions that have siloed licensing.
There are products that you buy type of expensive license for network monitoring, one for voice monitoring, one for APM, etc. If you have a product where that is abstracted and you're buying a license to monitor an object, whatever that object could be, it gives you agility. If you need to move your monitoring focus from one area to another area, you're not having to stand up new infrastructures. Significant capex that has to go an be obtained. It makes you more flexible as an organization.