04 — SaaS Product Development
Subscription software, built and actually operated
Multi-tenant products designed, built and run end to end — including our own, which other businesses pay to use every month.
The hard part of SaaS is not the first screen. It is the second tenant — the point where one customer’s data must be provably invisible to another, where billing has to survive a failed card, and where a bug does not mean one angry user but every user at once.
We build multi-tenant products with that in mind from the first migration: data scoped per tenant at the database level, payments routed to each tenant’s own account, and the operational rails — audit trails, backups, monitoring — treated as features rather than afterthoughts.
We also operate our own. Murielle Beauty Cloud gives beauty professionals their own booking site and shop, each connecting their own payment account. Running a product teaches you things that building one for someone else does not.
What you get
Multi-tenant from the first migration
Tenant isolation enforced in the database, not just in application code. Retrofitting this later is one of the most expensive mistakes in SaaS.
Subscriptions and billing
Plans, trials, upgrades, failed payments and dunning — the parts that decide whether revenue actually arrives.
Per-tenant payment accounts
Where your model needs it, each tenant connects their own processor and receives their customers’ money directly. That changes your regulatory position, for the better.
An admin surface for you
Tools to onboard, support and unblock a tenant without a developer and without raw database access.
Operational rails
Audit logging, backups, monitoring and a migration path — so the second year is not a rewrite.
How it works
The shape of the product
Who the tenant is, what they pay for, and what the first version must do to be worth paying for.
Architecture and a written scope
The tenancy and billing model decided on paper first, because both are painful to change later.
Build in slices that ship
Working software in stages you can show people, rather than a big reveal at the end.
Operate, or hand over
We can run it, or hand it over with the documentation to run it yourself. Your call, not ours.
Running in production
Murielle Beauty Cloud is our own multi-tenant platform: independent beauty businesses each get a booking site and shop, each connecting their own payment account. myVitalHarmony is a second platform built on the same principles. myvitalharmony.com ↗
Common questions
Will you build an MVP or the whole product?
Whichever is honest for where you are. If you have not proven anyone will pay, a smaller first version that reaches real users is worth more than a complete one that reaches nobody. If you already have paying users, building for the second year rather than the first month is the cheaper path.
Who owns the code?
You do. Source code, infrastructure and every account are in your name, the same as every other build we do.
Can you take over an existing codebase?
Often, yes. That starts with a paid review so we can tell you honestly whether it is worth continuing or whether you are better off rebuilding a part of it — a judgement that is unfair to make for free and unwise to make quickly.
What does it cost?
Scoped per build and quoted in writing. SaaS work varies too much for a list price, and a number given before the scoping conversation would only be a guess dressed as a quote.