Setting up a CRM pipeline that doesn't make you want to quit

You set up a CRM. You created a pipeline. You named it something reasonable. And then you added stages.

Maybe you got ambitious. "Initial Contact," "Discovery Call Scheduled," "Discovery Call Completed," "Needs Analysis," "Solution Presentation," "Proposal Draft," "Proposal Sent," "Negotiation," "Legal Review," "Verbal Commit," "Contract Sent," "Closed Won," "Closed Lost."

Thirteen stages. You felt organized. Thorough. Professional.

Nobody ever updated it.

Why pipelines fail

The failure mode is almost always the same: too many stages, too little discipline, and deals that sit in limbo for weeks because nobody knows which stage they're actually in.

Here's what happens with overbuilt pipelines:

People skip stages. If you have "Discovery Call Scheduled" and "Discovery Call Completed" as separate stages, that second move only happens if someone remembers to drag the card after the call. They won't. They're already thinking about what to say in the next email.

Stages become meaningless. When you have 10+ stages, the difference between "Needs Analysis" and "Solution Presentation" starts to blur. People assign deals to whichever stage feels closest, and your pipeline stops reflecting reality.

Reporting becomes fiction. Pipeline reports are only useful if the data is accurate. If deals are in the wrong stages, your conversion rates, your average time-in-stage, your forecasts — all fiction. Pretty charts, useless numbers.

The fix isn't a better training program or a sternly-worded email about pipeline hygiene. The fix is a simpler pipeline.

The 3-5 stage rule

The best pipelines we've seen have between three and five stages. That's it. Here's why this works:

Each stage represents a real, unmistakable change. Moving from "New" to "In Conversation" means you've actually talked to this person. Moving from "Proposal Sent" to "Won" means they said yes. There's no ambiguity about what qualifies.

People can hold 3-5 stages in their head. They don't need to look at a reference document to figure out where a deal goes. They just know.

Updates actually happen. The friction of updating a pipeline is directly proportional to how many stages you have to think about. Three stages? Easy. Twelve stages? I'll do it later. (They won't do it later.)

Here's a pipeline that works for most teams:

1. New — A deal exists. Someone expressed interest. You haven't had a real conversation yet.
2. In Conversation — You're actively talking. Could be email, phone, meetings, whatever. The key word is "active."
3. Proposal Sent — You've sent them something with a number on it. A quote, a proposal, a pricing doc.
4. Won — They said yes. The deal is done.
5. Lost — They said no, or they went silent for long enough that you're not pretending anymore.

Five stages. Each one is clear. Each one represents something that unmistakably happened. And the gap between them is small enough that moving a deal doesn't feel like a chore.

When to customize (and when not to)

Should you rename these stages? Sure, if the labels make more sense for your business. "Proposal Sent" might be "Demo Completed" if you sell software. "In Conversation" might be "Qualifying" if that's how your team thinks about it.

Should you add stages? Maybe, but be cautious. Here's the test: if you're adding a stage, can you clearly describe the single event that moves a deal into it? Not a feeling, not a judgment call — an event. "We scheduled the demo" or "They signed the NDA."

If the answer is "well, it's kind of when we feel like they're more serious," that's not a stage. That's a gut feeling, and gut feelings don't survive contact with a pipeline interface.

Things worth adding a stage for:

• A specific step in your process that every deal goes through (like a demo or a trial period)
• A gating event that requires action from the prospect (like a security review or legal approval)

Things not worth adding a stage for:

• Subdivisions of "we're talking to them" (Scheduled, Completed, Follow-up, Second Follow-up — just no)
• Internal process steps that don't change the deal's actual status
• Stages that exist so you can "track metrics" on something nobody will actually measure

Practical setup in Vigdis

Here's how to set this up in about two minutes.

Head to Settings > Pipeline in Vigdis. You'll see a default pipeline already created with sensible stages. You can rename any stage by clicking on it, drag to reorder, or add new ones with the + button.

For a basic setup:

1. Keep the default stages or rename them to match your language.
2. Set colors for visual clarity — green for Won, red for Lost, neutral for everything in between.
3. That's it. Go to your Deals view and you'll see the pipeline as a kanban board. Drag deals between columns.

If you want multiple pipelines (say, one for new business and one for renewals), you can add more from the same settings page. Each pipeline gets its own set of stages. But start with one. You can always add another later when you actually need it, not when you theoretically might.

The pipeline is a tool, not a process document

Here's the mindset shift that makes everything easier: your pipeline should reflect what's happening, not prescribe what should happen.

If your sales process has twelve steps, great. Document those somewhere. Train your team on them. But the pipeline — the thing people drag cards around in every day — should only track the big, obvious milestones.

Think of it like a GPS showing major highway exits, not every side street. You still drive through the side streets, but the overview map doesn't need to show them.

Keep it simple. Keep it honest. And if someone on your team stops updating it, that's not a people problem — it's a pipeline problem. Simplify until they do.