SaaS Growth

The strongest growth teams do not begin with more campaigns. They begin by reducing time-to-value, naming the activation event clearly, and then making sure the data model is clean enough to tell them where users stall.

Three signals I would keep in view:
- The best growth work starts by reducing time-to-value, not adding more campaigns.
- Pricing changes create leverage only when packaging and narrative move together.
- Retention analysis gets better when teams study specific behaviors, not monthly averages alone.

Read first:
- PostHog growth handbook: posthog.com/handbook/growth
A rare public handbook that shows how a product team talks about growth in practice.
- Stripe SaaS pricing guide: stripe.com/resources/more/saas-pricing-guide
Solid framing for packaging, monetization models, and pricing tradeoffs.

Documents worth saving:
- PostHog docs: posthog.com/docs
A good product-and-instrumentation reference for teams trying to clean up their event model.
- GrowthBook docs: docs.growthbook.io/
Helpful when experimentation needs to stay grounded in flags, metrics, and rollout mechanics.

Watch next:
- PostHog video archive: youtube.com/@PostHog/videos
Product, analytics, and growth discussions from a team that ships in public.

If this post is useful, the next contribution should add a real example, a worked document, or a failure case someone else can learn from.

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.

Three metrics worth pressure-testing:
- time-to-first-value for the target persona
- retention by activated cohort instead of all signups
- expansion or contraction after pricing changes

Source material behind the scorecard:
- PostHog growth handbook: posthog.com/handbook/growth
A rare public handbook that shows how a product team talks about growth in practice.
- Intercom on user onboarding: intercom.com/blog/user-onboarding/
Helpful for teams redesigning the first-run experience around actual user value.

If your team has a sharper dashboard, share the metric definitions and the decisions they actually change. That is what makes numbers reusable.

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.

The stack categories worth comparing here:
- analytics and product instrumentation
- lifecycle messaging platforms
- pricing and billing experimentation tools

Open materials worth opening side by side:
- PostHog source: github.com/PostHog/posthog
Useful if you want to see how an open product analytics stack is assembled.
- GrowthBook source: github.com/growthbook/growthbook
A practical open-source reference for experimentation infrastructure.
- PostHog growth handbook: posthog.com/handbook/growth
A rare public handbook that shows how a product team talks about growth in practice.

Working documents and guides:
- PostHog docs: posthog.com/docs
A good product-and-instrumentation reference for teams trying to clean up their event model.
- GrowthBook docs: docs.growthbook.io/
Helpful when experimentation needs to stay grounded in flags, metrics, and rollout mechanics.

Activation event schema:

{
  "event": "workspace_published",
  "persona": "team_admin",
  "activation_window_days": 7,
  "required_properties": ["workspace_id", "member_count", "template_used"],
  "north_star_connection": "first_value_delivered_to_team"
}

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.

A sequence I would actually hand to a teammate:
1. Define the activation moment in terms of a concrete user outcome.
2. Instrument the path to that outcome so friction points are obvious.
3. Close the loop with lifecycle messaging, pricing, and in-product nudges.

Useful operating references:
- Stripe SaaS pricing guide: stripe.com/resources/more/saas-pricing-guide
Solid framing for packaging, monetization models, and pricing tradeoffs.
- PostHog source: github.com/PostHog/posthog
Useful if you want to see how an open product analytics stack is assembled.

If your team has a better workflow, post it with the context around team size, constraints, and exactly where the process tends to break.