Freemium gives users a permanently free tier, trading revenue per user for volume and word of mouth. A free trial gives full access for a limited time, trading volume for urgency. In freemium vs free trial, the deciding factor is usually time to value: a product people understand in minutes can afford a clock, and one that takes weeks to show value usually cannot.
How it works
Dave Boyce's Freemium turns the choice into criteria (Ch 9). Freemium fits when value comes from a single user, serving a free user costs almost nothing, and the upgrade path is clear. A free trial fits when serving users costs real money, value needs a whole team, or the contract value is high.
A reverse trial starts users on the paid tier and moves them to a free one when the trial ends, which works when the tiers are clearly different. Boyce's view is that an experiment on new signups settles it.
He is just as specific about where a free plan's limit belongs: on one value metric, reached after a habit has formed, so the upgrade feels expected rather than like a wall. Zoom's 40-minute meetings and Dropbox's storage cap are among his examples (Ch 9 and Ch 10).
What it assumes your events already do
| Event | What the framework uses it for | What it reports when the event breaks |
|---|---|---|
Plan limit reachedlimit_hit | Where the free plan stops. | If the limit event stops firing, free-to-paid analysis loses its main trigger and the limit looks irrelevant. |
Plan changeplan_changed | Conversion, and downgrade at the end of a trial. | An automatic downgrade that fires the same event as a voluntary one makes trial-end look like customers choosing to leave. |
Activation or First Impact eventfirst_report_shared | The guardrail: charging earlier must not cut the share who reach value. | Without it, a pricing test can win on revenue while lowering the number of users who ever see the product work. |
Event names are illustrative; yours will differ. The dependency map shows which other frameworks share each event.
The reverse trial that looked like mass churn
Illustrative example. The company and the figures are invented to show the mechanism.
A company tests a reverse trial against its freemium plan. On day fourteen every reverse-trial user who has not paid moves to the free tier automatically, and billing fires the same plan_downgraded event it uses when a customer downgrades on purpose.
The dashboard shows the reverse-trial group downgrading at 85%, and the test is stopped as a failure. The comparison that mattered, how many of those users chose to pay, was never read.
Checks before you trust it
- Mark automatic plan changes differently from user-initiated ones, with a property on the event.
- Use the First Impact rate as a guardrail in any pricing test.
- Measure monetisation per cohort over a fixed window, such as six months, for both arms.
- Confirm the limit and upgrade events fire from every place the paywall appears.
Heard in The Question
Interviews in The Question that bear on this framework:
- Nima Aksoy: demand is the first dashboard. Which data deserves trust depends on the product's stage: market demand first, the activation drop-off next, financial reporting at maturity.
Check the events under it
Before Freemium vs free trial goes into a plan, find out whether the events it needs exist and still fire the way it assumes. The free audit maps what your product collects today: sign in, connect a GitHub repository or Supabase, and Skene returns one audit, with no card. On Pro, Skene Cloud reviews every pull request on a linked GitHub repository for removed or broken tracking, so a pull request that removes or renames one of these events is flagged before it merges.