Software you sell, not just software you use.
We build the platform that is your product: every client in their own properly separated space, with subscriptions, invoices and access rights. Separate data, recurring payments and room to grow are designed in on day one, not bolted on in year two.
- Tenants properly separated
- The code is yours
- We reply within 24 hours
Four situations in which your software turns into a product.
Today only you use it
You had something built that takes real work off your hands every day. Now you want to sell it to others instead of keeping it to yourself.
Others in your trade keep asking
Word has got around that you have your own tool. Everyone who asks about it is a paying client waiting for you to make it sellable.
You charge monthly or by usage
Your business does not run on one-off sales but on monthly amounts or units consumed. The software itself has to handle that, not your bookkeeping by hand.
Client data must be genuinely separate
A column holding a client number is not enough when one forgotten filter in the code shows one client another client’s figures. Separation belongs in the architecture.
Six building blocks every SaaS platform needs, and the ones that cost the most to add later.
Separate client spaces
Each client works inside their own space: their own data, their own users, their own settings and their own look. From the outside it looks like an application of their own.
Subscriptions and recurring payments
Plans, trial periods, upgrades, downgrades, cancellations and invoices all live inside the platform. Cards and direct debits run through an established payment service such as Stripe.
Users, roles and permissions
Your client invites their own colleagues and hands out permissions. Who may see and change what is decided inside their space, without you having to step in.
An admin area for you
An area for your team only: which clients are active, who uses how much, where a payment has stalled and who needs help. No detour through the database.
An API for your clients
A documented API with its own keys, so your clients can connect the platform to their own systems. That is often the reason they stay.
Usage metering and billing
Calls, documents, seats or gigabytes are counted and flow straight into the invoice. Your client can see where they stand at any time instead of being surprised at the end of the month.
Separate your clients before the first one arrives
In a SaaS platform every client’s data sits inside the same application. How cleanly it is separated is settled by the architecture, not by what is on the screen. Retrofitting it means touching practically every query in the application a second time, while the platform is already live.
Separation in the data model
Every query knows by itself which client it belongs to. A forgotten filter in the code then cannot hand out somebody else’s rows.
Separate in backups and deletion too
Backup, restore and deletion run per client. When one leaves, you can hand over their data and remove it without touching anyone else’s.
How much separation you actually need
A separate schema or a separate database per client: it depends on how sensitive the data is and what your clients have to guarantee in their own contracts. We settle it before the first line of code.
Billing that springs no unpleasant surprises
In SaaS the sale is not the moment of payment but the start of a long series of them. The software has to know in advance what happens in between: trials, plan changes, a card that fails, cancellations, invoices. Each of those rules is a commercial decision, not a technical footnote.
Trials and plan changes
Someone moving up to a larger plan mid-month pays pro rata, and so does someone moving back down. We settle those rules with you before they reach the code.
When a payment fails
Failed payments are routine, not the exception. Reminder, second attempt, suspension of access and reinstatement all run automatically and stay traceable.
Invoices your accountant recognises
Numbering, addresses, currency and the export into your bookkeeping all belong there from the start, so that nobody is retyping figures at the end of the month.
From your first client to your thousandth
A platform with five clients forgives almost every decision. With a thousand it forgives none. A handful of choices are therefore made correctly at the outset, even though nobody needs them on day one. They are precisely the ones that cannot be changed later without stopping the platform.
New clients without manual work
A new client sets themselves up: account, space, base data, invitations for colleagues. Otherwise every new arrival becomes your own workload.
Long jobs run in the background
Imports, exports, reports and mailings do not block the screen. Anything slow moves into a queue and reports back when it is finished.
Updating without shutting everyone out
New versions go live in small steps and can be rolled back. With luck your clients notice nothing at all.
Your own platform or a rented one?
Two ways to sell a product. One belongs to you, the other is quicker to stand up.
Who owns the product
Your own platform
You do. Code, database and accounts are all in your name.
A rented or low-code platform
Your data is yours, the product itself stays somebody else’s property.
Margin as you grow
Your own platform
Running costs grow considerably more slowly than your client count.
A rented or low-code platform
The provider earns per client or per user, permanently.
How far you can adapt it
Your own platform
No limit. Whatever your market asks for gets built.
A rented or low-code platform
As far as the platform allows, and not one step further.
Effort at the start
Your own platform
Higher. It gets built before there is anything to show.
A rented or low-code platform
Low. A first version stands up in a short time.
Dependence on the provider
Your own platform
None. Hosting can be moved whenever you choose.
A rented or low-code platform
Prices, limits and terms are set by the provider.
Getting out if you want to switch
Your own platform
A handover: source code, database, accounts.
A rented or low-code platform
A rebuild, because all the logic sits inside somebody else’s platform.
Honestly: if you are still finding out whether anyone will pay for this at all, renting is often the wiser first step. Building pays off once demand is proven and the rent per client starts to hurt.
Proven tools that still hold up at your thousandth client.
Front end
React, Next.js
Server
Node.js, Python, Go
Data
PostgreSQL with tenant separation, Redis
Billing and hosting
Stripe, AWS, Azure, Docker
What does a SaaS platform cost?
It depends on how much the first version already has to do, so we do not name a figure before we know that. At the free initial consultation we work out which functions are genuinely needed for your first paying client. You then receive a fixed price for exactly that scope, and anything added later is agreed separately.
Free initial consultationCan we start with only a few functions?
That is the usual route. Sign-in, separate client spaces and a subscription are enough to serve your first paying client. Everything else is built afterwards around what those clients actually ask for, rather than around a wish list written at the beginning.
How is my clients’ data kept separate?
Depending on the project, each client gets their own data area or their own database. Which route fits depends on how sensitive the data is, how many clients you expect and what you want to guarantee your own clients in your contracts. We settle it at the start, because it can barely be changed afterwards.
Do I own the platform at the end?
Yes. Source code, database and accounts are in your name and you receive all of it. You can take over the hosting yourself later, or hand it to somebody else, without starting from zero.
We have an internal tool. Can it become a product?
Often yes, but rarely unchanged. An internal application knows only one client, namely you. Sign-in, tenant separation, roles and billing all have to be added. We look at what exists and tell you plainly whether converting or rebuilding ends up cheaper.
Do we have to use Stripe?
No. Stripe is frequently the simplest choice for recurring payments, because cards, reminders and invoices are already solved there. If you prefer a different payment service, or want your existing bookkeeping connected, we build that instead.
Tell us what your platform needs to do.
At the free, no-obligation initial consultation we go through who your clients are, what they should be paying for and which first version is enough to get there. We reply within 24 hours.
Book an initial consultationJust a quick question? The AI assistant in the bottom right answers straight away.
Ready for the summit?
Tell us about your project. We reply within 24 hours with an honest assessment. Free and without obligation.
hallo@aurphi.chAurPhi MoukrimMarktstrasse 18, 8853 Lachen SZ, SwitzerlandPostal address, no walk-in service. Appointments by arrangement.