A brief that keeps the open questions.
Bring research documents together into a useful starting point, with references and a clear distinction between observations and assumptions.
Illustrative workflow. Interview notes and launch documents below are fictional.
Frame the research.
Turn these interview notes and launch assumptions into a market-entry brief. Separate supporting evidence from open questions.
Give the agent the decision to support, the authorized reference material, and the questions the brief needs to answer. Specialist instructions and reusable Skills can capture a team’s preferred research method.
An interview is a signal, not a market estimate.
In this fictional example, interview notes describe time spent reconciling spreadsheets, meeting notes, and slides before monthly reviews.
“For the monthly review, we rebuild the story from spreadsheets, notes, and slides. Checking the final numbers takes another round.”
Source: Customer interviews.pdf, page 2. Fictional excerpt.
This supports a hypothesis about reporting friction among the people interviewed. It does not establish market size, frequency across an industry, or willingness to pay.
Organize what is known and what is next.
Supported observation
The sample interview identifies a recurring reporting task with a separate verification step.
Working hypothesis
A focused pilot could test whether combining data and documents reduces the effort of that review.
Unvalidated assumptions
Willingness to pay, repeat usage, market size, and acquisition channels remain open. The supplied notes do not answer them.
Proposed next step
Define one pilot task and success criteria, then review the result with prospective users. This is a suggestion, not an observed outcome.
Make the brief usable by someone else.
Keep the original question, relevant references, conclusions, limitations, and proposed next steps together. Reports give your team an artifact to inspect and discuss; editing and sharing behavior depends on the configured workflow and permissions.