sales-mutual-action-plans
Skill0 starsChanged 42 days agoMITView on GitHub
Use when a complex B2B purchase involves multiple approvers, stalls before signature, or has slipping milestones.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- postgres-locking-joinsSkill
- ai-bug-patternsSkill
- compressed-ndjson-boundariesSkill
- http-resume-integritySkill
- linux-io-latency-triageSkill
- macos-disk-space-recoverySkill
- minimal-sufficient-evidenceSkill
- modularize-large-filesSkill
- patch-reproducer-validitySkill
- prompt-cache-boundariesSkill
- proton-drive-selective-backupSkill
- transactional-outbox-deliverySkill
- conventional-commitsSkill
- git-advanced-mergingSkill
- git-bisect-forensicsSkill
- git-data-recoverySkill
- git-hooksSkill
- git-rerereSkill
- git-reset-mechanicsSkill
- git-revisions-syntaxSkill
- git-rewriting-historySkill
- git-submodulesSkill
- git-worktreesSkill
- github-ssh-keysSkill
- npm-publish-ci-pitfallsSkill
- sapling-stacked-pr-workflowSkill
- go-concurrency-patternsSkill
- go-data-idiomsSkill
- go-error-handlingSkill
- go-interfaces-embeddingSkill
- go-pprof-profilingSkill
- marketing-funnel-diagnosisSkill
- marketing-geo-experimentsSkill
- marketing-incrementalitySkill
- marketing-positioning-testsSkill
- python-descriptors-mroSkill
- python-logging-cookbookSkill
- python-scaling-regression-testsSkill
- python-unicode-gotchasSkill
- rust-compile-time-invariantsSkill
- rust-deterministic-concurrency-testsSkill
- rust-error-identity-boundariesSkill
- rust-regex-search-contractsSkill
- rust-runtime-bug-classesSkill
- rust-tokio-actor-deliverySkill
- rust-tokio-cancellation-safetySkill
- sales-discovery-qualificationSkill
- sales-pipeline-forecast-calibrationSkill
- sales-value-negotiationSkill
- ai-triage-evaluationSkill
- container-image-patchingSkill
- dependency-artifact-integritySkill
- dnssec-sentinel-diagnosticsSkill
- iam-policy-change-replaySkill
- rbvm-applicabilitySkill
- rbvm-asset-evidenceSkill
- rbvm-guarded-remediationSkill
- rbvm-priority-decisionsSkill
- rbvm-risk-exceptionsSkill
- The first 60 shown.
The file
Files
Sales Mutual Action Plans
A deal is a network of buyer decisions and dependencies, not a seller's sequence of meetings. A mutual action plan works backward from the buyer's first useful outcome; both sides must confirm responsibilities and dates.
Map decisions before scheduling tasks
For each stakeholder, record role, desired outcome, decision authority, concern, evidence source, and agreed engagement route. People may hold several roles; unknown roles stay unfilled.
| Role | Evidence needed |
| Funding authority | Expenditure authority and conditions |
| Users and implementation owner | Acceptance criteria, capacity, adoption responsibilities |
| Security, legal, procurement | Applicable reviews, prerequisites, lead times, signature authority |
| Internal advocate | Demonstrated influence, personal stake in success, and internal advocacy |
Friendliness does not establish champion status. Verify advocacy through actions, such as securing a stakeholder discussion; avoid covert tests or bypassing contacts.
Build the dependency plan
- Confirm the buyer's outcome, target date, and reason the date matters. Include onboarding and realization of value, not only signature. Use estimated dates when urgency is unverified.
- Separate solution selection from purchasing mechanics. Map how approval becomes an executable agreement, including reviews that can run in parallel. Ask their owners for realistic durations.
- Co-create milestone rows: outcome, acceptance evidence, buyer owner, seller owner, due date, prerequisite, status, and next decision. Mark unconfirmed assignments as proposals.
- Find the dependency chain controlling the outcome date. When a step slips, show affected milestones and choices: move the outcome, change scope, or add authorized capacity. Reconfirm changed commitments.
- Review open decisions with the buyer at agreed checkpoints. If participation stops, diagnose priority or feasibility and revise confidence; rolling dates forward does not preserve agreement.
Example: A buyer requires security clearance before production access. Moving the contract date earlier does not accelerate clearance. Validate whether a limited, approved test can proceed independently; otherwise rebaseline implementation.
Sources
Pitfalls
- Seller quarter-end is not a buyer deadline.
- Calendar invitations and document views do not establish commitment.
- A shared plan must exclude private stakeholder assessments and internal negotiation limits.
- Named owners do not authorize outreach, document sharing, concessions, or contractual commitments.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

