Airtable for UX: research and operations

What it is and what it is not

Airtable is a database that looks like a spreadsheet. Each table has typed fields (text, single select, attachments, links to other records), and tables can be linked to each other. On top of that data you can build views: grid, gallery, Kanban, calendar or forms.

It is not a research tool on its own. It does not record sessions, analyze transcripts or recruit participants. It is where you keep what research produces, so the team can query and reuse it.

Why does it matter to a designer?

Because research loses value when findings stay in slides or in folders nobody opens. A well-built base lets you ask questions like “what did users say about checkout over the last six months?” and get an answer in minutes.

It also supports operations: design requests, project status, screen or content inventories. When the same team keeps several different spreadsheets for each of these, Airtable helps bring them together.

How do you use it for research?

Fresh Consulting (2020) describes a system with a single base that gathers observations from user testing, grouped by theme. Each insight is tagged with the session that surfaced it, and participant data is stored too so you can see high-level patterns or drill into each profile. Each snippet (a quote, an audio clip, a video) is linked to a business goal, a persona, a product feature or a design action item. Status tags remove outdated insights from the active views while keeping them searchable for historical reference. According to the article, the team measured that compiling everything took less than 10 extra hours.

A minimal schema to start with:

The most useful views are a gallery filtered by tag, a Kanban of findings by status and a grid sorted by severity. To turn findings into a summary, research synthesis is still the step that matters. And if the problem is information rather than interaction, the results of testing can feed a content inventory and audit.

What does Interface Designer offer?

Airtable has a feature called Interface Designer, which lets you build interfaces on top of existing tables. According to its official guide, interfaces are “built on top of the existing tables” in your data layer: you choose a layout and then a table. Typical use cases are approving creative assets, updating project status or showing metrics to leadership.

For research it is useful for showing findings to stakeholders on a simple screen, without giving them the whole base. Airtable’s support documentation says Interface Designer is available on all plans, with caveats: sharing an interface separately from the base is restricted to paid workspaces, and on the Free plan only base collaborators can see interfaces. Record editing is also off by default for each element, and base-level permissions (fields and tables) override interface settings. Review what each person can do before sharing a dashboard.

What plans and pricing does it have?

Airtable’s official pricing page (consulted on November 5, 2026) shows four tiers:

• Free: available at no cost.
• Team: $20 per user per month, billed annually.
• Business: $45 per user per month, billed annually.
• Enterprise Scale: custom pricing, through sales.

On paid plans only users with edit permission on at least one base count as seats. Read-only collaborators, people who submit forms and people who view shared links are not charged. The page only gives annual-billing prices. Per-base limits, according to Airtable’s plans support page, are: Free, 1,000 records and 1 GB of attachments; Team, 50,000 records and 20 GB; Business, 125,000 records and 100 GB. Enterprise Scale is handled through sales. Record limits are cumulative across all tables in the base. Figures change often, so confirm them on the official page before you decide.

When should you NOT use it?

• When the data is very large or very interrelated. Airtable has record limits per base depending on the plan (1,000 on Free) and does not replace a production database.
• When your team already lives in Notion and the research is light. Maintaining two tools for the same job wears people down.
• When the information is sensitive and your company’s policy does not allow user data outside its own systems. Before uploading transcripts or personal data, check your organization’s rules.
• When you only need a list. A simple spreadsheet costs less and is understood in five minutes.

If your need is the team conversation about the product, Notion for UX may be more natural. If you want a research repository with tagging and search across findings, also look at Dovetail and Condens.

Example

Illustrative example: a product team at a fintech runs twelve interviews about opening accounts. Each interview is logged in the sessions table, linked to its participant. Findings are created in a third table with tags such as “documents”, “verification” or “trust”. Before the monthly review, the Kanban view grouped by tag shows that nine of the twelve participants mentioned identity verification. The team prepares a list of decisions with owners and dates. Each decision is linked to the findings that justify it.

For tomorrow: create a base with two tables (sessions and findings), link one to the other and log three observations from your last study. If you can then filter by tag, you have a minimal repository.

Common mistakes

• Creating too many tables before having a clear flow. Start with two.
• Not linking records, and repeating the participant’s name in every row.
• Free-text tags with no controlled list: “usability”, “Usability” and “usab.” become three categories.
• Storing personal data without checking your company’s privacy policy.
• Using it as a dead archive: if nobody queries the base, it is useless.
• Trusting third-party prices without checking the official page.

Sources

• Airtable Pricing, official page
• Airtable plans and pricing, Airtable support (limits per plan)
• Getting started with Airtable Interface Designer, Airtable documentation
• Interface Designer: Your guide to designing an interface, Airtable
• Creating a UX Research System with Airtable, Fresh Consulting (Aravind Ravi, August 5, 2020)