#pricing

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.

The recurring mistake is optimizing acquisition while the first-run experience remains muddy. The next one is running pricing experiments without a packaging hypothesis, which usually means the test is teaching less than the dashboard suggests.

Common traps to watch:
- optimizing acquisition while activation remains fuzzy
- running pricing tests without clear packaging hypotheses
- calling every onboarding step a growth lever

References that help correct the drift:
- Stripe SaaS pricing guide: stripe.com/resources/more/saas-pricing-guide
Solid framing for packaging, monetization models, and pricing tradeoffs.
- PostHog product analytics reference: posthog.com/product-analytics
Useful screenshots and concepts for thinking about funnels, activation, and retention visually.

This folio post is meant to be saved and revised. Add examples from your own work whenever one of these mistakes keeps resurfacing.

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