Revenue Impact & Blocker Analysis
You have raised the same product gap in three deal reviews, and the backlog is still in date order. Opine links every request to the deals riding on it, so the gap arrives at the roadmap meeting priced in won, lost, and open pipeline.
trusted by the world's
highest performing revenue teams
Every request, with its pipeline attached
This is the Requests page. Four things on it do the work.
Blockers, important, and nice to have, each carrying the pipeline behind it and the number of deals it came from. Click the Blockers card and the whole view narrows to those.
Every request, with its pipeline attached
This is the Requests page. Four things on it do the work.
- 1
What each priority is worth
Blockers, important, and nice to have, each carrying the pipeline behind it and the number of deals it came from. Click the Blockers card and the whole view narrows to those.
- 2
Won, lost, and open per request
The Reports tab gives every gap one row: pipeline still in play, pipeline already lost, and the deals that closed anyway. Sort by total impact, or by how many deals raised it, and export the lot to CSV.
- 3
Filtered the way a leader asks
Pipeline, deal size, sales process, product, and any CRM deal or account property. Per-user CRM visibility applies on top, so nobody's rollup includes deals they aren't allowed to see.
- 4
The blocker follows the deal
Every deal card badges its count of open blockers. The thing standing between a deal and its close shows up in the pipeline view you already open, not in a backlog nobody does.
Your tracker holds the ticket. Your CRM holds the money.
A backlog item carries a comment thread, a label, an assignee. It does not carry a single dollar. Your CRM has the dollars and no idea the request exists, because a tracker has no deal model and a CRM has no request model. Opine keeps one normalized record per opportunity and lands the request on it. That join is the whole feature: it's why a gap can be priced in won, lost, and open pipeline at all, and why the number holds when someone asks where it came from.
Bring a number to the roadmap meeting
Every captured request is linked to real deals with real CRM amounts. That's the whole difference between a request list and a prioritization.
What each priority is worth
Blockers, important, and nice to have, each with its pipeline and its deal count. One click filters the view to the blockers.
Won and lost, not just what's still open
One row per gap, sortable by total impact: $780k still in play and $340k already gone is a fact about the same request.
The blocker rides on the deal
Open blocker counts badge every deal card, so a stalled deal carries the reason it stalled into your pipeline review.
Your CRM's dollars, under your CRM's rules
Amounts come off Salesforce and HubSpot, normalized across currencies, with per-user visibility enforced on every rollup.
What changes once the gap has a number on it
Nobody in this argument is being unreasonable. One side has the requests and the other has the revenue, and until now nothing joined them.
A prioritized list they didn't have to assemble
They were never ignoring you. They had a backlog in date order and no way to tell a nice-to-have from a deal blocker.
One number instead of two anecdotes
Anyone who doubts a figure clicks into the deals that make it up, so the meeting argues about priorities rather than about the data.
The gap you keep losing to, in writing
You have known for two quarters which unbuilt thing costs you deals. Now it badges them in the pipeline view and lands in the win/loss report.
Asked in real demos
Where the dollars come from, what the rollup won't do, and who is allowed to see it.
Have one we didn’t cover? Bring it to the demo →
Getting actionCan product and engineering actually see the dollars blocked, so they act on it?
That's what the rollup is for. Every request shows won, lost, and open pipeline with its deal count, sortable by total impact. One click on the Blockers card filters to the critical gaps, each linked to the specific deals and the value at stake. It's the number a prioritization call actually needs, on one screen, with the deals underneath it.
ReportingDoes it include revenue we already lost, or only what's still in play?
Both, side by side. The per-request breakdown splits won, lost, and open dollars, so “this gap is tied to $780k still in play and $340k already lost” is one row rather than two spreadsheets. It sorts by total impact and exports to CSV.
NumbersWhere do the dollar amounts come from, and can people see deals they shouldn't?
From your CRM, under your CRM's own visibility rules. Salesforce and HubSpot deal amounts, normalized across currencies, with per-user CRM visibility enforced on the rollup. Requests linked to accounts rather than open deals contribute an estimated value that's shown separately, never silently mixed in. A rep and a VP open the same report and correctly get different numbers.
AttributionIf one gap blocks five deals, how is the revenue attributed?
Each linked deal's full amount rolls into that request. A gap tied to five deals shows all five and their combined value, with the deal count alongside. There's no fractional attribution today: no weighting or multiplier math that splits one blocker's value across the deals it's holding up.
TrackersWe saw the dashboard with Jira. Does it work the same with Linear?
Identically. The rollup is built on Opine's requests and your CRM's deal amounts, not on the ticketing tool. It reads the same whether requests route to Jira, Linear, Notion, or Aha!, with each tool's statuses syncing into the view.
RankingsCan I see which gaps come up most often, not just which ones are worth the most?
Yes. That's the other ranking in the same view. The Reports view carries a most-common-requests ranking beside the dollar rollup, ordered by how many deals raised each gap. Most teams read the two together: the demand list says what your buyers keep asking for, and the dollar list says which of those is actually holding revenue. They are rarely the same order.
FilteringCan I cut this by segment? I only care about enterprise deals in EMEA.
Yes, including by your own CRM fields. The rollup filters by pipeline, deal size, sales process, and product, plus any CRM deal or account property you already keep. So the same six gaps re-rank for the segment you actually own, rather than for the company average.
ForecastHow does this reach the people running the forecast?
The blocker count travels with the deal. Every deal card badges its open blocker-priority requests, so a stalled deal shows the reason in the pipeline view rather than in a backlog. When the deal closes either way, the win/loss report folds in the gaps and requests logged against it, with ticket references and status.
SetupWhat does this need from us before the numbers mean anything?
Requests linked to deals, and your CRM connected. The pricing is a join between the two, so it needs your Salesforce or HubSpot connection and requests captured against deals. Capture and routing is the other half of this category and does that part on its own, from the calls and Slack threads your team is already having.
Proven in the field
Technical sales teams run their pipeline on Opine. The results are public.
“I’ve used countless presales tools over the years, and I can confirm that not a single one comes close to what Opine is doing. Because of their platform, win rates are up, SEs are more efficient, and leadership has access to never-before-seen pipeline intelligence. It’s amazing.”
Shaun Dolan
Director of Solutions Engineering at Orca Security
