If you are a research consultant, by the time you're sitting in the kick-off meeting, the fate of your research has already been decided. It was decided during the sale.
The statement of work was written. The budget was set. The timeline was locked. And somewhere in that process, research was either scoped as a real, funded activity – or it was reduced to a line on a slide that says "research-informed approach" and means nothing.
I've spent 20+ years as a consultant working with organizations like Harvard Medical School, The Rockefeller Foundation, St. Jude Children's Research Hospital, and S&P Global. And I've learned this the hard way: the best researchers in the world can't save a project that was sold without research in the budget. You can advocate all you want at the midpoint. By then, the money's gone.
So here's my argument: if you're a consultant who cares about doing real research – not just checking a box – you need to get involved before the contract is signed. The sales process is where research either gets protected or gets sacrificed. And most researchers treat it as somebody else's problem.
It's not. It's yours.
Why this matters more now than ever
There's a related trend making this worse: AI tools are flooding the market promising "research insights in minutes." What those tools are actually selling is a simulation of what consultants do – synthesis happening invisibly, by an unaccountable process, presented as a finished conclusion. The client can't see the reasoning. They can't challenge the methodology. They just get an answer.
That makes these tools a direct threat to the consultant model specifically. And it makes the quality of your research – and your ability to show clients the transparent path from data to conclusion – more important than it has ever been. You can't defend that path if research was never properly scoped in the first place.
10 practical suggestions
These are recommendations I presented at UXPA Boston 2026 with my co-author Denise da Costa Graeff. They emerged from our ongoing research into how organizations succeed and fail at spreading research practices beyond dedicated research teams. But you don't need to be running a formal program to use them. These apply to any consultant, on any engagement, who wants to do honest work.
1. Collaborate with sales and account management. Many sales and account management teams are already conducting original research for their pitches – usability tests, focus groups, competitor audits – but doing it poorly. Help them conduct real research and position yourself as someone who strengthens their pitches, not someone who slows their process. This is a relationship investment that pays off long before any specific project.
2. Review the RFPs. Ask to see the RFPs your company is pursuing. Use the question period to ask about existing research: what's been done, how old it is, whether you'll have access, and whether it can be reviewed before the pitch. These are reasonable questions. They also signal to the client that you take research seriously – which is a differentiator.
3. Preview sales presentations. Make sure real research is represented in the pitch – not just a slide that says "research-informed approach." Help your sales team describe it in language that meets your standards of rigor. If you can't explain what the research will actually involve, the client can't evaluate whether they're getting the real thing.
4. Document risk. Help the sales team articulate the risk of any research efforts the client chooses not to purchase. Make the cost of not doing research visible before the contract is signed. This isn't fear-mongering. It's professional responsibility. Doctors don't skip the diagnosis because the patient doesn't want to pay for blood work.
5. Insist on accurate cost estimates. Ensure the research cost estimate is sufficient to conduct real, thorough research. Underscoped research produces undercooked findings. And undercooked findings produce bad decisions that cost the client far more than the research would have. If you've ever had to cut a study short because the hours ran out, you know exactly what this feels like.
6. Review existing research. Insist that any research the client has conducted is accessible for your entire team's review – not just the strategist or researcher. This includes customer surveys, interviews, personas, journey maps, market research, competitor audits – anything that exists. Research that lives in one person's inbox isn't organizational knowledge. It's a liability.
7. Review the statement of work. Ask the sales team to document the risk of any research that is not included in the SOW. If it's not scoped, budgeted, and scheduled, it won't happen. This is the single most important sentence in this article. Say it again: if it's not scoped, budgeted, and scheduled, it won't happen.
8. Make it visible at kick-off. At kick-off, ensure the entire team understands the risk of any necessary research that was not included in the SOW. Make it visible from day one – not discovered at the midpoint when there's no time or budget to recover. The project manager needs to know. The designers need to know. The developers need to know. Everyone who will be making decisions based on research that doesn't exist needs to know it doesn't exist.
9. Fight for real stakeholder sessions. Try like hell to conduct sessions with people who reflect the organization's actual stakeholders – not hand-picked advocates with predetermined opinions. And all team members – not just strategists and researchers – should be invited to attend or review stakeholder sessions. When the designer hears the stakeholder say it, that's a different kind of evidence than when you summarize it in a slide.
10. Never conduct confirmational research. Though project managers may be persuasive, do not run studies designed to confirm what the client already believes or what your strategists have already recommended. Make sure every study is legitimately designed to discover what's true. This is the line. Everything else on this list is negotiation. This one isn't.
A reality check
It is unlikely that all ten of these will be available to you on any given engagement. Clients can be led to water but can't be made to drink. They will probably see research as an optional expense – nice to have, first to cut.
But documenting the risk helps. Every time you put the cost of not doing research in writing, you're building a case that outlasts the project. You're creating a record that says: we told you this mattered, we told you what would happen without it, and here's what happened. Over time, that record changes conversations.
And here's the thing about fighting the good fight: sometimes you lose the battle and win the war. The client who said no to research this year remembers that you were right when their redesign underperforms. The sales team that pushed back on your RFP questions starts asking them on their own when they see how the ones you scoped properly turned out.
Real research isn't just a deliverable. It's a reputation. Protect it.
Jim Dalglish is a digital strategist, UX researcher, and information architect with 20+ years of experience. He is co-author of the forthcoming book Research Literacy in the Age of AI with Denise da Costa Graeff, and co-developer of the Research Literacy Framework™. Their UXPA Boston 2026 talk, "Without Research Thinking, Your Democratization Program Isn't Research. It's Research Theater," explored why tool access without research thinking produces work that looks like research but fails like guessing. Learn more at researchliteracyframework.com.