The playbook
CRM Pipeline Stages: Template and Field Guide
This CRM pipeline stages template turns a broad task into a record another person can use. It captures stage, entry criteria, exit evidence, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
Define “qualified” by observable requirements and “proposal sent” by an actual offer reaching the buyer. Include a clear closed-won and closed-lost condition. Avoid allowing sellers to advance deals merely because they completed an internal activity.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| stage | Record the stage associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| entry criteria | Record the entry criteria associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| exit evidence | Record the exit evidence associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| owner | Record the owner associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with stage. Use the same reference throughout the record so notes are not attached to the wrong item. Then define stages using observable customer milestones. This establishes the information required before the worksheet becomes a request for action.
Next, write entry and exit criteria for each stage. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as using vague stages that mean different things to each seller, rather than a broad instruction to “improve performance.”
Finally, train the team using realistic opportunity examples. Put replace activity labels with consistent qualification milestones in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Using vague stages that mean different things to each seller |
| Action | Replace activity labels with consistent qualification milestones |
| First check | Define stages using observable customer milestones |
| Follow-up check | Train the team using realistic opportunity examples |
| Outcome to define | opportunities meeting stage criteria |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If entry criteria changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep opportunities meeting stage criteria connected to the item so the team can later assess whether the action was useful.
Distinguish a person, an organization, and an opportunity. One contact can participate in several buying decisions, and one company can have several contacts. Keep identifiers and relationships clear when reviewing counts or moving records.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now