- Industry
- Oil & Gas
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Assistant
- Approver
- Head of Digital Products
- Code
- PRD-04
It compares our fuel card app, loyalty app and distributor portal against rival fuel retailers' and card issuers' products, feature by feature, from public sources and win and loss notes. It updates the product battlecards for the sales and marketing teams.
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: win and loss reasons that name the rival products..
- 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 Digital Products with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the sales enablement library: it updates the product battlecard with the approved points. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The competitive product file: rival products and their public features, fees and acceptance networks, our features and roadmap, the allowed sources and the battlecard template.
Reads from
the CRM: win and loss reasons that name the rival products.
Acts in
the sales enablement library: it updates the product battlecard with the approved points.
Hands back
An object with features (a list, each with feature, ours, theirs (by competitor), source and date), material_gaps (a list with gap and losses), battlecard_points (a list with point and source) and stale_sources (a list).
Asks a person when
A changed battlecard claim would go to fleet and card sales, a claim rests on a single customer report, or a comparison could be used in public.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Oldest source (days) | 120 | Older sources are rechecked. |
| Allowed sources | public websites, app store listings, published fee schedules, customer reports | Comma-separated. |
| Losses that make a gap material | 3 | A gap named in this many losses in a quarter is material. |
| Battlecard audience | fleet and card sales | Who sees the battlecard. |
| Compare published fees | On | When on, published card and transaction fees are compared. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Use only public websites, app store listings, published fee schedules, customer reports, no older than 120 days; never use confidential information from a former employee or a partner.
- Compare published fees only when on is true and never speculate on a rival's pricing plans.
- A gap named in 3 losses in a quarter is material and goes to the roadmap.
- Each battlecard claim names its source; battlecards go to fleet and card sales.
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.