Success is gated by the
success feature flag. /success routes to /success/health when enabled and to /success-unlock when disabled.Success Sections
The in-app Success nav has six primary sections:Health
Risk and renewal triage. Health scores, risk factors, ARR exposure, renewal pressure, and payment state.
Convert
Trial and prospect prioritization. Conversion likelihood, trial urgency, expected value, and source filters.
Contracts
Contract and subscription ledger from Salesbricks and Stripe. MRR, ARR, renewal dates, payment state, and source reconciliation.
Pipeline
Opportunity board and table from Attio and/or Salesbricks, enriched with Health and Convert context.
Re-engage
Closed-lost revival queue. Salesbricks-backed lost deals, re-engagement scoring, and account context.
Releases / Close the Loop
Match customer requests to shipped work and draft “we shipped this” follow-up. The route is
/success/close-the-loop; /success/releases redirects there.Customer Detail
Customer Detail is the account hub behind the sections. Open it from Health, Convert, Contracts, Pipeline, or Re-engage to see score, activity, revenue sources, account context, HubSpot enrichment, risk factors, and account-scoped chat.Core Concepts
| Concept | What It Means |
|---|---|
| Health score | 0-100 account score derived from adoption, payment state, renewal pressure, and BuildBetter signals. |
| Risk factors | Explanation-first score contributors, such as low adoption, past-due payment, renewal pressure, or customer escalations. |
| Routed account | An account moved from one Success section to another, such as Health -> Convert or Pipeline -> Re-engage. |
| Revenue source | A Salesbricks contract or Stripe subscription attached to a customer account. |
| Connected source | An integration that supplied live page data, such as Salesbricks, Stripe, PostHog, Attio, HubSpot, or Salesforce. |
| Demo mode | Sample Pied Piper data used by several sections to preview the workflow before live integrations are connected. |
How the Sections Work Together
Success is not six isolated tabs. It is a customer workflow:Triage in Health
Start with critical and at-risk accounts, then inspect the factors behind each score.
Route the Account
Send an account to Convert, Pipeline, Contracts, or Re-engage when the next action belongs there.
Work in the Destination Section
Use the destination page’s queue, filters, detail sheet, or board to decide the next customer motion.
- Health -> Convert: A trial account is at risk but still likely to upgrade.
- Convert -> Pipeline: A trial has become a real opportunity.
- Pipeline -> Contracts: A deal is signed and needs renewal/payment tracking.
- Contracts -> Health: A renewal or payment issue creates new account risk.
- Releases -> Re-engage: A shipped feature removes the blocker from a closed-lost deal.
Data Sources
| Source | What It Powers |
|---|---|
| Salesbricks | Contracts, orders, trial metadata, deal stages, closed-lost reasons, renewal context. |
| Stripe | Subscriptions, invoices, payment state, MRR/ARR enrichment, trial detection. |
| PostHog | Product usage, active-user counts, adoption and recency inputs. |
| Attio | Pipeline source of truth and editable stage movement when connected. |
| HubSpot | Optional company enrichment on Customer Detail and optional pipeline source filtering when available. |
| Salesforce | Optional pipeline source filtering when available. |
| BuildBetter | Calls, signals, feedback, projects, requests, activity feed, and risk evidence. |
| GitHub / RSS / manual shipped features | Release catalog for Close the Loop and re-engagement coverage. |
Setup Readiness
The newer Success sections are backed by a shared setup/readiness contract. For Convert, Contracts, Pipeline, Re-engage, and Close the Loop, the backend can report:- Reused systems, such as CRM company identity, metadata projection, existing integration providers, signals, and workflow runtime.
- Connector readiness: connected, available, or provider missing.
- Fast paths to CRM, integrations, Health, Convert, Signals, Feedback Ops, or Workflows.
- Next steps for connecting sources or materializing snapshots.