Found a bug in our own funnel this week that I guarantee is live in someone's account reading this. A form posts to a GoHighLevel inbound webhook. The webhook fires. The workflow runs. The thank-you page shows. And no contact is ever created. The lead is gone. No error anywhere. Here is why: GHL inbound-webhook workflows run contactless. Unless the workflow has a Create or Update Contact action with the payload fields mapped, GHL executes the whole thing into the void. Tags fire on nobody. Emails send to no one. The execution log shows green. The test that catches it takes ninety seconds. Submit your own form with a real email. Wait a minute. Search Contacts for it. If it is not there, your form has been a paper shredder. This is one of seven silent failure modes I put into a free checklist, all from real broken accounts: get.ghlcommand.com/checklist. Work through it on your own account this week. Most agencies find at least one.

Build-in-public note, because that is the deal in here. Here is what today actually taught us and what it changed. Lesson 1: not everyone in this group owns the tool, and writing as if you all did was a mistake. Some of you are running GHL Command already. Some of you joined to look before you buy. We had been writing lessons as if everyone had the tool connected, which quietly leaves half the room out. So we fixed it. Nothing in here is locked. Every module is open. If you do not own the tool yet, the lessons now tell you what the screen would show and how far the free path gets you, so you can follow along and decide for yourself. The free assets, the second brain kit, the silent-failure checklist, the prompt swipe file, are yours either way. Lesson 2: the most useful on-ramp is not the advanced stuff, it is the mess. The people this is built for are not short on ideas. They are short on a system. Brilliant, scattered, ten tabs open, building instead of selling. So today we shipped a new module, The Scattered Founder's Operating System. It is the real story of turning a pile of plain-text files and an AI that actually reads them back to you into something that runs your day. If you have ever ended a busy day unsure what you actually moved, start there. Lesson 3: a thin prompt gets you a thin answer. Most prompt lists you have seen are one-liners. A one-liner gets a one-liner back. A real prompt briefs the AI the way you would brief a great hire on day one: who to be, what it is looking at, what good looks like, what to hand back. So we built an operator prompt pack to that bar. Not vending-machine prompts, full briefings you fill in with your details and run. It is going into the resources here. What is getting tested next: The comment-to-client module is built and gets its real test this weekend. Not a builder full of green checkmarks. An actual cold run, someone comments the keyword and we watch the whole thing fire end to end. If it breaks, you will hear exactly how, same as every war story in here. We do not call it working until it works in a stranger's hands.

Welcome in. You're a founding member, and I don't take that lightly. Quick on what this is. GHL Command is the room for agency owners who use AI to actually run their operations, not just market with it. I run a healthcare agency on this exact stack every day: the GHL Command MCP, Claude, and a small team of named agents. This is where I build it in public, drop the prompts and templates I'm using, and answer your GoHighLevel questions directly. What your membership includes, plainly: - The GHL Command tool (your license) at the founding rate of $97/mo, locked as long as you stay subscribed. - This community: the build-in-public room, the prompts and templates, and me answering questions. - Every new tool we ship, automatically, at no extra cost while you're a member. Billing lives in your account, not here. You can manage or cancel anytime. If you cancel, the license and your spot here wind down together. Simple. Your first 20 minutes: 1. Open the Start Here course in the Classroom. It gets GHL Command installed and gives you a real win in about 10 minutes (point Claude at one of your sub-accounts and have it tell you what's silently broken). 2. Come back and introduce yourself below: who you are, how many sub-accounts you run, and the one GHL task you're most tired of doing by hand. 3. Read the first war story I pinned: "The $5,000 pipeline ID mistake every GHL agency owner makes." It's the bug that started all of this. That's it. Get the tool running, get your first win, then tell me what you want me to build next. This thing grows around what you actually need. — Jerry

True story. This happened to me on one of my own projects, not a client. An intake workflow was working perfectly. Lead form fires, contact created, tagged, opportunity opens in the sales pipeline. Smooth. Then I renamed the pipeline. New name, same purpose. I updated the workflow's create_opportunity action. Two days later I noticed something off in my daily numbers. Leads coming in, no opportunities showing up. I checked the workflow execution history. It was running. Every step showed green. Forms firing, contacts created, tagged correctly. But no opportunities. Took me three hours to find it. The pipeline ID I'd entered didn't exist. The pipeline existed, but I'd typed one character wrong. GHL didn't error. The workflow didn't fail. The create_opportunity action just silently dropped. And here's the killer: every action after it in the workflow ran on the assumption the opportunity was created. Tags fired. Notifications sent. Internal Slack said "you have a new opportunity." But the opportunity didn't exist. I lost about 38 leads over 72 hours. By the time I caught it, the sales window on a couple of them was already gone. Approximate value: $5,000 in lost revenue. Not catastrophic, but the kind of mistake that gives you ulcers and makes you question every other workflow you've ever deployed. The rule I wrote for myself after that: "Verify ALL IDs (pipeline, stage, field, workflow) exist before deploying. Invalid IDs silently kill all subsequent actions." That rule lives in my CLAUDE.md to this day. This is the class of bug Vera catches automatically. Before any workflow deploys, Vera resolves every ID against the live GHL account. Mismatch means halt, alert, suggest the closest match. No more invisible failures. That's what we're building this week. If you run GHL workflows and you DON'T have something checking your IDs before deploy, you have this bug. You just haven't been bitten by it yet. See the attached screenshot. It's Vera catching exactly this class of bug in 345ms.