Product-Gap Channel
The field's product gaps rolled into one ranked list for product, with the revenue each gap is blocking attached.
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. It is the structured hand-off weekly-se-synthesis makes to PM.
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, or let weekly-se-synthesis populate them from the field on its schedule. 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.