CRM Sales Pipeline Template

A clean CRM pipeline with stages, exit rules, and follow-up discipline. Use the variants as-is, edit the placeholders, or download the editable Word doc.

Format
Editable Word .docx
Length
6 variants · copy-paste
Price
100% free
Setup
Copy or download

Get the editable Word doc in one click.

4.9·Free · No signup · Instant download
Connects to WebsiteWhatsAppTelegramInstagram
CRM

Template preview

Inbound SMB pipeline

CRM setup

Name: Inbound SMB pipeline

Owner: owner

Field or stage: CRM field

Definition

Use this when the contact matches inbound smb pipeline and there is enough context for a teammate to decide the next action without reading the full conversation.

Rules

  • Entry rule: specific detail is confirmed.
  • Required fields: customer name, specific detail, next step, owner, deadline.
  • Exit rule: the next action is completed, declined, scheduled, or moved to nurture with a reason.
  • Review rule: stale records are checked every deadline.

Automation note

Only automate from this field when the definition is stable. If two teammates would tag the same contact differently, the rule is not ready.

Team note

If the record does not change the next action, do not add the tag or stage. CRM data should make work easier, not noisier.

Download free template

6 ready-to-use variants

1

Inbound SMB pipeline

When to use: Use this when inbound smb pipeline needs a clear stage rule, owner, and next action inside the CRM.

CRM setup

Name: Inbound SMB pipeline

Owner: owner

Field or stage: CRM field

Definition

Use this when the contact matches inbound smb pipeline and there is enough context for a teammate to decide the next action without reading the full conversation.

Rules

  • Entry rule: specific detail is confirmed.
  • Required fields: customer name, specific detail, next step, owner, deadline.
  • Exit rule: the next action is completed, declined, scheduled, or moved to nurture with a reason.
  • Review rule: stale records are checked every deadline.

Automation note

Only automate from this field when the definition is stable. If two teammates would tag the same contact differently, the rule is not ready.

Team note

If the record does not change the next action, do not add the tag or stage. CRM data should make work easier, not noisier.

2

High-ticket service pipeline

When to use: Use this when high-ticket service pipeline needs a clear stage rule, owner, and next action inside the CRM.

CRM setup

Name: High-ticket service pipeline

Owner: owner

Field or stage: CRM field

Definition

Use this when the contact matches high-ticket service pipeline and there is enough context for a teammate to decide the next action without reading the full conversation.

Rules

  • Entry rule: specific detail is confirmed.
  • Required fields: customer name, specific detail, next step, owner, deadline.
  • Exit rule: the next action is completed, declined, scheduled, or moved to nurture with a reason.
  • Review rule: stale records are checked every deadline.

Automation note

Only automate from this field when the definition is stable. If two teammates would tag the same contact differently, the rule is not ready.

Team note

If the record does not change the next action, do not add the tag or stage. CRM data should make work easier, not noisier.

3

Agency retainer pipeline

When to use: Use this when agency retainer pipeline needs a clear stage rule, owner, and next action inside the CRM.

CRM setup

Name: Agency retainer pipeline

Owner: owner

Field or stage: CRM field

Definition

Use this when the contact matches agency retainer pipeline and there is enough context for a teammate to decide the next action without reading the full conversation.

Rules

  • Entry rule: specific detail is confirmed.
  • Required fields: customer name, specific detail, next step, owner, deadline.
  • Exit rule: the next action is completed, declined, scheduled, or moved to nurture with a reason.
  • Review rule: stale records are checked every deadline.

Automation note

Only automate from this field when the definition is stable. If two teammates would tag the same contact differently, the rule is not ready.

Team note

If the record does not change the next action, do not add the tag or stage. CRM data should make work easier, not noisier.

4

SaaS trial pipeline

When to use: Use this when saas trial pipeline needs a clear stage rule, owner, and next action inside the CRM.

CRM setup

Name: SaaS trial pipeline

Owner: owner

Field or stage: CRM field

Definition

Use this when the contact matches saas trial pipeline and there is enough context for a teammate to decide the next action without reading the full conversation.

Rules

  • Entry rule: specific detail is confirmed.
  • Required fields: customer name, specific detail, next step, owner, deadline.
  • Exit rule: the next action is completed, declined, scheduled, or moved to nurture with a reason.
  • Review rule: stale records are checked every deadline.

Automation note

Only automate from this field when the definition is stable. If two teammates would tag the same contact differently, the rule is not ready.

Team note

If the record does not change the next action, do not add the tag or stage. CRM data should make work easier, not noisier.

5

Renewal pipeline

When to use: Use this when renewal pipeline needs a clear stage rule, owner, and next action inside the CRM.

CRM setup

Name: Renewal pipeline

Owner: owner

Field or stage: CRM field

Definition

Use this when the contact matches renewal pipeline and there is enough context for a teammate to decide the next action without reading the full conversation.

Rules

  • Entry rule: specific detail is confirmed.
  • Required fields: customer name, specific detail, next step, owner, deadline.
  • Exit rule: the next action is completed, declined, scheduled, or moved to nurture with a reason.
  • Review rule: stale records are checked every deadline.

Automation note

Only automate from this field when the definition is stable. If two teammates would tag the same contact differently, the rule is not ready.

Team note

If the record does not change the next action, do not add the tag or stage. CRM data should make work easier, not noisier.

6

Lost deal nurture pipeline

When to use: Use this when lost deal nurture pipeline needs a clear stage rule, owner, and next action inside the CRM.

CRM setup

Name: Lost deal nurture pipeline

Owner: owner

Field or stage: CRM field

Definition

Use this when the contact matches lost deal nurture pipeline and there is enough context for a teammate to decide the next action without reading the full conversation.

Rules

  • Entry rule: specific detail is confirmed.
  • Required fields: customer name, specific detail, next step, owner, deadline.
  • Exit rule: the next action is completed, declined, scheduled, or moved to nurture with a reason.
  • Review rule: stale records are checked every deadline.

Automation note

Only automate from this field when the definition is stable. If two teammates would tag the same contact differently, the rule is not ready.

Team note

If the record does not change the next action, do not add the tag or stage. CRM data should make work easier, not noisier.

Do it in sem.chat

Let your AI agent put this to work

Load this template into sem.chat and your agent uses it automatically, in your brand voice, around the clock.

  • Save as reusable replies, scripts, or rules
  • Keeps every message on-brand and consistent
  • Hands the hard cases to a human

How to use this template

  1. 1

    Pick the closest variant. Choose based on the situation, not only the channel.

  2. 2

    Replace every placeholder. If you cannot fill a field, ask one clarifying question first.

  3. 3

    Save the final version into sem.chat, your CRM, or your help desk so the team stays consistent.

  4. 4

    Review results weekly. Drop variants that create confusion and improve the ones that work.

Frequently asked questions

Can I use these templates commercially?
Yes. Copy, edit, and use them in your business, client work, CRM, help desk, or sem.chat workspace.
Why are there six variants?
One generic template rarely fits every situation. Six variants give your team practical choices without a messy library.
Should I paste these into sem.chat?
Yes. Save the best variants as canned replies, knowledge base entries, routing rules, or CRM notes so your AI agent and team stay consistent.

Power it up with sem.chat

Everything you need to put this template to work.

Put this template to work in sem.chat

Use this in sem.chat and let your agent handle it, in your voice, around the clock.