On August 4, Bending Spoons announced a definitive agreement to acquire Airtable in an all-cash deal valuing the company at a $1.285 billion enterprise value. Including Airtable's net cash, the implied equity value is about $2.25 billion. The deal is expected to close before the end of the year, pending regulatory approval.
Although this is a billion-dollar exit, the end result is not something the shareholders had envisioned.
The Numbers
Airtable's annual recurring revenue was approximately $480 million as of June 2026, growing more than 20 percent year over year, with more than 500,000 organizations and 80 percent of the Fortune 100 as customers. At a $1.285 billion enterprise value, that is under 3x revenue for a business growing north of 20 percent with genuine enterprise penetration. Airtable last raised private capital at a valuation around $11 billion in late 2021.
One detail worth catching: close to a billion dollars of that $2.25 billion equity value is Airtable's own cash coming back to shareholders. The operating business itself was priced at $1.285 billion.
Why the multiple is that low
Airtable's promise was that someone who could not write code could still build a real application. That promise built a very good company, and it is the same promise generative AI now delivers without a proprietary platform in the middle. The interface layer got cheap.
What did not get cheap is the thing Bending Spoons actually paid for. Half a million organizations with their operations already inside the product do not move quickly. Switching costs on a system of record are brutal, so the revenue holds even if the roadmap slows and prices climb. At under 3x ARR, Airtable does not need to grow at all for this deal to work.
Howie Liu, Airtable's co-founder and CEO, said the deal gives the company the resources and long-term commitment it needs to build what he called the AI-native platform of the future. That reads like a founder who knows the rebuild ahead is significant enough that he would rather do it with a patient owner than under public market scrutiny or another painful private round.
The Bending Spoons playbook
Bending Spoons listed on Nasdaq on July 1 at $29 per share, valuing the company around $18.4 billion. Airtable is its first acquisition as a public company, following AOL in January and Eventbrite in March. The portfolio already includes Evernote, Vimeo, WeTransfer, Meetup, Brightcove, and Komoot.
The pattern across those deals is consistent:
- They cut the existing team heavily. Acquired teams are typically reduced well beyond a trim, with the product moving under Bending Spoons' own engineering organization.
- They raise prices. Often substantially, and often inside the first year.
- They move existing features into paid tiers. Functionality that was free or bundled into a lower plan gets repackaged upward.
- They go quiet on the public roadmap while the technology and interface get rebuilt internally.
This is just business. They buy durable revenue at a low multiple and manage it for margin, and it has worked well enough to take them public at $18.4 billion.
For Airtable customers, that playbook is the forecast. Expect significant headcount reductions. Expect pricing changes, particularly on the plans where enterprise customers have the most locked in. Expect features you depend on today to sit in a higher tier tomorrow.
What Airtable customers should do this quarter
Nothing changes until the deal closes. Three things are still worth doing now.
- Separate the critical use cases from the convenient ones. A marketing calendar in Airtable is low risk. A customer database, an inventory system, or a client-facing workflow your revenue depends on is a different category.
- Run your data export. Not confirm it exists in the documentation. Run it, and find out how long it takes and what breaks.
- Price the alternative before you need it. Knowing what a rebuild costs turns a future pricing conversation into a negotiation instead of an emergency.
This is not an argument for panic migrating. Airtable is a good product and it is not going anywhere. Platform risk just got demonstrated in public, and the teams who look at it early are the ones who will not be scrambling later.
If you do decide to move
The common failure is treating a migration as a data export problem when it is really a product problem. The tables move fine. What breaks is everything built around them: the automations, the views each department relies on, the integrations nobody documented, and a permissions model that quietly encodes how the business operates.
What works:
- Map the real system before you map the schema. Every automation, integration, and view in active use, plus who depends on it. This is the step teams skip, and it is why migrations slip.
- Decide what deserves a rebuild versus a port. A workflow carrying years of workarounds should not be recreated faithfully. Some of it exists only because the platform forced it to.
- Move onto infrastructure you control. A real database with a purpose-built interface on top of it. That costs far less to build in 2026 than it did two years ago, which changes the economics of the entire decision.
- Run both systems in parallel before you cut over. Nobody should discover during business hours that an automation stopped firing.
Scoped well, this is a smaller project than most teams expect. Scoped badly, it eats a quarter and lands worse than what it replaced.
Rapptr Labs has spent 15 years building and scaling digital products, and a growing share of that work is helping teams move business-critical operations off platforms they have outgrown and onto infrastructure they own. If you are looking at your Airtable footprint and trying to figure out what is genuinely at risk, we are happy to walk through it with you. Reach out at rapptrlabs.com and we will scope it honestly, including telling you when staying put is the right answer.