Records-per-staff is certainly an issue, but in fact the problem is much more severe.
A great deal of the value of the Airtable comes from having multiple sheets in a single base. Put another way, the value comes from the ability to maintain relationships of data.
So those 10 or 100 staff aren't just entering individual items. They are, say, adding project information--ideas, bugs, tasks, managing the next sprint. Every additional bit of information you add to Airtable compounds the problem.
Airtable is the only data management tool I've ever seen that punishes users for storing more data.
A great deal of the value of the Airtable comes from having multiple sheets in a single base. Put another way, the value comes from the ability to maintain relationships of data.
So those 10 or 100 staff aren't just entering individual items. They are, say, adding project information--ideas, bugs, tasks, managing the next sprint. Every additional bit of information you add to Airtable compounds the problem.
Airtable is the only data management tool I've ever seen that punishes users for storing more data.