Pipelines and stages — what they are and how to map your business

A pipeline is the journey board for your contacts: ordered stages people move through — sales, onboarding, support, collections.

Stages are the columns. Cards are contacts. Moving a card = changing operational status and (if you want) triggering a workflow.

What they’re for

• See at a glance where every lead or customer sits.
• Agree on a shared language (“they’re in Quoted,” not “I think I called them”).
• Chain automation: on entering Awaiting payment → send reminder.
• Give AI agents context (they can move stage if you allow it).

How to map your business (30-minute exercise)

1. Pick one journey (not five). Example: “Lead to closed” or “Ticket to resolved.”
2. List 4–7 stages the way you already talk in ops — not like a sales textbook.
3. Define entry (new contact? first message?) and exit (Won / Lost / Done).
4. For each stage: who’s the owner? What must happen before you move?
5. Publish the pipeline in Wroups and try it with 10 real contacts.

Retail / services example

New → Qualified → Quoted → Awaiting payment → Won / Lost

Support example

New → In diagnosis → Waiting on customer → Resolved

Common mistakes

• Too many columns (nobody moves anything).
• Vanity stages (“Love”) with no operational criteria.
• One pipeline for “the whole company” — better one per journey.
• Automating before the team moves stages by hand for a week.

In Wroups

Create the pipeline, publish it, open the board, link workflows on stage entry. Guide: Pipelines.

Sign up: msg.wroups.com/signup.