Most research doesn't fail in the field. It fails in the moment between what was found and what gets measured.
There is a room most senior researchers recognise.
A qualitative debrief. A finding appears that doesn't fit, a behaviour nobody anticipated, a motivation the brand has never named. There's a pause. Someone says interesting. The meeting moves on.
The next day, the quantitative design doesn't include it.
Not because anyone ignored it. Because the team already had a hypothesis. They'd worked in this category before. The finding didn't fit what they believed, so it got reframed, explained away as an outlier, a cultural nuance, something that probably wouldn't scale. Quietly removed from the design.
The research is completed. The data looks robust. The conclusions feel evidenced.
"Twelve months later, in market, the consumer behaves in a way the research said they wouldn't."
This is not an edge case. It is a structural flaw in how research is designed at scale. The methodology has no check on the interpretation layer, the point where unexpected findings are translated into what gets measured next. That is where prior belief reasserts itself. And where the error enters.
In beverages and FMCG across emerging markets, that error compounds quickly. Consumer behaviour in these markets shifts faster than trackers adapt. Assumptions that shaped a design in year one are often wrong by year two, not visibly, not dramatically, but wrong enough to misdirect a pricing call, a reformulation decision, a channel investment.
Experience doesn't solve this. At scale, it amplifies it. The more a team knows a category, the more confidently they interpret new evidence through what they already believe. The firms best placed to catch the error are the least likely to see it.
Cambridge Strategy & Insight was built around that specific failure point.
Independent check at the interpretation layer
Before the quantitative design is approved, before fieldwork begins, a review with no stake in the client relationship and no prior position on the category. Its only function is to ask what happened to the finding that didn't fit.
Disconfirmation in writing, before fieldwork begins
Where the hypothesis is unlikely to survive disconfirmation, that is stated in writing before a single question is written. This is not a feature of the work. It is a condition of it.
Local market knowledge built in from the outset
Not as validation at the end, as a structural input at the start. The team composition changes by market. Local design knowledge is built in, not consulted.
No retainers. No trackers. No volume.
Each engagement is built around a specific decision, scoped to what that decision requires. Fixed fee per project. Clients return for one reason: the last piece of work changed what they did next.
Experience built market by market, across six regions.
Organisations worked with — client-side, agency, and independent
We scope around the decision, not the research questions you arrive with.
We start every engagement by asking what you will do differently if the hypothesis is wrong.
If you cannot answer, we redesign the brief together before accepting it.