The All-in-One Pitch Is Working
Airtable built its reputation on a simple but powerful idea: give non-technical teams the structure of a relational database without requiring them to write a single line of SQL. For years, that proposition had almost no direct competition. Project managers, operations leads, and product teams paid Airtable’s premium pricing because nothing else did what it did at the same level of polish. That comfort zone is now shrinking fast.
Notion has spent the last two years quietly upgrading its database layer, adding features that were once considered Airtable’s exclusive territory – linked records, rollups, advanced filters, custom properties, and formula fields that actually behave like spreadsheet logic. The updates have not come with splashy announcements. They have come with consistent, incremental releases that Notion’s existing users discovered while already inside the product. That timing matters more than most people realize.
What Notion Actually Added
The gap between Notion’s database capabilities and Airtable’s used to be wide enough that switching was unthinkable for power users. Rollup fields – the ability to pull aggregated data from a linked table – were a core reason teams stayed on Airtable even when they preferred Notion for documentation. Once Notion added rollups and made them reliable, one of the strongest technical arguments for keeping two separate tools collapsed.
Formula support has followed a similar arc. Notion’s early formula system was limited, frustrating, and poorly documented. The upgraded version borrows heavily from the logic structure that spreadsheet-native users already understand. Teams that once used Airtable strictly for its formula capabilities are now finding that Notion covers roughly 80 percent of their actual use cases – and the remaining 20 percent is often edge-case functionality they rarely touched anyway.
Views have also expanded. Notion now supports board, calendar, gallery, list, and table views across its databases, with timeline view added for project tracking. Airtable’s view system is still more configurable at the granular level, but for most mid-market use cases, Notion’s view options are sufficient. The practical question for teams is no longer “does Notion have this feature” but “is Notion’s version good enough for what we actually do.”
The answer, increasingly, is yes. And that shift in the question itself signals a maturing product. Notion is no longer playing catch-up – it is playing a consolidation game, arguing that a team running its work inside one tool has structural advantages over a team running documentation in one place and data in another. That argument is easier to make when the data tool is genuinely functional.
Airtable’s Pricing Problem
Airtable’s pricing has never been quiet about its ambitions. The free tier is functional but constrained, and the jump to paid plans is steep enough that small and mid-size teams regularly debate whether the cost is justified. Notion’s pricing structure, by comparison, is more forgiving at the team level, and for organizations already paying for Notion, absorbing database functionality into an existing subscription feels like a gain rather than a new line item.
This is where the threat becomes structural rather than just competitive. Airtable loses users not because those users went looking for an alternative, but because they already had one sitting in their browser tab. The migration path from Notion-as-docs-tool to Notion-as-database-tool requires no new vendor negotiation, no new IT approval process, and no new learning curve for a team already fluent in the interface. Switching cost, historically Airtable’s strongest retention mechanism, has dropped significantly for this exact population of users.
Who Is Actually Switching
The users moving away from Airtable are not, in most cases, the data-heavy power users running complex automation stacks or deep API integrations. Those teams have built enough on top of Airtable’s infrastructure that the switching cost remains real. The users leaving are the ones who adopted Airtable for straightforward use cases – content calendars, CRM-lite pipelines, product roadmaps, and project trackers – where Notion’s current database feature set is more than adequate.
That segment is not a niche. It is likely the majority of Airtable’s installed base by headcount, even if not by revenue. Startups, creative agencies, solo operators, and small operations teams are exactly the kind of users who gravitate toward all-in-one tools as they grow. They do not want a dedicated database product if their documentation platform can handle it. Airtable’s enterprise customers may be stickier, but the pipeline of new users coming from that startup-and-SMB segment has to be narrowing. This pattern mirrors what Linear has been doing to Jira – capturing the next generation of users before the incumbent realizes the funnel is draining.
Airtable has responded by leaning further into its enterprise positioning, building out automation workflows, richer permission structures, and deeper integrations with tools like Salesforce and Slack. That is a rational strategic move, but it also accepts the premise that the simpler end of the market is harder to defend. Building upmarket while a competitor consolidates the middle is a pattern with a mixed track record in SaaS.
The Consolidation Pressure
The broader dynamic at play is a consolidation of work tools that has been building for several years. Teams that once managed four or five separate apps for different workflows are being pushed – by budget pressure, by tool fatigue, and by improving multi-purpose platforms – toward fewer, more integrated products. Notion’s positioning as a workspace rather than a single-purpose app makes it a direct beneficiary of that pressure. Every capability it adds increases the gravitational pull to stay inside it for more tasks.
Airtable still has genuine advantages in automation depth, API flexibility, and the kind of structured data management that genuinely complex operations require. But the product category it pioneered – accessible databases for business teams – is no longer a moat. It is a feature. And when a feature gets absorbed into a platform your team already lives in, the standalone version of that feature has a much harder argument to make on renewal day.
