- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add borghei/Claude-Skills --skill channel-economics -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add borghei/Claude-Skills --skill channel-economics -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add borghei/Claude-Skills --skill channel-economics -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add borghei/Claude-Skills --skill channel-economics -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/borghei/Claude-Skills/tree/HEAD/business-growth/channel-economicsDe l'éditeur
End-to-end financial modeling and design of go-to-market channels: direct sales economics, reseller / distributor margin structures, marketplace fees, partner tier economics, channel conflict resolution, and the TCO frameworks that compare channel options apples-to-apples.
This skill provides the financial backbone for channel strategy. For strategic partnership design (which channel to invest in, how to structure the partnership), see business-growth/partnerships-architect. For partner-deal-level approval mechanics, see business-growth/deal-desk.
Six core channel models. Most companies use a mix.
What's the product's complexity + price point?
Low complexity, low price (< $10k ACV):
├── Self-serve / PLG → no channel
├── E-commerce → direct via web
└── Marketplace (AWS / Azure / GCP / Salesforce AppExchange) → if buyer already there
Medium complexity, mid-market price ($10k - $250k ACV):
├── Inside sales / SDR-led direct → if buyer journey is well-understood
├── Reseller / VAR (Value-Added Reseller) → if local presence / language matters
├── Marketplace → if buyer prefers procurement via existing relationship
└── Embedded / OEM → if your product is a component in someone else's offering
High complexity, enterprise ($250k+ ACV):
├── Direct field sales → standard for high-touch enterprise
├── Strategic SI / Integrator (Accenture, Deloitte, etc.) → if implementation is a substantial project
├── ISV / Embedded → if you're a feature in a larger platform
└── Reseller / Distributor → for regional or vertical specialty
Operational / managed-service buyer:
└── MSP (Managed Service Provider) → if customer wants outsourced operations
See references/channel-models-direct-partner-marketplace.md for each model in depth: economic structure, typical margin splits, when each works / fails, contract patterns.
Apples-to-apples channel comparison requires a consistent TCO model. The naive comparison ("direct gets 100%, reseller gets 70%") misses critical costs.
Channel Contribution Margin
= Channel-attributed Revenue
− COGS
− Partner Discount/Commission
− Channel-specific Sales Cost (allocated)
− Channel-specific Marketing Cost (MDF, co-marketing)
− Partner Enablement Cost (training, certification)
− Channel Operations Cost (channel manager headcount)
− Channel-specific Support Cost (T1 partner support)
For a $100k ACV deal:
The "30% discount" reseller deal is more like 14.5% margin difference once everything's counted. Marketplace can look better than direct on per-deal basis (Amazon's sales team brings the buyer) — but volume varies.
Use scripts/channel_margin_calculator.py --deal deal.yaml --channel <type> to model this for any deal.
See references/margin-and-tco-frameworks.md for the full TCO framework, per-cost-line guidance, and how to allocate "fully-loaded" sales / marketing / ops costs.
Multi-tier partner programs (Authorized → Silver → Gold → Platinum) are common. Designed badly, they reward effort that isn't valuable; designed well, they reward outcomes that drive growth.
Use scripts/partner_tier_economics.py --tiers tiers.yaml to model tier economics: gross margin per tier, partner-side incentive, break-even revenue per partner per tier.
Three common reward structures, each with trade-offs:
Partner buys from you at a discount; sells to customer at list (or close). Margin = the spread.
Pros: Simple. Cash flow goes to partner immediately. Cons: Hard to incentivize specific behaviors. Discount is locked in regardless of performance.
Partner pays full price (or near it); earns rebate quarterly / annually based on revenue / tier achievement.
Pros: Ties reward to actual achievement; behaviors can be incentivized (e.g., bonus for selling new products). Cons: Cash-flow burden on partner. Complex to administer.
Per-deal or per-period bonuses for specific actions: bring leads, attend events, certify staff.
Pros: Highly targetable. Rewards specific behaviors you want. Cons: Easy to game; admin overhead high; partners often expect it without producing.
Channel conflict happens when multiple sales paths chase the same customer. Common forms:
Customer can buy via AWS Marketplace OR direct. If price is lower direct, customer feels gamed. If price is same, why not just use marketplace? Common resolution:
See references/channel-conflict-resolution.md for the full conflict-resolution playbook including deal registration process, neutral arbitration, conflict-of-interest disclosure.
Before modeling the channel economics, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
scripts/channel_margin_calculator.py per channel option at expected ACVscripts/partner_tier_economics.py to size the gates and benefitsbusiness-growth/contract-and-proposal-writer)scripts/channel_margin_calculator.py --deal deal.yaml --channel partnerscripts/channel_mix_optimizer.py --revenue revenue.csv examines contribution margin per channel + identifies under-/over-invested channelsAll scripts: stdlib only, argparse CLI, JSON or markdown output.
In Scope:
scripts/channel_margin_calculator.py, including an all-channel comparisonscripts/partner_tier_economics.pyscripts/channel_mix_optimizer.pyOut of Scope:
business-growth/partnerships-architect/)business-growth/deal-desk/)business-growth/contract-and-proposal-writer/)business-growth/pricing-strategy/)sales-success/sales-operations/)Important Caveats:
business-growth/partnerships-architect — strategic partnership design (this skill = the economics; that one = the strategy)business-growth/deal-desk — approval mechanics for partner deals (this skill = "what does it cost"; deal desk = "should we approve")business-growth/pricing-strategy — sets list pricing that channel economics deviates frombusiness-growth/revenue-operations — channel revenue is segmented in RevOps reportingbusiness-growth/contract-and-proposal-writer — drafts partner agreementssales-success/sales-operations — runs channel ops (deal registration, MDF approval, certification tracking)c-level-advisor/cs-cro-advisor — strategic channel-mix decisions are CRO-level>
---name: channel-economicsdescription: >---# business-growth/channel-economics/SKILL.mdFAQ
Téléchargez business-growth/channel-economics/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/borghei/Claude-Skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.