A free-tier change is evidence that the public acquisition or usage boundary moved. It may change who can evaluate the product, how quickly users reach a paid plan, or which capabilities remain accessible. It does not, by itself, prove growth, margin pressure, or a strategic pivot.
What this guide covers
- five types of free-tier movement;
- the fields required for a comparable record;
- plausible implications and alternative explanations;
- a decision memo for your own response.
Classify the movement first
Introduction
A previously paid or trial-only product adds ongoing free access.
Possible review: Does this lower evaluation friction or target a new individual/education/open-source audience?
Expansion
The free allowance, model access, projects, history, export, or collaboration becomes more generous.
Possible review: Does the product now cover a complete entry-level job that previously required payment?
Contraction
Usage, retention, projects, features, or support is reduced.
Possible review: Which active user segment reaches the paid boundary sooner?
Trial replacement
Ongoing free access becomes time-limited or vice versa.
Possible review: Did the evaluation path change from learning over time to a concentrated buying event?
Qualification change
Card requirements, verification, region, organization type, or eligibility changes.
Possible review: Is the vendor filtering abuse, serving a region differently, or changing the sales handoff? These remain hypotheses until corroborated.
Capture the complete boundary
Do not record only “Free plan added.” Save:
- eligible audience and region;
- time limit, if any;
- included usage and reset period;
- available models or capabilities;
- project, data, history, and export limits;
- collaboration and support;
- card or verification requirement;
- over-limit behavior;
- upgrade path and CTA.
Official plan pages such as GitHub Copilot, Lovable, and Langfuse show why “free” is not a standardized object. The value depends on the included job and the limit behavior.
Identify the affected user job
Map the free tier to a job, not a persona label.
Examples:
- evaluate the product with realistic data;
- complete a small personal project;
- learn and prototype;
- run a low-volume production workflow;
- collaborate with a small team;
- observe data without acting;
- contribute to open-source work.
A free plan that allows evaluation but not completion serves a different acquisition function from one that supports a durable low-volume job.
Build plausible interpretations
| Observed movement | Possible implication | Alternative explanation |
|---|---|---|
| Free plan introduced | acquisition broadening | limited launch or competitive response |
| Allowance increased | more value before paywall | lower unit cost or temporary promotion |
| Allowance reduced | faster monetization boundary | abuse control or capacity constraint |
| Feature moved to paid | higher willingness-to-pay test | packaging cleanup |
| Card now required | stronger qualification | fraud/abuse reduction |
| Trial replaces free | concentrated conversion motion | simplify legacy tiers |
Do not choose one explanation merely because it is narratively satisfying. Look for persistence, help-center updates, pricing context, product announcements, and your own customer evidence.
Decide whether to respond
Use three questions:
- Overlap: Does the new boundary affect the same user job or segment as ours?
- Materiality: Does it change the cost or friction of evaluation, adoption, or switching?
- Evidence: Is the movement persistent and corroborated by the relevant official pages?
Possible responses include:
- no change; record for context;
- update comparison or sales guidance;
- test a different activation or trial path;
- review an entitlement boundary;
- interview affected customers;
- monitor for conversion or positioning follow-through.
Copying the competitor's free plan is not a default response. Your economics, product job, and growth model may differ.
Free-tier response memo
# Free-tier movement: [Company]
Observed:
Source/region:
Movement: introduction / expansion / contraction / trial / qualification
## Boundary before
- audience:
- allowance:
- entitlements:
- duration/reset:
- entry requirement:
## Boundary after
- audience:
- allowance:
- entitlements:
- duration/reset:
- entry requirement:
## Affected job and segment
## What the evidence supports
## Plausible explanations and unknowns
## Our review
Owner:
Decision:
Customer evidence needed:
Outcome:Stripe's pricing and packaging guide is a useful strategic reference for matching metrics and tiers to value. Use EXVIV's pricing-monitoring page, market map, and Evidence Compare for the dated source record rather than relying on memory.
Related EXVIV research
Sources and further reading
Method note
This framework interprets a public acquisition boundary. It does not infer conversion, margin, abuse, or internal strategy without additional evidence. Recheck region, billing state, eligibility, and persistence before confirming a change.