Build
Report
Your project would typically start with a decision workshop, in person or remote. We invite people from your team who will use and act on the research findings. The job of that session is to name the business decisions the research has to support. From each decision we work out what has to be known, then who to ask and how. That decision matrix defines the scope, and nothing enters the study that does not trace back to a decision on it.
A study focusing on a new product, service or feature has to hold up in two streams at once. Product and pricing teams want the evidence on feature preferences and value. Local distribution channel teams want to know what customers in their territory actually said. We report for both.
What arrives, and when
- Decision matrix, agreed before a single interview is scheduled. It is the reference we report against at the end.
- Midpoint readout while fieldwork is still open. Early signals reach you in time to change the remaining waves.
- Full report: analysis, charts, customer evidence in their own words, video clips. Most importantly, you get a recommendation against each decision on the matrix.
- Executive presentation, delivered live to the group who was part of the design workshop.
- Underlying raw data delivered in a convenient format.
Trade-offs, and the simulator
When the question is a trade-off, price against a feature improvement, a service against delivery speed, we run choice-based conjoint and hand over a working simulator. Change a price point, add or remove a feature, and watch preference move across segments and against named competitors. We know that our clients use the simulators we built months after the report was signed off, often answering new questions that emerged after the study was fielded.