Product-Led Growth skill 03 of 13

Free Model Design: Freemium, Free Trials and Reverse Trials SKILL.md

The Free Model Design skill makes Claude, Codex or another AI agent design free offers that drive revenue. It compares freemium, time-limited trials, reverse trials, usage-based free tiers, open-source cores and free tools, places usage, seat, feature, time, history, branding and support gates where value grows, checks limits with data, sets trial length by time to value and designs the limit experience and fair migrations.

free-model-design/SKILL.md, version 1.0.0, 1,520 words.

The free offer is the front door of a product-led business. Too generous, and most users never need to pay; too stingy, and they never experience enough value to want to. The wrong type of free offer for the product (a 14-day trial for something that takes a month to set up, or freemium for a product whose value is all in advanced features) quietly caps growth. Designing the free model means choosing the type, the limits and gates, the upgrade triggers and the experience when users hit them.

This skill designs and reviews free models: freemium, free trials, reverse trials, usage-based free tiers and open-source cores, with limits, feature gates, trial length, card requirements and the upgrade experience, judged on activation, paid conversion and revenue.

Operating principles

  1. Free must deliver real value. Users should succeed at something meaningful on the free offer.
  2. Paid must solve a bigger problem. Gates should sit where value grows: teams, scale, control, advanced outcomes.
  3. Limits should be hit by the right users. Growing, engaged users should reach them; casual users shouldn't be pushed away.
  4. Upgrade moments should feel natural. Prompts appear when users need more, not randomly.
  5. Judge on revenue, not sign-ups. More free users is only good if paid conversion and retention follow.

Free model types

TypeHow it worksFits whenRisks
FreemiumFree plan forever with limitsLarge market, low cost to serve, network or viral effectsToo generous; support costs
Free trial (time-limited)Full or most features for 7 to 30 daysValue appears quickly; clear paid needTrial ends before value; pressure
Reverse trialStart with premium features for a period, then drop to freeYou want users to experience premium value and keep a free baseConfusion if not explained
Usage-based free tierFree up to a usage amountValue scales with usage (API calls, messages)Bill shock later; abuse
Open-source or community coreCore free; paid hosting, features or supportDeveloper tools, infrastructureHard to monetise if paid value unclear
Free tool or assessmentA standalone free tool that leads to the productComplex products with clear early insightsTool doesn't lead to product use

Limits and gates

Gate typeExampleWorks when
Usage limit3 projects, 1,000 contacts, 10 GBUsage grows with value
Seat limitUp to 3 usersValue grows with team size
Feature gateAutomation, integrations, SSO on paidAdvanced features matter to growing teams
Time limit14-day trialValue is quick and obvious
History limit90 days of history on freeLong-term data has value
Branding"Made with" badge on freeVisibility drives acquisition
Support levelCommunity support on freeBusinesses value faster support

When to use, and when not to

Use it when launching a free offer, when free-to-paid conversion is low, when free usage costs are high, when switching between trial and freemium and when packaging changes.

Don't use it to set list prices and tiers in depth (the Product Marketing pricing-packaging skill) or optimise the sign-up form (the CRO signup-flow-optimisation skill).

Inputs to ask for, in one message

  1. Product, value moment and how value grows with use.
  2. Current free offer, limits and plan distribution.
  3. Free-to-paid conversion, time to convert and churn by plan.
  4. Usage data: how many free users hit each limit, and their behaviour.
  5. Cost to serve free users.
  6. Competitor free offers.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as free-model-design/SKILL.md.

---
name: free-model-design
description: "Design free offers that drive revenue: freemium, time-limited trials, reverse trials, usage-based free tiers, open-source cores and free tools, usage, seat, feature, time, history, branding and support gates placed where value grows, limit analysis with data, trial length by time to value, the limit experience and fair migrations. Use whenever someone asks about freemium versus free trial, reverse trials, free plan limits, feature gating, trial length, card upfront for trials, free users not upgrading or redesigning a free plan."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/product-led-growth/free-model-design/
  category: marketing
  subcategory: product-led-growth
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Free Model Design: Freemium, Free Trials and Reverse Trials

The free offer is the front door of a product-led business. Too generous, and most users never need to pay; too stingy, and they never experience enough value to want to. The wrong type of free offer for the product (a 14-day trial for something that takes a month to set up, or freemium for a product whose value is all in advanced features) quietly caps growth. Designing the free model means choosing the type, the limits and gates, the upgrade triggers and the experience when users hit them.

This skill designs and reviews free models: freemium, free trials, reverse trials, usage-based free tiers and open-source cores, with limits, feature gates, trial length, card requirements and the upgrade experience, judged on activation, paid conversion and revenue.

## Operating principles
1. **Free must deliver real value.** Users should succeed at something meaningful on the free offer.
2. **Paid must solve a bigger problem.** Gates should sit where value grows: teams, scale, control, advanced outcomes.
3. **Limits should be hit by the right users.** Growing, engaged users should reach them; casual users shouldn't be pushed away.
4. **Upgrade moments should feel natural.** Prompts appear when users need more, not randomly.
5. **Judge on revenue, not sign-ups.** More free users is only good if paid conversion and retention follow.

## Free model types
| Type | How it works | Fits when | Risks |
|---|---|---|---|
| Freemium | Free plan forever with limits | Large market, low cost to serve, network or viral effects | Too generous; support costs |
| Free trial (time-limited) | Full or most features for 7 to 30 days | Value appears quickly; clear paid need | Trial ends before value; pressure |
| Reverse trial | Start with premium features for a period, then drop to free | You want users to experience premium value and keep a free base | Confusion if not explained |
| Usage-based free tier | Free up to a usage amount | Value scales with usage (API calls, messages) | Bill shock later; abuse |
| Open-source or community core | Core free; paid hosting, features or support | Developer tools, infrastructure | Hard to monetise if paid value unclear |
| Free tool or assessment | A standalone free tool that leads to the product | Complex products with clear early insights | Tool doesn't lead to product use |

## Limits and gates
| Gate type | Example | Works when |
|---|---|---|
| Usage limit | 3 projects, 1,000 contacts, 10 GB | Usage grows with value |
| Seat limit | Up to 3 users | Value grows with team size |
| Feature gate | Automation, integrations, SSO on paid | Advanced features matter to growing teams |
| Time limit | 14-day trial | Value is quick and obvious |
| History limit | 90 days of history on free | Long-term data has value |
| Branding | "Made with" badge on free | Visibility drives acquisition |
| Support level | Community support on free | Businesses value faster support |

## When to use, and when not to
Use it when launching a free offer, when free-to-paid conversion is low, when free usage costs are high, when switching between trial and freemium and when packaging changes.

Don't use it to set list prices and tiers in depth (the Product Marketing `pricing-packaging` skill) or optimise the sign-up form (the CRO `signup-flow-optimisation` skill).

## Inputs to ask for, in one message
1. Product, value moment and how value grows with use.
2. Current free offer, limits and plan distribution.
3. Free-to-paid conversion, time to convert and churn by plan.
4. Usage data: how many free users hit each limit, and their behaviour.
5. Cost to serve free users.
6. Competitor free offers.

## Workflow

### Step 1. Map how value grows
By usage, team size, advanced needs, history or outcomes.

### Step 2. Choose the type
Match to time to value, market size, cost to serve and how value grows.

### Step 3. Set gates
Place limits where growing, engaged users naturally need more.

### Step 4. Check with data
What share of free users reach each limit, and do they look like paying customers?

### Step 5. Design the limit experience
Clear messages before and at the limit, what upgrading adds, easy self-serve checkout and a way to talk to sales for larger needs.

### Step 6. Decide trial details
Length based on time to value, card upfront or not, what happens at the end (downgrade to free or lock).

### Step 7. Test and measure
Activation, free-to-paid conversion, revenue per sign-up, support cost and retention; test changes on new cohorts.

## Trial length guide
| Time to value | Suggested trial |
|---|---|
| Minutes to a day | 7 days |
| A few days | 14 days |
| One to three weeks | 21 to 30 days, or a reverse trial |
| Longer | Freemium, guided pilot or free assessment instead |

## Limit analysis template
```
| Limit | Free users reaching it (90 days) | Share who upgrade after reaching it | Their profile | Change? |
| 3 projects | 18% | 22% | Small agencies | Keep |
| 2 seats | 6% | 35% | Growing teams | Consider 3 seats to drive invites |
| 90-day history | 3% | 5% | Long-term users | Not a strong trigger |
```

## Reverse trial messaging
Tell users at sign-up that they have premium features for a set period, remind them before it ends, show what they used that is premium and explain what stays free. Clear messages turn the drop to free into a natural upgrade moment instead of a surprise.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Free plan too generous | Tighten gates for new users; grandfather existing users fairly |
| High abuse or fraud | Verification, rate limits and risk scoring |
| Card-upfront debate | Test on paid revenue per sign-up, not sign-up volume |
| Enterprise buyers | Free plan for individuals; trials or pilots for enterprise features |
| Infrastructure costs for free users | Usage caps, inactivity clean-up, lighter free infrastructure |

## Handoffs to related skills
- Strategy: `plg-strategy`
- Upgrade prompts: `in-app-upgrade-prompts`
- Seat growth and invites: `team-expansion-invites`
- Metrics: `plg-metrics`
- Pricing and packaging: the Product Marketing `pricing-packaging` skill
- Pricing page: the CRO `pricing-page-optimisation` skill

## Worked example
A form builder offered unlimited forms and responses on its free plan; 98% of users never paid. Analysis showed teams that grew paid for integrations and branding removal, while response volume tracked business value. The new model limited free plans to 100 responses a month and three forms, kept the "made with" badge on free, moved integrations to paid and launched a 14-day reverse trial of premium features for new sign-ups. Existing free users kept old limits for six months. Free-to-paid conversion rose several times over, and the badge continued to bring in new sign-ups.

## Output format
```
# Free model design: <product>, <date>
## How value grows
## Recommended type and rationale
## Limits and gates (with data)
## Limit and upgrade experience
## Trial details
## Migration plan for existing users
## Metrics and tests
```

## Common mistakes
- Free plans that cover most users' needs.
- Trials shorter than time to value.
- Gates on features users never reach.
- Judging changes on sign-ups.
- Surprising existing free users with sudden limits.

## Questions to ask before you design
- How does value grow as customers succeed?
- Which limits do your best paying customers hit first?
- How long does a new user take to reach value?

## Self-check before you answer
- Does free deliver real value?
- Are gates placed where value grows?
- Is the limit experience clear and helpful?
- Are changes judged on revenue and retention?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/product-led-growth/free-model-design/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Map how value grows

By usage, team size, advanced needs, history or outcomes.

Step 2. Choose the type

Match to time to value, market size, cost to serve and how value grows.

Step 3. Set gates

Place limits where growing, engaged users naturally need more.

Step 4. Check with data

What share of free users reach each limit, and do they look like paying customers?

Step 5. Design the limit experience

Clear messages before and at the limit, what upgrading adds, easy self-serve checkout and a way to talk to sales for larger needs.

Step 6. Decide trial details

Length based on time to value, card upfront or not, what happens at the end (downgrade to free or lock).

Step 7. Test and measure

Activation, free-to-paid conversion, revenue per sign-up, support cost and retention; test changes on new cohorts.

Trial length guide

Time to valueSuggested trial
Minutes to a day7 days
A few days14 days
One to three weeks21 to 30 days, or a reverse trial
LongerFreemium, guided pilot or free assessment instead

Limit analysis template

| Limit | Free users reaching it (90 days) | Share who upgrade after reaching it | Their profile | Change? |
| 3 projects | 18% | 22% | Small agencies | Keep |
| 2 seats | 6% | 35% | Growing teams | Consider 3 seats to drive invites |
| 90-day history | 3% | 5% | Long-term users | Not a strong trigger |

Reverse trial messaging

Tell users at sign-up that they have premium features for a set period, remind them before it ends, show what they used that is premium and explain what stays free. Clear messages turn the drop to free into a natural upgrade moment instead of a surprise.

Edge cases and judgement calls

SituationWhat to do
Free plan too generousTighten gates for new users; grandfather existing users fairly
High abuse or fraudVerification, rate limits and risk scoring
Card-upfront debateTest on paid revenue per sign-up, not sign-up volume
Enterprise buyersFree plan for individuals; trials or pilots for enterprise features
Infrastructure costs for free usersUsage caps, inactivity clean-up, lighter free infrastructure
  • Strategy: plg-strategy
  • Upgrade prompts: in-app-upgrade-prompts
  • Seat growth and invites: team-expansion-invites
  • Metrics: plg-metrics
  • Pricing and packaging: the Product Marketing pricing-packaging skill
  • Pricing page: the CRO pricing-page-optimisation skill

Worked example

A form builder offered unlimited forms and responses on its free plan; 98% of users never paid. Analysis showed teams that grew paid for integrations and branding removal, while response volume tracked business value. The new model limited free plans to 100 responses a month and three forms, kept the "made with" badge on free, moved integrations to paid and launched a 14-day reverse trial of premium features for new sign-ups. Existing free users kept old limits for six months. Free-to-paid conversion rose several times over, and the badge continued to bring in new sign-ups.

Output format

# Free model design: <product>, <date>
## How value grows
## Recommended type and rationale
## Limits and gates (with data)
## Limit and upgrade experience
## Trial details
## Migration plan for existing users
## Metrics and tests

Common mistakes

  • Free plans that cover most users' needs.
  • Trials shorter than time to value.
  • Gates on features users never reach.
  • Judging changes on sign-ups.
  • Surprising existing free users with sudden limits.

Questions to ask before you design

  • How does value grow as customers succeed?
  • Which limits do your best paying customers hit first?
  • How long does a new user take to reach value?

Self-check before you answer

  • Does free deliver real value?
  • Are gates placed where value grows?
  • Is the limit experience clear and helpful?
  • Are changes judged on revenue and retention?

When to use this skill, and when not to

Use it when launching a free offer, when free-to-paid conversion is low, when free usage costs are high, when switching between trial and freemium and when packaging changes.

Too generous a free offer means most users never pay; too stingy, and they never experience enough value to want to. The wrong type for the product, such as a 14-day trial for something that takes a month to set up, quietly caps growth.

Don’t use it to set list prices in depth (use the Product Marketing Pricing skill) or optimise sign-up forms (use the CRO Sign-Up Flow skill).

Example prompts

  • “Freemium, free trial or reverse trial for our product?”
  • “Our free plan is too generous. Redesign it.”
  • “How long should our trial be?”
  • “Which limits should trigger upgrades?”
  • “Should we require a card for trials?”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Free model: example form builder, 12 October 2026

Before: unlimited forms and responses free; 98% never paid
New: 100 responses a month and 3 forms on free; badge kept on free; integrations paid; 14-day reverse trial
Migration: existing free users keep old limits for 6 months
Result: free-to-paid conversion rose several times over

Changes are judged on revenue per sign-up and retention, not on how many people sign up.

What the agent needs from you

The skill asks for how value grows with use, the current free offer and plan distribution, free-to-paid conversion and churn by plan, data on users reaching each limit, cost to serve free users and competitor free offers.

How this skill hands off to related skills

The free model connects to the set: Strategy, Upgrade Prompts, Invites and Metrics, plus the Product Marketing Pricing and CRO Pricing Page skills.

How to run Free Model Design step by step

  1. Install the skill as free-model-design/SKILL.md.
  2. Map how value grows.
  3. Choose the free model type.
  4. Set gates and check them with data.
  5. Design the limit experience and trial details.
  6. Test on new cohorts and measure revenue.

Situations this skill handles

Free models fail in familiar ways. The skill handles these situations:

SituationWhat the skill does
Free plan too generousTighter gates for new users
Abuse or fraudVerification and rate limits
Card-upfront debateTested on revenue per sign-up
Enterprise buyersFree for individuals, pilots for enterprise
High infrastructure costUsage caps and clean-up
Trial shorter than time to valueLonger trial or reverse trial

What makes this skill different

Most free plans copy a competitor. This skill maps how value grows, places gates where engaged users naturally need more, checks limits against real usage and designs what happens at the limit.

It also plans fair migrations, so existing users are not surprised by sudden restrictions.

Practical tips from real projects

  • Free must deliver real value.
  • Paid must solve a bigger problem.
  • Limits hit by the right users.
  • Judge on revenue, not sign-ups.

A worked example: a form builder offered unlimited forms and responses on its free plan, and 98% of users never paid. Analysis showed growing teams paid for integrations and branding removal, while response volume tracked business value. The new model limited free plans to 100 responses a month and three forms, kept the made-with badge on free, moved integrations to paid and launched a 14-day reverse trial of premium features for new sign-ups. Existing free users kept their old limits for six months. Free-to-paid conversion rose several times over, and the badge continued to bring in new sign-ups.

Free model types each fit different products. Freemium suits large markets, low cost to serve and network effects but risks being too generous. Time-limited trials suit quick, obvious value but can end before users reach it. Reverse trials let users experience premium value and then keep a free base. Usage-based free tiers suit value that scales with usage. Open-source cores suit developer tools. Free tools or assessments suit complex products with clear early insights.

Gates work when they follow value: usage limits when usage grows with value, seat limits when value grows with team size, feature gates for advanced needs of growing teams, time limits for quick value, history limits when long-term data matters, branding on free outputs for visibility and support levels for businesses that value faster help.

Limit analysis checks each limit against data: the share of free users reaching it in 90 days, the share who upgrade afterwards and what those users look like. A project limit reached by small agencies who often upgrade is worth keeping; a history limit almost nobody reaches is a weak trigger.

Trial length follows time to value: around seven days when value appears within a day, 14 days for a few days, 21 to 30 days or a reverse trial for one to three weeks, and freemium, a guided pilot or a free assessment when value takes longer.

The limit experience warns users before they reach a limit, explains at the limit what upgrading adds, offers easy self-serve checkout and gives larger accounts a way to talk to sales.

Reverse trials need clear messaging: tell users at sign-up that they have premium features for a set period, remind them before it ends, show which premium features they used and explain what stays free. Card-upfront decisions are tested on paid revenue per sign-up rather than sign-up volume, and abuse is handled with verification, rate limits and risk scoring.

High infrastructure costs for free users are managed with usage caps, clean-up of inactive accounts and lighter free infrastructure.

Frequently asked questions

Freemium is a free plan forever with limits; a free trial gives full or most features for a limited time.

Users start with premium features for a set period, then drop to a free plan unless they upgrade.

Long enough to reach value: about 7 days for minutes-to-value products, 14 for a few days and 21 to 30 or a reverse trial for longer.

Where value grows, such as usage, seats, advanced features or history, so engaged, growing users reach them.

Test it on paid revenue per sign-up; card upfront usually means fewer sign-ups but higher conversion.

Apply new limits to new users first and give existing users notice and time.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.