Core Principle
Sales manages the commercial relationship. Fulfillment pipelines manage operational delivery. Completion transitions the client into retention, referral, and future offers.
One client, multiple opportunities
Do not force everything into a single opportunity. A client can have a Sales Opportunity (the original transaction) plus one or more Fulfillment Opportunities (Credit Repair, Document, Tradeline, Funding) running in parallel. When the client re-engages, create a new Sales Opportunity rather than reopening the old one — this preserves accurate lifetime revenue, close-rate, and retention reporting.
graph LR
A[ATTRACT] --> B[CONTACT] --> C[BOOK] --> D[QUALIFY] --> E[SELL] --> F[CONTRACT]
F --> G[COLLECT] --> H[ONBOARD] --> I[ROUTE] --> J[FULFILL] --> K[COMPLETE]
K --> L[REVIEW] --> M[REFER] --> N[RETAIN] --> O[RESELL]
style A fill:#7CFF00,color:#000,stroke:#000
style O fill:#7CFF00,color:#000,stroke:#000
style K fill:#111,color:#7CFF00,stroke:#111
Drag to scroll
Current Account State
Three pipelines, 35 workflows across two teams, and 143 custom fields are already in the account. The gap analysis below shows what still needs to be built.
| Pipeline | Stages | Built by | Status |
|---|---|---|---|
| BMF Sales Pipeline | 9 | VisionPlay CRM | Live |
| Credit Readiness Fulfillment | 13 | Other team | Live |
| Customer Support Tickets | 6 | Other team | Live |
| Document / Approval Pipeline | — | — | Not built |
| Tradeline Pipeline | — | — | Not built |
| Funding Pipeline | — | — | Not built |
| Category | Count | Built by | Status |
|---|---|---|---|
| BMF v2 workflows (sales + lead nurture) | 18 | VisionPlay CRM | Live / Published |
| BES fulfillment workflows | 10 | Other team | Mix of draft + live |
| Custom fields (contact + opportunity) | 143 | Both teams | Audit needed |
| Package routing engine | — | — | Not built |
| Retention workflows (6) | — | — | Not built |
| Stale opportunity governance | — | — | Not built |
| Completion controller | — | — | Not built |
Sales Pipeline
The architecture proposes a more granular Sales pipeline. The table below maps each proposed stage to the current stage and the action needed.
| # | Proposed Stage | Current Stage | Action |
|---|---|---|---|
| 1 | Hot Lead | New Intake | Rename |
| 2 | Attempting Contact | Missing | Add stage |
| 3 | Contacted / Nurture | Contacted | Rename |
| 4 | Booked | Profile Review Booked | Rename |
| 5 | No Show | Handled by workflow | Decide: add stage or keep as tag |
| 6 | Qualified / Package Selected | Review Completed | Rename |
| 7 | Agreement Sent | Agreement Sent | Keep |
| 8 | Agreement Signed | Missing | Add stage |
| 9 | Payment Pending | Missing | Add stage |
| 10 | Onboarding Pending | Missing | Add stage |
| 11 | Won / Routed to Fulfillment | Won / Enrolled | Rename |
| 12 | Lost / Not Qualified | Not a Fit | Rename |
| — | Not in proposal | University Enrolled | Decision needed |
| — | Not in proposal | Nurture | Decision needed |
Before renaming stages
Any contact currently in a stage will stay there after a rename. But any workflow trigger or condition referencing a stage by name must be updated. Confirm with the team which workflows reference pipeline stages before modifying the pipeline.
Package Routing Engine
When a Sales opportunity reaches "Won / Routed to Fulfillment," the routing engine reads the Package field and creates the correct fulfillment opportunities automatically. This matrix must be finalized from BMF's actual agreement templates before it can be automated.
| Package | Credit Repair | Document | Tradeline | Funding |
|---|---|---|---|---|
| Inquiry Removal | ||||
| ChexSystems + EWS | ||||
| Standard Approval | ||||
| Standard Housing | ||||
| Standard Vehicle | ||||
| Reconsult | ||||
| Restore | ||||
| Homeowner | ||||
| Car Owner | ||||
| Restore + Advanced | ||||
| Capitalized | ||||
| Mentorship |
This matrix should be confirmed against actual BMF service agreements before being wired into GHL automation.
Master Data Model
GHL supports both contact-level and opportunity-level custom fields. The architecture uses this distinction to keep per-transaction data on the opportunity (where it belongs) and lifetime client facts on the contact.
Contact Level
Facts true across all transactions
- Lead Source
- Preferred Contact Method
- Referral Source
- Client Lifecycle
- Original Acquisition Date
- First Purchase Date
- Last Purchase Date
- Lifetime Client (flag)
- Testimonial Status
- Referral Status
- Alumni Status
- Next Best Offer
- Overall Client Fulfillment Status
Sales Opportunity Level
Per-transaction data
- Package
- Price
- Payment Type
- Program Term
- Agreement Status
- Payment Status
- FanBasis Transaction ID
- Onboarding Status
- Required Fulfillment Routes
- Sales Agent
- Lost Reason
Fulfillment Opportunity Level
Per-department delivery data
- Parent Sales Opportunity Ref
- Package
- Fulfillment Type
- Fulfillment Status
- Hold Reason
- Assigned Specialist
- Start Date / Completion Date
- Outcome
- Next Action
- Previous Active Stage
Key lifecycle field values
Client Lifecycle
- Prospect
- Active Sales
- Active Client
- Fulfillment Hold
- Completed Client
- Alumni / Retention
- Re-Engaged
- Former Client
- Terminated
Overall Fulfillment Status
- Not Started
- Active
- Partially Completed
- Waiting on Client
- On Hold
- All Required Routes Completed
- Terminated
Phased Build Plan
Alignment Call
- Decide which workflow folder is active (BMF v2 vs. BES)
- Confirm no contacts are mid-sequence before any edits
- Finalize confirmed package list from agreements
- Confirm Credit Readiness pipeline is the Credit Repair route
- Assign conditional fields ownership
Data Model Cleanup
- Audit 143 existing fields against the 3-folder model
- Add missing contact-level fields (Client Lifecycle, Next Best Offer, lifecycle dates)
- Add Sales Opportunity-level fields
- Add Fulfillment Opportunity-level fields
- Configure conditional fields per stage (GHL Aug 2026 feature)
Pipeline Expansion
- Update Sales Pipeline to 12-stage structure (team sign-off required)
- Create Document / Approval Fulfillment Pipeline
- Create Tradeline Fulfillment Pipeline
- Create Funding Fulfillment Pipeline
Routing Engine
- Build "Won → Route to Fulfillment" workflow
- Read Package field on Sales opp, create correct fulfillment opp(s)
- Wire Package routing matrix (finalized from Phase 1)
- Dedup check: skip if open Sales opp already exists for contact
Fulfillment Route Workflows
- Credit Repair route automation (Credit Readiness pipeline — 3-day hold)
- Document / Approval route automation
- Tradeline route automation
- Funding route automation
- Multi-completion controller: all required routes done → trigger exit sequence
Retention Engine
- RETENTION 01: Client Completion exit sequence
- RETENTION 02: Testimonial Request (post-completion)
- RETENTION 03: Referral Request
- RETENTION 04: 30/60/90-Day Client Check-In
- RETENTION 05: Long-Term Alumni Nurture
- RETENTION 06: Re-Engagement to New Opportunity
Stale Governance
- Stale trigger per pipeline (Sales + 4 fulfillment)
- Alert → internal task → escalation chain
- No auto-moves: stale = human action required
Target State
- 5 pipelines (Sales + 4 fulfillment)
- ~30–35 verified custom fields (contact + opp level)
- ~30 workflows (current 18 + routing + fulfillment + retention + stale)
- Conditional fields per pipeline and stage
- Full lifecycle tracking from lead to alumni
System Relationship
graph TD
C([Contact]) --> SO1[Sales Opportunity #1\nPackage Purchased]
SO1 --> FO1[Fulfillment: Credit Repair\nCredit Readiness Pipeline]
SO1 --> FO2[Fulfillment: Documents\nDocument Pipeline]
SO1 --> FO3[Fulfillment: Tradeline\nTradeline Pipeline]
SO1 --> FO4[Fulfillment: Funding\nFunding Pipeline]
FO1 & FO2 & FO3 & FO4 --> CC{Completion\nController}
CC -->|All routes done| RET[Retention Engine\nTestimonial → Referral → Alumni]
RET --> SO2[Future Sales Opportunity #2\nNew Purchase / Upgrade]
SO2 --> C
style C fill:#7CFF00,color:#000,stroke:#000,font-weight:bold
style CC fill:#111,color:#7CFF00,stroke:#111
style RET fill:#f6f7f5,color:#111,stroke:#ccc
Scroll / pinch to zoom
Alignment Questions
Which workflow folder is the active one — BMF v2 (VisionPlay CRM) or BES (other team)? Both have overlapping sequences (booking confirmation, no-show recovery, onboarding). Are we merging or replacing?
Are any contacts currently enrolled in live workflows? If yes, which ones — to avoid disrupting active sequences before the merge is decided.
Is the Credit Readiness Fulfillment pipeline being used for active clients today, or is it still in setup?
What is the confirmed package list from BMF's current agreement templates? The routing matrix needs the exact package names before it can be automated.
Who owns the conditional fields configuration — the other team or VisionPlay CRM? This determines who builds Phase 2.
What is the target go-live date for the full system?