BuildBetter Docs

settings-and-data

Success aggregates live customer data from BuildBetter, CRM, billing, product analytics, and release sources. This page explains which sections depend on which inputs and how the newer setup/readiness model works.

Section Data Requirements

Section Primary Inputs Notes
Health Salesbricks, Stripe, PostHog, BuildBetter signals Computes account health, renewal pressure, payment risk, adoption, and risk factors.
Convert Salesbricks, Stripe, PostHog Syncs trials/prospects, filters candidate properties, and scores conversion likelihood.
Contracts Salesbricks, Stripe Builds a unified contract/subscription ledger with MRR, ARR, renewal dates, and payment state.
Pipeline Attio and/or Salesbricks Attio deals can be stage-editable. Salesbricks open orders are read-only in the current UI.
Re-engage Salesbricks Uses closed-lost opportunities and account context to produce a re-engagement queue.
Releases / Close the Loop BuildBetter requests, GitHub/RSS/manual shipped features Matches customer requests against shipped features and supports outreach drafting.
Knowledge Gaps Shipped features, documentation source URLs Checks shipped releases against configured docs sites and queues documentation findings. Requires the knowledge_gaps flag.
Customer Detail Health, activity, revenue, HubSpot enrichment, account identity Opens from the other sections and centers the account.

Required Integrations

Salesbricks

Powers: Contracts, Convert, Pipeline fallback/open orders, Re-engage, renewal context for Health.

Connect: Settings -> Integrations -> Salesbricks.

Stripe

Powers: Contracts, Convert, Health payment-state factors, Customer Detail revenue sources.

Connect: Settings -> Integrations -> Stripe.

PostHog

Powers: Health adoption scoring, Convert usage context, Customer Detail active-user metrics.

Connect: Settings -> Integrations -> PostHog.

Attio

Powers: Pipeline as a CRM opportunity source, including stage reads and editable stage movement when configured.

Connect: Settings -> Integrations -> Attio.

Optional Sources

HubSpot

Powers: Customer Detail enrichment and optional company context. The current matching key is company domain.

Salesforce

Powers: Optional pipeline source filtering when connected and surfaced by the pipeline data layer.

GitHub, RSS, and Manual Shipped Features

Powers: Releases / Close the Loop, and Knowledge Gaps. GitHub releases, RSS feeds, and manual shipped-feature entries form the release catalog that both request matching and documentation-gap analysis read from.

Documentation Sources

Powers: Knowledge Gaps. Each source is a docs site or help-center root URL tagged as Customer docs or Internal docs. Only active sources are searched during analysis, and the audience tag changes how strictly the classifier recommends customer-facing documentation.

Configure: Settings -> Features -> Success -> Documentation sources.

Section Setup Readiness

The backend exposes setup readiness for:

Endpoint:

GET /v3/rest/success/sections/:section/setup

The response includes:

Field Meaning
summary Plain-English status for that section.
reusedSystems Existing BuildBetter systems the section should reuse, such as CRM identity, metadata projection, Signals, Feedback Ops, or Workflows.
connectors Required or useful providers with connected, available, or provider_missing status.
fastPaths App links that help the user finish setup, such as CRM, Integrations, Health, Convert, Signals, Feedback Ops, or Workflows.
nextSteps Concrete setup or implementation steps derived from connector state plus the section definition.

Connector status means:

Status Meaning
connected The provider exists and the workspace has at least one healthy connection.
available The provider exists in the catalog, but the workspace has not connected it yet.
provider_missing The provider is not in the integration provider catalog.

Only healthy connection statuses count as connected. Inactive, disabled, errored, and reauth-needed connections do not count toward setup readiness.

Reused Systems by Section

Section Reused Foundations
Convert CRM companies and people, CRM metadata projection, Health scoring foundation.
Contracts CRM companies, CRM metadata projection, existing Stripe/Salesbricks provider patterns.
Pipeline CRM identity graph, Attio provider/sync stack, Convert and Health overlays.
Re-engage CRM account identity, Signals and feedback context, shipped-feature catalog foundation.
Close the Loop Feedback Ops queues, Signals/request evidence, workflow and task runtime.

The Route-Accounts Model

Each Success section can move an account into another section's queue. Routed accounts appear in the destination with origin context.

From To Why
Health Convert A trial needs conversion outreach.
Health Pipeline An at-risk account is also an opportunity.
Health Contracts Renewal or payment details need review.
Health Re-engage An account is leaving Health but may be worth a winback.
Convert Pipeline A trial has become an opportunity.
Convert Re-engage A trial stalled and may need revival later.
Pipeline Contracts A deal moved into contract/subscription tracking.
Contracts Health A renewal, invoice, or payment issue creates account risk.
Re-engage Pipeline A winback becomes a live opportunity.

Demo Mode

Demo mode is sample data, not a data import. It:

Health, Convert, Contracts, Pipeline, and Releases / Close the Loop have demo-mode paths in the UI. Re-engage currently requires Salesbricks live data and shows an integration prompt when disconnected.

Feature Flag and Routes

The whole workspace is gated by the success feature flag.

Tip: For rollout, enable the flag first, connect Salesbricks and Stripe, then add PostHog and Attio. That unlocks the highest-value path: Health -> Contracts -> Convert -> Pipeline.