Strategic Blueprint
Strategic Architecture Proposal
GST Business Operating System
Critical Module Consolidation & Revenue Optimization Architecture
Executive Summary
GST Financial Services possesses a structurally sound foundation for event marketing and lead capture. However, the current dashboard architecture suffers from "module sprawl"—over 40 disjointed navigation items, redundant prospect interfaces, and isolated AI features that force field builders to context-switch constantly.
This fragmentation dilutes focus from revenue-generating activities. This document outlines a radical consolidation strategy: merging fragmented tools into a single Unified Prospect Lifecycle System, transforming standalone AI pages into embedded contextual agents, and establishing a Field Builder Command Center that dictates daily execution.
The overarching goal is to transition the platform from a collection of isolated tools into a "Revenue-First Operating System" that actively drives appointment bookings, policy closures, and recruiting velocity through forced discipline and background automation.
System Consolidation & Master CRM Architecture
The Unified Prospect Lifecycle Concept
Currently, a field builder views a list of prospects in one module, moves them in a pipeline in another, logs activities globally, and visits a separate AI page to write a follow-up. This must stop.
Architecture Consolidation Directives
- Eliminate Duplicate Entry: Establish a single, global
<MasterProspectModal />. Whether added from an event, manual entry, or referral hub, all paths must point to this single component to ensure universal data hygiene. - Merge CRM Views: Combine
GSTProspectCRM(List) andCRMPipeline(Board) into a single module with a view-toggle. - Embed Activities & Tasks: Global logs are an anti-pattern.
Activities LogandTaskManagementmust be archived as standalone pages and rebuilt as embedded tabs directly inside the Prospect Detail View. - Demote Standalone AI: Archive
AIFollowUpandAIAppointmentsas navigation items. AI must be a background service or contextual button inside the CRM.
Priority-Based Module Classification
| Priority | Module / Feature | Business Impact Justification |
|---|---|---|
| CRITICAL | Master CRM (List + Pipeline) | Directly tracks money in motion. Without a unified view, follow-ups drop and deals die. |
| CRITICAL | Event Manager & RSVPs | The primary top-of-funnel engine for both new recruits and client prospects. |
| CRITICAL | Calendar Sync (App Connectors) | Reduces friction to closing. Disconnected calendars lead to missed FNAs and lost revenue. |
| HIGH | Fast Start / Onboarding Engine | Ensures new recruits get licensed and write their first app within 30 days (Retention). |
| HIGH | Command Center Dashboard | Forces daily execution discipline: "Who do I call today?" |
| MEDIUM | Campaign Analytics | Supportive for leadership to double down on high-ROI lead sources. |
| MEDIUM | Team Tree & Leaderboard | Gamification and visibility for upline management and motivation. |
| LOW | Standalone AI Pages | Cosmetic distraction; must be embedded directly into workflow to be useful. |
Gap Analysis (A-to-Z)
1. Email Communication BlockadeURGENT
Risk: Base44 native email cannot send to external prospects. Automated email follow-ups fail silently.
Fix: Integrate Resend via backend function. Route all `NotificationLog` email requests through this new provider.
2. Stale Lead / Funnel LeakageURGENT
Risk: Prospects sit in pipeline stages forever if a builder forgets them. Massive revenue left on the table.
Fix: Build a CRON background automation: If Stage="Invited/Follow-up" AND No Activity in 72hrs -> Auto-send SMS to prospect & trigger Task for builder.
3. Disconnected Activity TrackingHIGH
Risk: System sends automated SMS, but field builder looking at the CRM has no record of it on the timeline.
Fix: Update `sendSMS` and `submitRSVP` functions to inherently create an `Activity` entity record tied to the Prospect.
4. Duplicate Automation RiskHIGH
Risk: Two active CRON jobs (5m and 15m) are fighting to process the SMS queue, risking duplicate sends.
Fix: Archive the legacy 15-minute `processEventReminders` automation immediately.
5. Missing Calendar IntelligenceMEDIUM
Risk: Double-entry of appointments leads to friction and missed meetings.
Fix: Implement Google Calendar & Zoom OAuth via App Connectors. Build UI to schedule directly from the Prospect record.
Contextual AI Embedded Workflow
AI fails when it is a separate "tool" you have to remember to use. It succeeds when it is invisible infrastructure that assists existing habits.
1. Background Enrichment
Trigger: Prospect Creation.
Logic: `InvokeLLM` runs silently, evaluating data (job, email domain) to auto-populate `Priority`, `Persona`, and `Estimated BV` fields on the CRM card.
2. Contextual Scripting
Location: Prospect Detail View.
Logic: A single "Auto-Draft SMS" button. Click passes the entire `Activity` timeline to LLM, returning a highly contextual, personalized message ready to send.
3. Next Best Action (NBA)
Location: Command Center Dashboard.
Logic: AI evaluates lead scores and staleness to surface exactly 5 prioritized tasks daily: "Call John (Hot Lead, attended yesterday)" or "SMS Sarah (No contact in 5 days)".
Recruitment & Retention Engine
To increase associate licensing and production speed, the system must enforce visibility and discipline.
- Fast Start Dashboard: A dedicated widget showing exactly where a new recruit is in their first 30 days (Licensed? FNA complete? First policy written?). Red/Yellow/Green health indicators.
- Team Tree Motivation: Upline visibility into downline activity metrics (not just sales, but calls logged and RSVPs generated).
- The Command Center Model: The first page a builder sees upon login is NOT a chart of past performance, but a clear, gamified list: "Here are your 10 tasks to make money today." If they don't complete the tasks, the system flags their upline.
Phased Implementation Roadmap
Phase 1: Stabilization & Comms (Weeks 1-2)
- • Archive duplicate CRON automations.
- • Integrate external Email (Resend).
- • Update `sendSMS` to write to Activity Log.
Impact: Stops failures, ensures reliable delivery.
Phase 2: CRM Unification (Weeks 3-4)
- • Merge CRM List & Pipeline views.
- • Build Master Prospect Form component.
- • Embed Activity Timeline inside Prospect record.
- • Archive standalone Activity & Task pages.
Impact: Massive UX simplification, better user adoption.
Phase 3: Revenue Automation (Weeks 5-6)
- • Build 72-hour Stale Lead CRON logic.
- • Integrate Google Calendar / Zoom.
- • Develop the Command Center Dashboard UI.
Impact: Reactivates dead leads, drives daily discipline.
Phase 4: Contextual AI (Weeks 7-8)
- • Archive standalone AI navigation pages.
- • Wire `InvokeLLM` to "Draft Script" CRM buttons.
- • Implement background Prospect Enrichment scoring.
Impact: Makes AI practically useful rather than a gimmick.
GST Financial Services LLC © 2026
REVENUE OPTIMIZATION ARCHITECTURE