Skip to main content

We value your privacy

Only strictly necessary cookies until you opt in — see our Cookie Policy.

PYRAMYD

Products hub · Gaps

Fix the gaps that hurt the most customers first

See every gap with the customers and evidence behind it, from calls, tickets, and deals. See which gaps lose deals to each rival and the revenue riding on each, set a target per feature, and check after launch that the gap closed.

Included in Starter (when Products is the hub you pick), Growth, and Enterprise. See pricing

What teams do with Gaps

Four jobs, four real use cases

  1. Put the gap nine customers raised ahead of the one loud account

    Product manager · Product

    At Acme, one large account is pushing hard for its request, while a missing export option keeps coming up in calls and tickets.

    1. Open the gap matrix and sort the gaps by customers touched.
    2. See the export gap named by 9 customers across calls and tickets.
    3. Open its evidence to read what each customer said.
    4. Move it ahead of the large account’s request, with your reasons recorded.
    • Ranked by customers touched
    • Evidence from every channel
    • Triage with reasons
  2. Prepare for the feature a rival will attack in the bake-off

    Sales engineer · Sales

    Northwind meets the rival in a bake-off next week, and the sales engineer wants to know where the rival has been winning.

    1. Open Gaps › Competitors and pick the rival.
    2. See the three feature gaps that cost the most lost revenue against them last quarter.
    3. Read the call mentions, lost-deal notes, and tickets behind each gap.
    4. Prepare a workaround demo for each one.
    • Gaps per competitor
    • Evidence behind each gap
  3. Agree where a feature needs to be by June, and what it takes

    Product manager · Product

    Contoso’s audit logging trails the category, and leadership wants the gap closed by 30 June.

    1. Set a target score for audit logging on the gap matrix, due 30 June.
    2. Open Feature score to see audit logging against the category average and the criteria it does not meet yet.
    3. Copy those criteria into the sprint’s design document.
    4. Watch the gap to target shrink; it closes when the target is met.
    • Targets per feature
    • Gap to target
    • Closed when met

    3,899 feature targets set · production count, 30 Oct 2026

    Works withFeatures
  4. Show the revenue riding on a missing feature

    Head of product · Product, with Finance

    At Fabrikam’s quarterly roadmap review, the head of product has to justify building single sign-on ahead of two other bets.

    1. Open Gaps › Revenue.
    2. Read the annual value of the deals and calls that mention single sign-on: $1.6M of open deals name it.
    3. Read the loss reasons beside it.
    4. Bring the number to the review, in your own currency.
    • ARR at stake per feature
    • Loss reasons beside it
    • Your own currency

Also in Gaps

Prove the fix worked

  • ThemesWhat customers and reviewers keep raising about a product, grouped into themes, so you see which complaints come up most.
  • Gap history after launchHow a gap’s score moved before and after the feature shipped, with the ship date marked on the line, and which gaps closed or reopened.

That is all five. See every capability across the hubs

Know which gap to close first, and why

Gaps comes with the Products hub: in Starter when Products is the hub you pick, and in Growth and Enterprise.