Illustrative scenario

Illustrative scenario: an operator running nine firms under their own brands

Canadian accounting professionals — Illustrative scenario: an operator running nine firms under their own brands

An operator supporting nine independent bookkeeping firms has two requirements and no third: each member firm's clients must see that firm's brand and nothing else, and no member firm's data may ever be reachable from another. Everything else — plans, limits, provisioning — is administration.

Updated July 2026

The firm in this scenario

An archetype, not a client. The figures below describe the shape of the practice being modelled — they are inputs to the scenario, never results.

Firm profile — A nine-firm white-label network
AttributeDetail
ArchetypeMulti-firm operator running a branded network
LocationMulti-province (national)
Firm sizeAn operator supporting nine independent bookkeeping firms
Client profileEach member firm holds its own client base under its own brand
  • Super-admin provisioning
  • Per-tenant theming
  • Tenant isolation
  • Audit log

The problem

Each member firm wants its own name, logo and colours in front of its own clients. A shared platform whose brand shows through defeats the arrangement.

The operator needs provisioning and oversight without living inside member accounts, because 'the operator can see everything' is exactly the concern a member firm raises first.

The workflow, step by step

  1. 1

    Provision each firm as a tenant

    The super-admin console creates each member firm as its own tenant with its own plan and limits.

    Super-admin provisioning

  2. 2

    Theme each tenant end to end

    Name, logo, colours, letterhead and email sender are per-tenant, so the member firm's clients see the member firm across app, email and documents.

    Per-tenant white-label branding

  3. 3

    Isolate at the row level

    Tenant isolation is enforced in the data layer, not by a filter in the interface. Every member firm's data stays inside its own boundary.

    Row-level tenant isolation

  4. 4

    Oversee without occupying

    The operator manages plans and limits and reviews an append-only action log, rather than working day to day inside member accounts.

    Audit log

What this changes

Operators in this position typically evaluate exactly two things: whether the isolation is real, and whether the member firm's clients ever see the platform's name. This architecture is built so the answers are yes and never.

About this scenario

Start running a tidier, deadline-proof practice.

Set up your firm in minutes. No credit card to start.