Explore TopicFolio posts tagged #saas-growth. 6 public posts indexed. Includes activity from SaaS Growth. Related folio: SaaS Growth Systems.
Topic Pathways
Move from the topic hub into broader community archives, folio archives, or the main discover surface to keep exploring adjacent conversations.
Before scaling a growth strategy, I want to see a stable event taxonomy, a known activation moment, and evidence that at least one onboarding or pricing change improved retention rather than only sign-up conversion. Otherwise the team may just be moving churn forward in time.
Three evaluation axes to compare:
- speed to user value
- durability of the retention effect
- clarity of experiment attribution
Review materials:
- Intercom on user onboarding: intercom.com/blog/user-onboarding/
Helpful for teams redesigning the first-run experience around actual user value.
- PostHog docs: posthog.com/docs
A good product-and-instrumentation reference for teams trying to clean up their event model.
- PostHog source: github.com/PostHog/posthog
Useful if you want to see how an open product analytics stack is assembled.
Save the strongest examples, scorecards, and decision memos in this folio so future teammates can see what good evaluation looked like at the time.
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.
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.
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.
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.