Product Gap Tracking: How Presales Ties Feature Requests to Revenue
November 11, 2026 · Casey O'Brien
Product gap tracking is the practice of recording every capability a buyer needs and your product lacks, on the deal where it came up, with the revenue of that deal attached. Done well, it gives the product team a ranked list of gaps by revenue at risk, built from real opportunities instead of anecdotes.
Presales hears these gaps first, on discovery calls, in demos and during proofs of concept. Most of them never reach product with a number attached.
Why product gaps get lost
In my calls with 29 presales teams this year, about 5 raised lost product gaps without being asked. The pattern was the same each time:
- A buyer asks for a capability on a call.
- The engineer mentions it in Slack, adds a line to a Confluence page or simply remembers it.
- By the time product plans the next quarter, nobody knows how many deals raised it or what they were worth.
The result is a roadmap shaped by whoever was loudest in the last planning meeting, and a presales team that feels unheard because the requests it relays carry no weight.
What to capture for every product gap
| Field | Why it matters |
|---|---|
| The gap, in one sentence | So product can recognize duplicates across deals |
| The buyer’s words | A short quote of what they asked for and why |
| The opportunity it came from | This is what attaches revenue |
| Impact on the deal | Blocker, risk, or nice to have |
| Workaround, if any | Whether the deal can close without it |
| Who raised it and when | So product can follow up with the right person |
| Competitor context | Whether a competitor in the deal already has it |
The opportunity link is the field most teams skip and the one that matters most.
How to size the revenue at risk
Once each gap is tied to opportunities, sizing it is arithmetic:
- Group duplicates. Different buyers describe the same gap in different words. Merge them into one gap with many linked deals.
- Sum the open pipeline. Add the value of every open opportunity where the gap is a blocker or a risk.
- Count the losses separately. Add the value of lost deals where the gap was a stated reason. This is revenue already lost, and it is the most persuasive number in a roadmap meeting.
- Weight by impact. A blocker counts in full. A nice-to-have should be reported separately so it does not inflate the total.
The output is a short ranked list: the top gaps by revenue at risk, each with its linked deals and the buyers’ own words.
Report gaps where product already works
Product teams run on their own tracker, usually Jira. A gap list that lives in a presales spreadsheet asks product to come and look. A gap that lands in Jira with the revenue and the linked deals attached meets product where it works.
Keep it two-way. When product changes the status of an issue or ships it, presales should see it on the deals that raised it, so the engineer can go back to the buyer with good news. That loop is what makes engineers keep logging gaps.
How to run a monthly gap review with product
- Bring the top ten by revenue at risk. Rank by money, so the newest or loudest request does not jump the line.
- Separate blockers from risks. Product needs to know which gaps actually stop deals.
- Show the lost revenue. Lost deals with a stated gap are the strongest evidence you have.
- Ask for a decision on each. Planned, not planned, or needs more evidence. “Not planned” is a useful answer: presales can stop promising it.
- Close the loop with the field. Tell the engineers what was decided, so they can set buyer expectations.
How product gap data helps the presales team
Revenue-backed gap tracking does more than shape the roadmap. It is one of the five numbers that prove presales value to a CRO, because it shows presales as the team that knows where the money is. It also feeds win-loss analysis and competitive positioning, and it tells the team which deals to slow down before they burn a POC on a requirement the product cannot meet.
For the gaps a POC exposes, written success criteria make the difference between a gap the buyer can live with and one that ends the deal. The POC success criteria template shows how to write them.
Where PresalesIQ fits
PresalesIQ is purpose-built presales management software with product gap tracking built for this loop. Engineers log gaps on the deal where they came up, each gap shows the revenue at risk across every opportunity raising it, with the buyers’ own words attached, and gaps sync both ways with Jira, so status changes in product show up on the deals in presales. Revenue comes straight from the opportunities in Salesforce or HubSpot.
See product gaps priced in dollars.
Frequently asked questions
What is a product gap in sales? A capability a buyer needs that your product does not offer today. In presales, gaps surface during discovery, demos and proofs of concept.
How do you track feature requests from sales? Record each request on the opportunity where it came up, with the buyer’s words, its impact on the deal and any workaround. Linking it to the opportunity is what lets you attach revenue to it.
How do you calculate revenue at risk from a product gap? Sum the value of open opportunities where the gap is a blocker or a risk, and report lost deals where the gap was a stated reason separately. Merge duplicate requests first so each gap counts every deal that raised it.
Who should own product gap tracking? Presales, because presales hears the gaps first and understands the technical context. Product owns the decision on each gap, so the two teams should review the list together on a regular schedule.
Should product gaps be tracked in the CRM or in Jira? Capture them on the deal, where the revenue lives, and send them to Jira, where product works. Keeping the two in sync means product sees the revenue and presales sees the status.
How often should presales review product gaps with product? Monthly works for most teams, with an immediate escalation path for gaps blocking a large deal in its final stage.
Keep reading
- Demo Plan Template: How to Plan a Software Demo That Wins the Technical WinA demo plan template for presales teams: the eight sections every plan needs, a worked example and the tell-show-tell method that keeps demos on track.
- Why presales management still relies on manual loggingPresales teams still log their work by hand because CRMs weren't built for them. What that lag costs, and how AI-native capture removes it.
- Build vs Buy in 2026: Why Presales Teams Keep Building Their Own Tools32% of companies skipped a software purchase to build it with AI. Four presales leaders told me they did exactly that. Here is where each build stopped.