When Airtable gets expensive, move to a backend you own

Airtable is a fine tool, right up until its per-seat and per-record pricing outgrows what a small team needs. If you already pay for Google Workspace, the cheaper answer is often sitting in front of you.

When Airtable stops fitting

A product catalog started on Airtable because it was quick to set up. As it grew, the pricing started to bite: more records and more seats, for a job that was really just a structured list with images. The company was paying a growing bill for convenience it had stopped needing.

Use what you already pay for

The business already lived in Google Workspace, so the data moved to Google Sheets and Drive, which it already owned. Categories, products, and variants became sheet rows, and product images became files in a Drive folder. No new service, no new subscription, and the content stayed somewhere the team could edit.

Pull it at build time

Because the site is static, it does not need a live database at all. The build reads the sheet and the images, optimizes them, and bakes everything into plain HTML. At runtime there is nothing to pay for and nothing to attack: just files. The content changes when the next build runs.

Where I used it

This is how the product catalog site works now: off Airtable, onto a backend the company already owned, free and fully under its control, and edited from the same internal tools the rest of the business uses.