Description
Summary # Senior GoHighLevel Systems Architect | CRM Consolidation, APIs & Automation OnSite Energy is a residential solar company looking for a senior GoHighLevel systems architect and integration specialist to consolidate our software stack and make GoHighLevel our primary CRM and single source of truth. This is not a basic GHL funnel-building project. We need someone who can understand our entire customer journey, design the right system architecture, integrate multiple platforms, migrate and normalize data, build reliable automations, and help us simplify our software stack. ## Current Stack Our current systems include: * GoHighLevel — lead CRM * Quo — calls/text communications * PhoneBurner — high-volume outbound dialing * Enerflo — solar sales/operations CRM * Google Calendar * Zapier * Aurora Solar — solar design * Google Sheets * Google Workspace * Google Maps Our goal is to replace tools wherever GHL can reliably perform the same function and integrate the systems that still need to remain. ## Primary Objectives You will help us: * Audit our current systems and workflows * Design the future-state GHL architecture * Make GHL the master database for leads, contacts, appointments, communications, attribution, opportunities, and sales data * Determine which existing tools should be replaced, retained, or partially replaced * Configure GHL pipelines, custom fields, tags, calendars, workflows, permissions, forms, dashboards, and reporting * Integrate retained platforms with GHL using native integrations, APIs, webhooks, Zapier, Make, or custom scripting where necessary * Create clean field mapping and data ownership rules * Prevent duplicate or conflicting records * Migrate and clean existing data * Automate lead intake, speed-to-lead, appointment setting, reminders, no-shows, nurture, sales follow-up, internal notifications, and pipeline updates * Preserve accurate lead-source and marketing attribution * Build reliable reporting for marketing, call center, appointments, sales, and conversion performance * Test integrations, workflows, failures, edge cases, and data synchronization * Document the completed architecture and train us to maintain it ## Important: Live Collaborative Build This requirement is mandatory. I will be working alongside you virtually during a significant portion of the project through live screen-sharing sessions. I do not want someone to disappear, build everything independently, and hand me a finished system that I do not understand. I want to see how the architecture is designed, how integrations are created, why particular decisions are made, how data moves between systems, and how workflows are built. You must be comfortable teaching while implementing. My goal is to understand the completed system well enough that I can: * Modify workflows myself * Understand API/webhook connections * Troubleshoot common problems * Add fields and automations * Understand where every important piece of data originates * Maintain the system after implementation Strong communication and the ability to explain technical concepts clearly are therefore just as important as technical skill. ## Required Experience You should have advanced experience with: * GoHighLevel * CRM architecture * API integrations * REST APIs * Webhooks * Zapier and/or Make * Workflow automation * Data migration * Data normalization and deduplication * CRM field mapping * Lead attribution * Calling/SMS integrations * Appointment workflows * Integration monitoring and error handling Experience with solar, home services, Enerflo, PhoneBurner, Quo, Aurora Solar, or high-volume appointment-setting operations is a major plus. ## Ideal Working Style We want someone who thinks like a systems architect, not simply a task executor. You should be willing to recommend better solutions, identify unnecessary software, challenge inefficient processes, and explain the tradeoffs behind your recommendations. We expect this to be a large, multi-phase engagement completed over approximately 3–6 months. ## When Applying Please include: 1. Examples of complex GHL systems you have built 2. Examples where GHL was used as the central source of truth across multiple systems 3. Your experience with APIs, webhooks, Zapier, Make, and custom integrations 4. Your experience migrating and deduplicating CRM data 5. Any experience with solar or home-service companies 6. How you would approach deciding which of our current tools GHL should replace 7. How you prevent conflicting data when multiple systems update the same customer 8. How you monitor and troubleshoot failed integrations 9. Your availability for live screen-share sessions during U.S. Eastern Time 10. Your estimated timeline and weekly availability Please begin your proposal with **“GHL Solar Stack”** so we know you read the entire description.