ZAM

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.

Fourteen Airtable bases, one operation

  • Sales Hub (Sales & CRM)
  • CRM: Post-Sales Customer Success (Customer Service)
  • Apacible Sales & Inventory (Warehouse & Inventory)
  • Tarlac Sales & Inventory (Warehouse & Inventory)
  • Cebu Sales & Inventory (Warehouse & Inventory)
  • JMR Logistics (Operations & Dispatch)
  • JMR SMO (Service & Callouts)
  • JMR HRIS (HR, Payroll & Timekeeping)
  • JMR Finance App (Finance)
  • JMR Finance & Accounting (Accounting & Ledger)
  • JMR Asset Management (Assets & Fleet)
  • JMR Digital Asset (Assets & Fleet)
  • JMR Guards (Security & Access)
  • JMR PCO (Environmental Compliance)

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.

Command-centre dashboard of an operations portal built on Airtable for a 200-employee logistics company, with quick links, performance targets and a daily bonus tracker
The start-of-day screen, reading live from the Airtable bases. Sensitive figures blurred.
Multi-warehouse inventory screen built on Airtable, showing sold, received and transfer records broken down by warehouse
Stock, gate passes and transfers across three warehouses, one Airtable base per site.

Go deeper

Frequently asked questions

What does an Airtable consultant do?
Designs the base so it holds up as the team grows: the schema, permissions, interfaces, automations, client-facing portals, and the migration off the tools it replaces. Configuring a few tables is the easy part. The rest decides whether a base survives contact with a real team.
How much Airtable experience does ZAM have?
We run it in production. Fourteen live bases carry a roughly 200-employee operator across 16 departments, every working day, so the advice comes from bases that have to keep working rather than demos.
When is Airtable the wrong choice?
High-volume transactional work, anything that needs hard row-level guarantees, and reporting over millions of records. When a build hits that line we say so and build that piece properly elsewhere, with Airtable staying where it is genuinely strong.
Can staff or clients use Airtable without seeing everything?
Yes. Permissions and interfaces are designed up front, so each person sees only their part, and clients can work through a portal instead of the base itself. Deciding who sees what also shapes how the tables are split, which is why it is a design decision, not a settings screen.
Can you move our data into Airtable from the tools we use now?
Yes, and it is usually most of the work: the part most quotes leave out. We carry the records, their history and their attachments across, then run old and new side by side until the numbers agree before anything is switched off.
Do you only work with Toronto businesses?
No. We are based in Toronto and serve the GTA, and the work is remote, so we build Airtable systems for businesses across Canada and the United States as well.