Miro or Airtable renewal: run the owner-change checklist

A Miro or Airtable renewal can look like a small line item until the vendor changes hands. Bending Spoons announced on September 10, 2026 that it had agreed to acquire Miro in an all-cash transaction valued at $1.36 billion. That price was approximately 90% below the $17.5 billion valuation Miro reached in late 2021. Miro's ownership transfer was not scheduled to be completed until the fourth quarter of 2026. Bending Spoons had bought Airtable in August 2026 for $1.29 billion.

Miro generated roughly $600 million in annual recurring revenue, with business and enterprise customers accounting for nearly 90% of it. For a small team, the renewal is the risk: it can land while the vendor change is still moving. The tool may keep working while the pricing page stays quiet, the account owner changes, export permissions tighten, and the seat count drifts from the people who actually use it. The team has to make the choice, not the vendor.

The renewal date is the first line in the file

The date is the first line because it tells the team when the decision becomes real. An annual renewal makes the date a deadline; a monthly renewal makes it a habit. Either way, it belongs in a document that survives a founder's busy week. A renewal without a named owner stays unowned.

Put the date next to the payment method and the contract. If the vendor sends a renewal notice, the file should already show whether the team is renewing, reducing, or leaving. That keeps the decision out of the inbox and into the operating calendar.

Seat math tells you what the tool is actually doing

Unused seats are a cost, not a perk. A tool that everyone touches is different from a tool that a few people use for a project. The seat count is the fastest way to see whether the renewal is still earning its place. It also gives you a number to negotiate, reduce, or walk away from.

A clean seat count also tells you who to ask before a renewal call: a project team owns a project tool, while ops owns a company-wide tool. The file should show which team owns the tool.

Exit path and data capture are the real decision

An ownership change can alter the terms you assumed. The vendor may keep the product stable, or it may fold it into a larger platform. Know where the data sits before the question becomes urgent. If the team cannot export what it needs, the renewal becomes a dependency question.

A replacement option only needs to be good enough for the next sprint. The migration owner should be able to name the early moves, the later moves, and what stays behind. That makes the exit path a plan.

• Renewal date: locate the next invoice date, the billing cycle, and the person who can stop it.
• Seat math: calculate active seats, unused seats, and the cost per seat at current pricing.
• Exit path: define the replacement option, the migration owner, and the deadline for a clean handoff.
• Data capture: note where boards, templates, permissions, and exports live, and who can retrieve them before the ownership transfer is complete.

A named owner makes the checklist real

Assign a person to keep the file. That person should be able to give the renewal date, the seat count, and the data location without asking around. If the answer is hard to find, the file is not ready. A short review is enough if the file is current. The team should be able to make the decision before the invoice arrives.