The playbook
CRM Implementation: Template and Field Guide
This CRM implementation template turns a broad task into a record another person can use. It captures record type, field, stage, 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
Begin with a small representative sample: a new inquiry, an existing customer, an open deal, and a lost deal. Confirm how contacts, accounts, and opportunities relate. Test ownership and the next action before importing the full database.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| record type | Record the record type associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| field | Record the field associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| stage | Record the stage 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 record type. Use the same reference throughout the record so notes are not attached to the wrong item. Then define contact account and opportunity records. This establishes the information required before the worksheet becomes a request for action.
Next, map real sales stages and required information. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as importing every historical field before defining how the team will work, rather than a broad instruction to “improve performance.”
Finally, test a sample lead from capture through closure. Put start with the minimum information needed for the live process 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 | Importing every historical field before defining how the team will work |
| Action | Start with the minimum information needed for the live process |
| First check | Define contact account and opportunity records |
| Follow-up check | Test a sample lead from capture through closure |
| Outcome to define | active opportunities with a next action |
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 field 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 active opportunities with a next action connected to the item so the team can later assess whether the action was useful.
Use observable customer milestones when assessing progress. A seller sending a message is an activity; a buyer agreeing to a next meeting is a different event. Recording both helps the team locate the actual constraint.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now