CRM Pipeline Design

SKILL.md Preview

---
name: crm-pipeline-design
description: Use this skill when the user asks Claude to design a sales pipeline, set up CRM stages, map a deal flow, or decide what stages they need. Trigger when the user mentions setting up their CRM, organizing leads and deals, or phrases like 'what stages should my pipeline have.' This skill helps produce a stage-by-stage pipeline blueprint with entry and exit criteria and automation hooks.
compatibility: Claude.ai, Claude Desktop
---

# CRM Pipeline Design

## Purpose
Produce a pipeline blueprint with clearly defined stages, so deals move through a consistent flow and the user knows exactly what each stage means and triggers.

## When to Use This Skill
Use it when setting up or restructuring a CRM pipeline for sales or post-sale delivery.

## When Not to Use This Skill
Do not use it to spec full funnels (use the F.F.E.W.S. skill) or to write outreach copy. Do not use it without understanding the buyer journey.

## Required Inputs
- The business and what is being sold.
- The buyer journey from first contact to close.
- The sales cycle length.
- Any post-sale stages needed (onboarding, fulfillment).

## Workflow
1. Confirm inputs in one batch.
2. Name the pipeline and what it tracks.
3. Define stages in order, each with entry criterion, exit criterion, and the expected owner action.
4. Add automation hooks per stage (tags, emails, tasks).
5. Define won and lost, and add a second post-sale pipeline if needed.

## Output Format
Return the pipeline as a stage-by-stage table or list with entry and exit criteria, owner actions, automation hooks, and the won and lost definitions.

## Quality Standards
- Every stage has a clear entry and exit rule.
- Stages are action-based ('Proposal Sent'), not feeling-based ('Warm').
- Automation hooks are concrete.
- Uses contractions, no em dashes, no hype.

## Edge Cases
If the buyer journey is unclear, map it with the user before defining stages. If the business has multiple offer types with different flows, recommend separate pipelines.

## Safety and Limitations
Keep automations and stage logic honest; do not design pipelines that hide or misrepresent deal status.

## Test Prompts
1. I'm setting up GoHighLevel for my coaching business. I sell a $3,000 program after a discovery call. Design my sales pipeline with stages, entry and exit rules, and automation hooks.
2. Design a CRM pipeline for my web design agency. Leads come from referrals and a contact form, the cycle is about 3 weeks, and I want a separate pipeline for delivery after they sign.
3. My pipeline is a mess of vague stages like 'hot' and 'warm.' Rebuild it into clear action-based stages for a B2B service with a 6-week sales cycle.

Skill Details

Package Preview

Trigger Phrases

• "I'm setting up GoHighLevel for my coaching business. I sell a $3,000 program after a discovery call. Design my sales pipeline with stages, entry and exit rules, and automation hooks."
• "Design a CRM pipeline for my web design agency. Leads come from referrals and a contact form, the cycle is about 3 weeks, and I want a separate pipeline for delivery after they sign."
• "My pipeline is a mess of vague stages like 'hot' and 'warm.' Rebuild it into clear action-based stages for a B2B service with a 6-week sales cycle."