Ah, the excitement of a greenfield project. It’s almost like the smell of Spring when everything is just about in bloom, and there’s the promise of life begun anew. Your team has a pretty good idea of the business goals; they’re researching best-of-breed solutions to achieve them and looking forward to learning new technologies. It’s one of the most enjoyable times for a project team. But somewhere between starting to write the RFP and vendor demonstrations, it’s time to pump the brakes. Hard.

Have you seen an enterprise software contract recently? It reads like a menu written in a language that’s still being invented, with editions stacked on tiers, stacked on add-ons, each one priced differently depending on three other things you also did or didn’t buy.

Why? Because the right solution may not be one of the members of the assumed short list. It may not have the new feature that has your team members salivating. It might not even have everything needed to meet every requirement of the matrix that hasn’t been prioritized yet. But it has one major advantage over all of the others – your organization already owns it.

Don’t believe it? Here’s a challenge: walk into any large enterprise organization and ask where the list of all the software currently licensed is. You’ll be met with a blank stare. OK, fine. Ask who you can talk to who owns those licenses. Again, blank stare. Even if you’re lucky enough to find a person who owns one, it’s guaranteed that they don’t own all, or even most of them.

For the sake of argument, let’s say everyone who owns a software license in the organization still works there, and you have managed to assemble them all in a single room. Ask them what you are entitled to use in their contract. Again, a guaranteed blank stare. Sure, they will probably know what was used in the project it was originally procured for, but that’s not remotely close to the full picture.

Have you seen an enterprise software contract recently? It reads like a menu written in a language that’s still being invented, with editions stacked on tiers, stacked on add-ons, each one priced differently depending on three other things you also did or didn’t buy. As these companies grow through acquisition, the contracts have become impenetrable even to the veterans who negotiate them for a living.

So, here’s the key: Before the RFP, before demos, before the team falls in love with a feature, spend the effort to find out what you already own. Take the time to understand the full picture, not just the piece that was used on the project it was originally bought for. Find the dormant modules, the switched-off features, and the capabilities buried in an agreement that nobody’s read since it was signed.

It’s tedious work. Nobody gets promoted for it. But the incumbent doesn’t have to win on features. It only has to do enough, at a fraction of the total cost of standing up something new. Licensing, infrastructure, integration, and upskilling: choosing a new platform means paying for all of those again. The one you own has already paid for most of them.

That’s the calculation that actually belongs in the business case. No magic quadrant can tell you that.