Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt

Use this file to discover all available pages before exploring further.

Success aggregates data from several systems. This page is the reference for what each integration powers, where the routing model lives, and how demo mode works.

​
Required Integrations

Success will load — and demo mode works — without any integrations, but the live data depends on each connection.

​
Salesbricks

Powers: Contracts (the primary source), Convert (orders + trial metadata), Pipeline (if Attio isn’t connected), Re-engage (closed-lost deals). Connect: Settings → Integrations → Salesbricks. OAuth-based. Status surfaces on: Health Settings sheet, each Success page’s connection warning banner.

​
Stripe

Powers: Contracts (subscription side), Convert (Stripe trial detection), Health (payment-state risk factors), Customer Detail (revenue sources card). Connect: Settings → Integrations → Stripe.

​
PostHog

Powers: Health (adoption scoring), Customer Detail (active-user metrics + weekly trend). Connect: Settings → Integrations → PostHog.

​
Optional Integrations

​
Attio

Powers: Pipeline (as an alternative to Salesbricks for deal source). Use when: Your team runs Attio as the primary CRM and Salesbricks just for contracting.

​
HubSpot

Powers: Customer Detail (HubSpot Enrichment panel — industry, size, location, custom fields). Match key: Company domain. The enrichment panel surfaces fields where the domain matches a HubSpot company record.

​
The Route-Accounts Model

Success isn’t six separate tabs — it’s a workflow you flow accounts through. Each page’s row menu has a Route to action that moves the account to another Success section. When an account is routed:
  • It appears at the top of the destination page
  • A Routed from badge marks the row
  • The destination shows the originating reason if one was supplied
Routes are reversible — route back to Health any time.

​
When to Route Each Direction

FromToWhy
Health → ConvertA trial that needs conversion outreach
Health → PipelineAn at-risk account that’s also an expansion opportunity
Health → ContractsA renewal that needs renewal-specific attention
Health → Re-engageAn account you’ve decided to retire but want a winback window for
Convert → PipelineA trial that’s become a real deal
Convert → Re-engageA trial that flatlined and isn’t coming back
Pipeline → ContractsA signed deal that’s now active
Contracts → HealthA renewal that’s developed risk
Re-engage → PipelineA winback that’s reactivated as a live deal

​
Demo Mode

Every Success page has a Preview with demo data button visible whenever a required integration isn’t connected. Clicking it:
  • Loads the Pied Piper sample dataset for the page
  • Shows a subtle banner at the top of the page reading “Viewing demo data”
  • Lets you explore the layout, filters, scoring, and detail views before connecting real systems
Demo mode is per-page and resets when you navigate away. It does not write any data and does not affect your real workspace.

​
Health Settings Sheet

The Settings button on the Health page opens a sheet for tuning the scoring:
  • Scoring weights — Adoption / Payment / Renewal pressure proportions
  • Integration status — per-source connection state, quick-link to fix
  • Untracked accounts — review and manage excluded accounts with reason fields
See Health for the detailed breakdown.

​
Convert Settings Tab

Convert has a dedicated Settings tab in the page (not a sheet) for tuning what counts as a convert candidate:
  • Salesbricks orderType filter
  • Salesbricks stage filter
  • Stripe subscription status filter
  • Trial name patterns for fuzzy matching against product/plan/buyer names
All settings autosave 600 ms after edit. See Convert for details.

​
Pipeline Settings Tab

Pipeline has a Settings tab for:
  • Stage filter — which CRM stages count as pipeline
  • Source field — Attio vs. Salesbricks as the primary deal source

​
Close-the-Loop Settings Tab

Close-the-Loop has a Settings tab for shipped-feature sources:
  • GitHub repos to sync
  • RSS feeds
  • External changelog sources
  • Manual feature entries
  • Refresh GitHub repos button
See Close the Loop for the full reference.

​
Disconnect Warnings

If a required integration disconnects (token expired, webhook stopped firing), each Success page surfaces an inline alert:
“Health is not connected yet” — with Open Integrations and Preview with demo data buttons.
Click Open Integrations to land on the Settings → Integrations page where you can reauthorize.

​
Feature Flag

The whole Success workspace is gated by the success feature flag. Without access:
  • /success redirects to /success-unlock
  • /success-unlock is a landing page with a Request Access button (opens Intercom chat or mailto support)
  • Once enabled, every Success page is available to anyone in the workspace with standard access (no role-level gating on top)
The fastest way to evaluate Success without disrupting anything is to enable the feature flag, click Preview with demo data on every page, and walk a CSM through the routing model. You’ll know within 15 minutes whether the workflow fits your team — and you haven’t touched any of your real customer data.