Airtable consultant and developer in Toronto
We do not just configure Airtable, we run it in production. Fourteen live bases carry a roughly 200-employee operator across 16 departments, every working day.
Where Airtable is the right answer
It is excellent for operations that change shape as you learn. It is the wrong answer for high-volume transactional work, and we will say so rather than sell you a build.
Past the point most consultants stop
Permissions, client-facing portals, automations, scheduled agents, and the migration off the tools it replaces. Those are the parts that decide whether a base survives contact with a real team.
What running fourteen production bases taught us
- Schema first. A base that grew by adding fields becomes unworkable at exactly the moment it matters, and fixing it later means moving live data.
- Permissions are a design problem, not a settings screen. Deciding who can see what shapes how the tables have to be split.
- Every automation needs an agreed exception path. The happy path is the easy half.
- Interfaces are the product for everyone who is not technical. If your team lives in the grid view, the build is not finished.
- The migration off the old tools is most of the work, and the part most quotes leave out.
Where Airtable stops being the answer
High-volume transactional work, anything needing hard row-level guarantees, and reporting over millions of records. When we hit that line we say so and build the piece properly elsewhere, with Airtable staying where it is genuinely strong. A consultant who says it fits everything is selling, not advising.