# Airtable

You know how to use a spreadsheet. You've also felt where it falls apart: the
file with twelve tabs, the "do not delete this column" notes, the moment two
people overwrite each other's work and you can't tell what changed. Airtable
is what you reach for when a spreadsheet has stopped being enough but a real
database feels like a step too far. It looks like a grid, so you already know
how to type into it. Underneath, it behaves like a database - and that
difference is the whole point.

This guide is for the founder running their pipeline in a Google Sheet, the
ops person tracking inventory across three tabs, the analyst who keeps a
"master list" everyone copies and breaks. You don't need to be technical.
You need to understand a handful of ideas - fields that have types, records
that link to each other, views that show the same data different ways - and
then you can build something that holds up when more than one person touches
it.

We'll go in four steps. First, why Airtable is a database wearing a
spreadsheet's clothes, and what "fields have types" and "linked records"
actually buy you. Second, the parts that make it feel like an app: links,
lookups, the different views, filtering, and automations that do work for you
while you're asleep. Third, Interfaces - turning your data into a clean
screen other people can use without seeing the messy grid - plus sharing,
permissions, and the real limits on how much data Airtable will hold. By the
end you'll know what Airtable is great at, and the exact moment it's time to
move on to something heavier.