Skip to content

Sales-Loss Feature Gap Report

Example prompt: "Every Monday morning, look at the deals we lost in HubSpot last week where the closed-lost reason mentions a missing feature, group them by what was actually missing, weight by deal value, and post a summary to #product on Slack so we know which gaps cost us the most this week."

The Problem

Sales reps mark a deal closed-lost and pick a reason from a drop-down — "Missing feature", "Price", "Timing" — then add a note in their own words about what the customer actually wanted. The notes are gold for product, because they describe specific gaps that real prospects with real budgets walked away over. In practice nobody reads them after the deal is closed. The "Missing feature" reason sits as an unanalysed bucket while the sales manager and the head of product argue about which features matter, with neither side bringing the data. The gap between "we know we're losing deals over X" and "we can show you we lost £180k over X last quarter" is the difference between the roadmap moving and the roadmap not moving.

How GloriaMundo Solves It

We build a workflow that runs every Monday morning. An integration step reads HubSpot deals that closed-lost in the previous week with the close reason set to "Missing feature". An LLM step reads each deal's notes and the close-lost summary, and extracts the specific feature gap as a short, normalised phrase — "SAML SSO", "bulk CSV import", "Salesforce sync" — along with the customer name and deal value. A code step groups the extracted gaps by phrase, sums the deal values per group, and ranks them by revenue lost. A second integration step searches Linear for backlog items that match each gap by title or description, attaching the matching issue ID where one exists. An integration step posts a Slack summary to #product with the top gaps, the revenue impact for each, the linked Linear issue or a "no backlog item" flag, and the specific deal names so the PM can dig in. Glass Box preview shows the parsed gaps and the Slack message before any of it goes out.

Example Workflow Steps

  1. Trigger (scheduled): Runs every Monday at 09:00.
  2. Step 1 (integration): Read HubSpot deals closed-lost in the last 7 days where the close reason is "Missing feature" — deal name, amount, owner, close notes, close-lost summary.
  3. Step 2 (LLM): For each deal, extract the specific feature gap as a short normalised phrase and confirm the deal value.
  4. Step 3 (code): Group by feature gap phrase, sum the deal values per group, and sort by revenue lost descending.
  5. Step 4 (integration): For each top gap, search Linear for backlog items with a similar title or description and attach the strongest match.
  6. Step 5 (conditional): Flag any gap that has no matching Linear item as a "no backlog item" line in the report.
  7. Step 6 (integration): Post the summary to #product on Slack with the top gaps, revenue impact, linked Linear issues, and the specific deal names.
  8. Step 7 (integration): Append the same summary as a dated section to a "Sales Loss Gap Reports" page in Notion for week-on-week comparison.

Integrations Used

  • HubSpot — source of closed-lost deals and the sales rep's notes about what the customer actually wanted
  • Linear — backlog cross-reference so each gap is matched to an existing item or flagged as missing
  • Slack — where the weekly summary is delivered to the product team
  • Notion — running history of weekly reports so the trend over quarters is visible

Who This Is For

Product managers at B2B SaaS companies where the sales team uses HubSpot and closes between 10 and 100 deals a week, of which a meaningful share are lost to missing features. Especially useful for PMs whose head of sales keeps asking "are we going to build the thing the last five prospects asked for" without saying which thing or which prospects.

Time & Cost Saved

Doing this honestly by hand — reading every closed-lost deal with the "Missing feature" reason, normalising the gap descriptions, summing the values, cross-checking the backlog — takes 60-90 minutes a week and is the kind of work that quietly stops happening when the PM is busy. In practice it usually never happens at all, which is the real cost: roadmap arguments resolved by whoever has the loudest opinion rather than by the numbers. This workflow makes the numbers a Monday-morning given.