CRM Architecture · Solar

Solar CRM Pipeline Blueprint - Multi-Client Operations

A privacy-safe CRM architecture note for managing multiple client campaigns, lead routing, follow-up, and reporting from one operating layer.

Start a ProjectAll Case Studies
Ongoing (2024–2025)
build time
4
outcomes
6
stack tools
0
build steps

Built with real HMX CRM tool paths

GGoHighLevel (13 sub-accounts)
ZZapier (47 active zaps)
DDiscord Webhooks
TTwilio SMS
MMulti-timezone Calendars
AAutomated Reporting
GGoHighLevel (13 sub-accounts)
ZZapier (47 active zaps)
DDiscord Webhooks
TTwilio SMS
MMulti-timezone Calendars
AAutomated Reporting

Outcome
signals

These are the real outcome statements attached to this HMX CRM case study.

Multi-client
pipeline structure for separate accounts and owners
Faster
lead routing target after form submission
Cleaner
admin handoff pattern for follow-up teams
Visible
reporting surface for conversion and exception checks

Case architecture

Solar CRM Pipeline Architecture

5 nodes
Ad Platform
GoHighLevel
Zapier
Discord
Twilio SMS
  1. 01Ad Platform

    Lead source (Facebook/Google Ads)

  2. 02GoHighLevel

    CRM - 13 sub-accounts

  3. 03Zapier

    47 active automation zaps

  4. 04Discord

    Real-time closer alerts

  5. 05Twilio SMS

    Automated follow-up sequences

Problem

The operating gap

A solar lead generation operation can become hard to manage when each client has separate lead sources, sales teams, follow-up scripts, and reporting needs. Manual CRM updates, inconsistent follow-up, and scattered conversion views make the system fragile.

Build

What gets built

Designed and built a unified CRM architecture inside GoHighLevel that could serve all 13 sub-accounts from a single operational layer. Each client got their own pipeline, customised follow-up sequences (SMS + email + voicemail drops), and timezone-aware scheduling (EDT, MDT, PDT). A Zapier automation stack routed leads from ad platforms into the correct sub-account within seconds of form submission. Discord webhooks pushed real-time alerts to closers the moment a lead was qualified — no more checking dashboards. Automated weekly reporting eliminated manual pulls entirely.

Build
steps

Solar CRM Pipeline Blueprint - Multi-Client Operations uses a CRM operating layer for CRM Systems. A privacy-safe CRM architecture note for managing multiple client campaigns, lead routing, follow-up, and reporting from one operating layer. The architecture connects capture solar crm pipeline, gohighlevel, zapier, and pipeline outcome with an explicit control path.

Stack

Tools and layers

  • GoHighLevel (13 sub-accounts)
  • Zapier (47 active zaps)
  • Discord Webhooks
  • Twilio SMS
  • Multi-timezone Calendars
  • Automated Reporting
  • Capture layer: Capture Solar CRM Pipeline Blueprint source and context.
  • Rules layer: Validate the fields needed for Solar CRM Pipeline Blueprint.
  • CRM State layer: GoHighLevel (13 sub-accounts) stores the canonical CRM state for Solar CRM Pipeline Blueprint so reporting and follow-up read from one place.
  • Automation layer: Zapier (47 active zaps) handles routine steps while designed and built a unified CRM architecture inside GoHighLevel that could serve all 13 sub-accounts from a single operational layer.
  • Human Review layer: Multi-client pipeline structure for separate accounts and owners; Faster lead routing target after form submission; Cleaner admin handoff pattern f...

Data flow

  1. 01Capture Solar CRM Pipeline Blueprint source and context.
  2. 02Validate the fields needed for Solar CRM Pipeline Blueprint.
  3. 03Apply GoHighLevel (13 sub-accounts) rules and write the record state.
  4. 04Notify the owner or dashboard with the context attached.

Controls

  • A solar lead generation operation can become hard to manage when each client has separate lead sources, sales teams, follow-up scripts, and reporti...
  • Designed and built a unified CRM architecture inside GoHighLevel that could serve all 13 sub-accounts from a single operational layer.
  • When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

Research
basis

Build a CRM with the same traceability

The intake starts with lead sources, stages, and follow-up rules so the scope stays honest.

Start a ProjectAll Case Studies