Six instruments, calibrated for one-to-ten-person teams.
Built for founders who shipped the product but kept deferring the systems around it. The instrument behind the SaaS — wired in once, owned by you, readable on a Sunday afternoon.
01 · Onboarding flow
Self-serve sign-up to first value.
Sign-up, identity, payment, activation events, welcome cadence — wired so a new user gets to the "aha" without you in the loop.
Stripe checkout & trial logic
Auth0 / Clerk identity
Loops onboarding sequence
Activation event instrumentation
02 · Churn signals
Catch leavers before they cancel.
Usage drop, login gap, feature abandonment — surfaced as a weekly leaver-watch list, not a quarterly post-mortem. Save accounts before the cancel button.
June or Paddle Retain integration
Custom event-pipeline scoring
At-risk weekly digest
Save-play playbook routing
03 · Billing reconciliation
Stripe ↔ Xero, owner-readable.
Stripe charges, refunds, disputes, and fees reconciled into Xero on a schedule. The accountant call gets shorter. The VAT return adds up the first time.
Stripe → Xero sync via Synder
Refund & dispute reconciliation
VAT-aware revenue ledger
Owner-readable monthly close
04 · Activation & onboarding cohorts
Self-serve to first value, measured.
Trial sign-up to "aha" — instrumented as a cohort funnel, not a vanity dashboard. Drop-off surfaced by step, by segment, by week. The activation lift is something you ship, not something you hope for.
PostHog cohort funnels
Mixpanel or June.so activation
Per-segment drop-off view
A/B test infrastructure
05 · Pricing & packaging
Tier changes without downtime.
Plan migrations, proration, grandfathered customers, usage-based bolt-ons — handled in the billing system, not in a panicked Stripe-dashboard session. Ship the new pricing on a Tuesday, not a quarter from now.
Stripe Billing tier migrations
Chargebee or Paddle billing
Proration & grandfathering
Usage-based metering hooks
06 · BrainBase
Engineering wiki + customer-success playbook.
Architecture notes, runbooks, save-plays, onboarding scripts, investor-FAQ — searchable from the IDE, the inbox, the dashboard. The team doc that survives the next hire.
Runbooks & architecture notes
Customer-success playbooks
Investor-FAQ & metric defs
AI-assisted retrieval everywhere
Sample engagement
The founder who replaced four spreadsheets with one dashboard.
Two founders. Four hundred paying accounts. MRR tracked across four manual sheets.
An indie B2B SaaS hit £24k MRR pre-Series-A with two founders, four hundred paying accounts, and four manual spreadsheets stitching Stripe, PostHog, Xero, and a churn tracker the CTO refreshed weekly. Two-week build: Stripe Sigma plus PostHog wired into one founder dashboard, churn signals routed to a save-play queue, Stripe ↔ Xero reconciled by Synder. Three months in: investor update written in twenty minutes instead of a Sunday, eleven percent activation lift, and the CTO got Sundays back.
How we measure: activation = % of trials hitting the defined "first-value" event in week one, baseline drawn from 90 days of PostHog data (n = 612 trials) vs 90 days post-build; investor-update writing time logged by founder, weeks 1, 4, 12.
4 → 1spreadsheets replaced
+11%trial activation rate
20 mininvestor update, end to end
Adjacent industries
Different shape of the same problem.
If your work isn't exactly this, the nearest sectors share the rhythm. Or browse every industry we build for.