29 October 2026 EN ES
The First Users

How products get their first real users

Converting

How to kill your free plan without losing your first users

A free-tier kill test and migration playbook for early-stage founders: retire the demo, move existing users to paid, and keep a clean export path.

Illustration: How to kill your free plan without losing your first users

You have a free plan, a handful of users, and a support inbox full of the same question. When your free plan is only a demo of the paid plan, retire it for new users and move existing users to paid with a clean export.

Notenz retired its free tier, which had been limited to one note and one recipient, with no file uploads, no SMS alerts, and only monthly check-ins. It moved existing free users to Guardian, its paid plan, at no cost for six months.

You have already spent the unscalable hours: manual outreach, hand-holding, and repeated support. You do not have distribution yet. You have a first hundred, and the free tier is either earning that relationship or consuming the time you need to keep the people who will pay.

A free plan is a demo until it has an owner

A SaaS free tier usually has no accountable person, no profit goal, and no scheduled review. Paid plans get someone accountable, a cost line, and a date to check. Free plans drift, and the missing controls show up as a support queue, a hidden subsidy, and a demo that never gets reviewed. Growth tactics that need scale are the wrong tool for a free tier that cannot pay for itself.

Run the kill test before you announce anything

  • Ask whether the free plan is a real product or a demo. It passes only when it creates a habit that leads to payment, not just a preview of the paid feature. A preview-only free tier should be retired for new users.
  • Before keeping a free tier, set a responsible person, a profit goal, and a regular review. Done means a named person, a margin target, and a scheduled review exist.
  • Choose the repricing move. Freemium repricing can take three forms: change what the free edition contains, turn it into a trial or bounded entry, or end it for new users. Write down the decision instead of promising to tighten it later.
  • Stop new free signups. Close the free path for new accounts and point them to the paid plan or a trial, so the signup page no longer creates a migration problem.

Do not quietly change the free tier and call it a trial. Existing users who see a new limit without a path will read a pricing decision as a trust problem. The migration email needs a timeline, a reason, and an exit.

Moving existing users to paid is a trust test

Existing users are the people you have already hand-held. They deserve a clear timeline, a fair price, and a usable export. Keeping them on a limited free plan means you keep paying the support cost forever. Moving them to paid requires a move that is easy to understand.

Copy the shape: a paid plan, no cost for the window, and a clear end date. The window gives users time to decide without a surprise charge, and it gives you a date to check whether they stay.

Notenz's Guardian plan costs EUR 3.99 per month or EUR 29.99 per year, equivalent to EUR 2.50 per month when billed annually. Guardian includes file uploads up to 250 MB and a 24-hour recall window. Guardian offers a 30-day money-back guarantee, provided the vault has not already executed. The paid plan must be cheap enough to be a decision, useful enough to keep, and safe enough to try.

A clean export path keeps trust

Before you announce the change, build the export path. Done means a button that produces a file the user can open, not a support ticket. A user who can leave with their data will read the paid offer as fair.

Make the export format useful. A plain data file is fine when the product is data. A readable document is better when the product is a note. The export is ready when the user can start again somewhere else without asking you for help.

Do not hide the export behind a support request. When the user has to ask for their data, you have already made the product feel hostile. Put the export button on the account page before you send the migration email.

Advertisement