Skip to content

Guide · SaaS

SaaS Development Guide

A SaaS product serves many customer organisations from one system, charges them on a recurring basis and must keep each one’s data separate. This guide covers tenancy, billing and permissions, the three foundations that are hardest to change once customers depend on them.

Tenancy model chosen before the first table

Billing and entitlements kept separate

Permissions designed around customer roles

Before you build

Decisions to make before you build a SaaS product.

01Decide

Tenancy model

One shared database keyed by tenant, separate schemas, or an isolated database for each customer. Shared is cheapest to run; separate databases simplify isolation and data residency but cost more to operate.

02Decide

Who your buyer and user are

Self-serve products sold to individuals by card need fast sign-up and in-app upgrades; products sold to companies need trials for teams, invoices, procurement documents and admin controls.

03Decide

Pricing metric

Per seat, per usage unit, tiered features or a flat fee. The metric should grow with the value customers get, and it decides what you must meter accurately.

04Decide

Permission model

Fixed roles such as owner, admin and member suit most products early; custom roles and resource-level permissions are often needed for larger customers.

05Decide

Enterprise requirements to plan for

Single sign-on, audit logs, data export, regional hosting and security questionnaires appear as soon as you sell to larger organisations. Decide which you will support and when.

Structure

How a SaaS product is structured.

01Layer

Identity and tenant layer

Sign-up, organisation creation, invitations, authentication including single sign-on, and tenant context attached to every request.

02Layer

Authorisation layer

Roles, permissions and checks enforced on the server for every action and query, so one tenant can never read or change another’s data.

03Layer

Billing and entitlements

Plans, subscriptions, trials, invoices, tax and dunning handled with a billing provider, plus an entitlements service that decides which features and limits each tenant has.

04Layer

Core product domain

The workflows customers pay for, built on a data model where every record belongs to a tenant and can be exported.

05Layer

Operations and admin

Internal tools for support, impersonation with consent and logging, usage analytics, feature flags, monitoring and backups.

Planning sequence

A planning sequence for a SaaS product.

  1. 01Step 1

    Define the tenant and role model

    Write down what an organisation is, which roles exist and what each can do before designing screens. Changing these later touches every query.

  2. 02Step 2

    Choose the pricing metric

    Test pricing with prospective customers early and decide what must be metered. Billing logic is easier to build once than to retrofit.

  3. 03Step 3

    Design onboarding to first value

    Map the steps from sign-up to the moment a new customer sees results, such as importing data or inviting colleagues, and remove friction there first.

  4. 04Step 4

    Build isolation tests in from the start

    Automated tests that try to access another tenant’s data should run on every change. Isolation failures are the most damaging bugs a SaaS can ship.

  5. 05Step 5

    Add enterprise features with demand

    Add single sign-on, audit logs and custom roles when real deals need them, but keep the data model ready so they are not rewrites.

Mistakes

Mistakes that derail a SaaS product.

01Avoid

Bolting on multi-tenancy later

Products built for one customer and then shared across many tend to leak data through forgotten queries. Tenant context belongs in the data model from day one.

02Avoid

Hard-coding plans into features

Checks like if plan equals pro scattered through the code make pricing changes slow and risky. A central entitlements layer keeps billing and features apart.

03Avoid

Permissions checked only in the interface

Hiding a button does not stop someone calling the API. Every permission must be enforced on the server.

04Avoid

Ignoring failed payments

Cards expire and payments fail. Without automatic retries, reminder emails and grace periods, avoidable churn quietly eats revenue.

Tenancy is a foundation, not a feature

Every SaaS product must answer a simple question on every request: which customer organisation is this for, and is this user allowed to do this? Building that into authentication, data access and caching from the beginning is far easier than adding it later.

The physical model (shared tables, schemas or databases) can evolve, but the logical model should not. If every record carries a tenant identifier and every query is scoped, moving a large customer to its own database later is an operational task rather than a rewrite.

Billing and entitlements

Billing tells you what a customer has paid for; entitlements tell the product what to allow. Keeping them separate lets you change prices, run trials, grant exceptions to key accounts and migrate plans without touching feature code.

Choose a pricing metric you can measure reliably and that customers understand. Usage-based pricing needs accurate metering, clear usage views for customers and alerts before limits are reached, or it generates disputes.

Permissions that fit real organisations

Customers are teams with different responsibilities. Start with a few clear roles and enforce them on the server. As larger customers arrive, they will ask for custom roles, team-level access and approval steps.

Design the permission system so it can grow: actions defined centrally, roles as collections of actions and checks in one place. Log permission changes, since administrators will need to know who granted access to whom.

Onboarding and activation

Recurring revenue depends on customers reaching value quickly and staying. Map the activation steps (connecting data, inviting colleagues, completing a first workflow) and measure where new accounts stall.

Templates, sample data, guided setup and import tools often do more for retention than new features. For products sold to companies, an admin who can set things up for their whole team is a key user to design for.

Operating a SaaS product

Customers expect the service to be available, fast and secure all the time. Monitoring, alerting, backups that are tested by restoring them and a clear incident process are part of the product, not extras.

Support teams need safe internal tools: viewing a customer’s configuration, impersonating a user with consent and logging, and adjusting entitlements. Without them, engineers become the support desk.

What drives SaaS cost

Cost rises with the tenancy model, the number of integrations, enterprise features such as single sign-on and audit logs, data residency in several regions and the depth of reporting customers expect.

Ongoing spending includes hosting that grows with customers, third-party services billed per seat or usage, security work and compliance audits. Tracking cost per tenant early shows whether pricing covers the customers you are winning.

FAQ

Questions to resolve before the build.

01Which tenancy model should we choose?

A shared database with strict tenant scoping suits most early products because it is cheaper and simpler to operate. Separate databases make sense when customers require isolation, regional hosting or very different scale. Some products mix the two for their largest customers.

02Should we build billing ourselves?

Rarely. Billing providers handle subscriptions, proration, invoices, tax calculation in many regions, card updates and failed payment retries. You still need your own entitlements logic and a record of what each tenant is allowed to use.

03When do we need single sign-on?

Usually when selling to larger organisations, whose IT teams expect users to sign in through their identity provider. It is often a requirement in security reviews. Supporting standard protocols such as SAML or OpenID Connect avoids custom work per customer.

04How do we handle customer data requests?

Plan for exporting a tenant’s data, deleting it when a contract ends and answering individual requests under data protection law. A data model where every record has a clear tenant owner makes this practical.

05What security standards do buyers ask about?

Larger buyers often ask about SOC 2 or ISO 27001 and send detailed questionnaires. You do not need certification on day one, but good practice in access control, logging, encryption and backups makes later audits much easier.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
  2. 02
  3. 03

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.