How much to charge for an Airtable build
How much to charge for an Airtable build comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is the yearly value of the manual work the base removes, plus whatever tools or spreadsheet juggling it replaces. Your quote sits between the two. The typical job is a team running something important out of a pile of spreadsheets: projects, inventory, applicants, content, orders, or client work that lives in five tabs and three people's heads.
I am not giving you a market dollar figure. A single table with a form in front of it and a linked base with interfaces for three departments and a dozen automations are different jobs. One number would be noise. Your rate and the client's numbers will get you a real one.
Airtable looks like a spreadsheet, and that is the pricing trap. The client thinks they are paying you to make a nicer spreadsheet. They are actually paying for a data model that does not fall apart in six months. Where Claude Code earns its place is the work around the base: scripts that clean and reshape the old data before import, scripting steps inside automations, webhook handlers for apps with no ready-made connection, and test records that prove the whole thing works before the team moves in.
Calculate your floor and ceiling
Run this before you name a price. Every input is yours or the client's, so you can show the working in the proposal.
The Airtable build calculation
| Number | How to get it | Who supplies it |
|---|---|---|
| Floor | Your estimated hours for each line in the quote, plus a buffer you choose for edge cases and revisions, times your hourly rate | You |
| Time value per year | Hours per week spent copying between sheets, chasing status updates and fixing conflicting versions, times 52, times what an hour of that person's time costs | Client |
| Spend replaced | What they pay per year for tools the base takes over, if any | Client |
| Cost of a miss | Only if they can point to real examples: a double-booked job, an order nobody owned, stock that ran out because the count was in an old tab | Client's own history, your judgment |
| Ceiling | Time value plus spend replaced, plus the miss line only if it is documented, minus the yearly Airtable cost the build adds | Calculated |
Notice the last line. Airtable charges per collaborator, so a build for a team of fifteen carries a real monthly cost. If the floor plus a year of the plan is above the ceiling, the base will not pay for itself. Say so and offer a smaller version, such as one table and one interface for the process that hurts most.
Check the plan limits before you quote
Airtable plans set hard limits on records, automation runs and API calls, and the plan the client needs changes your design and their running cost. These are the self-serve plan figures as of this post:
Airtable self-serve plan limits
| Limit | Free | Team | Business |
|---|---|---|---|
| Price per collaborator per month | N/A | $24 monthly, or $20 billed annually | $54 monthly, or $45 billed annually |
| Records per base | 1,000 | 50,000 | 125,000 |
| Automation runs per workspace per month | 100 | 25,000 | 100,000 |
| Unique automations per base | 75 | 100 | 150 |
| API calls per workspace per month | 1,000 | 100,000 | Unlimited |
| Attachment storage per base | 1GB | 20GB | 100GB |
| Revision and snapshot history | 2 weeks | 1 year | 1 year |
Three things to take from that table into the proposal. First, the Free plan caps a workspace at five collaborators with Editor or Creator permissions, so almost every real client build means a paid plan. Second, records per base is a ceiling on the whole base, not each table, so a client importing five years of orders can hit it on day one. Count their existing rows before you design. Third, automation runs and API calls are counted per workspace per month, so every automation you build draws from one shared allowance.
On Team and the self-serve Business plan, Owners, Creators and Editors in the workspace are billable. Read-only collaborators are not. That is a design lever: if half the team only needs to look things up, an interface with read-only access for them can cut the client's bill. Business and Enterprise Scale plans also require a private email domain, so a client running the business on Gmail addresses cannot upgrade to them.
The CCC Base Quote
Six parts of an Airtable build quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Data model | The tables, fields, links and views, written up and signed off by the owner before the build | Walk me through one job, order or project from start to finish, and show me every place it gets written down |
| Migration | Cleaning, deduplicating and importing the existing data, with a count before and after | How many rows are in your current sheets, and which one is the real version? |
| Interfaces | The screens each role works in, so people do not edit raw tables | Who uses this every day, and what is the one thing each of them needs to see? |
| Automations | Notifications, status changes, record creation and any scripting or webhook steps, sized against the plan's run allowance | What happens today when something changes status, and who has to be told? |
| Permissions and plan | Who is Creator, Editor or Read-only, and which plan that requires | Who needs to change data, and who only needs to look? |
| Handover and tuning window | A walkthrough, notes on the data model and each automation, and adjustments after the first weeks of real use | Who will own the base once it is live? |
The data model is your anchor line. It is the part the client cannot see and the part that decides whether the base still works in a year. A base built table by table, as requests come in, ends up as the same mess the spreadsheets were, only slower to fix. Price the model as its own line and get it signed before you build.
Migration is the line clients underestimate. Real data has the same client spelled four ways, dates typed as text and rows that contradict each other. Quote the cleanup rules explicitly and give the owner a row count before and after, so nobody later asks where the missing records went.
Agree who owns the workspace
Put ownership in the proposal. The Airtable workspace, every connected app and any API keys stay in the client's name, and the subscription goes on their card. If you build in your own workspace and the client leaves, their operating data is in your account, and that is a conversation nobody wants. Ask to be added as a collaborator in their workspace and agree the date your access ends.
Then put responsibility in writing. The owner signs off the data model and the cleanup rules. If they later add a department or a new process, that is a change request, not a bug. Define done: which tables, which interfaces, which automations, and which test records went through every step.
Always quote the tuning window
An Airtable base meets reality the first week the whole team works in it. Someone needs a field nobody mentioned, a view is missing the filter one person relies on, or an automation fires more often than the owner guessed and starts eating the monthly run allowance. If you have not quoted for that, you fix it for free while the team drifts back to the spreadsheet.
Put a fixed tuning window in the first proposal, next to the build price. Say what it covers: fixing broken automations, adjusting views and interfaces, and a check of automation runs and record counts against the plan after the first full month. Say what it does not cover: new tables, new departments and new processes. For ongoing work, offer a retainer. How to price a maintenance retainer covers the structure.
How to present the Airtable build quote
- Lead with the outcome in the owner's words. One line on what changes, such as every job, its owner and its status in one place without anyone asking, then the price.
- Offer three options. A starter that moves the one process that hurts most into a single base, a standard that adds the migration of active records and an interface for each role, and a full version that covers the related processes with a longer tuning window. Make the middle one the clear best value.
- Show your calculation. Put their own hours and tool spend in the proposal, and show the yearly Airtable plan cost for their team size as its own line so the value is net of it.
- Itemize it. Data model, migration, interfaces, automations, permissions and plan, then handover and the tuning window. That gives the client a line to trim instead of a reason to say no.
- Take a deposit and tie the rest to milestones, with the signed data model and the completed migration count as two of them. How much deposit to charge covers the schedule.
Skip hourly on the invoice, even though hours set your floor. Why I stopped charging hourly for AI builds explains why. If you are not sure what the client actually needs, sell paid discovery first. Client discovery questions before you quote has the questions.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for an Airtable build?
Work out a floor from your estimated hours times your rate, and a ceiling from the manual hours it removes per year plus any tools it replaces, minus the yearly Airtable plan cost. Quote between the two and itemize each part.
Who pays for the Airtable subscription?
The client. The workspace and the subscription stay in their name and on their card, and your collaborator access ends on an agreed date. Show the plan they need and its yearly cost in your proposal.
Can a client run their business on the Airtable Free plan?
Rarely. The Free plan allows 1,000 records per base, 100 automation runs per workspace per month and five collaborators with Editor or Creator permissions, which most real client builds outgrow quickly.
Does every Airtable user cost money?
Not on Team or self-serve Business. Owners, Creators and Editors in the workspace are billable, while read-only collaborators are not, so giving view-only staff read-only access keeps the plan cost down.
Should I charge per table or a fixed price?
Charge a fixed price for the project, itemized by part, then a monthly retainer if the client wants ongoing changes. Per-table pricing rewards splitting data into more tables, which is usually the wrong design.
Can Claude Code help with an Airtable build?
Claude Code can write the scripts that clean and import existing data, scripting steps inside automations, webhook handlers and test records. You still own the data model, the client conversations and the sign-off with the team.
Last reviewed by Duncan Rogoff on November 16, 2026


