Independent tool profilePostHog for a New SaaS: Funnels, Free Limits & Fit
Plan a useful SaaS activation funnel with PostHog. Check monthly event and replay allowances, per-product billing limits and a focused measurement checklist.
By AIIndieKit editorial · Official sources checked · Public-source research, not a hands-on benchmark
Editorial judgment
Measure the next product decision before collecting everything.
For a newly launched SaaS with a signup flow and one core action, consider PostHog when you need to understand where people stop. Start with a question such as whether new accounts complete that action, then define the minimum events that answer it. Visits, successful payments and product activation are different signals; more captured events do not automatically make the answer more reliable.
Official facts
What the provider documents
The facts below come from the dated official sources linked beside each entry. Use them to check the workflow and plan constraints before trying this tool; fit, budget cautions and evaluation steps are our editorial judgments.
- Product Analytics documents funnels that follow a series of actions, with filters and ordering options to examine drop-off between steps. [Source 2]
- The pricing page lists monthly free allowances of 1 million analytics events and 5,000 session recordings. These are different usage units, not a combined allowance or a number of users. [Source 1]
- Free usage stops at the free limits without a payment card. Pay-as-you-go retains monthly free allowances and supports a separate billing limit for each product. Prices are in USD and exclude taxes. [Source 1]
- The pricing FAQ gives different retention periods for events and recordings. Free recordings are retained for one month; paid recordings normally have 90-day retention, with longer retention available through add-ons. [Source 1]
A good fit when
- You have one actionable funnel question and can define consistent events across the relevant steps.
- You can distinguish internal testing, anonymous visits and real customer activity.
Reconsider when
- You need only a simple traffic count and cannot commit time to event definitions and interpretation.
- You intend to capture every interaction before deciding which data is necessary or appropriate to collect.
Editorial interpretation
Read the bill beyond the headline
Count events rather than equating 1 million events with 1 million visitors. Session replay, feature flags and other products use their own meters and limits; estimate the products you actually need. The free allowance renews monthly, and paid USD prices exclude tax. This profile has not installed a tracker, audited consent requirements or established attribution to revenue.
Before you commit
- Write a decision question first: for example, which step prevents a new account from completing its first useful action?
- Define signup completion and the core action consistently; distinguish server-confirmed payment from clicking a checkout button.
- Review properties and collection settings before implementation. Keep credentials, private text and unnecessary identifiers out of events; check masking before considering replay.
- Use a disposable test flow to check duplicate events, identity changes, failed actions and exclusion of team tests.
- Estimate each product's usage independently and set appropriate billing limits if you later enable paid usage. Expect missing data when collection stops.
Continue the decision
Method and sources
We reviewed the official pages below on 2026-10-07. Fit, checklists, and budget cautions are our editorial judgment. We did not benchmark speed, uptime, inbox placement, or productivity. These are ordinary provider links; no approved affiliate partnership or commission is claimed. Check the latest terms before subscribing.