# A customer success plan template starts from what the deal promised

Guide, 10 Nov 2026, read 10 Nov 2026

**The short answer.** HubSpot, GUIDEcx and Rocketlane each document how a closed deal becomes a customer plan. This guide sets out the fields a customer success plan should inherit from the sale, what vendors say they carry over, and a template of sections for the first ninety days.

## Fields that must come from the deal

A customer success plan built from a blank page repeats discovery. GUIDEcx's Salesforce page says project details, customer records, assigned team members, billing information and custom fields are mapped from Salesforce into the project, and that Salesforce data selects the project, phase and milestone templates for each customer. That is the model: the deal record picks the template and fills the known fields.

Our minimum set of inherited fields: the goal and success criteria, the stakeholders and their roles, the commitments made in the sales cycle, the package bought, the go-live date, the known technical requirements and the risks the seller saw. The Template Library gives a step for each; the point of the plan is that none of them is asked again.

- Goal and success criteria, as written in the sales plan.
- Stakeholders, roles and the champion.
- Commitments and promised dates.
- Package or modules purchased.
- Technical requirements and integrations.
- Open risks and objections.

## What the vendors say they carry over

Vendor statements differ, and one says outright what it does not do. HubSpot's help center on onboarding plans describes tracking tasks, milestones and deadlines with customers in the customer success space of the portal, with changes syncing both ways, on Service Hub Professional and Enterprise. It does not say that a sales deal plan's milestones carry into the onboarding plan automatically.

Rocketlane's help center says a deal closing in HubSpot can trigger automated project creation, and GUIDEcx says a Closed Won opportunity starts a new project. Trumpet's onboarding page says closing and onboarding happen on the same link. Flowla says its agent builds the onboarding plan from sales call notes before kickoff. Dock's client portal page says each customer gets a branded workspace from kickoff to renewal. All are vendor statements read on 10 Nov 2026.

## Sections of the plan

A customer success plan that a customer follows has six sections, in this order: outcome, people, first thirty days, days thirty to sixty, days sixty to ninety, and review dates. Each task has an owner on a named side, a date and an exit criterion. Dock's onboarding page says customers can update implementation plan tasks, comment and upload files in the same plan, which is the behavior to look for: the customer works in the plan, not around it.

The first thirty days carry the highest risk, so they are the most detailed. Kickoff with the sponsor, access and permissions, data or content the customer must supply, the first training session and the first measured result. Each has a customer owner; if a step has only a vendor owner, it is not a joint plan.

## Checkpoints and nudges

Reminders belong in the plan rather than in the calendar of one person. GUIDEcx's pricing page says task owners get actionable emails and can update task status by clicking a link. Rocketlane's help center describes automations that notify the project owner when a task is overdue. Aligned's pricing page lists automatic client reminders on its plan comparison. Choose a tool where the reminder goes to the task owner on the customer side, not only to your team.

Write three checkpoints into the plan: a thirty-day review of the first measured result, a sixty-day review of adoption and a ninety-day review of the success criteria. The renewal template in our library starts at the ninety-day mark so the renewal conversation opens with a record.

## Where the template lives

Keep the template in the system that creates the customer plan, with the CRM field mapping in place. HubSpot's help center sets deal plan template milestones by days after creation, and the same approach works for onboarding: offsets from kickoff, not calendar dates. The [Template Library](/templates/) uses day offsets for that reason. For the tools that cover the post-sale plan, see the [platform pages](/platforms/guidecx/).

## Sources

- GUIDEcx, Salesforce integration: https://www.guidecx.com/products/integrations/salesforce/ (read 10 Nov 2026)
- HubSpot knowledge base, customer onboarding plans: https://knowledge.hubspot.com/customer-success/create-and-manage-customer-onboarding-plans (read 10 Nov 2026)
- Rocketlane help center, HubSpot integration: https://help.rocketlane.com/support/solutions/articles/67000715492-rocketlane-s-integration-for-hubspot (read 10 Nov 2026)
- Trumpet, customer onboarding: https://www.sendtrumpet.com/use-cases/customer-onboarding (read 10 Nov 2026)
- Flowla, customer onboarding: https://www.flowla.com/customer-onboarding (read 10 Nov 2026)
- Dock, onboarding and implementations: https://www.dock.us/features/onboarding-implementations (read 10 Nov 2026)
- Dock, client portal: https://www.dock.us/solutions/client-portal (read 10 Nov 2026)
- GUIDEcx, pricing page: https://www.guidecx.com/products/pricing/ (read 10 Nov 2026)
- Aligned, pricing page: https://alignedup.com/pricing/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://themutualactionplan.com/guides/customer-success-plan-template/
