Services/SaaS development
SaaS that’s ready for paying customers.
One app serving many customers, each in their own workspace, with roles, billing, admin and an API. Built so your first big customer doesn’t force a rebuild.
tenant_id = 'harbour'Included in every SaaS
What every SaaS needs.
Every first release we build includes these. They’re quick to get right at the start and expensive to add later.
Organisations, invitations and seats.
Owner, admin, member, or your own.
Google, Microsoft and SAML for enterprise.
Plans, trials, proration and invoices.
See accounts, fix data, help customers.
Who changed what, and when.
What customers use, and where they stop.
Onboarding, receipts and notifications.
For your apps and your customers.
Uploads kept per tenant, access-checked.
Automatic, with a tested restore.
Errors and slow pages caught first.
Architecture
How the layers fit together.
Choose a layer to see what we build in it.
Multi-tenancy
Each customer’s data, kept apart in the app and in the database.
How we choose between shared tables, schemas and separate databases.
In production
Estimark runs on these foundations, with paying customers.
Web, iPhone and Android, one backend.
Build log
More on building SaaS
What goes into a SaaS MVP, and what waits
An MVP is the smallest product someone will pay for, not the smallest product you can build. Here is what belongs in the first release and what can wait for real users.
SaaS security before your first enterprise customer: what buyers ask
Large customers send a security questionnaire before they sign. Have MFA, tested backups, an incident plan, Cyber Essentials, a recent pen test and a data processing agreement ready first.
Multi-tenancy: how a SaaS keeps each customer’s data apart
Every SaaS has to answer one question early: how is one customer’s data kept away from another’s? There are three common answers, each with different costs.