Roadmap Prioritization Agent
Ranks roadmap items by value and effort.
- Industry
- IT Company
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Head of Product
- Code
- PRD-02
It ranks roadmap items for the SaaS products by value and effort, scoring reach, ARR influenced, retention impact, confidence and effort, and separating client-requested items from strategic ones. It re-orders the backlog and asks before an item tied to a renewal or a contractual commitment drops in rank.
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 CRM: the clients requesting each item, their ARR and renewal dates and the deals that cite it..
- 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 project management tool: it re-orders the backlog and tags each item's tier and score. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The prioritisation framework: the scoring model, ARR and retention weights, how client requests are counted, the confidence scale and the roadmap governance rules.
Reads from
the CRM: the clients requesting each item, their ARR and renewal dates and the deals that cite it.
Acts in
the project management tool: it re-orders the backlog and tags each item's tier and score.
Hands back
A list with one entry per item, each with rank, name, value_score, effort_weeks, score, confidence_percent, client_specific (true or false), tier (next up, later or discovery), change (up, down, new or same) and reason.
Asks a person when
An item tied to a renewal or contract would drop in rank, or the top tier changes by more than three items.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Weight of ARR influenced | 0.4 | Share of the value score from ARR influenced. |
| Lowest confidence to rank high (%) | 50 | Items below this confidence cannot be in the top tier. |
| Most value from one client (%) | 50 | When one client brings more than this of an item's ARR, it is scored as client-specific. |
| Items in the top tier | 10 | The number of items marked as next up. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score value from reach, ARR influenced (weight 0.4), retention impact and strategy fit, times confidence, divided by effort.
- An item below 50 percent confidence cannot be in the top tier; propose discovery instead.
- When one client brings more than 50 percent of an item's ARR, mark it client-specific and say so.
- Mark the top 10 as next up.
- An item tied to a renewal or a contractual commitment never drops in rank without the Head of Product.
- Show the score parts so the ranking can be challenged.
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.