Airtable systems that run the business, not a spreadsheet that looks like one.
Below is a system running on four active building sites right now. Two of its views are open — sort them, filter them, export them, without asking us for anything.
S J Construction
A contractor running four sites. Everything used to move by WhatsApp, on paper, and through one evening a month spent typing receipts into a spreadsheet.
Bags of cement on the supplier’s delivery note.
Counted off the truck. The delivery is valued on this one.
Every delivery records both numbers. The system works out the difference and values the delivery on what somebody stood there and counted — never on what the note claimed. Across three test deliveries that gap was worth Rs 8,100.
Eight linked tables — projects, materials, vendors, orders, deliveries, site reports and stage-wise billing. Two forms pinned in the WhatsApp group the team already used, so a supervisor files a report in a few taps without installing anything.
Open it yourself.
The contractor’s own views, embedded live.
The delivery log — claimed against counted, on every line.
The site report form, as a supervisor sees it on a phone.
Three things worth knowing before you build on it.
All three are checkable — they are in Airtable’s own documentation or in public contracts — and all three cost money to find out late.
The cheap plan can cost more than the expensive one
Team bills anyone with commenter access. Business bills only editors. So Business at $45 is cheaper than Team at $20 the moment commenters outnumber editors by more than 1.25 to 1 — four editors and six commenters is $200 a month on Team and $180 on Business. It sits in Airtable’s own billing documentation and nobody puts it in front of a buyer.
The limits are architecture, not pricing
Every Airtable ceiling is per base, because a base is one process holding all of its data in memory. That is why links cannot cross bases, why the record ceiling exists, and why the API never exceeds five requests a second on any plan. Upgrading will not lift it. Splitting the base is the only answer Airtable can give — and splitting breaks the links, which is the trap most builds hit in year two.
There is no discount to negotiate
We checked this against published US federal and UK government contracts rather than asking a salesperson. A hundred-seat order paid slightly above the public list price. A multi-year commitment moved it by about nine per cent. Anyone promising to negotiate your licence down is selling something they cannot deliver.
Where we work.
Four, chosen because the work pays and we can show it — not because the list looked complete.
Construction — live client
Multi-site material ledgers, site reporting from a phone, stage-wise client billing.
Manufacturing
Order to production to dispatch, stage reconciliation, buyer POs and export paperwork.
Healthcare operations
Intake, referral tracking and care registers with a real permission layer. Synthetic data in every demo — never patient data.
Enterprise
Large record volumes, restructured schemas, and the governance work that lets a business unit adopt it.
Who builds it
A team of certified developers. The system above is the argument.
We work async, by email, and reply within one business day. Every engagement starts with a written scope and a fixed price, and you own all of it at the end — the base, the scripts, the credentials and a runbook.