Bending Spoons Acquires Airtable: What It Means for Customers

Bending Spoons is buying Airtable for US$1.285bn. What changes for solo users, small teams, mid-market and enterprise customers, and what to do before the deal closes.

The deal has not closed. Airtable and Bending Spoons will operate separately until they receive the required approvals, so customers do not need to act today.

After closing, expect staff and support changes within a few months. Pricing, plan and usage changes are more likely during 2027.

Our view at OpsTwo is that the deal will be good for long term success of Airtable and its customers. The main risk falls on small and mid-market customers.

The deal was cheap

Bending Spoons will pay US$1.285 billion in enterprise value. Airtable’s net cash raises the implied equity value to about US$2.25 billion.

Airtable reported about US$480 million in annual recurring revenue in June 2026, growing by more than 20% a year. The deal therefore values the business at about 2.7 times annual recurring revenue.

More than 500,000 organisations use Airtable, including 80 of the Fortune 100. The official acquisition announcement gives the transaction details.

Bending Spoons bought a growing company at a low revenue multiple. It does not need to double prices or damage the small-business product to earn a return.

Cost cuts could improve profits. Continued growth could do the same.

Public ownership changes the pressure

This is Bending Spoons’ first acquisition since listing on Nasdaq on 1 July 2026.

The listing raised US$1.68 billion and valued the company at about US$18.4 billion. Bending Spoons also carries substantial debt.

Debt payments and quarterly reporting create pressure to cut costs and raise margins.

Public ownership also makes customer losses, poor support and product failures visible to investors. Bending Spoons cannot damage a growing US$480 million subscription business without the effect reaching its results.

The bear case

The worst outcome is clear:

  • Airtable cuts most of its staff.
  • Support becomes weaker.
  • The Free plan loses useful features.
  • Paid plans become much more expensive.
  • AI use becomes costly at scale.

Bending Spoons’ record supports this concern.

After buying Evernote, it moved operations to Europe, cut most US- and Chile-based roles, restricted the Free plan and raised prices.

It announced plans to cut 75% of WeTransfer’s staff within weeks of that acquisition. Vimeo also made large cuts within months of its deal closing.

Airtable customers should expect a reorganisation.

Airtable is different

Airtable is growing by more than 20% a year. It has large enterprise contracts, high switching costs and a direct role in critical business operations.

That changes the incentives.

Weak support could place major contracts at risk. Tight limits could damage the small-team adoption path that feeds larger enterprise accounts.

Bending Spoons has also shown that staff cuts do not always mean slower product work. Evernote shipped major interface, collaboration and AI changes after its acquisition.

Airtable may end up with fewer employees and faster work on fewer priorities.

The likely priorities are AI, administration, security, performance and governance. Airtable has not published a post-acquisition roadmap.

The announcement also does not confirm Howie Liu’s role after closing.

AI credits may change first

The first commercial change may not be a higher seat price.

Bending Spoons often places AI at the centre of product changes. Airtable has also described the deal as support for an AI-native platform.

Airtable could change included AI credits, credit prices or feature access before changing seat prices.

If Airtable pushes prices or limits too far, competing platforms and specialist agencies will target the SMB and mid-market gap.

What solo users should do

Solo users and teams running non-critical systems should test alternatives while migration remains simple.

A personal CRM, content calendar or basic tracker may work in Baserow, Zite, Softr or another tool with its own database, UI and automation features.

Consider moving when the system:

  • Holds little data.
  • Uses few integrations.
  • Does not affect customers or revenue.
  • Costs more than the value it creates.

Do not spend 40 hours rebuilding a system to save US$20 a month.

Export the data, rebuild one workflow and run both systems together before closing the Airtable base.

What small teams should do

Small teams should usually keep Airtable as the central database and reduce paid access.

Many employees only need to submit a request, update assigned records or view a dashboard. They do not need full base access.

A Softr or Zite interface can sit above Airtable. Airtable remains the database and automation layer, while fewer users need paid seats.

Before renewal:

  1. Remove former employees and unused collaborators.
  2. Reduce occasional users to read-only access.
  3. Move submissions to forms or external interfaces.
  4. Combine duplicate bases where practical.
  5. Record current AI and automation use.

The OpsTwo guide to hidden SaaS costs explains how unused seats and plan upgrades increase software bills.

What mid-market customers should do

Mid-market customers face the greatest risk.

They have enough users and integrations to make migration expensive, but they may lack enterprise buying power.

Model three planning cases before renewal:

  • A 25% price increase.
  • A 50% price increase.
  • A 150% price increase.

For each case, compare three options:

  1. Keep Airtable and reduce paid users.
  2. Move selected workflows to another platform.
  3. Build a coded application backed by Postgres or another managed database.

Test one contained workflow first.

Measure migration work, permissions, integrations, training, hosting and maintenance. A lower licence price may still create a higher total cost.

Self-hosted tools reduce vendor dependence but make your team responsible for security, backups, upgrades and support.

Modular stacks can offer more control, but they add products, integrations, maintenance, and failure points. That complexity works against the main appeal of no-code and AI-assisted development.

What enterprise customers should do

Most enterprise customers will probably stay with Airtable, even if the price rises.

Airtable could still offer good value at twice its current price when it supports critical work and costs less than Salesforce, ServiceNow or a custom build.

That is not a prediction that Airtable will double its prices.

Enterprise customers should compare these choices:

  • Keep Airtable and increase the value it produces.
  • Reduce paid seats through forms, portals and limited interfaces.
  • Replace selected systems with custom code.

Custom code offers more control. It also requires developers, hosting, security, monitoring, documentation and long-term ownership.

A company without a capable software team may create more risk by leaving Airtable than by accepting a higher price.

Enterprise teams should also review change-of-control clauses, renewal terms, subprocessors, data residency, AI-data terms, export rights and support commitments.

The goal is not to cut the bill at any cost. The goal is to retain the value of each dollar invested and keep a practical exit route.

Our build-versus-rent guide explains how to compare a managed platform with a custom system.

Our forecast

After the deal closes, we expect:

  • Staff and support changes within four months.
  • More investment in AI and enterprise controls.
  • Tighter plan limits during 2027.
  • AI credit changes before or alongside seat-price changes.
  • More pressure on small and mid-market customers than on enterprises.

We expect Bending Spoons to make Airtable a stronger enterprise platform.

Customers should not leave because ownership is changing. They should measure the value Airtable creates, remove unnecessary access and prepare an alternative before they need one.

Subscribe to OpsTwo

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe