The observation is accurate, and the assumption doing the most work here is that "unlimited" is a storage claim when it is almost always a display and retrieval claim. Most platforms that quote unlimited contacts cap something adjacent: API call limits per day, activity log retention windows (90 days visible, archived after, gone after two years in some tiers), or the number of automations that can fire against a single contact record. The per-object record count is almost never the headline stat, and it is the one that compounds fastest in a relationship-heavy pipeline.
The eighteen-month seller lead is the right stress test. That contact is not a lead, it is a relationship file, and the CRM has to function as a longitudinal record, not a pipeline card. Where I see systems break is not at the contact count but at the automation trigger depth. When a contact has 200 activities logged, some platforms deprioritize that record in workflow queues because the activity table query slows. The UI still shows the contact. The automation just stops firing on time. That failure is invisible until you audit trigger timestamps against intended send times.
The other thing worth checking is what "attached files" actually means in the plan tier. Many platforms count file storage separately from the contact limit. A dozen attached docs per record across a working pipeline adds up faster than the sales rep's math suggests. Ask for the storage cap in gigabytes, not the contact cap in rows.
For anyone building or evaluating these systems professionally, the Guide tab on the CRM setup strategy page covers the platform evaluation framework in more depth, including the questions worth running through on a vendor call before you see a contract.
What platform are you building on, and are your automations triggering off activity count, elapsed time, or stage change? That detail changes which limit is most likely to surface first.
