Key takeaways
- Airtable client portals are priced in packages, and in my experience the per-client economics turn somewhere between 30 and 50 portals. That is my observation from client work, not a published Airtable policy.
- Below that line, Airtable portals are a genuinely good answer: fast to ship, native to the data, no extra vendor.
- Past it, agencies and service firms typically move the portal layer to Softr on top of the same Airtable base, or to a custom build when compliance or complexity demands it.
- The decision is about trajectory, not the current count: a firm adding clients monthly should do the math on where it will be, not where it is.
Airtable sells client portals in packages, and there is a line, in my experience somewhere between 30 and 50 portals, where the per-client math stops making sense. I want to be precise about what that claim is: it is what I have seen repeatedly in client work as portal counts grow, not a number Airtable publishes. Your pricing conversation with them may land differently, and their published plans are always the thing to check.
The mechanics behind it are published, and worth having in front of you: Airtable sells portal access in seat packs of 15, 25, 50, 100 and 200, at $120 a month for 15 seats on the Team plan and $150 for 15 on Business (verified against Airtable’s documentation, August 2026). Each pack is a step, and every batch of new clients climbs one. Run that against a growing client list and you can see where my 30-to-50 observation comes from: at 40 client portals you are holding two or three packs for a layer that does nothing more per client than it did at 15.
The pattern has repeated enough times across builds that I now treat it as a planning input, and it changes what I recommend depending on where a business sits relative to that line.
When is an Airtable portal the right answer?
Below the line, often. If your operation already runs on an Airtable base, portals that live inside the same vendor are the shortest path to giving clients a window into their own records: no second platform, no sync layer, one bill, and the portal inherits the base’s structure.
For a consultancy with a dozen active clients, or a firm whose client list turns over slowly, this is usually where I land. The count matters more than the ambition: at that scale the packaged pricing is a rounding error next to what the portal saves in status-update emails.
What happens at the 30-to-50 line?
The portal packages scale by portal, and your client count scales by success. Those two curves cross. An agency at 15 clients doing the math on portal packages sees a reasonable line item; the same agency at 45 sees a recurring cost that grows with every win, for a layer that does not do more per client than it did at 15.
That is the point where the businesses I work with restructure the layer rather than renegotiate it: keep Airtable as the data foundation, move the client-facing surface to Softr, which prices by app rather than per portal, and serves each client a filtered view of the same base. Same data, same automations underneath, different door for the clients, and the per-client cost curve goes flat.
Side by side, the three ways to run the portal layer:
| Airtable portals | Softr on Airtable | Custom build | |
|---|---|---|---|
| Pricing shape | Per portal, in packages | Per app, flat as clients grow | Build once, own outright |
| Cost curve as clients grow | Climbs with every client | Flat | Flat, and improves per client |
| Fits best at | Up to the 30–50 range | Growing client counts on an Airtable base | Compliance, complexity, product-like portals |
| PHI / HIPAA | Airtable’s own datasheet says no patient portals | No BAA at all | Built on covered infrastructure |
| Time to first portal | Fastest | Fast | Slowest, by design |
| Who owns the layer | Vendor subscription | Vendor subscription | You |
When is neither the answer?
Two cases push past both options.
Compliance. If the portal serves patient data, the calculus changes entirely: Airtable’s own health documentation says not to use it as a patient portal, and Softr signs no BAA at all. Healthcare portals get built on covered infrastructure, where the constraint is regulation, not portal count.
Complexity. When each client’s view stops being “a filtered slice of the base” and becomes its own workflows, roles and logic, the portal is turning into a product. At that point a custom build, owned outright, with no per-portal or per-app pricing at all, is the version whose economics improve with every client instead of degrading. That is the trajectory C.A. Ellis followed: a dozen provider organizations, each seeing their own compliance standing in a portal over one Airtable architecture.
The math, on your numbers
Approaching the 30-to-50 line?
Bring your client count and growth rate, and we will put the three options against your actual numbers in one call. If staying on Airtable portals is the right answer, that is what we will tell you.
Run the numbers with usHow do I decide for my own business?
Three questions, in order. Where will the client count be in a year, not today? Does any portal data fall under HIPAA or similar regulation, because that answers the question by itself? And is each client’s portal the same view filtered, or its own logic? Filtered-same points at Airtable then Softr; regulated points at a custom build; own-logic points at treating the portal as a product.
Signals you are approaching the line, from the builds where we have watched it happen: the portal line item gets its own row in the budget review; someone proposes “only giving portals to the big clients”, which means rationing a thing that should scale; and new-client onboarding starts including a conversation about whether they get a portal at all. Each of those is the cost curve talking.
The wrong move is the default one: staying with the packaged option out of inertia while the client count climbs, and paying the growing delta every month for the privilege of not deciding.
We build all three versions, which is why this post does not end by declaring one of them the answer. If you want the decision made against your actual numbers, book a call and bring your client count.