A specific product. A market you are entering. A question the published report does not cover.
We define the scope, sources and deliverables around your question.
Start your research brief Explore an exampleExplore how a business question changes the scope, evidence and intended output of a research project.
Installation data, product specifications and operator interviews, where feasible.
A segment-level opportunity assessment, with the market boundary and key assumptions made explicit.
Company disclosures, technical portfolios and industry enquiries, with coverage gaps identified.
A supplier landscape organised by product capability, application and geographic presence.
Product requirements, technical literature and customer interviews, subject to participant access.
An assessment of purchasing criteria and application needs, with interview scope and evidence limits stated.
Illustrative examples. The scope and feasibility of each project are agreed individually.
The useful work starts with agreement on what the research needs to answer.
Our research approachClarify the product, geography, intended use and questions the study should answer.
Review the proposed approach, sources, deliverables, timing and fee before commissioning.
Bring relevant primary and secondary evidence together. Discuss progress and examine gaps as the work develops.
Review the report and its findings with the research team, including the assumptions and limitations.
A custom study should connect the business decision to evidence that can change it. The exact scope is agreed for each project.
Illustrative deliverable excerpt · EAA in packaging
This is an original public-source illustration, not a completed client engagement or a promise that private records will be available.
Read the analysis behind the excerptStart with the decision and the information that could change it. Name the product or activity being assessed, the geography, the decision horizon and the output you need.
The brief can be developed in discussion. Separating essential questions from useful context gives the project a testable scope without requiring a fully drafted specification.
Check for a specific usable output in the selected edition: the required geography, measure, segment or company coverage. A matching title is a starting point, not proof that the report answers your question.
Where published coverage fits, use it as the starting point. Where a defined gap remains, describe that gap before considering custom work.
Explore published researchDefine the deliverables, investigation depth and available evidence first. Access to sources and the work needed to reconcile them affect the research approach; a requested deadline is a constraint to discuss.
Timing and cost are set out in the project proposal. A narrow, verifiable question and a broad market investigation should not be treated as equivalent scopes.
Identify which conclusion depends on the missing evidence and whether an alternative source can answer the same question. An adjacent indicator may explain context without replacing the missing observation.
Discuss whether the question, scope or interpretation needs to change. Keep the gap visible rather than presenting unsupported precision as a completed answer.
Timing and fees depend on the agreed scope.
Local integration preview. Enquiries are stored in the local test database.