Why every SaaS is waiting for you to outgrow the free plan
A free plan is the most expensive pricing page a vendor publishes, because it is doing a sales job every other page gets to skip. It hands you a working product, learns exactly how you use it, and waits. When your needs grow past the line, the upgrade is not a decision — it is a rescue.
The line keeps moving
The clearest evidence that free plans are strategic, not generous, is that their limits shrink. Mailchimp's free tier used to cover 500 contacts; at the time we verified it in Mailchimp pricing explained, it covered 250 — with 500 sends a month and a 250-per-day cap. Nothing about the product got cheaper to run. The line moved because enough users were now inside the funnel that the free tier could be tightened without losing the ones who matter: the ones about to need more.
Contrast that with a vendor still fighting for the top of the funnel. Kit's free plan covers 10,000 subscribers with unlimited sends — a genuinely huge allowance, documented in Kit pricing explained. Both companies are rational. Mailchimp already owns distribution; Kit is buying it. A free plan's size tells you where the vendor is in that fight, not how good the product is.
What crossing the line actually looks like
The second thing free plans are engineered around is what happens at the boundary. There are three designs:
- Block. The feature stops working until you upgrade. Annoying, honest, and rare on the limits that generate revenue.
- Silence. The limit is inside a menu you never open, and the first sign is a symptom — sends not arriving, an export missing a field, a second seat unable to edit.
- Bill. The plan keeps working and an invoice appears. Mailchimp's paid plans do exactly this: exceed your contact tier and you are charged for the higher tier automatically — the account keeps sending and the billing quietly steps up. We put that behaviour at the centre of our Mailchimp breakdown because it converts a pricing page into an open-ended commitment.
The third design is the most profitable, and it is why every pricing page you have ever read buries the limit three clicks deep. We catalogued all four ways a limit can hit you in what happens when you hit a free plan's limit.
Why the free plan knows you better than the paid one does
When you use a free plan for six months, the vendor accumulates something a trial never produces: your real shape. How many contacts you actually add per month. Whether you ever touched automations. Whether you invite a second person. The upgrade pitch you eventually see is not a price list — it is a summary of exactly which wall you are closest to. That is why the free-to-paid conversion feels uncannily timed. It is not a coincidence; it is the product doing its job.
How to use a free plan without being used by it
- Find the hard limit before you build on it. Kit's 10,000-subscriber allowance is real, but its free plan excludes automations and sequences — the moment you need a welcome series, you are on the paid ladder. We mapped that boundary in the Kit piece.
- Know the exit before you enter. Everything you upload should be exportable in a format another tool accepts. The platforms that make export awkward are telling you something. Our migration walkthrough for leaving Mailchimp is in moving from Mailchimp to Kit.
- Do the arithmetic on your own growth. If you add 100 contacts a month, a 250-contact free tier is a 10-week lease, not a home. The honest comparison is not "free vs $20" — it is how many months of each. We ran that arithmetic per platform in what a 500-subscriber list costs.
What we cannot verify
The Mailchimp limits cited here were read from Mailchimp's pricing pages on October 23, 2026, and change without notice — the 500-to-250 cut is itself proof. Kit's subscriber allowance and feature exclusions were verified the same day. We have not measured how vendors target upgrade prompts to individual accounts, and no vendor publishes that logic; the account-shape description above is how freemium is generally designed, not a documented claim about any specific vendor's prompts. See How We Test.