Roadmap Prioritization Agent
Ranks roadmap items by value and effort.
- Industry
- Procure AI
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Product
- Code
- PRD-02
It scores roadmap items for the procurement platform, such as new RFx templates, auto-matching rules, supplier portal changes or analytics views, on reach across clients, impact on service KPIs, confidence and effort, weights them for strategic themes and the client revenue at stake, and ranks the backlog. It forecasts what the new order does to committed dates, sends low-confidence items to discovery and updates the ranks in the roadmap tool.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the roadmap tool: the backlog items with scores, themes, client links and committed dates..
- 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.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Product with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the roadmap tool: it updates each item's rank and moves low-confidence items to discovery. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The prioritisation model, strategic themes, the KPI each item moves (first-time-match rate, PO cycle time, maverick-spend share), client requests with their annual contract values and the dates promised to clients.
Reads from
the roadmap tool: the backlog items with scores, themes, client links and committed dates.
Acts in
the roadmap tool: it updates each item's rank and moves low-confidence items to discovery.
Hands back
A list with one entry per item, each with item_id, title, score, rank, previous_rank, theme, kpi_moved, to_discovery (true or false) and committed_date_at_risk (true or false).
Asks a person when
A committed item drops more than 5 places or out of the top 10, an item tied to client revenue moves down, or the new order pushes back a date promised to a client.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Scoring model | RICE | How items are scored. |
| Weight for a strategic theme | 1.5 | The multiplier for items on a strategic theme. |
| Largest boost for client revenue at stake (%) | 30 | Client revenue at stake can raise a score by at most this share. |
| Confidence below which an item goes to discovery (%) | 50 | Items below this confidence go to discovery first. |
| Items published as the top of the roadmap | 10 | The top items shown to clients and sales. |
| Rank drop that needs review (places) | 5 | A committed item falling more than this needs the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score with RICE; reach counts client organisations and their active users, impact is the movement in the named service KPI.
- Items on a strategic theme are multiplied by 1.5; client revenue at stake raises a score by at most 30 percent so one large client cannot set the roadmap.
- An item below 50 percent confidence goes to discovery, not the ranked roadmap.
- A regulatory item, such as a country e-invoicing format or a sanctions-list change, is ranked above discretionary work whatever its score.
- Only the top 10 are published; a committed item dropping more than 5 places goes to the Head of Product.
See the Roadmap Prioritization Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.