Flip360 CRM · Live Sign in
Pre-Payment Pilot mode. Real CMs · real providers · real conversations. No money moves until Stripe live-wire (AF-9.5). Every activation carries pre_payment_pilot=1. Pilot status →
Flip360 CRM
Role guide — Platform Admin
Platform Admin (Phase 1: Matt, Phase 2: dedicated) · HUMAN

 Platform Admin — Platform Admin (Phase 1: Matt, Phase 2: dedicated)

I am
the Platform Admin of Flip360. I configure the commission rule engine, I version the rate cards, I onboard new verticals and products, I manage the integrations, I am the super-admin who can see everything and change anything.
I need
a rate card editor with versioning + audit trail, a rule engine UI (PO-configurable per migration 0001), a vertical/product taxonomy admin, integration health (Stripe, Twilio, Pine Lawyers, KYC provider), and a system-wide audit log.
So I can
introduce a new vertical (Trades, Insurance, Legal etc.) within 1 sprint, change commission rules with full version history, and keep the platform configurable without code changes.
So that (financial outcome)
Flip360 scales from 1 vertical to 9 to 19 without engineering bottleneck — which is the unit-economic assumption baked into the FY29→FY31 trajectory.
Who fills this role

Platform Admin (Phase 1: Matt, Phase 2: dedicated) · Platform Admin · Rate Cards · Rule Engine · Super-admin · Human role · PHASE 1 — PRE G4 CUTOVER

The CRM screens I use

  1. Rate card editor (versioned)
  2. Rule engine UI
  3. Verticals + products admin
  4. Integration health dashboard
  5. System audit log
  6. User & role management

My KPIs (every one is linked to the FY31 trajectory)

KPITargetAnchored to (financial source-of-truth)
Time to add new vertical < 1 sprint engagement.tsx WS2
Rate card change cycle time < 1 day engagement.tsx PO-control
Integration uptime ≥ 99.5% engagement.tsx NFRs
What good looks like

Platform Admin adds the Legal vertical Monday. Tuesday it's live with rate card v15 + 3 products. Wednesday Olivia Park signs as a MEMBER. Thursday her first deal flows. Friday her first RCTI issues. One sprint, no code changes.

What bad looks like

New verticals require eng tickets. Rate cards are hard-coded. Adding a product takes a sprint. Configurability is theoretical. Scale stalls.

Who I work with

Back to dashboard Read all 13 roles Switch role
Matt's page