Pipelines and sales
Stand up a pipeline
Stages, fields, and tags for a new client in one conversation.
What you'll get
- A pipeline with stages named the way this business actually sells, not GHL's defaults.
- The custom fields and tags the pipeline depends on, created at the same time so nothing points at a field that does not exist.
- The real stage IDs written down, which is what everything you build later has to reference.
Say this
Set up a pipeline for a med spa: new lead, consult booked, consult done, treatment scheduled, treated.
Add a stage called Deposit Paid between consult done and treatment scheduled.
Show me the pipelines in this account with their stages.
The pro prompt
The exact ask we run on real client accounts
Proven liveIn my [Radiance Med Spa] account, create a pipeline called "[Patient Journey]" with these stages in order: [New Lead], [Consult Booked], [Consult Completed], [Treatment Scheduled], [Treated], [Lost]. Also create the custom fields this needs: [Consult Date] as a date, and [Quoted Value] as a number. When you are done, read the pipeline back to me from the account and show me the real stage names in order, so I know it saved the way I asked. Do not add any contacts or deals to it yet.
Click the box to select it, then press ⌘C (or Ctrl+C)
Everything in [brackets] is yours to change. The read-back line is the one that matters: you are being shown what GHL actually stored, not what Claude intended to store.
What happens when you ask
- Claude creates the pipeline and its stages in order.
- It creates any custom fields you asked for alongside it.
- It reads the whole thing back out of the account so you can see what really landed.
Good to know
- Name stages after what the business does, not after sales jargon. "Consult Booked" beats "Qualified" for a clinic, every time.
- Fewer stages is better. Six is plenty. Ten stages means nobody keeps the board clean.
- Keep the pipeline. When stages change, ask Claude to update the pipeline in place. Deleting and recreating gives every stage a new ID, and every workflow that referenced the old ones goes silently dead.
- Needs the full license.
Where people go wrong
| What happened | The fix |
|---|---|
| "I recreated the pipeline and all my automations stopped." | Recreating changes every stage ID. Say "update the existing pipeline" instead, and Claude keeps the IDs alive. |
| "A workflow that moves deals does nothing." | It is pointing at a stage that no longer exists. Run a workflow audit; this is the single most common find. |
| "The stage order came out wrong." | Say the stages in order in one line and ask for the read-back. The read-back shows you the true order. |