← All guides

CRM and automation

How to organize a simple CRM pipeline

A pipeline is a list of possible jobs grouped by what happens next. Keep the stages clear enough that two people would put the same inquiry in the same place.

By Keith Uy · Published September 6, 2026 · Reviewed September 6, 2026

The whole process, at a glance

  1. Define the stages1 of 3
  2. Give each inquiry an owner2 of 3
  3. Keep the next action current3 of 3

Before you start

Use this with a spreadsheet or the CRM you already have. List your real sales steps and decide who is responsible for each inquiry. The example below is a suggested process, not a platform’s default stages.

Follow these steps

  1. Separate people from possible jobs

    A contact is a person or organization you know. An opportunity or deal is a possible piece of work. A returning customer may create a new deal without becoming a duplicate contact. Agree what counts as one opportunity before importing or automating anything.

  2. Choose a small set of observable stages

    Start with stages such as New inquiry, Reviewing fit, Conversation booked, Proposal sent, Won, and Lost. Adapt them to your actual process. Avoid a stage called “Follow up” if almost every open deal needs a follow-up.

  3. Write the rule for moving each card

    Define entry and exit conditions. “Proposal sent” means the customer received the offer, not that someone started writing it. “Won” should use your business’s actual acceptance or payment rule. Record a loss reason without leaving dead opportunities in an active stage indefinitely.

    Example stageEvidence needed
    New inquiryA genuine request has arrived
    Reviewing fitSomeone is checking suitability
    Conversation bookedA meeting has a confirmed time
    Proposal sentThe offer was sent to the customer
    Won / LostThe agreed close condition or reason is recorded
  4. Assign one owner and one physical next action

    Every open deal needs a responsible person, a concrete action, and a due date. Write “Send the revised scope by Thursday,” rather than “Follow up soon.” If waiting for the customer, set a date to check back. Important history belongs in notes; it should not replace the next action.

  5. Review the pipeline regularly

    Look for overdue actions, missing owners, duplicates, and stale deals. Move cards only when the stage rule is met. Separate activity from outcomes: sending ten emails is not ten new deals. Change the process when experience reveals a confusing rule, then update the team’s definition before changing automation.

You’re finished when…

Each active opportunity has an understandable stage, one responsible person, and a dated next action. Closed opportunities have an honest outcome.

If you get stuck

Should we add more stages?

Add a stage only when it describes a meaningful change in the process. Extra columns can hide work if nobody agrees how to use them.

What happens to a lead that goes quiet?

Keep a clear follow-up date while you are still pursuing it. After your agreed stopping point, close or park it according to an explicit rule.

Can a spreadsheet be enough?

Yes for a simple process. Keep the same essentials: identity, stage, owner, next action, due date, and outcome. Tool choice depends on scale and integration needs.

Official sources and further reading

Reviewed September 6, 2026. Platform menus can vary by account and change over time. Examples and checklists are WinflowAI’s own guidance; follow the linked vendor instructions for your account.

Useful next guides

How to map a process before automating it →How to tell where website inquiries come from →How to test an automation before turning it on →

Need help with your website or inquiry workflow? See how WinflowAI can help.