Skip to main content
The Releases / Close the Loop page (/success/close-the-loop) is the account-level view of shipped features against customer requests. The in-app section label is Releases; the docs and route also describe the customer workflow as Close the Loop. The old /success/releases route redirects here. Where the Projects close-the-loop card handles one project’s requesters, this page handles requests across accounts and matches them against the shipped-feature catalog.

​
The Four Tabs

​
Overview

  • Summary cards for requests, shipped features, matches, pending drafts, and completed sends.
  • Customer-level match list for follow-up.
  • Analysis progress card with phase, processed count, elapsed time, and matches found so far.
  • Run analysis action, with upfront credit estimate when available.
The matcher may auto-run once per browser session when there are requests and shipped features but no matches yet. Manual analysis is still available from the page.

​
Requests

Shows customer feature requests in the workspace. You can sync requests, add manual requests, delete requests, and review matched releases. Typical request sources are BuildBetter signals, feedback, and manually entered requests.

​
Shipped

Shows shipped features grouped from configured release sources:
  • GitHub releases and tags.
  • RSS feeds.
  • Changelog-style external sources where configured.
  • Manual shipped-feature entries.

​
Settings

Configure shipped-feature sources:
  • GitHub repositories.
  • RSS feeds.
  • External changelog sources.
  • Manual feature entries.
  • Refresh/sync actions.
  • Source test actions where available.
Settings are disabled in demo mode. Turn off demo mode to configure live GitHub or RSS release sources.

​
The Matching Engine

Analysis compares requests with shipped features and creates request-to-release matches. It uses semantic similarity, explicit terms, and confidence scoring. High-confidence matches become candidates for close-the-loop outreach. The progress card distinguishes indexing from matching and reports how many requests/features have been processed.

​
Workflow

1

Configure release sources

Add GitHub repositories, RSS feeds, or manual shipped features on the Settings tab.
2

Sync requests and shipped features

Pull the current request and release catalog into the page.
3

Run analysis

Wait for indexing and matching to finish. Large workspaces may take several minutes.
4

Review matches

Check high-confidence matches and customer-level grouped results.
5

Draft and send follow-up

Use the matched request, request evidence, and release context to draft “we shipped this” outreach.

​
Manual Entry

Use manual entry when:
  • A customer request was not captured as a signal.
  • A shipped feature does not appear in GitHub, RSS, or the public changelog.
  • The team needs to seed a release before a formal changelog is published.
Manual entries feed back into the matching run.

​
How It Connects to Re-engage

Re-engage should use the same shipped-feature foundation. When a closed-lost deal was blocked by a missing feature, a later shipped-feature match can raise that account’s re-engagement priority.

​
Demo Mode

Demo mode loads sample requests, customers, matches, and shipped features. It is useful for exploring Overview, Requests, and Shipped. Settings are disabled while demo mode is active.

​
Empty States

  • No requests: Sync requests or add a manual request.
  • No shipped features: Configure GitHub/RSS/manual shipped sources.
  • No matches: Run analysis after both requests and shipped features exist.
  • Analysis running: Wait for the progress card to complete before assuming matches are missing.
Run Releases / Close the Loop after every meaningful release. The matched-request list becomes a targeted customer campaign grounded in what each account asked for.