salesascode
← All feature docs
Feature docs · /product-gaps

Product-Gap Channel

The field's product gaps rolled into one ranked list for product, with the revenue each gap is blocking attached.

Included with secronjob . A seat without it sees an upsell here instead of the page.

Overview

Product-Gap Channel is the loop from the field back to product. SEs hear the same missing capabilities across deals; this aggregates those field reports into a single ranked list, with the revenue each gap is blocking attached, so product hears the gap costing the most, not the one raised most recently. What you log is saved, so the list is a live channel from the field, not a one-off export.

What it is for, on the page. Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.

Ranked by revenue at stake

Reports about the same capability are grouped by theme (so "SSO / SAML" and "sso saml" count together), and each theme is ranked by the total ARR of the deals it is blocking, then by how many reports cite it, then by how many were called blockers. The result is a short list product can prioritize, where position reflects real revenue exposure.

Revenue is a floor, never fabricated

ARR is summed only from reports that carry a real figure. A gap raised without a revenue number still counts by frequency, and the panel shows how many of its reports had no ARR attached, so the total is an honest floor rather than an inflated estimate. Nothing is invented to make a gap look larger than it is.

Where the reports come from

Log gaps directly, one per line with a theme and, optionally, the ARR at stake, a severity, and a note. What you log is saved for your team, keyed by theme so re-logging a gap updates it rather than stacking a duplicate: Show stored brings your logged gaps back on a later visit, and the same list feeds the gap section of the SE Signals board. The most representative note per theme, from the highest-severity, highest-value report, is carried through so product has the context, not just the count.