SaaS platforms

Selling software to other companies is not the same as using software. Accounts that must never mix, plans that have to be billed, customers growing at different rates, and an admin side to govern all of it. We built that for ourselves, with the advantage of having suffered it first.

Free review

When you need this

You have an internal tool that works and several people have asked whether you sell it.
You want to charge by subscription rather than by project.
You will have customers whose data must never be visible to each other, not even by accident.
You need to onboard a new customer without that being a deployment.

What it includes

Per-company accounts, with their own users and permissions.
Data isolation between customers, decided in the architecture and not afterwards.
Plans, limits and recurring billing.
Customer onboarding without anyone technical in the loop.
The admin side from which you see and govern all of the above.

How we do it

Isolation between customers is the most expensive decision in the whole project to reverse, so it is taken during architecture, on the table and in writing, before anything gets built. Changing it once you have customers means rebuilding the product.

Five phases, each with its own acceptance criteria

Questions about this service

Can we turn the tool we already use into a product?

Sometimes yes, and sometimes it costs more than starting again. The audit decides. What usually settles it is not the code, it is whether different customers’ data can be cleanly separated.

Who handles billing?

We integrate whichever payment provider you prefer and build the plans, the limits and what happens when someone stops paying on top of it, which is the part nobody remembers until it happens.

Usually comes with

Infrastructure