What happens when you hit a free plan's limit: the four ways it fails
Every free plan ends somewhere. What almost nobody checks is how it ends — and the difference matters enormously. A tool that blocks an upload is annoying. A tool that silently stops sending your welcome emails is a business problem you discover three weeks late.
The four failure modes
- Hard block. The action fails and you are told. Best case — you find out immediately.
- Soft block with upsell. The action fails, and a pricing modal appears. Annoying, honest, unavoidable.
- Silent degradation. The feature keeps accepting input but stops doing the work. The dangerous one.
- Overage billing. It keeps working and you are charged. Fine, provided you knew the rate.
What we can document on the tools we cover
| Tool | The limit | What the vendor documents |
|---|---|---|
| ClickUp Free | 60 MB total storage | Uploads blocked beyond the cap; some features (custom fields, Gantt, timeline) lock after a trial despite appearing available |
| monday Free / Basic | 250 automation actions per month | Actions are consumed per fire; when exhausted, automations stop running until the period resets or you upgrade |
| Notion Free | 5 MB per file; 7-day page history | Uploads over 5 MB rejected; versions older than 7 days are gone — the second one is discovered only when you need it |
| Kit Free | No automations or sequences | The visual automation builder and sequences are simply not present on the plan — a clean absence rather than a limit you hit |
| systeme.io Free | 2,000 contacts · 3 funnels · 1 automation rule | Counted resources; adding beyond the count requires the next tier |
| Streak Free | No pipelines | Pipelines are the feature the plan withholds entirely — see Streak pricing |
Note what these have in common: the limit is on a resource you consume slowly — storage, contacts, actions, file size. That is by design. A cap on page count would be discovered in an afternoon; a cap on file size is discovered when you upload your first video.
The two limits that cost real money
- Automation quotas. monday's 250 actions on Free and Basic is not a nudge, it is a cliff. A five-person team with three active workflows exhausts it in days. Standard raises it to 25,000 — a 100× jump at $3/seat. If your workflows stop firing and nobody notices, you lose the deals those workflows were tracking.
- Page history. Notion Free keeps 7 days. If someone overwrites a client brief on a Friday and you look for it two weeks later, it is gone. This is the only limit in this article whose failure is permanent.
How to prepare, in fifteen minutes
- Write down the limit in the unit you consume. Not "60 MB" but "about sixty screenshots." Not "250 actions" but "roughly how many status changes per day."
- Test the failure once, deliberately. Upload a file that exceeds the cap, or build one automation that fires repeatedly. Seeing the failure mode on your own terms is worth more than reading about it.
- Put a monitor on the quiet ones. Anything measured monthly — actions, sends, contacts — deserves a calendar reminder at 70% of the allowance. Silent degradation is only silent because nobody set a reminder.
- Keep files outside task tools. The single most common free-tier failure is storage. Link from Drive instead of uploading, and the cap stops mattering.
- Export quarterly. Whatever the limit is, the exit matters more. Open the export file at least once and check that tags, custom fields and notes survived.
The judgement call
Hitting a limit is not automatically a signal to upgrade. Ask what the limit was protecting you from. If you are working around 60 MB of storage with a link convention and it costs you two minutes a week, do not pay for storage — pay for nothing and keep the convention. If you are working around a missing automation by doing it manually every Monday, that is the one to buy your way out of. We wrote the arithmetic for that in Free vs paid: when an upgrade pays for itself.
What we cannot verify
The limits above come from vendor pricing pages and plan-comparison tables, verified October 23, 2026, and we re-check quarterly. The descriptions of how each limit behaves are drawn from vendor documentation and plan design; we have not yet deliberately exhausted every one of them in a live account, so some failure modes are documented rather than observed. Our testing cycle will record actual behaviour per tool, and those observations will replace the descriptions above, per our How We Test process.