Account Assignment Engine · Revenue Enablement

How accounts move
through the machine

Owner confirmed Owner TBD
Carved out — never enter
Partnerships · SUD · TAD stay manually managed, upstream of the engine
All SF Referral Accountsevery account enters the waterfall
01

Pre-Run Setup

Build the eligible pool and tell the machine what it’s running
Run Config Owner TBD Options ↓
Growth Strat
Sets scope — global / region / single rep / churn / new-starter class — plus params & covered-states map
eligible pool — churned + non-productive books surfaced in
02

Lock Lists from Reps

Each rep’s protected keep-list, settled before anything redistributes
Rep Input Owner TBD Options ↓
Reps · GS caps
L3M referrers auto-lock + 5 dormant / 5 never-referred picks · hard cap at book size (100)
locks hold — everything else stays in the pool
03

Assignment Algorithm

NSGA-II — Phase 2 referring balance (opps + BPS + TAM), Phase 3 value distribution
Optimizer DS — Van + JC
Data Science
Covered states hard · drive-time soft · capacity 100 hard · ties → the better-performing rep
Unplaced overflow
→ Inside Sales — ARM · Growers · Activators. No account goes unworked
proposed books — up to 100 accounts per rep
04

RD Review Lists

Full before / after diff per rep, a reason attached to every move
Manager Review Owner TBD Options ↓
Regional Directors
±5 add / drop per rep book — judging morale, disruption, and edge cases the data can’t see
05

GS Review

Region-level validation and sign-off — the final human gate
Region Sign-Off Owner TBD Options ↓
Growth Strat
Minimal pass, no ± bound — validates books are sound before anything writes
approved diff
06

Final Assignments → Salesforce

API write-back to the Account Owner field — nothing else, no custom objects
System Write BizSys — Sam
BizSys
“The last mile” — confirmed in the Jun 10 sync; lives inside the SF codebase
New Books Live in SFquarterly rotations + event-driven re-runs repeat the loop
The Open Builds

How the undecided modules get built

Build options per module, from the assigner syncs — owner decision pending with Sebastian
01

Pre-Run Setup

Run-config front end — lean still open
  • Hex-hosted vibe-coded app — writes values to a G-sheet
  • Standalone vibe-coded UI
  • Salesforce-native interface
  • G-sheet
  • Command line
02

Lock Lists from Reps

Collection interface — keep / don’t-keep with decision stats
  • Hex-hosted vibe-coded app — writes values to a G-sheetLean
  • Standalone vibe-coded UI — writes values to a G-sheet
  • Salesforce-native interface
  • G-sheet
04

RD Review Lists

Diff review + bounded add / drop overrides
  • Hex-hosted vibe-coded app — writes values to a G-sheetLean
  • Standalone vibe-coded UI — writes values to a G-sheet
  • Salesforce-native interface
  • G-sheet
05

GS Review

Region-level sign-off — lightest of the four
  • Hex — review dashboard + sign-offProbably this
  • A few other routes possible — not worth speccing until the RD review surface lands
Source: Account Assignment Engine PRD (§3, §8) · BizSys <> Outreach sync, Jun 10 — owners as discussed; interface ownership pending (Sebastian)