CRM Pipeline & Tag Infrastructure

You design and build CRM pipeline and tag infrastructure in GoHighLevel (GHL). You understand pipeline stage design methodology, tag taxonomy and naming conventions, tag-workflow coupling, multi-brand isolation, and verification patterns.

Pipeline Design Methodology

Step 1: Understand the Vertical

Before creating a pipeline, identify:

• Vertical: CRE, mortgage, insurance, general sales, etc.
• Business model: Transactional, subscription, retainer, one-time
• Sales cycle length: Days (simple), weeks (moderate), months (complex)
• Team structure: Solo, team with roles, multi-location

Step 2: Match Existing Patterns

Check for existing pipelines in the GHL account to maintain consistency:

1. Open Opportunities → Pipelines in GHL
2. Review stage names, order, and naming conventions of existing pipelines
3. Adapt the new pipeline to match existing patterns (e.g., if existing pipelines use "New Lead" as stage 1, don't use "Fresh Lead")

Why consistency matters: Users (and automations) expect predictable stage names. Inconsistent naming causes workflow errors and confusion.

Step 3: Design Stages

Every pipeline needs these core phases (with vertical-specific names):

[Entry] → [Qualification] → [Engagement] → [Decision] → [Outcome]

Map to your vertical:

Phase	CRE	Mortgage	Insurance	General Sales
Entry	New CRE Lead	New Mortgage Lead	New Quote Request	New Lead
Qualification	Qualified Investor	Pre-Qualified	Coverage Assessed	Qualified
Engagement	Property Presented	Rate Quoted	Quote Presented	Proposal Sent
Decision	Under Negotiation	Application Submitted	Policy Review	Negotiation
Won	Deal Closed	Loan Funded	Policy Bound	Won
Lost	Deal Lost	Withdrawn	Not Interested	Lost

Consult references/pipeline_patterns.md for complete stage templates by vertical.

Stage design rules:

• 5-8 stages maximum (more stages = more friction in manual updates)
• Each stage should represent a meaningful status change (not just a task completion)
• Include both "Won" and "Lost" outcomes
• Consider adding a "Nurture" or "Long-Term Follow-Up" stage for leads that aren't ready

Step 4: Create Pipeline in GHL

1. Navigate to Opportunities → Pipelines
2. Click + Create Pipeline (or + Add Pipeline)
3. Enter pipeline name: [Brand] - [Vertical] Pipeline (e.g., "UBI Group - CRE Pipeline")
4. Add stages in order:
   • Click + Add Stage for each stage
   • Enter stage name
   • Set stage order (drag to reorder)
5. Save pipeline
6. Verify: Switch to Board View and confirm all stages appear in correct order

Tag Taxonomy

Naming Convention

Tags follow the pattern: {brand-prefix}-{category}-{descriptor}

Brand prefix: Lowercase, hyphenated brand identifier

• ubi-group-co for UBI Group Co.
• acme-lending for Acme Lending
• Keep prefix consistent across ALL tags for a brand

Category prefixes:

Category	Prefix	Purpose	Example
Lead Source	lead	Where the lead came from	ubi-group-co-lead-tiktok
Nurture	nurture	Nurture sequence enrollment	ubi-group-co-nurture-cre
Welcome	welcome	Welcome sequence enrollment	ubi-group-co-welcome-new
Prospect	prospect	Prospect status	ubi-group-co-prospect-qualified
Opportunity	opp	Opportunity/deal status	ubi-group-co-opp-cre-active
Product	product	Product interest	ubi-group-co-product-multifamily
Channel	channel	Communication channel	ubi-group-co-channel-instagram
Campaign	campaign	Marketing campaign	ubi-group-co-campaign-q1-cre
Status	status	Contact status flags	ubi-group-co-status-dnc

Consult references/tag_taxonomy.md for the complete naming convention reference.

Common Tag Sets by Workflow Type

New Lead Workflow Tags:

{brand}-lead-{source}          (e.g., ubi-group-co-lead-tiktok)
{brand}-welcome-new            (triggers welcome sequence)
{brand}-prospect-new           (marks as new prospect)

Nurture Workflow Tags:

{brand}-nurture-{vertical}     (e.g., ubi-group-co-nurture-cre)
{brand}-nurture-active         (currently in nurture)
{brand}-nurture-completed      (finished nurture sequence)

Pipeline Movement Tags:

{brand}-opp-{vertical}-new     (new opportunity created)
{brand}-opp-{vertical}-active  (opportunity in progress)
{brand}-opp-{vertical}-won     (deal won)
{brand}-opp-{vertical}-lost    (deal lost)

Multi-Brand Tag Isolation

When a GHL account manages multiple brands:

• Every tag MUST have the brand prefix — no generic tags
• Search before creating — verify a similar tag doesn't already exist
• Separate workflows per brand — don't share workflows between brands unless intentional
• Audit regularly — use cross-platform-audit skill to verify tag-workflow integrity

Batch Tag Creation

When creating multiple tags at once in GHL:

Sequential Dialog Cycle

1. Navigate to Settings → Tags (or use the tag manager in Contacts)
2. Click + New Tag (or Create Tag)
3. Enter tag name following the naming convention
4. Click Create (or Save)
5. Dialog closes — tag appears in list
6. Immediately click + New Tag again — don't navigate away
7. Repeat steps 3-6 for each tag

Recommended Creation Order

Create tags in this order to avoid referencing nonexistent tags in workflows:

1. Lead source tags first (these are applied by external systems like ManyChat)
2. Status/prospect tags second (used in workflow conditions)
3. Nurture/welcome tags third (trigger nurture workflows)
4. Opportunity tags fourth (used in pipeline workflows)
5. Campaign-specific tags last (most specific, least reused)

Tag-Workflow Coupling

Tags are the primary mechanism for triggering GHL workflows. Design them together:

Pattern: Tag → Workflow Trigger

[External Event] → [Tag Applied to Contact] → [GHL Workflow Triggers] → [Actions]

Example: ManyChat captures a TikTok lead

ManyChat sync → applies "ubi-group-co-lead-tiktok" tag
                → GHL workflow triggers on "ubi-group-co-lead-tiktok"
                → Workflow adds to CRE Pipeline → sends welcome email → notifies team

Creating Tag-Triggered Workflows

1. Create the tag FIRST (it must exist before the workflow references it)
2. Create the workflow
3. Set trigger: Contact Tag → select the specific tag
4. Build workflow actions
5. Publish workflow
6. Verify: Apply the tag to a test contact and confirm workflow fires

Cross-Reference Checklist

After building tag-workflow pairs:

• Every tag referenced in a workflow exists in the tag list
• Every workflow trigger tag has at least one source (ManyChat, form, manual, another workflow)
• No orphan tags (tags that exist but aren't used by any workflow or external system)
• No orphan workflows (workflows with triggers that no system ever fires)
• Tag names in ManyChat exactly match tag names in GHL (case-sensitive)

Verification Pattern

After creating pipeline + tag infrastructure:

Pipeline Verification

1. Navigate to Opportunities → Pipelines
2. Select the new pipeline
3. Switch to Board View
4. Confirm all stages appear in correct order
5. Create a test opportunity and move it through stages

Tag Verification

1. Navigate to Settings → Tags (or Contacts → tag filter)
2. Search for the brand prefix (e.g., "ubi-group-co")
3. Verify all expected tags appear
4. Confirm tag count matches your creation list

Workflow Verification

1. Navigate to Automation → Workflows
2. Find workflows associated with the new tags
3. Open each workflow, verify:
   • Trigger matches the correct tag
   • Actions are correct (pipeline assignment, notifications, etc.)
   • Workflow status is "Published" (not Draft)
4. Run a test: Apply trigger tag to test contact, monitor workflow execution

Integration with Other Skills

• social-funnel-automation: Defines which tags ManyChat should apply → use this skill to create those tags in GHL
• manychat-automation: ManyChat flow sends tags → this skill ensures receiving infrastructure exists
• cross-platform-audit: Use after setup to verify all tags, pipelines, and workflows are properly connected
• workflow-design: Use for detailed workflow design once tags and pipeline are in place