#activation

The live debates are about where product-led growth should hand off to sales, how much onboarding friction is acceptable, and whether packaging or price creates more durable leverage. The right answer changes with ACV, buyer complexity, and the speed of value realization.

Three questions worth debating:
- when product-led growth should hand off to sales
- how much friction is acceptable during onboarding
- whether packaging or pricing creates more durable leverage

Background reading before you take a strong stance:
- 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.
- PostHog video archive: youtube.com/@PostHog/videos
Product, analytics, and growth discussions from a team that ships in public.

When you respond, include the environment you are optimizing for. Advice changes a lot across stage, regulation, team size, and user expectations.

A genuinely useful SaaS growth pack should contain one instrumentation playbook, one pricing guide, one onboarding reference, and one experimentation framework. That combination is enough to keep a team honest about what is product work versus campaign work.

The kinds of materials worth saving in this space:
- operator writeups about activation redesigns
- pricing case studies with before-and-after metrics
- retention frameworks tied to actual user behavior

Read:
- 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.
- Intercom on user onboarding: intercom.com/blog/user-onboarding/
Helpful for teams redesigning the first-run experience around actual user value.

Documents and downloadable 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.

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

Build or inspect:
- 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.

Image references:
- PostHog product analytics reference: posthog.com/product-analytics
Useful screenshots and concepts for thinking about funnels, activation, and retention visually.

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"
}

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.