Product tour · early concept

How Relay could work

A clickable prototype of the idea. Demo data only: nothing here is connected, and every screen will change based on what early teams tell us.

Step 1 of 6Admin

Connect Pipedrive and Jira

Connect your CRM and issue tracker once. Relay reads what it needs for scoring and writes delivery dates back. Nothing new for sales to learn.

Pipedrive

CRM

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

Not connected

Jira

Issue tracking

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

Not connected

Step 2 of 6Sales

Sales links a deal to what it needs

From the deal, an account executive picks the building blocks it depends on and how strongly. Try changing one: it feeds straight into the score.

Step 3 of 6Product

The same request, merged once

Customers describe the same need in different words, in different places. Relay suggests which requests belong together, and product confirms.

Step 4 of 6Product

One transparent, weighted score

Revenue at stake, timing, customer breadth and strategic fit, divided by effort. Move the weights and watch the ranking change. Every number traces back to a deal.

Step 5 of 6Product + Sales

Commit it to the roadmap, with the trade-off in view

Pick a delivery sprint and see which deals it reaches in time and which it misses. Then commit the item to the roadmap. Before anything is written, review exactly what changes on the Jira issue and on each Pipedrive deal.

Step 6 of 6Sales + CS

Everyone knows when it ships

The committed date lands on every waiting deal and account. When it moves, the owners hear about it first.