Thank you for letting us know that pricing changes are in the plans.
I think that Scripting is hugely powerful and I would like to see a model where limited access to scripting remains free, but full access to scripting becomes a paid feature.
It is extremely difficult for users without experience with scripting to understand the value of scripting without experiencing it first hand themselves. I also find that Airtable scripting is an amazing platform for the code curious to develop coding skills.
Running scripting automations is a paid feature. In a free workspace, I cannot create a scripting automation. If I move a base with a scripting automation into a free workspace, I can edit the script, but I cannot test or run it–I get an error. I suggest a model where creators in all bases could create and test scripting automations, but not turn them on. If a base is duplicated or moved into a free workspace, any scripting automations would be turned off. Zapier has a similar model where a free account can test multi-step zaps but cannot turn them on. This lets users see the value of a scripting automation with their specific base before having to pay for it.
Scripting app would be a bit trickier to keep it both free and paid. One option would be …
- if a free base does not have any instances of Scripting app, allow a creator to install a single instance of Scripting app
- if a free base already has any instances of Scripting app, do not allow new installations and do not allow duplicating existing instances, but let existing instances run.
This would allow existing free bases with scripting to continue to function after the deadline (and avoid suddenly having a bunch of upset users whose scripts stop working). It would also allow users to try out scripting with their bases and recognize the value before upgrading. Students could also continue to develop their coding skills for free, which they will then bring to their future employers. Plus, I find that once users have one script, they often find other situations where additional scripts would be very useful.
There would be the opportunity for abuse by duplicating bases or moving bases between free and paid workspaces. However, I find that using these methods often introduces more headaches than they are worth.
(I actually like this idea of limiting the number of instances of apps per base as a pricing model. For example, free bases could have only one instance of one app per base. This lets users try out every single app before deciding that it would would be worthwhile to pay to not have to constantly delete, install, and configure a new app whenever they want to switch out apps. The two week pro trial is barely long enough for new users to learn how Airtable works, much less experiment with apps.)