Airtable is a strong project-management fit when your team’s core problem is organizing connected records and presenting them in useful ways. A marketing team, for example, can link campaigns, assets, owners, approvals and deadlines, then give each role a focused view. If the harder problem is assigning work, managing dependencies and coordinating delivery across teams, compare Airtable with a task-centered platform before committing.
This review covers product, ownership and pricing information checked on October 23, 2026. Airtable’s public prices and sales-led plan terms can change, so confirm the current offer, permissions and contractual requirements before purchase.
The practical question is not whether Airtable has a board or calendar view. It is whether your team’s primary object is a connected record or an assigned unit of work. That distinction affects the schema, permissions, automation design and total cost.
The short answer: Airtable fits record-centered work
Use a primary-object test. If the central object is a request, campaign, vendor, asset or deliverable with structured details and relationships to other records, Airtable is worth evaluating. If the central object is a task moving between owners, deadlines, dependencies and delivery stages, test whether Airtable’s record model supports that execution without excessive design and upkeep.
Airtable can support project workflows, but a view does not by itself prove that the platform meets your needs for dependency planning, workload management or cross-team ownership. Pilot one representative process with the people, permissions and exceptions that will exist after rollout.
Choose the system around the primary object: connected records and custom views point toward Airtable; assigned work and delivery coordination require a task-centered fit test.
What the acquisition has and has not changed
Bending Spoons announced an agreement to acquire Airtable on August 4, 2026, and completed the acquisition on September 4, 2026. The completion notice says Bending Spoons acquired all issued and outstanding Airtable shares. Airtable is therefore no longer independently owned.
The transaction announcement reported an enterprise value of $1.285 billion and approximately $480 million in annual recurring revenue as of June 2026, growing more than 20% year over year. Those figures were supplied by Bending Spoons in the announcement and are not independently audited operating metrics. See the acquisition announcement and completion notice.
Airtable’s October 12 update described a leaner team, named Alessandro Savarese as product lead, and stated priorities involving the core product, enterprise security, reliability and AI. That confirms staffing and leadership changes, not a guaranteed customer-facing roadmap. The reviewed official sources do not show a replacement public Airtable pricing schedule tied to the acquisition. Check Airtable’s current pricing page rather than treating predictions about future licensing or product terms as facts.
For a renewal or migration decision, record your current plan, renewal date, critical integrations and export requirements. Then reassess against published terms and a tested workflow.
How Airtable works in practice
An Airtable base contains tables. A table holds records, similar to rows, and fields, similar to columns. A record might represent one supplier request, with fields for a request ID, status, owner, source and due date. Linked records connect entities such as requests and suppliers without copying every supplier detail into each request.
Views present the same underlying table in different formats. Airtable documents grid, form, calendar, gallery, Kanban, timeline, list and Gantt views, although availability and capabilities can vary by plan. A team might use a grid for intake review, Kanban for status and a calendar for deadlines. The Airtable views guide explains the documented behavior.
Interface Designer presents selected base data in layouts such as dashboards and record-review screens. Publishing and sharing settings matter. An interface is not automatically a substitute for base permissions or row-level security, and interface-only access can require verified Airtable accounts and a paid plan. The Interface Designer guide covers the access model. Verify the exact plan and account requirements for the people who will use the interface.
Omni, Airtable AI, Field Agents and MCP should not be treated as one interchangeable feature. Airtable markets Field Agents for work such as document analysis, web search and structured field tasks. Airtable’s MCP documentation says the connected agent inherits the user’s permissions and that automations created through MCP arrive paused for review. These are vendor-described capabilities, so validate generated work and inspect proposed configuration before it affects live records. See the Field Agents overview and MCP documentation.
Before building, name the entity represented by each table and identify the authoritative fields. Give an independent lifecycle its own record type. Requests, AI runs and citations should not be combined in one overloaded row when a request can have several runs or several sources.
Choose the row grain before choosing fields. Use one request record for the request, one run record for each AI execution, and one citation record for each source. This prevents later runs or citations from overwriting one another and makes review history measurable.
Airtable pricing: compare the billable workflow
As of October 23, 2026, Airtable’s public pricing lists Free at no cost, Team at $20 per collaborator per month when billed annually or $24 monthly, Business at $45 per user per month when billed annually, and Enterprise Scale at custom pricing. Confirm the current figures and terms before buying, especially for sales-led plans.
| Plan | Public price | Selected documented limits |
|---|---|---|
| Free | No cost | 1,000 records per base; 500 AI credits per editor or higher per month |
| Team | $20 annually billed; $24 monthly | 50,000 records per base; 100,000 API calls per workspace per month |
| Business | $45 per user monthly, billed annually | Self-serve plan includes 125,000 records per base |
| Enterprise Scale | Custom | Confirm record, API and enterprise controls in the contract |
Airtable says Team and Business do not charge for read-only collaborators, form submissions and share links. Do not extend that statement to every plan or access arrangement. Count people who need edit access, then verify whether the selected base, view or interface permissions are available on the selected plan.
AI credits are pooled at workspace or organization level, and usage varies with the task, input, model and output. Credits expire at the end of the applicable period. Team includes 15,000 AI credits per billable collaborator per month, while self-serve Business includes 20,000 per paid user and Enterprise Scale lists 25,000 per paid user at list price in the plan documentation. Pooling means these figures should not be treated as isolated personal allowances.
Estimate billable editors, required permissions, record growth, API volume and likely AI use together. A short pilot using representative activity is more useful than multiplying the headline seat price alone. The plan overview and AI billing guide document additional details.
Design a workflow before you automate it
Consider a hypothetical supplier-onboarding request. The system of record is an Airtable Requests table with one row per submitted request. A stable request ID distinguishes the request from later AI runs or source citations. A process owner handles exceptions, and an authorized reviewer approves consequential write-back.
Required fields, allowed labels, duplicate checks and status transitions should be deterministic. AI can suggest a category or summarize unstructured text, but it should not decide whether a request is authorized or whether an external record may be changed. The following is an illustrative output contract, not an Airtable feature or template:
{
"category": "Procurement",
"summary": "Review supplier onboarding documents before the meeting.",
"confidence_band": "high",
"source_url": "https://example.invalid/request/418",
"review_status": "NEEDS_REVIEW"
}The request record can hold the current proposed result and fields such as validation_status, reviewed_by, reviewed_at and writeback_status. If the workflow needs a history of multiple AI runs, create a separate run record with its own run_id, input reference and agent or model version. If a run produces multiple citations, create one citation record per source and link it to the run.
request_id. Define the owner, required source fields and duplicate rule before adding AI.NEEDS_REVIEW.A practical state sequence is NEW to AI_PROCESSED, then either NEEDS_REVIEW or APPROVED, followed by WRITTEN_BACK. Add VALIDATION_FAILED, RETRY_PENDING and PERMANENT_ERROR routes so failures remain visible.
For status changes and notifications, use explicit rules. Check required fields, permitted transitions and whether an action key or processed timestamp already exists. Airtable documents trigger-and-action automations, but its overview does not establish exactly-once execution or transactional writes across systems. Keep failures visible in a field and assign an owner to stale or failed actions. See Airtable’s automation overview.
API and automation limits that affect operations
Airtable’s Web API returns up to 100 records per page. Larger reads require following the returned offset. Airtable documents a limit of five requests per second per base and 50 requests per second for traffic using a personal access token. Free has a 1,000-call monthly workspace quota, Team has 100,000, and the support documentation lists no monthly call cap for Business and Enterprise Scale. Rate limits and other constraints still apply.
For a read sync, persist the current offset or completed-page state so a job can resume, continue while an offset is returned, and back off after HTTP 429 responses. Airtable documents batching, caching and performUpsert as mechanisms to investigate for writes. Verify that the chosen API operation or connector exposes the required upsert behavior and matching fields. The Web API guide and API limits guide provide the documented details.
A lookup-then-create sequence is not safe as the only concurrent deduplication mechanism. Two workers can check at the same time and both find no record. Use a stable key such as source_system + source_event_id, then enforce uniqueness in the originating or intermediary database. Where direct Airtable writes are appropriate, verify and use a transactional upsert capability where supported. Log the key, outcome, retry state and error code for every attempted write.
For a citation row, a suitable illustrative key is run_id + normalized_source_url + citation_index, or a content hash when citation order is unstable. For a run row, use the request or event ID together with a run ID or model version and timestamp. Do not use only an entity and date when several runs or sources can occur on that date. If implementation support is useful, Zapier automation services may be relevant, but confirm the selected connector’s authentication, pagination, error handling and upsert support before promising a build.
Airtable versus ClickUp: choose by operating model
This is a decision framework, not an objective ranking. Airtable’s documented model centers on connected data, views, interfaces and app building. ClickUp’s public product positioning centers on tasks, project work and collaboration. Compare the actual process your team must run rather than assuming a category label settles the choice.
| Decision point | Airtable | ClickUp |
|---|---|---|
| Primary object | Connected records such as requests, assets or vendors | Tasks and project work |
| Pilot focus | Schema, linked data, views, interface access and reporting | Ownership, dependencies, workload, collaboration and reporting |
| Public core pricing | Team $20 annually billed or $24 monthly; Business $45 annually billed | Unlimited $7 annually billed or $10 monthly; Business $12 annually billed or $19 monthly |
ClickUp’s pricing page lists Free Forever, Unlimited, Business and Enterprise, with AI offerings presented separately. Normalize seats, required features and AI costs before comparing totals. ClickUp’s Table View page describes its own spreadsheet-style task view, but it is not an independent benchmark against Airtable.
Pilot one representative workflow from intake to completion in both systems. Count the steps needed to assign work, manage dependencies, expose records safely, report status and handle exceptions. Teams assessing a task-centered operating model can also review ClickUp consulting.
Security, compliance and final selection
Airtable lists SOC 2 Type 2 and ISO/IEC 27001:2022 among its security materials. Procurement should confirm report scope, dates, covered services and contractual controls rather than treating a certification listing as proof that every configuration meets your obligations. See Airtable’s trust and security materials.
For HIPAA use, Airtable’s documentation specifies Enterprise Scale, a Health Information Exhibit and a business associate agreement, alongside required safeguards. A plan name alone does not make a workspace compliant. Map sensitive fields to user roles and review every integration or AI service that receives the data. Airtable’s HIPAA guidance describes the conditions.
- Define the primary object and complete one representative workflow from intake through completion.
- Count billable editors and verify the required base, view or interface access on the selected plan.
- Estimate record growth, API calls, pooled AI-credit use and expected 429 handling with realistic activity.
- Map sensitive fields to user roles and confirm contractual safeguards for regulated data.
- Test pagination, deduplication, exception handling and integration permissions with representative accounts.
Choose Airtable when connected records and custom operational interfaces are the hard problem. Keep evaluating task-centered platforms when execution structure, dependencies and cross-team delivery are the hard problem.
Frequently asked questions
Is Airtable still independent after the Bending Spoons acquisition?
No. Bending Spoons completed the acquisition on September 4, 2026.
Did Airtable publish new prices because of the acquisition?
The reviewed official sources do not show a replacement public pricing schedule tied to the acquisition. Check Airtable’s current pricing page before purchase or renewal.
How many records can Airtable’s API return?
Up to 100 records per page. Follow the returned offset to retrieve additional pages.
Can Airtable replace project-management software?
It can support project workflows. Whether it is a good replacement depends on whether the central need is connected record modeling or task execution, ownership and dependencies.
Is Airtable HIPAA-ready on every plan?
No. Airtable’s documentation specifies Enterprise Scale conditions, a BAA and related safeguards for HIPAA support.