The playbook
Customer Segmentation: Template and Field Guide
This customer segmentation template turns a broad task into a record another person can use. It captures segment, criteria, action, 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
Separate customers by differences that justify action, such as service need, lifecycle stage, or adoption pattern. A segment is useful when it changes the message, support, or offer. Revisit membership when the underlying information changes.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| segment | Record the segment associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| criteria | Record the criteria associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| action | Record the action associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| update trigger | Record the update trigger 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 segment. Use the same reference throughout the record so notes are not attached to the wrong item. Then choose attributes tied to needs behavior or relationship stage. This establishes the information required before the worksheet becomes a request for action.
Next, define segment membership and update rules. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as creating many segments that receive the same treatment, rather than a broad instruction to “improve performance.”
Finally, test whether actions differ meaningfully by segment. Put use fewer groups with clearly different decisions 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 | Creating many segments that receive the same treatment |
| Action | Use fewer groups with clearly different decisions |
| First check | Choose attributes tied to needs behavior or relationship stage |
| Follow-up check | Test whether actions differ meaningfully by segment |
| Outcome to define | segments with distinct useful actions |
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 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 segments with distinct useful actions 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