Your roadmap, argued with.
Calibro Prioritize reads your Jira Product Discovery ideas — the insights, ratings, goals, estimates and linked Confluence pages already on them — and ranks them against a strategy written in your team's own words. Then it tells you exactly where it disagrees with your order, and shows the evidence it would bring to the meeting.
Not released yet. Registering tells us to email you when it is — nothing else.
The disagreement first, then the case for it
The first frame is where every session starts: the ideas Calibro would move, and why. The rest follow one argument all the way down — from the full ranking to a single idea's evidence.
Screenshots show sample data, not a real customer's instance.
It argues — it doesn't overwrite
Your rank order, your Priority field and every other field stay untouched. The only thing Prioritize can ever write is two fields of its own — a rank and a one-paragraph rationale — on the ideas you just reviewed, after a dialog that names both.
Evidence, inference and unknowns — kept apart
Every recommendation opens into a case with three registers: what is on the record, with a source on every line; what Calibro is inferring, labelled as inference; and what nobody has written down. A team will only argue with a ranking it can argue against.
An unknown is never a zero
Zero linked insights is a fact about demand. A project with no insights field has said nothing — and the two never reach the score the same way. An idea nobody has sized is capped at Low confidence, because an unsized bet is a schedule risk, not a plan.
The strategy is yours, and it's inspectable
No black-box score. You write how your team decides in plain sentences; the weights read out of them are shown next to the words that set them, and you can drag any slider the reader got wrong. The weights are what rank the ideas — nothing else does.
It reads the record you already keep
Insight counts, impact and effort ratings, goals, due dates, delivery links — and the Confluence pages linked to each idea, so "named in the FY27 strategy with $840k attached" arrives as evidence with the page cited, not as something someone remembers in the meeting.
Nothing leaves your site
Built entirely on Atlassian Forge, like Track, Sketch, Pulse, Explore and Plan. Your ideas and pages are read and ranked inside Atlassian's infrastructure — there is no server of ours for them to travel to, and no model API either: the analysis declares no external egress at all.
It isn't finished, and we'd rather say so.
Calibro Prioritize works — the screenshots on this page are the real interface, not a mockup — but it is not on the Marketplace and there is no date on it yet.
The thing we most want to hear is whether the disagreements are the useful kind. A prioritization tool earns its keep the day it changes one decision in a roadmap review — and the backlogs it gets pointed at are the only way to find out whether these arguments are worth having.
So: no launch date, no waiting list theatre, no drip campaign. One email when there's something to install.
Where it's up to
Want it?
Leave an address and we'll tell you when it's installable. That's the whole commitment — for you and for us.