- Industry
- IT Company
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Assistant
- Approver
- Head of Product
- Code
- PRD-04
It compares the company's SaaS products feature by feature with rival products: integrations, security and compliance features, deployment options, pricing tiers and service levels. It writes a sourced comparison for product and sales and never states a rival capability without a public source.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: deals won and lost against these rival products, with the feature reasons given..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it files the comparison as a page on the product's competitive board. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The competitive library: rival product profiles, their public documentation and pricing pages, our feature matrix and release history, and the rules on comparative claims.
Reads from
the CRM: deals won and lost against these rival products, with the feature reasons given.
Acts in
the project management tool: it files the comparison as a page on the product's competitive board.
Hands back
An object with matrix (a list, each with area, capability, ours, theirs (per competitor) and source), we_lead (a list), they_lead (a list) and implications (a list).
Asks a person when
The comparison will be used outside the company, or it shows roadmap items.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Oldest source (months) | 9 | Older sources are marked possibly out of date. |
| Use only public sources | On | When on, rival capabilities come only from public material. |
| Show our roadmap items | Off | When on, planned features are shown, marked as planned; when off, only shipped features count. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- When on is true, state a rival capability only from public material, with its source and date.
- Mark sources older than 9 months as possibly out of date.
- Compare shipped features only unless off is true, and mark planned ones clearly.
- Name gaps where the rival is ahead plainly.
- Never say a rival lacks a feature unless its documentation shows it.
See the Competitive Product Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.