<< All versions
Skill v1.0.0
currentAutomated scan100/100kami-community/kami/sales-strategy
──Details
PublishedNovember 4, 2026 at 05:18 AM
Content Hashsha256:1c1519f4bc8d44c7...
Git SHA28346b92e415
──Files
Files (1 file, 1.5 KB)
SKILL.md1.5 KBactive
SKILL.md · 33 lines · 1.5 KB
name: sales_strategy description: Propose 1–2 sales motions, tier structure, channel mix, risks, and approval boundaries from a campaign brief. Use when creating or revising a SalesPlan. metadata: version: "1.0.0"
Sales Strategy Planning
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