A four-session live intensive for the person responsible for an Airtable system other people depend on.
Learn how to govern, maintain, improve, validate, document, and eventually hand over your system while building the operating Playbook for your actual base.
Join the Founding CohortFour weekly live sessions and applied work against the Airtable system you already operate.
At some point, the base you built stopped being a useful tool and became something people depended on.
Somewhere along the way, you became responsible for an operational system, often without anyone defining what responsible ownership actually looks like.
The Airtable Champion Intensive is designed for that moment.
A healthy Airtable system shouldn't depend on one person remembering how everything works.
During the Intensive, you'll take what currently lives in your head and make it explicit: how the system works, who owns what, how changes get made, what needs monitoring, how requests are handled, and what another person would need to know.
Map the purpose of your system, the workflows it supports, its users, dependencies, ownership boundaries, and the operational responsibilities that come with being its Champion.
Define how your system should be maintained, monitored, governed, and documented instead of relying on memory and reacting when something goes wrong.
Learn to observe before diagnosing, understand what someone is actually trying to accomplish, evaluate the implications of a request, and validate changes before releasing them.
Document enough context, decisions, routines, and ownership that another knowledgeable person could step in without reconstructing the entire system from scratch.
Throughout the Intensive, you'll build your Champion Playbook against your own Airtable environment.
It becomes the durable operating record for the system you manage: what it exists to do, how its critical workflows operate, who owns what, how changes should be handled, how the system is monitored and validated, and what someone else needs to know to operate it responsibly.
This isn't homework created to prove you completed a course.
It's documentation your organization can actually keep using after the Intensive ends.
It also gives you a framework for making decisions the next time the system changes.
An Airtable base can function perfectly today and still carry substantial operational dependency.
If critical knowledge lives primarily with one person, routine changes depend on that person's judgment, requests arrive without a consistent process, or system health is discovered through user complaints, the organization hasn't fully operationalized what it built.
No fictional company. No sample base you abandon when the course ends.
You bring an Airtable system you currently own or help operate. Each session, you'll learn an operating principle and immediately apply it to that environment.
Learn the thinking behind ownership, governance, change, validation, monitoring, documentation, and continuity.
Identify where the principle shows up in the system you already manage.
Determine how your organization should handle ownership, requests, changes, responsibilities, and exceptions.
Capture what you've decided in your Champion Playbook so the knowledge no longer depends on memory.
Use the live sessions to test your thinking against real workflows, edge cases, and questions from your environment.
The live sessions are designed for the questions that aren't answered by a help article.
You won't just have consumed training.
Built around the Airtable system you actually own and operate.
Documented purpose, workflows, users, ownership, dependencies, and responsibilities.
A framework for evaluating requests and validating changes before they are released.
Documentation and routines designed to support continuity and eventual handover.
The title on your org chart doesn't need to say "Airtable Champion."
Building the system is only part of implementation.
Someone inside the organization ultimately needs enough context and operating discipline to steward it.
They need to understand what the system supports, evaluate requests, coordinate changes, recognize when something needs attention, maintain institutional knowledge, and know when outside expertise is actually required.
The Airtable Champion Intensive gives that person a structured operating framework while they document the system they're already responsible for.
You're developing internal capability around a system your organization already depends on.
The result is clearer ownership, stronger operating practices, better documentation, more disciplined change, and less dependence on undocumented knowledge held by one person.
Sponsor a ChampionMost people don't deliberately become the Airtable person.
They build something useful. More people start using it. More workflows move into it. Eventually, they're responsible for a system the business relies on without ever having been taught how to operate one.
I've seen the consequences of that repeatedly in Airtable consulting.
The build itself is rarely the whole challenge.
The harder questions come afterward. Who owns this? Who can change it? How should requests be evaluated? How do we know a change actually works? What should be monitored? What needs to be documented? What happens when the person who understands all of this leaves?
I built the Airtable Champion Intensive to give internal system owners a framework for answering those questions and a place to document the answers.
Starts October 14, 2026
The founding cohort meets live once a week for four sessions.
Live session dates:
October 14
October 21
October 28
November 4
Recordings are available if you need to miss a session.
Work between sessions is applied directly to the Airtable environment you already manage.
You should currently own, administer, or play a meaningful role in operating an Airtable system.
You don't need to be an Airtable developer.
You do need a real system to work on.
If you're the person everyone relies on to understand the Airtable system, the role already exists, whether anyone formally named it or not.
Turn that responsibility into an operating practice someone else could understand, follow, and eventually inherit.
Join the Founding Cohort