Enterprise technology buyers are not lacking information. If anything, they are overwhelmed by it. Between analyst reports, comparison charts, vendor demos, peer reviews, and now an endless stream of AI-generated summaries, it has become relatively easy to understand what a product does.
What has not become easier is answering a much simpler question: what will this actually be worth to me?
That gap has been there for a long time, but it is becoming more visible now. Buyers are expected to justify decisions more rigorously, budgets are under pressure, and the tolerance for vague “business value” claims is steadily declining. And yet, most of the material available to support decisions still operates on the level of capability, not outcome.
We have optimized for understanding products, not decisions
Analyst research has traditionally been very good at helping buyers understand markets and compare vendors. That is what formats like our own Leadership Compass are designed to do, and they do it well. They provide structure, orientation, and a reasonably objective view of where vendors stand.
But they stop short of answering the economic question. They tell you which product is strong, not whether it is worth the investment in your specific context. Vendors, of course, try to close that gap with ROI calculators and business case tools. These can be useful inputs, but they are not independent. Their purpose is not to challenge assumptions, but to support a purchase decision. As my colleague Jonathan Care put it in a recent discussion, relying on vendor ROI claims is “like asking a chef to review their own restaurant.”
The result is a consistent pattern: buyers move through a structured process of market research and shortlisting, and then switch, quite abruptly, into a much less structured phase where value is estimated, inferred, or simply assumed.
What the Product Value Navigator is trying to do
The Product Value Navigator (PVN) format is an attempt to address exactly that transition point. It was developed by Jonathan Care as a structured methodology to quantify and calculate the value of enterprise technology products in a way that is as close to objective as possible in a space that is inherently difficult to measure.
The idea itself is not to eliminate uncertainty (this would be unrealistic) but to reduce subjectivity and make assumptions explicit. Instead of relying on vendor narratives or opaque ROI calculators, the PVN applies a consistent framework that connects technical capabilities with measurable outcomes and then translates those outcomes into economic terms.
What makes this more than just another report format is the way the methodology is implemented. Alongside the conceptual framework, Jonathan has developed a set of supporting tools that automate large parts of the process. These cover, for example, the structured collection of customer input, the analysis and classification of vendor claims, and the validation of those claims against available external data sources. This is not just about efficiency; it is about consistency and traceability. The same logic is applied across assessments, and the steps can be revisited and reviewed.
The financial modeling itself follows the same principle. The calculations are based on a defined set of formulas that are intentionally simple enough to be understood by non-technical stakeholders, while still being robust enough to produce reliable results. This is a delicate balance, but an important one. If the model is too complex, it becomes opaque. If it is too simplistic, it becomes meaningless. The PVN tries to stay in the middle, with a model that is transparent, reproducible, and capable of providing an audit trail for how each result was derived.
What this looks like in reality
The first example of this approach is the PVN for ManageEngine PAM360. What is interesting here is less the headline than the structure behind it.
- The model arrives at a 219% return on investment with a payback period of just under four months, based on a defined baseline scenario.
- Only hard savings are used to calculate that ROI, while softer effects such as productivity gains or risk reduction are quantified separately but not used to inflate the core number.
- The assumptions are visible and tied to external benchmarks, rather than embedded in a black-box calculator.
- Perhaps most importantly, the limitations are explicit, including the fact that only a subset of vendor claims can be independently validated at this stage.
This does not eliminate uncertainty, but it makes that uncertainty visible, which is arguably more useful than pretending it does not exist.
Why this matters now more than ever
There is a broader shift underway in how technology decisions are evaluated. The industry is slowly moving away from feature-centric thinking towards outcome-oriented decision making. Finance departments are asking harder questions, boards expect clearer justification, and “because it is the best product” is no longer a sufficient answer.
At the same time, the overall quality of available information is becoming more uneven. The rise of AI-generated content makes it easier to produce plausible-looking analysis at scale, but it also increases the difficulty of distinguishing between well-founded conclusions and recycled assumptions. In that environment, transparency of methodology becomes critical.
Against that backdrop, the idea of an independent, structured view on economic value starts to make more sense. Not because it provides certainty but because it introduces a level of discipline into a part of the process that has historically been quite loose.
A shift in expectations
It is important to see the PVN in the right context. It is not a replacement for existing research formats. Understanding market positioning and technical capabilities remains essential, and nothing in this approach changes that. What it adds is a structured attempt to connect capabilities to measurable outcomes. In that sense, it sits later in the decision process, closer to the point where buyers have already narrowed down their options and need to justify a choice.
If buyers begin to expect independent validation of value, not just capability, then this changes the expectations placed on vendors as well. Claims about ROI or efficiency gains will need to withstand external scrutiny, rather than being accepted at face value.
For analysts, the same logic applies. If independence is the core value proposition, then it needs to extend to the dimension that ultimately drives decisions. That dimension is not functionality or market position, but whether the investment makes sense.
The question that remains
Every technology decision eventually leads to the same question, even if it is not always asked explicitly: was it worth it? We have spent a lot of time helping buyers get to the point where they can decide with confidence. We have spent less time helping them answer that question in advance.
The Product Value Navigator is an attempt to close that gap. It will not remove uncertainty, and it should not claim to. But it does move the discussion from assumption to analysis, and that alone is a step in the right direction.
