ChatPlus Sales OS GHL Snapshot Build Workspace · v1.1
Builder: Julius (ChatPlus) Snapshot est: ~20–25 hrs 0% complete

Project Overview

GHL snapshot build for ChatPlus Sales OS · Built once in a master sub-account, deployed into N client sub-accounts · Single 7-stage pipeline
Snapshot build est.
20–25hrs
One-time · spec claims 14h
Workflows
29
17 primary + 12 helper engines
Pipeline
1
Single 7-stage pipeline
Email + SMS templates
87
64 email shells + 23 SMS shells
How to use this workspace

This is a self-contained snapshot-build packet. Open the tabs in order:

  1. Flowchart — the 7-stage pipeline and the 29 workflows clustered by stage.
  2. Build Spec — phase-by-phase, workflow-by-workflow execution plan. Build in numerical order.
  3. Action Items — 20 items needed from the client / decisions to lock before and during the build.
  4. Copy Templates — 87 email/SMS shells. Claude can PAT-load email bodies once finalised.
  5. Ops Intel — build economics, burn-down, the shared-field dependency map, risk register, comms.

All progress is stored in your browser. Marking items complete updates the badges in the top nav. No login required.

Build phases
⚠ Gating dependencies (travels with the snapshot)
  • No native workflow loop: the W9a / W10a pause-on-future-booking pattern must be prototyped and signed off first. Action Item #19.
  • Smart Tag drift: Smart Tag rules have a history of not surviving snapshot transfer — verify on every deployment.
  • A2P 10DLC: 1–2 week carrier approval window per client sub-account. File on Day 1 of each deployment.
  • Stripe Connect: authed per client sub-account. Action Item #14. Gates the Invoice Nudge.
  • Sender domain + CSV: client-provided per deployment. Action Items #16–17.

Flowchart

Single 7-stage pipeline · ownership flips Setter → Closer at Discovery Booked · 29 workflows clustered by stage

Build Spec

Full snapshot-build plan · 6 phases · 29 workflows + foundation/config items · Build top-to-bottom
Tick workflows as you complete them. Progress saves automatically.

Action Items

20 items needed from the client / decisions to lock before and during the build · Tick when received · Type response inline
0 of 20 received

Copy Templates

87 templates · 64 emails (Subject / Preview / Body / Attachment) + 23 SMS (Body) · Claude PAT-loads email bodies once copy is finalised
Note for builder

In Phase 1.7 / 1.8, create empty named template shells in GHL matching the names below. The 64 email bodies can be PAT-loaded by Claude once copy is finalised; SMS shells are manual. This tab tracks copy-delivery progress.

Click any template to expand. Drafts save automatically.

Ops Intel

Build economics, burn-down timeline, the shared-field dependency map, risk register, and comms cadence