What you need to know
- Separate transaction announcements from completed ownership changes.
- Check present service commitments and future roadmap promises independently.
- Test workflow portability before a renewal or migration becomes urgent.
A larger platform for software acquisitions
CNBC’s October 17 report examines Bending Spoons’ growing role as a buyer of established software businesses. The attention follows an October 14 company announcement of a further $330 million investment from Berkshire Hathaway, after its $600 million investment at the July IPO.
Bending Spoons said the private placement would issue 10 million shares at $33 each, bringing Berkshire’s ownership to 4%. Its announcement made closing subject to customary conditions. The company describes a strategy of improving acquired businesses and reinvesting earnings in further deals.
Airtable makes the operational stakes concrete
Airtable’s October 12 update says a large portion of its pre-acquisition team would leave that week. It also says customer plans, prices, and service offerings remain unchanged, and its customer-facing organization has not been affected.
The same statement outlines planned work on platform performance, automations, and centralized administration. Proposed enterprise capabilities include agent permissions and audit logs. These are roadmap commitments; customers should check availability and contractual coverage before building a dependent workflow around them.
Keep a proposed deal separate from an operating change
Miro is a separate transaction. In September, Bending Spoons announced an agreement with a $1.355 billion enterprise value and approximately $1.79 billion equity value including net cash. The release expected completion in the fourth quarter of 2026, subject to approvals and other conditions, with the businesses operating independently until closing.
Our view: document the dependencies before renewal
An ownership change is a useful moment to inspect a supplier relationship. It does not, by itself, establish that a product will improve or deteriorate. Enterprise teams can make the uncertainty manageable by recording which business processes depend on the service and who owns each integration.
A practical review should test whether a data export contains enough structure to reconstruct a critical workflow elsewhere. A downloaded spreadsheet may preserve records while leaving permissions, automation rules, or application behavior behind. Record those gaps before an urgent migration makes them expensive to discover.
At renewal, compare current contractual protections with the service the team actually uses: support response expectations, notice of material changes, and assistance moving data. Ask the supplier to distinguish delivered features from planned work. That creates a concrete basis for continuing the relationship and a usable fallback if requirements change.
Sources & further reading
This article draws on the source material and official product documentation below. Product capabilities can change; check each source for current details.
