Research
Research brief
Answer a research question with a sourced brief: the answer first, then the evidence, how confident it is, and what could not be found.
Add in the app
Research · For your bots
Competitor scan
Compare named competitors on what matters to a decision (price, audience, features, recent moves) from their own public pages.
In Lobstack: Skills › Library › Add
Download LobstackWhen to use it
Someone needs to know how a product stacks up against named competitors, or who the competitors are.
What your bot will do
- 01
Confirm the list and the decision behind it: pricing, a pitch, a roadmap call. With no list, propose five and wait for a yes.
- 02
For each, read their own pricing page, product pages, changelog and docs. Record the date you read each; pricing changes.
- 03
Build one table: company, who it is for, entry price and what it includes, three strongest features, one thing it does not do, most notable move in the last six months.
- 04
Mark anything inferred rather than read. "Price on request" stays that; never estimate a price and present it as found.
- 05
Under the table, What this means: three to five points tied to the decision, including where we are behind. A scan that finds only strengths is not believed.
- 06
Where prices are comparable, add a bar chart of entry and mid tiers in a chart fence.
- 07
Post it as a document with every row linked to its source, and offer to repeat it on a schedule.
Public information only: no trial sign-ups, forms or contacting sales without asking first.
The file
---name: competitor-scandescription: "Compare named competitors on what matters to a decision (price, audience, features, recent moves) from their own public pages."metadata: title: "Competitor scan" category: research tags: [competitors, market]--- ## When to use this Someone needs to know how a product stacks up against named competitors, or whothe competitors are. ## How 1. Confirm the list and the decision behind it: pricing, a pitch, a roadmap call. With no list, propose five and wait for a yes.2. For each, read their own pricing page, product pages, changelog and docs. Record the date you read each; pricing changes.3. Build one table: company, who it is for, entry price and what it includes, three strongest features, one thing it does not do, most notable move in the last six months.4. Mark anything inferred rather than read. "Price on request" stays that; never estimate a price and present it as found.5. Under the table, What this means: three to five points tied to the decision, including where we are behind. A scan that finds only strengths is not believed.6. Where prices are comparable, add a bar chart of entry and mid tiers in a chart fence.7. Post it as a document with every row linked to its source, and offer to repeat it on a schedule. Public information only: no trial sign-ups, forms or contacting sales withoutasking first.