Airtable's New Owner Makes Portability Worth Testing • The Weighted Average

Bending Spoons completed its Airtable acquisition on September 4, making product continuity and workflow portability live procurement questions for existing customers. The announced $1.285 billion enterprise value, spread across the closing release’s more than 500,000 organizations, implies less than $2,570 per organization—a measure of the acquired footprint, not a customer bill or a reason to assume prices will rise.

This backfill was reconstructed on September 7, 2026, from records available by September 5, 2026.

The purchase price describes the owner, not your renewal

The closing announcement says Bending Spoons acquired all of Airtable’s issued and outstanding shares in an all-cash transaction. It promises investment in product, customer support, and go-to-market capabilities. For customers, the event removes the uncertainty of whether the transaction will close. It does not resolve what the new owner’s operating choices will mean for a particular workspace.

The financial terms need their original labels. In the August 4 acquisition agreement announcement, Bending Spoons assigned Airtable an enterprise value of $1.285 billion and an implied equity value of approximately $2.25 billion after incorporating net cash and cash equivalents. Those are different measures. Calling the lower number the complete equity purchase price would erase the distinction the buyer itself published.

The footprint calculation combines that agreement with the September closing record. Divide $1,285,000,000 by 500,000 organizations: $2,570. Because the closing release says the base exceeds 500,000, the implied enterprise value per organization is below $2,570 using the announced transaction value. This is an upper-bound normalization of the footprint, not an estimate of paid revenue, customer lifetime value, acquisition cost, or what a workspace should cost to run.

The denominator is the important caveat. Organizations are not necessarily paying accounts, equally large deployments, or comparable sources of revenue. A small team and a substantial enterprise can each count as an organization while presenting different requirements. The ratio therefore helps describe what the acquisition buys—an installed workflow footprint—but cannot support a claim about the price the buyer must charge each customer to earn a return.

The August announcement also reported approximately $480 million in annual recurring revenue as of June, growing more than 20% year over year. That is useful context for the buyer’s claim that it is acquiring a growing business. It is still not a customer-level retention report, margin disclosure, or independent test of AI productivity. Builders should not let financial normalization substitute for the evidence relevant to their own deployment.

Airtable’s own closing statement endorses Bending Spoons’ long-term approach and investment capacity. It repeats the ambition to bring data, context, and AI agents together in one flexible workspace. The operative promise is continuity plus development, not a specified migration or a published price change. Neither that statement nor the buyer’s closing release is evidence that customers must leave immediately.

Test the exit before a renewal makes it urgent

The sensible first move is an inventory, not an evacuation. An Airtable customer should identify which workflows are merely convenient and which are dependencies for another system. Record who owns each critical process, what data it uses, which approvals it requires, and what happens if it stops. The acquisition makes that exercise timely because ownership has changed; it does not make undocumented workflows a new problem created by the buyer.

There is a concrete reason to ask about change. In its description of the acquisition model, Bending Spoons says transformations can include reorganizing teams, overhauling technology, redesigning interfaces, accelerating development, and enhancing monetization. That is the company’s stated operating philosophy, not a forecast of a particular Airtable action. Customers should ask which elements apply to their product and what notice they will receive.

For a builder adding agents to an existing workflow, portability should include behavior as well as data. A copy of the records alone may not reproduce approval logic, integrations, permissions, or the operational knowledge held by the team. Test a representative workflow outside its current environment before calling it portable. Record the gaps and estimate the work needed to recreate the business outcome, rather than declaring success because an export file exists.

That extends our earlier analysis of mature automation platforms. The durable value of a workflow tool is not merely that it can connect applications; it is that a team can change, test, and operate those connections deliberately. An alternative should be assessed against the whole process. Replacing a familiar tool with a loosely assembled agent system can exchange a visible subscription expense for a less visible maintenance burden.

The costs remain specific to the customer. The closing materials publish no revised Airtable rate card, mandatory conversion schedule, or quantified migration cost. Procurement should request renewal terms, support commitments, and a written account of any announced changes. Engineering should estimate the cost of preserving the current system, qualifying an alternative, and operating both during a transition. Do not populate that estimate with the acquisition’s enterprise-value-per-organization ratio; it measures a transaction, not the work of leaving.

The strongest counterpoint is that a well-resourced owner could improve the product and reduce the customer’s maintenance burden. Both companies explicitly promise investment. A continuity review should leave room for that outcome. It should also distinguish a contractual commitment from a statement of intent. A customer gains little by migrating prematurely only to discover that the new environment requires more engineering and offers weaker operational support.

Today’s Gimlet lead makes the complementary point about coordination layers: abstraction is valuable when its delivered benefit exceeds the new dependency. For Airtable users, the dependency is a working application estate. The acquisition is a reason to make that estate legible and testable, not a shortcut to deciding that every managed platform is a trap.

The verdict is to stay where the workflow works while buying a credible option to leave. Teams with critical dependencies should request continuity evidence now and test a bounded alternative before renewal pressure removes their room to choose. A demonstrably better product, stable terms, and responsive support would strengthen the case for staying. Materially worse economics, missing capabilities, or inadequate transition support would justify switching. The new owner has bought a substantial footprint; customers should make sure their own choices remain larger than a renewal deadline.