The playbook
Customer Onboarding: Template and Field Guide
This customer onboarding template turns a broad task into a record another person can use. It captures customer, first outcome, required input, 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 first value in terms the customer recognizes, such as the first working website inquiry or the first usable pipeline. Request only the inputs needed for that milestone initially. Give each request a purpose, owner, and clear next step.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| customer | Record the customer associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| first outcome | Record the first outcome associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| required input | Record the required input 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 customer. Use the same reference throughout the record so notes are not attached to the wrong item. Then confirm purchased scope and success criteria. This establishes the information required before the worksheet becomes a request for action.
Next, collect the inputs needed for the first delivery milestone. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as overwhelming customers with tasks unrelated to first value, rather than a broad instruction to “improve performance.”
Finally, assign an owner and communicate the immediate next step. Put sequence requests around the first usable outcome 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 | Overwhelming customers with tasks unrelated to first value |
| Action | Sequence requests around the first usable outcome |
| First check | Confirm purchased scope and success criteria |
| Follow-up check | Assign an owner and communicate the immediate next step |
| Outcome to define | customers reaching first value |
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 first outcome 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 customers reaching first value connected to the item so the team can later assess whether the action was useful.
Preserve the context of the last meaningful conversation. The next owner should know what was promised, what remains unresolved, and who is expected to act. A stage label alone rarely supplies enough information.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now