Use case

Competitive research you can still follow next week.

Give each competitor and each question its own branch, keep the sources attached, and merge the findings into one comparison.

Try Bonscape

What the canvas looks like

  1. 01

    Put your requirements on the canvas

    Add the brief or requirements document once. Every branch can use it.

  2. 02

    Branch per competitor

    Ask the same questions in each branch, with web search on for current pricing and features.

  3. 03

    Go deep where it matters

    Fork a branch to test one risk, such as a rate limit or a missing integration, without disturbing the overview.

  4. 04

    Merge into a recommendation

    Bring the branches together and ask for a comparison against your requirements.

Research in one chat: Findings about one vendor leak into the next

Research on the canvas: One branch per competitor keeps them apart

Research in one chat: Sources are links you pasted somewhere

Research on the canvas: Pricing pages and docs sit next to the claims

Research in one chat: “Why did we rule them out?” means scrolling

Research on the canvas: The branch that ruled them out is still there

Guide

How to do competitive research with AI

AI is good at reading a lot of public material quickly. It is less good at keeping five companies straight in one conversation. A sound process plays to the first and protects against the second.

Start from what you need to decide

Competitive research without a question becomes a pile of facts. Write down what the research is for: choosing a vendor, positioning a product, pricing a plan. Then list the criteria that matter. Put that document on the canvas first, because every later step will be measured against it.

Keep each competitor separate

When several companies are discussed in one thread, details migrate. A feature of one gets attributed to another, and by the tenth message nobody can say where a claim came from. Giving each competitor its own branch prevents this. Ask the same set of questions in each, with web search on so pricing and features are current and cited.

Go deep without derailing

Some questions need more than an overview: will this API limit hold at twice our volume, does this integration cover our case. Fork those from the relevant competitor’s branch. The deep dive is recorded where it belongs and the overview stays readable.

Merge, then verify

Merge the competitor branches into one chat and ask for a comparison against your criteria. Before you share it, open the sources behind any claim the decision rests on. Public pages go out of date and models can misread them.

When you send the result to colleagues, share the project instead of pasting the summary. They get the reasoning and the rejected options along with the conclusion.

Bring one critical discussion to Bonscape and see how it makes every dot connect.

Try Bonscape