What do you like best about Airtable?
What I like best about Airtable is the flexibility to build real business systems without starting from a heavy development process. As a business automation consultant, I use Airtable for many different clients, and it allows me to design databases, connect processes, create interfaces, and automate repetitive work in one platform.
The biggest value for me is that Airtable is both simple enough for business users and powerful enough for complex workflows. I can start with a clear data structure, add relationships between tables, build views for different teams, and then connect automations or external tools when needed. The integrations are very important for my work, because Airtable can become the center of the process and still connect to tools like forms, email, project management platforms, Make, Zapier, n8n and custom APIs.
I also like the Interface Designer very much. It helps me create clean working screens for users, so they do not need to see the full database behind the system. This makes adoption much easier, especially for teams that are moving from spreadsheets or manual processes. In most cases, users understand the system quite quickly, and there is also good documentation and community knowledge that helps with onboarding and support.
From a performance point of view, Airtable is usually stable and responsive for the operational systems I build. Of course, when the solution becomes very complex, it is important to design the base correctly, but with good architecture it works well for many business use cases.
For pricing and ROI, I think the value is strong. It can save a lot of development time and reduce manual work, so for many companies the return is much faster than building a custom system from zero. The AI and intelligence features are also interesting, especially for things like summarizing information, classifying records, and helping teams get insights from their data.
For me, Airtable is not just a database tool. It is a strong foundation for building practical operational systems quickly, while still keeping the solution organized, scalable, and easy to improve over time. Review collected by and hosted on G2.com.
What do you dislike about Airtable?
What I dislike about Airtable is that when a base becomes more complex, it can be harder to manage and maintain over time. Airtable is very flexible, but this also means that if the architecture is not planned well from the beginning, the system can become messy with many views, fields, automations, and dependencies.
Another point is performance. For small and medium solutions Airtable works very well, but in larger bases with many records, linked tables, lookups, rollups, and automations, sometimes the experience can become slower. This is especially important when clients use Airtable as a core operational system and not only as a simple database.
I also think the pricing can become a challenge for some clients. The value is usually strong, but when a company needs many users, advanced permissions, interfaces, automations, or AI features, the total cost can grow quite fast. For smaller businesses, this sometimes makes the decision harder.
In addition, I would like to see more advanced native tools for documentation, change tracking, and automation debugging. As an implementer, it is important for me to understand what changed, why an automation failed, and how different parts of the system are connected.
Overall, I still think Airtable is a very strong platform, but these areas can make complex implementations more challenging and require good planning and governance. Review collected by and hosted on G2.com.