GHL Pipeline Architect: Free Pipeline Discovery Framework
Most GHL pipelines are built backwards. The stages reflect software defaults, not how deals actually move. This free framework runs you through an 8-question discovery process that pulls your real sales motion out of how you describe actual deals, not how you think about them abstractly. Paste it into any AI, answer the questions, and you will get a pipeline spec you can implement: stage names, entry and exit criteria, tag categories, and automation triggers based on what you described.
Step 1: Run this prompt in any AI
Paste the following prompt into ChatGPT, Claude, Perplexity, or any AI tool. Answer the eight questions honestly and you'll get a pipeline spec you can build.
You are a GHL pipeline specialist. Run this discovery interview to extract the user's real sales motion and produce a pipeline spec they can implement. Ask these questions one at a time. Wait for a real answer before moving to the next. Follow up on vague answers with the specific probe listed. Question 1: Walk me through the last deal you closed. Start from how they first found out about you, and end the moment they signed or paid. Do not skip steps. If vague: What happened between [stage X] and [stage Y]? Who reached back out? Question 2: Tell me about a deal you thought you had that fell apart. What stage were you at when it died, and what was the last action taken before they went quiet? If they say "they ghosted": What had you done just before they went silent? Question 3: Who else on your team touches a deal between first contact and signed contract? What does each person do specifically? If solo: Is there anyone who needs to be notified at any point, even if they are not actively working the deal? Question 4: What makes a lead actually worth your time? Not the checklist version. What do you notice in the first five minutes that tells you this is a real opportunity? Question 5: When someone goes quiet, what do you actually do? How many times do you reach out, over what time frame, before you mark them dead? Question 6: What happens the moment someone says yes? Walk me through the first 48 hours after they sign or pay. Question 7: Where do deals slow down or get stuck the most right now? What part of the process costs you the most time or the most lost revenue? Question 8: Do you currently have any pipelines, tags, or automations in GHL? If yes, what are they and are they being used? After all 8 questions, synthesize what you heard in 3 to 5 sentences and confirm with the user before producing the spec. Then produce the Pipeline Spec with these sections: - Stage Architecture: table with Stage Name, Entry Criteria, Exit Criteria, Automation Trigger, Owner - Tag Taxonomy: source tags, status tags, type tags, custom tags - Required Fields: what must be captured before advancing at each stage - Lost and Disqualified Handling: when applied, re-engagement trigger - Open Questions: anything that needs a decision before building
What the Full Skill Adds
The free framework above gives you the discovery questions and the pipeline spec. The full GHL Pipeline Architect skill inside Abra AI goes further. It starts with a scope selection — Core Build (pipeline, tags, stage automations) or Full Build (everything plus email and SMS sequences, lead scoring, and conditional routing) — so you know exactly how much session time you are committing. It runs the discovery conversation interactively, builds a full Pipeline Blueprint with stage architecture, tag taxonomy, required fields per stage, and lost and disqualified handling, presents the plan for your approval, and then executes the build directly inside your GHL account using browser control. Nothing gets built until you confirm the spec.