Bayside  /  Case Studies /  Insurance White-Label Platform
Custom softwareWhite-labelInsuranceIn production

A white‑label platform for insurance agencies.

The outbound operation behind our SMS revenue platform wanted to sell it to the insurance agencies it serves, not just use it. We rebuilt it as a white-label system: every agency gets an isolated account of its own, while the operator keeps control of numbers, messaging and margin.

1
Codebase
Every client account, one platform
7,000+
New leads, one client
In a single week
$3.8M
Pipeline, same client
Added that week
3-step
Client sign-in
Password, authenticator, passkey
01 — The problem

Good enough to sell.

The platform was producing leads at a volume the operation's clients wanted for themselves. But every client needed their own leads, agents and bill, and no client could ever see another's data.

Constraints we designed around
  • Every client's data fully isolated
  • The operator keeps numbers, messaging and costs
  • Each client billed at its own rate
  • New clients set up without engineering work
  • Prospects can try it before they buy
02 — The system

One codebase. An account for every client.

Clients log into their own account. The operator runs all of them from one place.

ops.yourcompany.com/leads
A client account's Lead Database in the white-label platform, with leads classified from their text replies
A client account's lead database, shown with demo data.
01

An isolated account per client

Every query is scoped to the client, with row-level security underneath.

02

Operator control

Numbers, messages, send windows and rates stay with the operator.

03

Self-serve outbound

Clients upload a list and pick dates and agents. The rest is preset.

04

Per-client AI

Each account gets its own AI inbox prompts and pipeline settings.

05

Usage billing

Per contact, at each client's own rate. Carrier costs stay private.

06

Live demo accounts

Prospects open a full demo account with no login. It clears after 24 hours.

Who sees what.

Four roles, each seeing only what it should.

IOperator
Every client account · Numbers and senders · Rates and margin · Open as client
IIClient owner
Their leads and inbox · Their campaigns · Their agents · Their team
IIIClient team
Admins and members · Same account, scoped access
IVAgents
Routed leads by sheet and SMS alert · Weekly caps
03 — Launching a client

From one form to a live account.

No code changes and no new deployment. The operator fills in a form and the account is ready.

The steps
  1. The operator enters the client's name, address and owner email; defaults fill in
  2. The owner gets an invite link and signs in with a password, an authenticator code and a passkey
  3. The operator assigns sending numbers and presets the message
  4. The client uploads a list, picks dates and agents, and leads land in their account
04 — The results

Built for one operation, sold to many.

The same platform runs the operator's own campaigns and a roster of client accounts, from one codebase and one database.

It worked well enough that we've shipped the pattern again: a lead-ops console that deploys under a partner's name, color and logo, from the same commit.

One client · one week
Billed for usage
$7.8K
New leads produced
7,000+
Projected sales
$200K+
Pipeline added
$3.8M
The platform behind it →
Your platform, next

Software you can run yourself, or resell.

We'll scope the version built around your business, under your brand.