
I use Airtable as the backbone for several operational and sustainability systems across multiple international sites within a regulated life sciences environment.
What started as structured inventory control has evolved into linked systems covering procurement governance, supplier mapping, waste consolidation and Scope 1–3 emissions tracking. The ability to build relational, auditable data structures without heavy IT involvement has been a major advantage.
Airtable gives me database-level capability while remaining flexible enough to adapt as reporting expectations evolve. I can design systems around how the organisation actually operates rather than forcing processes into rigid software templates. Review collected by and hosted on G2.com.
I genuinely have very few issues with Airtable, but as bases grow and datasets become larger, performance can slow slightly if they are not structured well. In my experience, this is largely mitigated through thoughtful architecture, clean relationships and good data organisation, but it does require some planning as systems scale.
One area I would like to see improved is how AI fields handle incomplete inputs. When an AI field depends on multiple other fields, it can stop generating output if some of those fields are blank. It would be useful if the AI could instead produce a partial output and clearly state which information is missing, rather than failing entirely. That would make AI-driven workflows more resilient in real-world use where data is not always perfectly complete. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.






