Start with the decision
Explain what your team needs to decide and what is preventing progress. Examples include identifying product associations, screening potential implementations, prioritizing families or understanding a technology field. Mention any decision date. A research service name is less useful than a clear description of the problem.
Bring the information you already have
A non-confidential summary can identify the approximate number of families, whether products are known, relevant versions, markets and the existing source materials. Do not upload privileged or sensitive information in the initial inquiry. Confidentiality and a suitable transfer method can be discussed before more detailed materials are shared.
State what would make the work usable
Explain who will review the findings and whether they need a workbook, chart, report or briefing. Say what existing process or identifiers the output should fit. Identify which questions require legal judgment, engineering input or internal approval rather than expecting the research to settle them automatically.
Questions to ask on the call
Ask what the proposed work includes, who researches and reviews it, how uncertainty is recorded, what happens when evidence is unavailable and which further work is excluded. Discuss timing, revision scope and a fixed-fee proposal after the research boundaries are understood. Prices are agreed privately.
A useful first message
We have a defined portfolio or product question and need help establishing the evidence. We can describe the relevant technology, what we know already and the decision this affects. We would like to discuss a practical scope and the output our team would receive.