Custom Market Research Brief: How to Write One
A strong custom market research brief explains the decision behind the research, the market boundary, the audience, the evidence needed, and the form the answer should take. It gives a research partner enough direction to work well without pretending the conclusion is already known.
What decision should the brief support?
Open with the decision, not the request for a report. Are you assessing a market entry, product roadmap, acquisition, pricing move, capacity plan, partnership, or investment? State what will happen after the work is delivered and who will use it.
**A research brief should make the decision visible while leaving the answer open.** If the team has a preferred conclusion, record it as a hypothesis to test. This protects the work from becoming a search for confirmation.
How should scope and market boundaries be written?
Define the product or service, customer groups, use cases, geography, channels, time horizon, and adjacent alternatives. Note what is out of scope. If terminology differs by region or industry, include the working definitions and the terms people use in the market.
Describe the level of detail needed: global view, country cuts, segment comparison, competitor profiles, buyer interviews, channel analysis, or a forecast. **A narrow scope with a clear decision is usually more useful than a broad inventory of everything related.**
What evidence should the research collect?
List the questions that cannot be answered from existing internal knowledge. Separate secondary research, expert interviews, buyer research, channel evidence, company analysis, and quantitative modelling. Explain how evidence should be challenged and how conflicting signals should be handled.
Ask for source transparency and a distinction between observed evidence, respondent opinion, analyst interpretation, and scenario assumption. The [ICC and ESOMAR International Code](https://shop.esomar.org/uploads/public/knowledge-and-standards/codes-and-guidelines/ESOMAR_ICC-ESOMAR_Code_English.pdf) is a useful reference for responsible research relationships and participant protection.
How should respondents or participants be described?
Define the role, organisation type, geography, experience, and decision responsibility that matter. Avoid choosing respondents only because they are easy to reach. Explain screening requirements, exclusions, incentives where relevant, consent expectations, and how sensitive information will be handled.
If the audience is hard to reach, say so early. A research partner can then propose a feasible sample or a different evidence path. **The brief should make access constraints explicit rather than hiding them until fieldwork begins.**
Which deliverables and review points are useful?
Name the output needed for the decision: a market model, interview synthesis, competitor map, opportunity shortlist, scenario view, workshop, executive summary, or a deeper report. Specify the audience, format, working session, data files, and whether the underlying assumptions must be editable.
Set review points for the framework, instrument, early signals, and draft conclusion. Review should test relevance and reasoning, not steer the answer toward a predetermined outcome. Include the final questions the team should be able to answer after delivery.
What should a supplier compare in its proposal?
Compare the proposed method, evidence plan, team, timing, deliverables, assumptions, access approach, quality controls, and total cost. Ask what the supplier will not be able to answer and what client inputs are required. A clear limitation is better than an implied promise.
Consider how the work will be used after delivery. If the model needs monthly updates or a leadership workshop, include that in the scope. **The best proposal is the one that matches the decision and can be operated by the buyer.**
Options compared
A rapid desk study, a focused custom brief, a mixed-method project, or an ongoing research programme can each be right for a different decision.
Choose the smallest research design that can answer the material questions with credible evidence and a usable decision path.
| Brief type | Best fit | Strength | Limit |
|---|---|---|---|
| Rapid desk study | Early directional question | Fast context | Limited primary evidence |
| Focused custom brief | One material decision | Clear relevance | Narrow scope |
| Mixed-method project | Complex market uncertainty | Triangulated evidence | More time and coordination |
| Ongoing programme | Repeated strategic questions | Continuity and learning | Longer commitment |
What does not matter as much as buyers think
A long list of research questions, a famous method label, and a thick report do not guarantee a useful result. **A clear decision, disciplined scope, transparent evidence, and an agreed use for the answer matter more.**
Do not write the brief as a disguised solution specification. Describe the problem, the evidence needed, and the decision criteria so the research can reveal an inconvenient answer when the evidence warrants it.
Buyer checklist
- Define the custom market research brief: how to write one decision in terms of the users, scope, timing, and owner who will act on the result.
- List the inputs, dependencies, boundaries, and exclusions that shape this market research reports question before comparing suppliers or methods.
- Separate observed evidence, supplier claims, assumptions, and judgement so the final recommendation remains traceable.
- Test the normal path, a missing input, an exception, an outage, and a change in ownership before calling the option ready.
- Model implementation, support, governance, monitoring, training, renewal, and exit instead of comparing only the purchase price.
- Set a baseline, success criteria, review date, and stop or scale condition that the operating team can measure.
- Record what would change the decision, which evidence is still missing, and who owns the next review.
Use this checklist as a working brief for the custom market research brief: how to write one decision. Keep the evidence, assumptions, and open questions together so a later review can update the conclusion without rebuilding the entire case.
Questions to take into a review
- Which user, customer, or operator is this custom market research brief: how to write one decision meant to help?
- What evidence supports the proposed result, and what evidence is still a claim or assumption?
- What happens when the input is incomplete, delayed, wrong, or unavailable?
- Which team owns the workflow after implementation, including support, monitoring, and exception handling?
- What dependencies, permissions, integrations, or changes could delay adoption?
- How will the organisation measure value, risk, cost, and unintended work after launch?
- What is the smallest reversible test that could strengthen or reject the decision?
For a custom market research brief: how to write one review, keep the decision boundary explicit. If the evidence answers a narrower question than the team wants to decide, say so. A useful next step may be more data, a smaller pilot, a different supplier, or a decision to wait. That clarity is part of the research value. It also makes the final recommendation easier to explain to finance, operations, risk, and leadership teams. Do not hide uncertainty in a footnote. Keep the working record with the final answer so future reviewers can see how the conclusion was formed. That is how a useful article becomes a disciplined decision brief for review. It keeps the scope honest when several teams have different expectations about what the evidence can prove. That discipline prevents a technical benchmark from being mistaken for a complete business case. It also gives the buyer a clean record for procurement, implementation, and later renewal decisions. That record should be brief enough to use, and detailed enough for teams to audit and revisit in a later review.
FAQ
What should a custom research brief start with?
The decision, audience, timing, and consequence the research is meant to support.
Should a brief include a hypothesis?
Yes, when useful, but label it as a hypothesis to test rather than a conclusion the research must confirm.
How much scope is enough?
Enough to define the market boundary, key questions, evidence, audience, deliverables, and exclusions without prescribing a result.
What should a buyer ask a research partner?
Ask what the method can answer, what it cannot answer, what client inputs are needed, how evidence is checked, and how the findings will be used.
Where can I start the conversation?
Review the [market research category](/categories/market-research/) and [talk to an analyst](/contact/) about the decision and scope.
Sources and further reading
Browse the research categories, read a related report, or talk to an analyst about a focused brief.