An honest comparison for construction teams, written the week Bending Spoons announced it is acquiring Airtable. We sell project controls software, and this page says so at the bottom — but the comparison starts with what Airtable genuinely does well, because not everything it does is our job to replace.
Airtable is a flexible database you can shape into almost anything. RFI logs, submittal trackers, defect registers, procurement schedules — if the job is "track structured data and let the team see it", Airtable does it well and has done for years.
It is not project controls software. It does not compute earned value from a schedule import, analyse a critical path, quantify risk exposure probabilistically, or write an assessment that traces to the numbers behind it. Those are different problems, and they need a tool built around them.
The acquisition changes the risk profile, not the capability. What Airtable can and cannot do has not changed since 4 August. What has changed is who owns it, and what the new owner's track record suggests about pricing, staffing and long-term product direction.
On 4 August 2026, Bending Spoons announced a definitive agreement to acquire Airtable for US $1.285 billion in cash. Airtable was last privately valued at $11.7 billion in December 2021 — the acquisition price represents roughly an 89% discount from that peak.
Bending Spoons is an Italian software company that listed on Nasdaq on 1 July 2026. Its portfolio includes Evernote, WeTransfer, Eventbrite and Vimeo. The pattern across those acquisitions has been: acquire at a significant discount, cut costs, raise prices, and run the product for margin. Whether that pattern repeats here is speculation — but it is why people are asking the question.
Nothing has changed for Airtable customers today. The deal is expected to close later in 2026, subject to regulatory approval. If you are mid-project on Airtable, there is no immediate reason to panic. There is a reason to plan.
Taken seriously, because dismissing a tool used by 500,000 organisations would be dishonest.
If you are using Airtable for RFI tracking, submittal logs or defect registers, Aegis is not the replacement and we are not pretending it is. Keep a structured database for structured data.
These are not criticisms. They are category boundaries — the point where a general-purpose database meets a domain-specific problem it was not designed to solve.
Construction schedules live in Primavera P6, Microsoft Project or Asta Powerproject. Airtable has no native import for .xer, .mpp or .xml schedule files. You can paste data into it, but pasting is not parsing — the logic ties, calendars, resource assignments and WBS hierarchy are lost, and without them there is no critical path and no earned value.
CPI, SPI, EAC, TCPI — these are not opinions, they are calculations with specific definitions. Airtable can store a number someone typed in. It cannot derive that number from a schedule import, a cost baseline and an actual-cost feed, and show the working.
The DCMA 14-point checks, missing logic detection, float analysis, critical-path integrity — none of these exist in Airtable because they require a scheduling engine, not a database. A base that lists activities is not the same as a model that understands the relationships between them.
A risk register in Airtable is a list with a likelihood column and a consequence column. That is qualitative risk. Quantitative risk — a Monte Carlo simulation that produces a P50 and P80 completion date — requires a model that understands the schedule, not a table that records what someone assessed.
The monthly status report a client reads should trace every rating to the number behind it. Airtable can store the report as a long-text field. It cannot generate an assessment where "Amber" means CPI fell below 0.95 and the critical path consumed 12 days of float — because it did not compute those figures.
Usually a person. Someone exports from P6, opens a spreadsheet, manually calculates earned value, hand-writes the assessment, and pastes the risk register into a slide deck. The tool is free of blame — it was never designed to do this work. The cost is the hours, and the fact that the interesting question ("what changed and does it matter?") gets whatever time is left after the assembly.
| Airtable | Aegis Command | |
|---|---|---|
| Built for | Any structured data, any industry | Construction project controls |
| Schedule import | Manual paste only | P6 (.xer), MS Project (.mpp/.xml), Asta, Excel, CSV |
| Earned value | Not computed | CPI, SPI, EAC, ETC, TCPI — derived from imports |
| Critical path | No scheduling engine | Parsed from schedule import, float computed |
| Risk quantification | Qualitative register (likelihood/consequence) | Quantitative — Monte Carlo, P50/P80 dates |
| Schedule quality | Not assessed | DCMA 14-point checks, logic integrity |
| Monthly assessment | Manual — typed into a field | Generated, every rating traceable to the number |
| Audit trail | Record-level revision history | Period-over-period, tied to schedule versions |
| Flexibility | Total — build any structure | Bounded by project controls domain |
| RFI/submittal tracking | Excellent | Not its job |
| Pricing model | Per user per month | Per combined contract value, not per seat |
| Ownership | Bending Spoons (acquisition pending) | Independent, Australian |
Three things are worth thinking about regardless of what Bending Spoons does next.
Airtable charges per user per month. On a project team of 15 people across Business tier, that is roughly US $5,400 a year before you have computed anything specific to project controls. If prices rise — as they have after previous Bending Spoons acquisitions — the cost of a general-purpose tool doing a specialised job gets harder to justify. Aegis charges on combined contract value, not per seat. A team of five and a team of fifteen pay the same.
Airtable bases are not portable. The views, automations, linked records and interface layouts do not export to anything another tool can read. The deeper the build, the harder it is to leave — which is exactly the position that makes price increases stick. If you are early in an Airtable build for project controls, this is the moment to ask whether a general-purpose platform is the right foundation for a domain-specific function.
Bending Spoons' stated strategy is to acquire products with strong revenue and improve their margins. Whether that means investment or cost-cutting depends on who you ask. What is observable is the pattern: Evernote, WeTransfer, Eventbrite and Vimeo each saw staffing reductions after acquisition. Fewer people building the product means a slower roadmap — and a slower roadmap in a general-purpose tool means the construction-specific gap widens, not narrows.
We wrote this page the week the acquisition was announced. That is not a coincidence — it is the moment the question is being asked, and we would rather answer it honestly than leave it to a vendor that does not work in construction.
Nothing in this comparison changes if the acquisition falls through. Airtable was not project controls software before the deal, and it will not become project controls software after it.
If your earned value, cost tracking, risk register and monthly status report all live in Airtable bases — and someone is manually computing them each period — that is the work Aegis displaces. The schedule import, the computations and the traceable assessment are what you are buying.
RFI logs, submittal registers, inspection checklists, procurement trackers — these are structured-data problems and Airtable is good at them. Aegis does not do this work and is not trying to. Keep the right tool for the job.
Most teams that use Airtable in construction are not using it for project controls — they are using it alongside a controls function that lives somewhere else (usually a spreadsheet). The acquisition is a prompt to separate the two jobs properly: a structured database for operational tracking, and a controls tool for the computations and reporting that a database cannot do.
If you decide to move your project controls out of Airtable, the path is a CSV export. No API integration, no middleware — just the data you already have.
Open the Airtable base that holds your tasks or activities. Switch to Grid view, click the view menu (⋯) and choose Download CSV. If your schedule spans multiple tables, export each one separately.
If you track risks in a separate table or base, export that the same way. Column names like "Risk Name", "Likelihood", "Impact" and "Owner" are auto-detected on import.
Sign up, go to New Project, and upload your CSV. The column mapper recognises Airtable field names — "Task Name", "Due Date", "Assignee", "Budget", "Completion" — and maps them automatically. Review the parsed table, confirm, and you have a live project with earned value, critical path and risk quantification computed from day one.
Task names, dates, budgets, progress, predecessors (if you tracked them), and your risk register with likelihood, consequence, owner and mitigation. What does not carry over: Airtable views, automations, linked-record relationships and interface layouts — those are platform-specific and not portable to any tool.
Aegis reads what your scheduling tool already exports — P6, MS Project, Asta, Excel, CSV — and computes earned value, schedule quality, risk exposure and a probabilistic forecast from it. Every rating in the monthly assessment traces to the number that produced it.
It does not replace P6, MS Project or Procore. It does not replace Airtable for the things Airtable does well. It replaces the manual monthly rebuild: the spreadsheet cost tracker, the hand-calculated EV, the risk register that nobody updates, and the report that takes three days to assemble and an hour to read.
Yes. On 4 August 2026, Bending Spoons announced a definitive agreement to acquire Airtable for US $1.285 billion. The deal is expected to close later in 2026.
You can track data in it, but it cannot compute earned value, analyse a critical path, run schedule quality checks, or produce a traceable assessment. The gap is category, not configuration.
No changes have been announced. Bending Spoons' previous acquisitions have been followed by pricing adjustments, which is why the question exists. Review your contract terms and understand what happens at renewal.
Only for the controls function. If you use Airtable for RFI logs, submittals or general tracking, keep it — that is not what Aegis does. If you are manually computing earned value and writing reports from Airtable data, that is the job Aegis is built for.
Export your Airtable base as a CSV (Grid view → view menu → Download CSV), then upload it to Aegis via New Project. The column mapper auto-detects Airtable field names. If you have a separate risk register table, export that too and paste it in the risks section.
No, and it should not try. Aegis is project controls software — schedule analysis, cost tracking, risk quantification, reporting. It does not do general-purpose data management, RFI tracking or submittal logging. Different tools for different jobs.
Aegis reads what P6, MS Project, Excel or CSV already export each period and turns it into earned value, a quantified risk position, a probabilistic forecast and a written assessment — with every rating traceable to the number behind it.
Start your 14-day trial →