<aside> 🔄
This updates the original Counselors Review. After exploring the Onboarding Pipeline database, Operations Tasks database, Technical Implementation Hub, and the full SOP, the picture has changed significantly. The pipeline system addresses several gaps that the original 6-document plan did not.
</aside>
The original review evaluated 6 documents (Internal SOP, Client Onboarding main page, Day 1, Day 2/Session 1, Day 30, What to Expect guide). Those documents described a session-based cadence with a 30-day roadmap.
The system that was actually built is fundamentally different:
| Dimension | Original 6-Document Plan | Actual Pipeline System |
|---|---|---|
| Tracking | No database. Session agendas on pages. | Two linked Notion databases: Pipeline (per-client) + Operations Tasks (per-step). Formula-driven status rollup. |
| Steps | 4 sessions (vaguely defined) | 17 discrete onboarding steps with subtask databases inside each task |
| Dependencies | None | Blocked By / Blocking self-relations. 4 critical paths defined. |
| Phases | Day 1 → Day 30 | P1 (Pre-Onboarding) → P2 (Onboarding, 12 steps) → P3 (Post-Launch, 5 steps) |
| Launch Date Tracking | "Day 30: The Finish Line" | Original Launch Date (frozen baseline) + Estimated Launch Date (living) + Actual Launch Date + Change Log with reasons |
| Status Granularity | None | 6 status levels per task (To Do, In Progress, Waiting on Client, Waiting on Us, Blocked, Complete) with color coding |
| Scope Management | One-size-fits-all | Onboarding Type (Full, Email Only, SMS+Email, Migration) determines which of 17 steps apply |
| Cadence | 2 sessions/week (calendar-driven) | 8 structured sessions mapped to phases + 6 parallel swim lanes (Client, CS, Engineering, Merchant, SMS/Email, HubSpot Automation) |
| Red Flags | None | Defined warning signs: >15 days at <50% completion, any step "Waiting on Client" >7 days, anything "Blocked", shortcode not started Week 1 |
| Root Cause | Original Plan | Pipeline System | Remaining Gap |
|---|---|---|---|
| Inventory file chain | ~35% | ~65% | Import File Setup is step 1 with subtasks and dependency tracking. Still missing: CMS-specific export playbooks, downloadable template at contract signature. |
| Payment/treasury | ~15% | ~60% | Merchant Onboarding is a named step (P2) on a parallel critical path (Document Uploads → Merchant → IVR). Tech Hub tracks Implementation Pillar "Merchant App" separately. Still missing: treasury stakeholder named before kickoff. |
| Wrong stakeholders | ~35% | ~45% | Step 0 Kickoff Meeting involves Ops Manager + CS + Sales. Owner assigned per client. Still missing: RACI matrix, decision-maker attendance requirement, escalation for absent stakeholders. |
| Sales handoff | 0% | ~30% | Step 0 Kickoff Meeting covers scope, Onboarding Type, and special requirements. Sales joins "as needed." Still missing: formal handoff artifact, product fit validation, what-was-sold documentation. |
| Reactive sessions | ~50% | ~75% | 8 structured sessions mapped to phases. 4 critical paths with formal Blocked By relations. Subtask-level status tracking. Still missing: hard prerequisite gates (sessions can still proceed when blockers aren't resolved), automated enforcement. |
<aside> 📈
Revised overall coverage: ~55% (up from ~30% in the original plan). The pipeline system is a genuine operational improvement, not just a packaging upgrade.
</aside>
The Blocked By / Blocking self-relations on Operations Tasks create a formal dependency graph. The 4 critical paths are explicitly defined:
The Pipeline database's 17 status columns and 17 deadline columns are formula fields that pull automatically from linked tasks. No manual status updates on the pipeline — update the task, the pipeline reflects it. This eliminates the "status meeting about status" problem.