Guide, 10 Nov 2026, read 10 Nov 2026
A joint execution plan is a mutual action plan with the project-plan parts switched on
The name and what it signals
Dock's page names the joint execution plan as one of the aliases for a mutual action plan, next to mutual success plan, go-live plan and close plan. In practice the label signals a bigger plan. Teams say joint execution plan when the deal ends in a delivery that both companies must staff: an integration, a migration, a rollout across regions. The plan has to cover the buying steps and the first months of the work.
Accord's implementation page, read on 10 Nov 2026, describes this shape: customers commit to specific milestones, deadlines and resources, and both sides track who owns what and when. The word resources is the difference. A short plan lists actions. A joint execution plan also lists who from each company is on the hook, with how much of their time.
Parts a project-plan form adds
Rocketlane's help center describes a project plan with a Timeline view in Gantt form and a Responsible filter that shows only the tasks owned by the customer company or only those owned by the vendor's company. GUIDEcx's pricing page lists Gantt, list and board views, approval flows, and merge tags for task instructions and assignment emails. Those are project tools, built for the delivery phase, and both vendors document the sales-to-onboarding handoff as their entry point.
For a sales team, four additions turn a mutual action plan into a joint execution plan.
- Dependencies: step B cannot start until step A closes, for example no integration work before the security review is passed.
- Resourcing: the named person on each side and the hours expected from them.
- Phases: buying, contracting, kickoff, build, go-live, each with its own exit criterion.
- Approval steps: a named approver for any change to scope or date.
The responsible filter is the test
Rocketlane's filter is a useful test for any plan, in any tool. Filter the plan to the buyer's tasks. If the result is two lines, the plan is a seller plan. If a single buyer person owns fifteen of them, the plan has a single point of failure on the buyer side, and you should ask for a second owner before kickoff.
Then filter to your own tasks and check the dates against your team's calendar. A plan that promises a kickoff in the week your implementation lead is on leave is already late. Rocketlane's help center also describes automations that watch due dates and notify the project owner when a task is overdue, so someone is told when a date is missed.
Where the sales deal stops and the project starts
The handoff is documented differently by each vendor. Rocketlane's help center says a deal-based HubSpot workflow creates a project when a deal reaches configured stages such as Closed Won or Contract Sent. GUIDEcx's Salesforce page says a Salesforce opportunity that reaches Closed Won, or another chosen stage, starts a new project, and that project details, customer records, assigned team members, billing information and custom fields are mapped across.
Both start a new project from the deal record. Flowla's onboarding page says its agent builds the onboarding plan from the sales call notes when a deal closes won in the CRM, before kickoff. All three are vendor statements read on 10 Nov 2026. If your joint execution plan is built before signature, check that the signed plan and the project plan are the same document, or at least that nobody retypes the dates.
When not to use one
A joint execution plan on a small deal is theater. A buyer who wants to subscribe to a tool for ten seats does not need phases and resourcing. Use the heavier form when the buyer will assign staff to the work, when legal and security each have their own timeline, or when go-live depends on something outside the contract such as a data migration.
For everything else, keep to the shorter plan. The library templates for a services-heavy implementation deal and a proof of concept use the project form; the templates for an SMB self-serve upgrade and a renewal do not. See the Template Library.
Sources
- Dock, mutual action plan page, read 10 Nov 2026
- Accord, implementation use case, read 10 Nov 2026
- Rocketlane help center, project plan, read 10 Nov 2026
- GUIDEcx, pricing page, read 10 Nov 2026
- GUIDEcx, Salesforce integration, read 10 Nov 2026
- Rocketlane help center, HubSpot integration, read 10 Nov 2026
- Flowla, customer onboarding, read 10 Nov 2026
Last reviewed 10 Nov 2026.