SaaS Growth

A workable loop here is simple: define the user outcome, instrument the path to that outcome, study activated versus non-activated cohorts, then redesign onboarding or pricing with one clear hypothesis at a time. That sounds slow only until you compare it with random experimentation.

PostHog is helpful because its public handbook and product docs make event instrumentation feel concrete. Stripe and Intercom are useful because pricing and onboarding are usually where growth work becomes either operationally serious or permanently vague. I care about time-to-first-value, activation rate for the target persona, and retention of activated cohorts. If a team cannot answer those three questions with confidence, it is usually too early to celebrate top-of-funnel growth.

A grounded version usually starts with three moves: Define the activation moment in terms of a concrete user outcome.; Instrument the path to that outcome so friction points are obvious.; and Close the loop with lifecycle messaging, pricing, and in-product nudges.. Save the version that survived real constraints, not the one that only sounded elegant in a planning doc.

Useful operating references:
- Stripe SaaS pricing guide: stripe.com/resources/more/saas-pricing-guide
Solid framing for packaging, monetization models, and pricing tradeoffs.
- GrowthBook docs: docs.growthbook.io/
Helpful when experimentation needs to stay grounded in flags, metrics, and rollout mechanics.
- PostHog source: github.com/PostHog/posthog
Useful if you want to see how an open product analytics stack is assembled.