Airtable made a database behave like a spreadsheet

A funding story that is also the earliest public record

The earliest dated, opened account of Airtable as a public product is a TechCrunch report from 25 February 2015, covering a $3 million funding round and describing founder Howie Liu's product as combining the ease of use of spreadsheets with the power of relational databases. Airtable's own about page, retrieved 16 September 2026, dates the company's founding belief, that the people who know the work should build the systems, to 2012, three years before that funding coverage. No document reviewed here states a separate, earlier date on which the product became available to the public, so the February 2015 press record is treated as the earliest confirmed public marker rather than as a definitive launch day.

A spreadsheet's grid, a database's structure

Airtable's own support documentation lays out the mechanism: a base holds tables, a table holds records, and each record's fields can be linked to other tables rather than existing as flat text, which is the core difference from a spreadsheet cell. The same documentation describes multiple views, including grid, form, gallery, calendar, kanban and timeline, over the same underlying data, so the way a marketer sees the base and the way an operations lead sees it can differ without duplicating the information. That linking and multiple-view capability is what the 2015 press coverage meant by relational database power inside a familiar grid.

Where the spreadsheet mental model breaks

A spreadsheet user expects to type a formula referencing any cell freely; Airtable's linked-record model instead expects the relationship between two pieces of data to be declared structurally, as a link field, before it can be used, which is a database habit rather than a spreadsheet one. Teams that start by copying a spreadsheet's flat layout into Airtable often rebuild it later once they need one record to relate to several others, because the flat structure that felt natural at first does not carry the relational structure the tool was actually built around. Neither of Airtable's own documents frames this as a limitation; it is simply the trade-off of choosing structure over the total freedom a blank spreadsheet cell allows.

Questions to ask before you adopt it

• Does your data actually have relationships between records, or would a flat spreadsheet describe it just as well?
• Who is responsible for redesigning the base when the linked-record structure stops fitting the work?
• Which views does each person on the team actually need, and who maintains them as fields change?

Airtable's pitch worked because a grid looks familiar. The relational structure underneath is what a spreadsheet habit will not prepare a new user for.