Many research teams try to solve a communication problem with a metrics problem.
There is a particular kind of frustration that shows up in insights functions that are doing good work and still struggling to be heard. The research is rigorous, the outputs are well-presented, the team responds quickly to requests, but when budget season arrives, research is still the first thing under scrutiny.
The usual response is to build a better case. Track cost-per-study, calculate time saved, develop an ROI model that assigns a value to each insight delivered. Some teams create dashboards, some benchmark themselves against agency rates, some try to attribute a percentage of revenue to studies completed. These efforts are not wrong, but they tend not to work. They answer a question leadership is not asking.
The ROI frame vs. the evidence frame
An ROI framework is, at its core, a defense. It argues that research is worth what it costs, designed to survive a budget challenge rather than shape a strategy conversation.
Leadership does not need to be convinced that research is worth its cost. They need to believe it helps them make better decisions, and those are different problems.
The evidence frame starts somewhere else entirely. Instead of asking “was this research worth it?”, it asks: which decision did this research improve, and what happened as a result? That reframe changes what the team tracks, how it presents findings, and what counts as success. An insight that never reached a decision is not evidence of value, but a recommendation that changed a roadmap, pricing strategy, or customer program, and that can be traced forward to an outcome, is.
What leadership actually wants
Leaders are accountable for results, and when they bring a question to the insights function, they are not looking for a research artifact. They are looking for confidence — specifically, they want to understand what is true about their customers, their market, or their product well enough to commit to a direction.
This means the insights function’s most valuable contribution is rarely the study itself. It is the recommendation that emerges from it: the judgment about what the evidence means and what the business should consider doing next. Delivering that judgment requires understanding what is at stake, which means knowing what decision is being informed, what options are on the table, and what the business would do differently depending on the answer. That context does not always arrive with the research request, and part of the insights leader’s job is to ask for it.
The same principle applies after the study. Following up on what happened, which recommendation was taken and what it produced, is not administrative work. It is how the team builds a credible record of its contribution.
Connecting research to revenue outcomes
Specificity matters here more than scale.
“Our research contributed to a 12% improvement in retention” is a claim that is difficult to make and easy to challenge. “We identified that new customers were struggling to reach their first successful outcome, the product team simplified onboarding based on that finding, and retention among new customers improved in the following quarter” is a story that connects evidence to action to result.
Not every study produces a finding that links cleanly to a revenue number, and that is fine. What the business needs is a pattern of examples demonstrating that research is shaping real decisions on products, customers, pricing, messaging, and investment priorities. Building that record takes time and requires choosing where to focus. Research that reaches a decision, however small, is worth more than research that sits in a library.
Building that record takes time and requires choosing where to focus. Research that reaches a decision, however small, is worth more than research that sits in a library.
Building the internal case
The instinct, when asked to justify research investment, is to build a model: calculate what insights would cost from an agency, or estimate the revenue at risk from a poor product decision. These models have their place, but the more durable case is built from history, not projections.
Start with decisions already made. Identify three or four moments in the past year where research shaped a choice the business made, and describe the decision, the evidence that informed it, and where possible, what followed. This is not a research report; it is a short record of useful contributions. Bring it into the next planning conversation not as a defense, but as a demonstration of how the team works and what it is positioned to do.
The internal case for research investment is not a measurement problem. It is a visibility problem. Leadership tends to undervalue what they do not see working, so the solution is not a better ROI model but a clearer account of what research made possible, told in the language of decisions the business cares about most.
The strongest argument for investing in research is not that the numbers add up. It is that the company keeps making better decisions.
