Skill 1
Milestone intake and confirmation check
Use when buyer and seller milestones, dates, owners, or dependencies need to be sorted by confirmation status before building a mutual action plan.
Back to Skill Library
Deal execution workflow library
Mutual action plan
Build shared milestones, owners, blockers, and approval checkpoints for deals or customer implementations.
This is a complete workflow library with 5 individual skills. Download the full library or pick the specific skill folder your team needs first.
Individual skills in this library
Use one skill at a time, or keep the full workflow together.
Some AI tools expect one skill folder per upload. Download the full library when you want the whole workflow, or download an individual skill when you only need one job done.
Skill 2
MAP builder
Use when reviewed milestones and dependencies need to become a clear mutual action plan with owners, dates, assumptions, and approval gates.
Skill 3
Approval gate mapper
Use when MAP milestones may require legal, security, procurement, implementation, finance, or executive review before customer sharing.
Skill 4
MAP risk and blocker brief
Use when a mutual action plan needs internal risk, blocker, dependency, or slippage visibility before buyer-facing recap.
Skill 5
Buyer-facing MAP recap
Use when a buyer-facing mutual action plan recap must be prepared after internal review of milestones, risks, commitments, and approval gates.
Security fit check
Is the public Mutual action plan library enough, or does this need deeper review?
Use the public library when the workflow is low-risk, the inputs are already sanitized, and a team member can review the output before it reaches a buyer or customer.
Do deeper review when this workflow touches real tools, data sources, role ownership, approval paths, or customer-facing output.
Deal executionAccount ExecutiveSales ManagerCustomer Success
Good deeper-review trigger signals
- The workflow touches customer, prospect, CRM, proposal, security, pricing, or campaign data.
- Different teams disagree on the approved source of truth.
- The AI output could become customer-facing, revenue-impacting, or compliance-sensitive.
- You need reusable eval checks before asking more people to use the workflow.