Workload view is brilliant
Rolling up hours per person against capacity finally showed us who was overloaded.
Browse
Turn messy spreadsheets into a linked Airtable base with views, formulas, interfaces and automations that run your team's daily operations
Created by Marta Kowalska
Many teams run their operations on spreadsheets that grew without a plan: a tab for clients, a tab for projects, names typed differently in every row and nobody sure which version is current. Airtable gives you the familiarity of a spreadsheet with the structure of a database, plus views, interfaces and automations on top.
You will build an operations base for a small creative agency, covering clients, projects, tasks, team members and invoices. By the end, it will replace four separate spreadsheets and a lot of manual follow up.
Operations managers, project coordinators, office managers, freelancers and small business owners who manage work in spreadsheets today. No database or coding experience is required. We start with the ideas behind good data structure, then build everything step by step.
The free Airtable plan is enough for most of the course. Some features, such as certain automation limits, interface permissions and larger record counts, depend on your plan, and I point these out as we go. Airtable updates its interface regularly, so some buttons may have moved slightly since recording.
Automation consultant teaching Zapier, Make, n8n and Airtable for real operations work
I help small teams remove repetitive work. In practice that means mapping how a process really runs, finding the copy and paste steps, and replacing them with automations and simple internal tools built in Zapier, Make, n8n and Airtable.
I teach automation as a craft with rules: start from the process, not the tool, design for failures, log what happens and document each flow so someone else can maintain it. I also cover the less glamorous topics such as API keys, webhooks, rate limits and data privacy.
Each course is built around workflows I have set up many times, like lead routing, invoice handling and onboarding checklists, so you can adapt them straight away.
Rolling up hours per person against capacity finally showed us who was overloaded.
Our agency now runs on one base. Linked records alone stopped the endless client name typos.
Our designers only see their tasks now, and the dashboard shows workload clearly.
I had never thought about data structure. The one table per kind of thing rule made everything click.
Formula errors used to scare me. The traffic light status example is now in three of our bases.
Some buttons have moved since recording, but the concepts are solid and easy to follow.
Recurring tasks and notifications saved our coordinator a lot of reminders each week.