01
Opinions dressed up as scores
An impact of 3 out of 5 is still someone's opinion. It can't tell a €120k deal closing next month from a nice-to-have next year.
Early access · Pipedrive + Jira
Most roadmaps are still decided by the loudest voice and a gut-feel score nobody can explain. Relay replaces that with a transparent, data-driven score: real deals from your CRM, how many customers need it, and how it fits your strategy.
Building block
+ 2 renewals from customer success
Sent to 3 deals in your CRM
Expected delivery: Sprint 47 · around 12 Dec
The problem
Prioritisation frameworks look objective, but their inputs are guesses. The people closest to revenue can't see how decisions are made, so they escalate.
01
An impact of 3 out of 5 is still someone's opinion. It can't tell a €120k deal closing next month from a nice-to-have next year.
02
Why is this first? The answer lives in a meeting, a spreadsheet or someone's head. Sales and CS learn the outcome, never the reasoning.
03
Vision and long-term bets are argued case by case instead of being weighed openly against customer demand and revenue.
The shift
What changes when prioritisation runs on data your teams can see and check.
How it works
Every input is either data from your tools or a judgement written down. Nothing is decided off the record.
Sales tags a Pipedrive deal with the capabilities it depends on, and how strongly: blocker, important or nice to have.
Five customers asking for SSO in five different words become one building block with five deals behind it.
Deal size, win probability, close date and the number of customers combine with product's own judgement into one transparent score.
Product ranks and commits. Jira delivery dates flow back to every waiting deal, so sales and CS know when to expect it.
The score
Deal value × win probability × dependency strength, summed over every waiting deal.
From Pipedrive
Deals that close before the feature could ship count more. Waiting has a cost.
From Pipedrive + Jira
How many distinct customers need it. Ten mid-size accounts can outweigh one large deal.
From Pipedrive + CS
Product's judgement on vision, platform value and risk. Evidence informs it, it doesn't replace it.
From Product team
÷ Effort from Jira estimates
Integrations
No new place for sales to log requests. The work happens in Pipedrive and Jira; we connect the two.
CRM
Issue tracking
Also planned: HubSpotCRM
GitLabIssue tracking
Considered next: Salesforce Linear Slack Intercom
Who it's for
Made for B2B software companies where deals depend on what product ships next.
Heads of product and product managers
Every quarter turns into a negotiation between the loudest requests.
See which building blocks carry the most pipeline and customers, and decide with the evidence in view.
Account executives and sales leads
You can't tell a prospect when the feature they need will land.
Link a deal once. See the expected delivery on the deal and get told when it moves.
CS managers and account managers
Renewals are at risk and nobody knows a customer has been waiting for months.
Know which accounts wait on what, and get ahead of a slipping date.
Waiting list
Join the waiting list for early access to evidence-based prioritisation, and a say in the first integrations.