Sales Strategy Planning
SkillDev toolsPropose 1, 2 sales motions, tier structure, channel mix, risks, and approval boundaries from a campaign brief. Use when creating or revising a SalesPlan.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Sales Strategy Planning skill
What this skill tells your AI
The instructions your AI receives, as published by kami-community/kami in skills/sales_strategy/SKILL.md and read by ahel’s review.
Procedure
- Read campaign config: offer, ICP, geo, exclusions, deal range, approved claims, caps, allowed channels, autonomy policy.
- Classify the primary goal: book meetings vs drive pipeline vs re-engage dormant accounts.
- Propose 1–2 motions (e.g. signal_outreach + x_dm) with rationale tied to ICP and deal size.
- Define 3 tiers:
- Tier 1: highest fit + recent intent signal; buying-group mapping; manual approval before send
- Tier 2: good fit, moderate signals; reviewer-gated sequences
- Tier 3: broad fit; lower touch, capped volume
- Write channel_rationale — why email primary, when X is additive (never bulk X).
- List risks (deliverability, thin evidence, long sales cycle) and prerequisites (sender DNS, approved claims locked).
- Estimate weekly activity: accounts researched, contacts, sends, followups.
- Set approval_scope: always include
first_sendif policy requires; addx_dm,calendar_invite,sequence_activationas applicable.
Output
Return a SalesPlan JSON object with status: "draft". Never include prose-only plans.
Hard rules
- Motions must use only channels in
allowed_channels - Do not promise reply rates or revenue without cohort evidence
- Revise plans increment
version; never overwrite approved plans in place
Signals
- GitHub stars
- 64
- Forks
- 9
- Last commit
- Aug 2026
Advanced
- Item type
- skill
- Key
sales-strategy-kami-community- Source
- github.com/kami-community/kami