Free tool
Your company tool, sold to other companies: which multi-tenant model?
You built a system for your own company, with AI or without, and other companies want to pay for it. The first question is how to keep their data apart without running a separate copy for each of them. Enter your numbers and see which model fits, what every release will cost you in work, and how many weeks it takes.
How the model is chosen
The names come from the AWS SaaS Lens: silo means dedicated resources per client, pool means shared, and a mix of both. The AWS storage whitepaper maps them to databases: a separate database per client, a schema per client, or shared tables. My rule of thumb: if contracts require a separate database, give it to those clients only; if clients need their own fields and you expect up to 100 of them, a schema per client; otherwise shared tables.
How the work is counted
Work a month is database updates per release times releases a month times the minutes of attention you enter (default 5: run, check, note). The comparison line shows the same for a separate copy per client, the setup most company tools start from.
What the build covers
Your current data moved in as the first client, sign-up and invitations, roles, billing and invoices, settings per client, one deploy that updates everyone, restoring a single client, and the first three paying clients onboarded with you. Weeks start at 4 and grow with moving existing copies, separate databases and per-client fields, up to 10, as in the configurator.
Questions
We run a separate copy for each company today. Is that wrong?
It works for two or three. Every release then means updating every copy, and every client is a separate server to watch. The calculator shows when that stops paying off.
Do we have to rewrite the app?
Usually not. The client identifier goes into the tables and the queries, login learns which client a person belongs to, and your own company becomes the first client.
What about clients who want their data in a separate database?
Give it to them, on the same code and the same release, often as a higher plan. That is the mixed model.
Can you build it with us?
Yes, in 4 to 10 weeks, and then stay on as the engineer of the product if you want. The configurator shows the price and the start date.
Sources
Want to sell your company tool to other companies?
I turn it into a product: clients in one database, sign-up, roles, billing, one deploy for everyone, and your own company moved in as the first client. Then I can stay on as its engineer.
