Capability claim · evidenced by build, not by client logos
Can you handle our mess?
The highest-paid Airtable work is not building something new. It is taking thirty-six tables, eight hundred automations and three hundred thousand records that nobody dares touch, and making them safe to change.
Why this sector
Scale breaks Airtable bases in specific, knowable ways — record ceilings that count across every table, API budgets that a single integration can exhaust, revision history that is shorter than anyone assumes, and permission models that only exist above a certain plan. Knowing where those walls sit before you build is the whole job.
What it would do
Mechanics, not features — each one is a number that either ties out or announces that it does not.
Architecture review as a deliverable
Findings, risks and a remediation order, written for a technical buyer to grade. Sold as a review rather than as hourly repair — the same work, correctly named, sits a tier higher on every rate table we have measured.
Traps we have already paid for
A paginated source that silently restarts at page one past a depth limit will cost you the tail of every large slice — we found that one the hard way across 120,000 records, and now we assert the offset on every request. Rate-limit clearance, hung requests without timeouts and download suppression are all in the same category: failures that return success.
Plan ceilings, named up front
Records count across the whole base, not per table. API calls are metered per workspace per month. Field-level edit permissions do not exist below a certain plan. Revision history is two weeks on the free tier. Every one of those changes the design, and all of them are cheaper to know than to discover.
What we sell here
In the order it matters. We do not lead with the word "automation" — it is the most crowded and worst-paid label on the board, and it describes the least valuable part of the job.
- Solution architecture & review — the highest-paid work on the board, sold as a written artefact
- Restructure — a documented before and after, with the reasoning kept
- Integration at scale — pagination, rate limits and the traps that silently lose the tail of a dataset
- Custom apps & scripting — where the platform stops
- Governance — the layer that lets a business unit adopt it without a fight
What we are not claiming
Our named clients are small and mid-sized businesses. Enterprise here is a claim about capability — scale handling, governance design and architecture review — not a claim to enterprise customers we do not have. We would rather say that plainly than have it asked.
The other three
Tell us what your operation actually does.
Not what you want the software to do — what your team does today, and where the numbers stop being trustworthy. That conversation is free, and it usually decides whether Airtable is the right answer at all.