Six workspaces. 54 families. One database.

Steps mix a path (/pricing) with events (signup started, organization created) because both live in the same events table.

Audience

Trial ended, last seen > 14d

Channel

Email

Snapshotted

1,284 people

Awaiting approval A second operator has to approve before anything is sent. Delivery rows record each message.

1. ifplan is one of team, businesson
2. else ifcountry is DEoff
3. elseeveryone else25% rollout, hashed on distinct id

const enabled = await spm.flags.isEnabled("new-onboarding");

The browser and the server bucket a person identically: both hash the distinct id with the same murmurhash3_32 from @saaspro/shared.

Quality gate: score ≥ 0.85, failures ≤ 5% — passed

Which release dropped checkout conversion?

web@2026.9.1. The pricing funnel fell 4.1 points; 38 people hit ERR_CHECKOUT_TIMEOUT. Flag checkout.edge is at 25%.

Answers only from this application's data, with the same permissions the operator holds. Enabling the module requires at least one data module to read.

Six adapters: Meta CAPI, Google Ads (click conversions or GA4), TikTok Events, LinkedIn Conversions, a signed webhook, and Slack. Emails and phone numbers are SHA-256 hashed before they leave; the raw IP never existed to send.

import { createConnectorHandler } from "@saaspro/node";

export const POST = createConnectorHandler({
  publicKey: process.env.SPM_CONNECTOR_PUBLIC_KEY!,
  audience: process.env.SPM_APP_ID!,
  handlers: {
    listUsers, getUser, applyControl,
  },
});

• GET /health capabilities the console may use
• GET /users paged, filtered, PII redacted unless the caller holds people.pii.read
• GET /users/{id} dossier: facts, activity, available controls
• POST /users/{id}/controls a reversible action, with a reason