Early access · Pipedrive + Jira

Prioritise on evidence, not opinion.

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.

Planned for PipedriveJiraHubSpotGitLab

Building block

SSO via SAML

#1OF 6 ITEMS
8.1PRIORITY
Pipeline at stake
€143k
Customers
5
Expected
12 Dec
  • Nordwind Logistics Blocker €120k · 70% · 28 Nov
  • Helio Health Blocker €72k · 50% · 15 Dec
  • Kestrel Labs Important €48k · 80% · 20 Jan

+ 2 renewals from customer success

Sent to 3 deals in your CRM
Expected delivery: Sprint 47 · around 12 Dec

Example data for illustration.

The problem

Roadmaps are decided by opinion, behind closed doors

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

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.

02

Decisions nobody can trace

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

Strategy stays implicit

Vision and long-term bets are argued case by case instead of being weighed openly against customer demand and revenue.

The shift

From opinion to evidence

What changes when prioritisation runs on data your teams can see and check.

Today With Relay
The loudest voice or biggest escalation wins Revenue at stake and the number of customers decide the order
Impact is guessed on a 1–5 scale Impact is calculated from real deals: value, win probability and close date
Priorities are set in a product-only meeting Sales, CS and product feed the same model, product makes the call
Nobody can explain why something ranks first Every rank traces back to deals, weights and a written rationale
Strategy is argued case by case Strategic fit is an explicit, weighted factor next to the data

How it works

From scattered requests to one shared priority list

Every input is either data from your tools or a judgement written down. Nothing is decided off the record.

  1. 1

    Link deals to building blocks

    Sales tags a Pipedrive deal with the capabilities it depends on, and how strongly: blocker, important or nice to have.

  2. 2

    Merge the same request

    Five customers asking for SSO in five different words become one building block with five deals behind it.

  3. 3

    Weigh the evidence

    Deal size, win probability, close date and the number of customers combine with product's own judgement into one transparent score.

  4. 4

    Decide together, share the dates

    Product ranks and commits. Jira delivery dates flow back to every waiting deal, so sales and CS know when to expect it.

The score

A transparent score instead of a gut feeling

Revenue at stake

Deal value × win probability × dependency strength, summed over every waiting deal.

From Pipedrive

Timing

Deals that close before the feature could ship count more. Waiting has a cost.

From Pipedrive + Jira

Customer breadth

How many distinct customers need it. Ten mid-size accounts can outweigh one large deal.

From Pipedrive + CS

Strategic fit

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

Built around the tools your teams already live in

No new place for sales to log requests. The work happens in Pipedrive and Jira; we connect the two.

Pipedrive

Planned · first integration

CRM

Reads
Deals, value, stage, win probability, expected close date, organisation
Writes back
Expected delivery date and status on every linked deal

Jira

Planned · first integration

Issue tracking

Reads
Epics and issues, estimates, status, fix versions, sprint dates
Writes back
Linked deals and revenue at stake on the epic

Also planned: HubSpotCRMGitLabIssue tracking

Considered next: Salesforce Linear Slack Intercom

Who it's for

One list. Three teams. Fewer escalations.

Made for B2B software companies where deals depend on what product ships next.

Product

Heads of product and product managers

Today

Every quarter turns into a negotiation between the loudest requests.

With Relay

See which building blocks carry the most pipeline and customers, and decide with the evidence in view.

Sales

Account executives and sales leads

Today

You can't tell a prospect when the feature they need will land.

With Relay

Link a deal once. See the expected delivery on the deal and get told when it moves.

Customer success

CS managers and account managers

Today

Renewals are at risk and nobody knows a customer has been waiting for months.

With Relay

Know which accounts wait on what, and get ahead of a slipping date.

Product tour

See the concept in six steps.

Click through an early prototype: linking a deal, merging requests, tuning the score, and the delivery date landing back on the deal.

Take the product tour

Waiting list

Make your next roadmap decision one you can explain.

Join the waiting list for early access to evidence-based prioritisation, and a say in the first integrations.

  • Early access before public launch
  • A say in the first integrations
  • No spam: a handful of updates, unsubscribe anytime
Tools you use (optional)

We'll send one email to confirm your address.