How to use the Competitive Research Question Generator.
Competitive research should answer a decision the team can act on. Limit the questions to evidence that can be collected legitimately.
Make the workflow fit your task.
Start with the business decision and identify the evidence needed to resolve it. Form questions about workflows, constraints, alternatives and tradeoffs, then map each to a legitimate research source. Avoid a feature inventory that has no connection to the decision.
- What you provide
- Decision and known market context.
- What you get
- Focused questions and evidence collection plan.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Decision: build scheduled imports or occasional file comparison first. Research must distinguish those needs; no competitor facts supplied.
Completed example
Research questions: 1. How often do buyers receive updated files? 2. Who reviews changes before data is accepted? 3. What happens when an unattended import fails? 4. Which existing products support review before applying changes? 5. What setup and maintenance do those options require? Decision use: compare evidence for recurring unattended work against occasional human-reviewed comparisons; do not rank products before collecting it.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should competitor research ask which product has the most features?
Only if feature breadth is relevant to the decision. Workflow fit, switching costs and failure handling may be more informative.
Why do research answers fail to change the team's decision?
The questions may not distinguish between the options under consideration. Tie each question to a possible decision consequence.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑