# How to Delegate Competitor Research Without Getting a Generic Report A competitor research workflow that answers a specific decision, checks primary sources, and separates evidence from interpretation. By Righthand Team · 2026-10-07 Source: https://www.righthand.ai/blog/how-to-delegate-competitor-research-without-getting-a-generic-report ## Quick answer Delegate competitor research around a decision, a shortlist, and a set of comparison questions. Require current primary sources for features, pricing, and policies, with links and observation dates. Ask the assistant to explain what each finding changes about your decision, rather than filling a long report with company descriptions. A generic competitor report tends to list what companies say about themselves. Useful research tests a narrower question: how do alternatives serve a particular buyer or workflow, and where does your proposed approach differ? That requires consistent criteria and careful distinctions between public claims, observed behavior, and inference. ## Start with one comparison unit Choose a customer, job, and situation. “Compare productivity products” is too broad. “Compare how a three-person consultancy coordinates client follow-ups through its existing email account” provides a usable boundary. Define the comparison fields before research begins. For that consultancy, relevant fields might include supported communication channels, approval controls, account identity, setup requirements, and the evidence available after an action. A vendor's unrelated analytics dashboard should not dominate the report merely because it has a large feature page. Limit the first pass to a manageable shortlist. Ask the assistant to explain exclusions so you can see whether it has omitted a real alternative or simply avoided an awkward comparison. ## An illustrative competitor question Suppose a founder is considering a follow-up product. The research question is whether existing alternatives leave a meaningful gap between preparing a draft and completing an approved action. No particular vendor behavior is assumed in this example. The assistant should inspect each selected vendor's official documentation for draft handling, send authority, and status reporting. If documentation establishes only draft generation, it should say that. It should not infer autonomous sending from a broad phrase such as “AI-powered workflow.” The resulting brief might identify confirmed capabilities, unconfirmed claims, and questions that require a hands-on trial. Those categories matter more than a decorative score out of ten. They show where the founder can make a decision now and where evidence is still missing. ## A competitor research assignment > Compare the shortlisted products for a three-person consultancy managing client follow-ups. Use current official product pages, help documentation, and published terms where relevant. For each criterion, give the source link and date checked. Separate vendor claims, documented functionality, and your inference. Flag missing or contradictory information. Do not invent tests, customer results, rankings, or prices. Finish with the three differences that matter most to our decision and the trial questions still unanswered. Specify the decision deadline and how much detail you want. An executive brief with a source appendix often works better than a report that interleaves every citation with several paragraphs of background. ## Guard against weak comparisons Compare equivalent plans and use cases. A free tier and an enterprise deployment may serve different audiences. When a capability depends on a plan, deployment option, or connector, preserve that condition in the finding. Record pricing as observed, including billing period and known usage assumptions. If the available page does not resolve your scenario, request a quote or report the gap. Do not turn an incomplete public price into a confident total cost calculation. Include the current workaround as an alternative. A buyer may choose an existing process, a human coordinator, or a shared document rather than another subscription. Research that excludes those options can overstate the value of a new product. Finally, ask what would disprove the proposed differentiation. If your supposed advantage already appears in official documentation, update the hypothesis. The research should be allowed to change the plan. ## Frequently asked questions ### Can the assistant claim it tested competitors? Only if actual tests were conducted and their method and results are recorded. Reading vendor documentation supports a documentation comparison, not a claim of hands-on testing. ### How often should I refresh the research? Refresh decision-critical facts before using them in a purchase or public comparison. Features, plans, and terms can change. Keep the observation date with each finding. ### Where does Righthand help? The [product manager role](/roles/product-manager) includes research-oriented work. Pair it with [task delegation](/features/task-delegation) to define a bounded, source-backed assignment rather than an open-ended competitive overview.