Hi everyone,
In my work as a digitization / no-code agency, I help companies build internal systems based on relational databases. Tools like Teable are very interesting for me in that context.
One approach I’m exploring would be to use Teable as the underlying infrastructure and build or operate solutions for clients within my own workspace. That would allow me to deliver complete, managed systems instead of just advising.
So yes — Teable would become part of what I’m offering and charging for.
At the same time, I’m not talking about reselling accounts as a standalone product. It would always be bundled into services like designing, building, support or maintenance.
From my perspective, this sits somewhere between internal usage and classical reselling.
What I’m trying to understand better is the reasoning behind the current limitation:
If the concern is that one account is used to serve many end users, similar scaling effects can also happen within purely internal setups (e.g. large teams, complex systems, heavy usage within a single workspace).
So I’m curious:
Is the distinction mainly based on who the users are (internal vs external), rather than how the system is actually used?
Additionally, from a growth perspective, increased usage within a single workspace doesn’t necessarily eliminate monetization opportunities. In practice, as systems grow in complexity and usage, add-ons like the teable automation, rows, and data storage extensions packages may become relevant and they may be purchased to support that growth.
And how do others here approach this in an agency context?