← Back to Use Cases
Product · Strategy

Market Mapping And Product Signals

Teams tracking a fast-moving category need more than scattered screenshots and notes. This workflow keeps launches, pricing shifts, messaging changes, and competitor moves in one place.

Electron App · Deep Research

Track The Market As A Living System, Not A One-Time Scan

Use Deep Research to watch category shifts, compare product moves, and keep a living market map instead of restarting the scan every time.

Research Question
Map the category, track what changed across competitors, and turn this cycle into a KB that supports the next strategic question without another fresh crawl.
Kendr Electron app Deep Research workspace for market mapping and product signals
Output package
Market map, signal tracker, implication summary
The run should turn noisy movement into something the team can act on.
Decision motion
Track category change without losing the long view
This is for teams watching launches, pricing, and message shifts over time.
Reusable memory
Market KB + change cycle
Each cycle should leave behind a better category record.
Focus
Category map, messaging, pricing, launches
Watch what changed and where whitespace is opening up.
Source families
Product sites, docs, news, launch pages
Use both official claims and public market signals.
Output package
Map, signal log, implications
Keep the output useful for product and strategy conversations.
Knowledge retention
Market KB + change cycle
One tracking cycle should make the next one easier.

Primary workflow

Deep Research

Track competitors, launches, messaging, and pricing across many sources.

Secondary value

Knowledge Base

Turn one-off scans into a living category record the team can return to.

Why Kendr

Continuous market context

The value compounds when market research becomes reusable rather than disposable.

Run with a live category

Use the prompts below against a category you actively track. The placeholders on this page are intended to hold real signal maps, change logs, and reusable competitive KB views after your Kendr run.

What The Team Needs

Product and strategy teams need a repeatable way to see who changed messaging, where pricing moved, which launches matter, and where whitespace is opening up.

What Kendr Should Produce

A market map, a competitor signal log, a concise takeaway deck or summary, and a reusable KB that supports future follow-up questions.

Prompt Samples

Run These In Kendr

Prompt 01 · Category Scan
Map the [category name] landscape.

Focus on:
- major players and their ICPs
- product positioning and messaging
- pricing and packaging patterns
- notable launches, integrations, or capability claims
- where the category appears crowded versus under-served

Keep citations for every signal and flag weak evidence separately.
Prompt 02 · Product Signal Tracker
Track product and messaging changes for [company list] over the last [time period].

I want:
- notable website or messaging changes
- launch announcements or roadmap clues
- changes to pricing, packaging, or ICP emphasis
- strategic implications for our product team

Summarize what changed, why it matters, and what we should monitor next.
Prompt 03 · Market KB
Create or update a KB session named market-intel-[category]-[date].

Store the market map, competitor pages, launch notes, pricing evidence, and summary artifacts.

Then provide:
- the current market narrative
- what changed materially in this cycle
- what future questions this KB can now answer faster
Example Deliverables

What The Team Gets Back

Category map

Add the structured market map produced from Prompt 01.

Change log

Insert the product and messaging changes captured in Prompt 02.

Implication summary

List the top decisions or product implications for the team.

Market KB snapshot

Show the saved knowledge base and what it now contains.

Join Early Access