From a tool gap to a question to verify
Illustrative example: an author asks how to manage support conversations without manual copying. First understand the volume, workflow, and tools they have tried.
Use job-focused keywords
Try terms about support workflows, repeated tasks, and tool searches; exclude topics your team does not serve.
Retain source evidence
Record the observed need and unknowns in the Inbox. Use separate tags for feature research and potential assistance.
Choose a useful response
Read the rules and consider a clarifying question before a product introduction. Refer only to verified product capabilities.
Bring the evidence into a team research loop
Sync source-backed leads to the workspace. Group recurring problems, revisit disproven assumptions, and update the AI profile when positioning changes.
- Do not infer a budget merely because the author dislikes a tool.
- A competitor mention is not a confirmed purchase signal.
- Research findings do not guarantee conversion or revenue.
