What Jackie's weekly operating view looks like once 3-4 modules are live. Every metric is illustrative - real numbers populate from GHL, LinkedIn, and the platform's Friday report. This is the interface, not the data.
The dashboard is a product of the modules, not a standalone tool. Build order follows module delivery.
| Phase | Trigger | What gets added to the dashboard |
|---|---|---|
| Pre-requisite | GHL already live (Jackie uses it today) | CRM pipeline view - existing data visible now. No build needed, just a clean read-only display. |
| Month 1 | LinkedIn outbound running (M6) + Review agent live (M3) | Pipeline funnel (connections to bookings). Review score tracker. Activity feed. These 3 panels populate with real data from M6 + M3. |
| Month 2 | Sales agent deployed for first 2-3 Jackie clients (M7) | Sales agent performance panel: leads captured per client, bookings generated. This becomes Jackie's renewal conversation data. |
| Month 3+ | All 7 modules live and generating signals | Full cockpit: module health strip (live vs in-build vs scoped), churn signal from CRM, weekly LinkedIn + YouTube + email performance combined. |
A dashboard is only as good as the data feeding it. Before month 3, Jackie has two live data sources: GHL (CRM) and LinkedIn (outbound). That is not enough panels to justify a full cockpit. Building it prematurely means showing empty panels and explaining why they're empty instead of showing results. The sequence is: modules prove value individually, the dashboard surfaces that value once it's real. Jackie sees the mockup now to understand the destination - not to use it today.