The short version
Free plans are useful as staging grounds, not long-term production platforms. Which limit trips you depends on the type of work you do: messaging teams run into history retention, design and commenting tools block editable files, databases die on record counts or attachment space, and marketing platforms cap contacts and sends. Below I list the practical ceilings you will meet first for the most common free-tier choices and point to vendor documentation for details.
How to read this: what I mean by "you'll hit first"
"Hit first" means the feature or resource that becomes the practical blocker for normal team activity (not the fanciest paid feature). These are the constraints that force one of three reactions: pay, work around the limit (export, archive, invite fewer people), or move tools.
Messaging: Slack — message history and data deletion
The free Slack workspace hides older messages and files to make room for new ones; the historic short limit is 90 days of searchable history and Slack has warned that in free workspaces customer data older than one year may be deleted on a rolling basis. For teams that treat Slack as a searchable knowledge base or that onboard people by searching past channels, the absence of long message history is the first, and most painful, limit you’ll hit. See Slack’s usage and free-workspace pages for the official wording. slack.com
Design & collaboration: Figma — editable files and editor seats
Figma’s free tier lets you invite unlimited viewers (people who can comment, inspect or export) but restricts editable files. The company explicitly limits co-editing to a small number of files on the free plan (the pricing FAQ gives the usable co-edit files limit and related multiplayer behaviour details). For teams that collaborate live on many active files, you’ll usually hit the editable-file ceiling before you hit a storage issue. Vendor pricing and FAQ pages describe these limits and the viewer/editor distinctions. figma.com
Notes and documentation: Notion — automations, attachments and guest behaviour
Notion’s free offering is generous for individuals: many long-running users report the free tier supports extensive use. However, there are clear practical ceilings around file uploads and some automation capabilities; the pricing/docs pages list the current feature breakdown and upload limits (per-file upload size is constrained on the free plan). If your workflow depends on automated database actions or heavy attachment use, those are the first limits you’ll notice. Check Notion’s pricing and help pages for the precise, current restrictions. notion.com
Project boards: Trello — attachment size and per-file limits
Trello’s free plan places the practical storage constraint at attachment size: each file you attach is limited (10MB per attachment on the free tier). There is no hard total storage cap listed the same way some vendors publish, but the per-file ceiling forces a different workflow — link to cloud storage rather than attach high-resolution assets directly. For teams exchanging many visual assets, that per-file limit becomes the friction point. See Trello/Atlassian documentation for the exact per-attachment limit. support.atlassian.com
Databases: Airtable — records per base and attachment space
Airtable’s free plan documents a clear record cap: 1,000 records per base and 1GB of attachment space per base. If your team uses bases as anything more than short-term trackers (for CRM-lite, product backlogs, or content repositories), that 1,000-record ceiling is usually the limiting factor; once you reach it you must either split data into multiple bases (which breaks views and automations) or upgrade. Airtable’s plans and support pages state these limits directly. support.airtable.com
Design assets: Canva — cloud storage
Canva’s free tier is functionally useful for single creators and very small teams, but it caps cloud storage (Canva and many public handouts list a 5GB free-storage figure). For teams building many large templates, video exports or heavy brand kits, storage — not the editor feature set — is the practical ceiling. Vendor pages outline current free-storage allowances. michigan.gov
Project & work management: ClickUp — workspace storage and structure limits
ClickUp’s Free Forever plan advertises unlimited tasks and members but places explicit limits on attachment storage (60MB workspace storage on the free plan) and on certain structural elements (a limited number of Spaces, lists and folders). The common user experience: you can create many tasks, but you quickly run out of attachment space and cannot centralise lots of file-heavy work in one free workspace. ClickUp’s help centre and pricing pages list these caps. help.clickup.com
Marketing: Mailchimp — contacts and monthly sends
Mailchimp’s free Marketing plan limits the number of contacts and the number of sends per month. As of vendor pricing statements in 2026, the Free plan includes up to 250 contacts and 500 sends per month with a daily send limit; if your use case is periodic newsletters to a modest list you may be fine, but almost any growing audience will force you to pay. Mailchimp’s pricing and help pages explain how sends and contact counts are calculated. mailchimp.com
Work OS: monday.com — board and item limits on free plans
monday.com’s free plan is useful for small teams and basic boards but enforces limits on active items, boards and advanced features. The vendor’s help and pricing pages explain referral-based item increases (you can add extra items by inviting users) and show the feature matrix between free and paid plans. In practice the first friction is the number of boards or items you need to manage centralised workflows. support.monday.com
Practical rules of thumb
- Messaging and knowledge: if your team depends on searchable history and onboarding by search, free Slack is temporary — history retention is the likely blocker. slack.com
- Live collaboration: free Figma is great for showing work to many viewers; if multiple active editable files are core to your process, you’ll need paid editors. figma.com
- Databases and CRMs: check record and attachment caps — Airtable’s 1,000-record and 1GB per-base limits are the most common surprise. support.airtable.com
- Attachments and media-heavy work: per-file attachment limits (Trello) or tiny workspace storage (ClickUp) force external linking sooner than you expect. support.atlassian.com
- Marketing: free tiers are fragile because contact and send caps are hard limits that directly block campaigns. Mailchimp’s free-contact/send numbers are clear gatekeepers. mailchimp.com
Workarounds that often work (and their costs)
- Archive and export: export history or data regularly and store it elsewhere — cheap, but destroys searchability and increases friction.
- Split projects: create multiple smaller bases/files/workspaces. This avoids upgrades but fragments workflows and breaks cross-project reporting.
- Use hybrid tooling: combine a free visual tool for presentation with a paid backend for storage or mailing lists. This keeps costs down but adds complexity.
How our catalogue ties in
Our catalogue lists the products covered and their entry prices where we hold them — for example, Slack, Figma, Notion, Trello, Airtable, ClickUp, Canva, Mailchimp, and monday.com. Those entry prices are a guide to expected paid cost when the free tier stops being viable: for small, seat-based teams the entry monthly figures in our catalogue indicate the likely jump in monthly cost once you need the paid feature set.
Decision guide: when to upgrade
- Upgrade Slack when message search becomes necessary for onboarding or customer history beyond the 90‑day window. slack.com
- Upgrade Figma when you regularly need more editable files or paid seat features like advanced versioning.
- Upgrade Airtable or move data when a single base approaches 1,000 records or 1GB of attachments. support.airtable.com
- Move Mailchimp or upgrade when your contact list or required sends exceed the vendor’s free-contact/send limits. mailchimp.com
Final word
Free tiers let you evaluate and minimise cost early, but they are engineered to prompt either operational workarounds or upgrades. Look at the single resource a vendor caps (history, records, storage, sends) and ask whether you can live with an external archive or a fractured workflow. If the answer is no, budget for the vendor’s entry paid tier — our catalogue lists those entry prices where we hold them to help with that calculation.