Channel Economics

channel-economics

Purpose

Help Head of Commercial / RevOps / VP Sales answer three questions at the quarterly channel review:

1. What does each channel actually cost to serve, fully loaded? (direct headcount, channel manager attribution, partner discount, MDF, enablement time, support load, allocated overhead) 2. What is the ROI of each channel under three lenses? (cash ROI year-1, LTV-adjusted ROI, marginal ROI — next dollar of investment) 3. What is the optimal channel mix subject to our strategic constraints? (minimum direct floor, maximum partner concentration ceiling, sensitivity to CAC shifts)

The skill emits per-channel verdicts (DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT), a sensitivity-tested mix recommendation, and the diminishing-returns inflection point. It does not pick the strategy — humans do, with the numbers loaded honestly for the first time.

When to use

• Quarterly channel review: pipeline is 60/40 or 50/50 direct vs partner and you don't actually know which one is profitable
• Considering hiring a channel manager — need to know if the channel can clear the loaded-cost bar
• Partner program ROI question from the board ("we spent $X on MDF — what did we get?")
• A segment is over-indexed to one channel and you suspect mix dogma is blocking the other
• About to expand into a new region and need to decide direct-first vs partner-first
• M&A diligence: target company claims "partner-led at 70% gross margin" — need to validate after loading

Do not use for:

• Designing partner tiers, joint GTM motion, revshare splits → partnerships-architect
• SDR-to-AE routing, lead scoring, MQL definitions → business-growth/revenue-operations
• Strategic CRO decisions ("should we hire a VP Sales?", comp plan design) → c-level-advisor/cro-advisor
• Quarterly close, GAAP revenue recognition, channel-level P&L for historical reporting → finance/financial-analysis
• Per-deal discount approval → deal-desk
• Pricing model design → pricing-strategist

Workflow

Step 1 — Intake channel data

Fill assets/channel_data_template.md (≈ 20 min). Capture per channel: deal count TTM, ARR TTM, avg deal size, gross margin %, CAC, sales-cycle days, retention rate, expansion rate, partner discount %, all attributable costs (SDR / AE / SE / channel manager / CS / support / marketing / partner MDF / tooling / overhead allocation %).

The template surfaces the costs teams most often forget: partner enablement time, certification investment, channel-conflict resolution overhead, channel-manager headcount cost.

Step 2 — Compute cost-to-serve per channel

Run scripts/cost_to_serve_calculator.py --input channel.json --output markdown.

Output: fully-loaded cost-to-serve per deal AND per dollar of ARR, with direct costs broken out from allocated overhead, and a "true gross margin" line after channel-specific load. Flags double-counting and surfaces hidden costs.

Run once per channel. The "true gross margin" line is the input the next two scripts care about.

Step 3 — Compute ROI per channel under three lenses

Run scripts/channel_roi_analyzer.py --input roi.json --profile saas --output markdown.

Output: per channel, three ROI numbers (Cash year-1, LTV-adjusted, Marginal), the diminishing-returns inflection point, and a verdict: DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT.

Verdict logic is deterministic and surfaced in the report. Humans can override; the skill won't.

Step 4 — Optimize channel mix subject to constraints

Run scripts/channel_mix_optimizer.py --input mix.json --profile saas --output markdown.

Output: recommended mix that maximizes effective ARR subject to constraints (min direct %, max partner concentration), plus a sensitivity table (what if direct CAC rises 20%? what if partner discount widens 5 points?).

Step 5 — Decide

Take the three reports into the quarterly channel review. The skill recommends; the human commits.

Scripts

• scripts/cost_to_serve_calculator.py — fully-loaded cost-to-serve per deal AND per $ ARR, with hidden-cost surfacing
• scripts/channel_roi_analyzer.py — 3-lens ROI (Cash / LTV / Marginal) with verdicts and diminishing-returns inflection
• scripts/channel_mix_optimizer.py — constrained mix optimizer with sensitivity scenarios

All scripts: stdlib only. --help, --sample, --input, --output work on all three. Industry tuning via --profile {saas,api,enterprise-software,marketplace,hardware} on the two analyzers.

Quick example

# Emits fully-loaded cost-to-serve per channel (direct vs partner-led) for the built-in sample channel data
cd commercial/skills/channel-economics && python3 scripts/cost_to_serve_calculator.py --sample

References

• references/channel_economics_canon.md — Skok, Bessemer State of the Cloud, Tunguz, Pacific Crest / KeyBanc SaaS Survey, Ramanujam, Jay McBain (Canalys)
• references/cost_to_serve_canon.md — Kaplan & Cooper (ABC), Horngren, Jeremy Hope, IBM CTS case studies, McKinsey, Gartner, BCG
• references/channel_anti_patterns.md — Forrester, Tunguz, Hessling, HBR, SiriusDecisions, MIT Sloan, Gartner

Assumptions

• Channel economics is a forward-looking question. Historical channel P&L is finance's job; this skill loads forward economics for a decision.
• "Channel" means a coherent go-to-market motion (direct outbound, partner-led, marketplace, reseller, OEM). It does not mean a marketing source.
• Cost-to-serve requires honest overhead allocation. The script validates that overhead % is consistent across channels — false partner-margin lift from inconsistent allocation is the #1 anti-pattern.
• LTV inputs (retention, expansion) are per-channel, not pooled. Partner-sourced customers often retain differently than direct-sourced — this difference is usually the largest economic variable and the most ignored.
• Industry profiles (--profile) tune defaults for benchmarks (e.g., SaaS direct CAC payback target ~12mo, enterprise ~18mo) — they don't override your numbers.
• This is a decision-support skill. Output is verdicts and a recommended mix, never an automatic resource reallocation.

Anti-patterns

• Treating "influenced" deals as "sourced" deals. A partner that touched a deal your AE already had is not channel-sourced revenue. Loading this as partner revenue inflates partner ROI and inflates direct CAC simultaneously.
• Inconsistent overhead allocation. Allocating 25% overhead to direct deals and 5% to partner deals because "the partner handles the overhead" is false. The partner manager, partner program, MDF, certification, and conflict-resolution all live in your P&L.
• Ignoring enablement time as a cost. Every hour your AE spends co-selling with a partner is a direct cost charged to the partner channel — most teams forget to load it.
• MDF without ROI tracking. Market Development Funds disbursed without an attributable pipeline ROI are just a partner-discount extension. The skill flags MDF with no return.
• Channel-mix dogma. "We're a partner-first company" / "we don't sell direct" blocks profitable segments. Mix should follow the math, not the slogan.
• Computing channel ROI without retention differential. If partner-sourced customers churn 5 points higher than direct, ignoring it overstates partner LTV by 30-50%. Per-channel retention is mandatory input.
• No cost-attribution for channel-manager headcount. A $200k channel manager managing $4M of partner ARR is $50 of channel-manager cost per $1k ARR — material to the verdict.
• Confusing this skill with partnerships-architect. That skill designs the partner program. This skill tells you whether the program pays for itself.

Distinct from

• commercial/partnerships-architect — partner tier design, joint GTM motion, revshare splits, partner enablement. Partner program structure, not partner program economics. This skill consumes the program structure as input and emits the economic verdict.
• business-growth/revenue-operations — lead routing, SDR motion, MQL definition, pipeline operations. RevOps owns the funnel mechanics; this skill loads the channel-level economic outcome.
• c-level-advisor/cro-advisor — strategic CRO judgment: when to hire a VP Sales, comp plan philosophy, territory design, multi-year revenue strategy. CRO advisor consumes channel-economics output as one input among many.
• finance/financial-analysis — close-and-report on historical channel P&L per GAAP. This skill is forward-looking decision support; finance is historical record. Different time horizon, different audience, different output.
• commercial/deal-desk — per-deal discount approval. Operates daily; this skill operates quarterly.
• commercial/pricing-strategist — pricing model and tier design. Pricing is input; channel economics is what happens at that pricing across channels.

Forcing-question library (Matt Pocock grill discipline)

Walked one at a time by /cs:grill-commercial or the orchestrator. Recommended answer + canon citation per question. Never bundled.

1. "What's your fully-loaded cost-to-serve per channel — including channel-manager headcount, MDF, partner enablement time, and overhead allocation?" Recommended: load all four. Most teams load partner discount but forget the channel-manager headcount and the enablement time, inflating partner margin by 8-15 points. Canon: Kaplan & Cooper (HBR 1988) — Measure Costs Right: Make the Right Decisions. Activity-Based Costing was invented precisely because channel costs hide in overhead and distort margin comparisons.

2. "What is the retention differential between direct-sourced and partner-sourced customers?" Recommended: instrument per-channel retention BEFORE running channel ROI. A 5-point retention gap moves LTV by 30-50%. Canon: David Skok (For Entrepreneurs — SaaS Metrics 2.0). LTV = (ARPA × Gross Margin) / Churn. Channel-blind churn is the most common source of false channel ROI.

3. "What share of 'channel-sourced' pipeline did your team actually originate?" Recommended: if your AE already had the account, it's not channel-sourced — it's channel-influenced. Influence and source are different economic lines. Canon: SiriusDecisions / Forrester channel attribution research — confused source vs. influence is the #1 reason partner ROI is overstated industry-wide.

4. "What is the marginal ROI of the next dollar invested in partner program vs. direct sales?" Recommended: compute the diminishing-returns curve on both. Average ROI hides the fact that the next dollar might earn 0.3x while the average earns 2.1x. Canon: Tomasz Tunguz (Tomasz Tunguz blog — channel CAC analyses). Average ROI is a vanity metric; marginal ROI drives investment decisions.

5. "What's your MDF-to-attributable-pipeline ratio in the last 4 quarters?" Recommended: < 5:1 (every $1 of MDF should generate ≥ $5 of attributable pipeline within 2 quarters). Anything looser is partner-discount theatre. Canon: Jay McBain (Canalys) — State of the Channel research. MDF without attribution discipline is the most expensive form of channel subsidy.

6. "Is your channel-mix dogma blocking a profitable segment?" Recommended: surface the dogma ("we're partner-first", "we don't sell direct in SMB") explicitly. Mix should follow the segment math. Canon: MIT Sloan Management Review — When Channel Conflict Means Growth. Dogmatic single-channel strategies forfeit 15-25% of TAM in mid-market specifically.

7. "What overhead-allocation methodology are you applying — and is it consistent across direct and partner?" Recommended: same methodology, same denominator, both channels. Inconsistent allocation is the silent killer of channel-economics analysis. Canon: Charles Horngren (Cost Accounting: A Managerial Emphasis) — allocation consistency is the precondition for cross-segment margin comparison. Without it, every conclusion is contaminated.

Walk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invoke cost_to_serve_calculator.py → channel_roi_analyzer.py → channel_mix_optimizer.py in sequence.

Channel Data Template

Fill this out in ~20 minutes. The three scripts in this skill all consume JSON; this template gives you the schema with annotations on what to put and why.

If you don't know a value, leave it `null` (or the explicit "$0 unknown") and note it — the scripts surface unknowns explicitly rather than silently substituting.

---

Intake checklist (before you fill anything)

• [ ] Define "channel" — a coherent go-to-market motion (e.g., direct, partner-led, marketplace, reseller, oem). NOT a marketing source.
• [ ] Confirm allocation methodology is the same across all channels (revenue-share or activity-driver, not mixed)
• [ ] Confirm retention numbers are per-channel, not pooled
• [ ] Confirm "channel-sourced" deals meet the strict definition: partner originated the opportunity AND brought it unqualified
• [ ] Identify your industry profile: saas | api | enterprise-software | marketplace | hardware

---

Template 1 — Input for cost_to_serve_calculator.py

Run once per channel.

{
  "channel_name": "partner-led-EMEA",
  "deal_volume": 80,
  "gross_revenue": 4000000,
  "costs": {
    "sdr_attribution": 60000,
    "ae_attribution": 240000,
    "sales_engineer_attribution": 90000,
    "channel_manager_attribution": 180000,
    "customer_success_attribution": 120000,
    "support_attribution": 70000,
    "marketing_attribution": 50000,
    "partner_discount": 600000,
    "partner_MDF": 80000,
    "partner_enablement_time": 40000,
    "certification_investment": 20000,
    "channel_conflict_overhead": 15000,
    "tooling_attribution": 25000,
    "overhead_allocation_pct": 15.0
  }
}

Field-by-field guidance

---

Template 2 — Input for channel_roi_analyzer.py

Run once across all channels.

{
  "profile": "saas",
  "channels": [
    {
      "channel": "direct",
      "investment_ttm": {
        "programs": 200000,
        "headcount_cost": 1600000,
        "partner_program_cost": 0,
        "mdf": 0,
        "tooling": 80000,
        "training": 60000
      },
      "returns_ttm": {
        "new_arr": 3800000,
        "expansion_arr": 900000,
        "retained_arr_attributable": 2400000
      }
    },
    {
      "channel": "partner-led",
      "investment_ttm": {
        "programs": 150000,
        "headcount_cost": 360000,
        "partner_program_cost": 280000,
        "mdf": 120000,
        "tooling": 30000,
        "training": 80000
      },
      "returns_ttm": {
        "new_arr": 1400000,
        "expansion_arr": 200000,
        "retained_arr_attributable": 900000
      }
    }
  ]
}

Field guidance

---

Template 3 — Input for channel_mix_optimizer.py

Run once across all channels with constraints.

{
  "profile": "saas",
  "channels": [
    {
      "name": "direct",
      "deal_count_ttm": 120,
      "arr_ttm": 6000000,
      "avg_deal_size": 50000,
      "gross_margin_pct": 75,
      "cac": 18000,
      "sales_cycle_days": 75,
      "retention_rate": 0.92,
      "expansion_rate": 1.18,
      "partner_discount_pct": 0
    },
    {
      "name": "partner-led",
      "deal_count_ttm": 80,
      "arr_ttm": 4000000,
      "avg_deal_size": 50000,
      "gross_margin_pct": 75,
      "cac": 10000,
      "sales_cycle_days": 90,
      "retention_rate": 0.86,
      "expansion_rate": 1.08,
      "partner_discount_pct": 20
    }
  ],
  "constraints": {
    "min_direct_pct": 30,
    "max_partner_concentration_pct": 50
  }
}

Field guidance

---

After filling

1. Save each template as a JSON file (e.g., channel-cts-partner.json, channel-roi.json, channel-mix.json) 2. Run in sequence:

   python scripts/cost_to_serve_calculator.py --input channel-cts-partner.json --output markdown > out-cts-partner.md
   python scripts/channel_roi_analyzer.py --input channel-roi.json --profile saas --output markdown > out-roi.md
   python scripts/channel_mix_optimizer.py --input channel-mix.json --profile saas --output markdown > out-mix.md

3. Bring all three reports to the quarterly channel review.

Channel Anti-Patterns

The eight anti-patterns this skill is built to detect, with citations. Most channel-economics decisions fail because of these patterns, not because the math is wrong.

---

1. Channel-led deals from your own pipeline = direct cost + partner cut

Pattern: Your AE sources an account, qualifies it, runs discovery, scopes the solution — and then a partner gets attached at the contract stage for the partner cut. The deal closes, is reported as "channel-sourced", and the partner gets margin.

Why it kills: You paid full direct cost (AE time, SE time, marketing) AND gave away partner margin. The deal looks profitable as "channel-led" but is value-destroying in reality.

Detection: require first-touch attribution in CRM. If the first-touch is internal but the deal closes as channel-sourced, flag it.

Source: Forrester Research, The Channel-Influence vs. Channel-Source Gap, 2019. Industry data: 25-40% of "channel-sourced" deals are actually channel-influenced direct deals.

---

2. No overhead allocation = false partner-margin lift

Pattern: Partner channel reports 75% gross margin while direct reports 60%. Look closer: direct channel gets 25% overhead allocation; partner channel gets 5% "because the partner handles overhead." The partner does not, in fact, handle overhead — your channel manager, partner program, MDF, and certification are all in YOUR P&L.

Why it kills: Apparent partner-margin lift drives over-investment in partner program. When the executive team eventually does honest allocation, partner margin collapses 8-15 points.

Detection: validate overhead-% is consistent across channels. If partner overhead allocation is <50% of direct, flag for review.

Source: Tomasz Tunguz, The Hidden Costs of Channel Programs, tomtunguz.com analyses 2021-2023. See also Horngren on allocation consistency.

---

3. Ignoring enablement time as cost

Pattern: Your AE spends 4 hours/week on partner co-selling, your SE spends 6 hours/week on partner technical enablement, your CS team handles tier-2 support that partners offload. None of this is loaded into channel cost.

Why it kills: Partner enablement time is often 15-30% of total channel cost, completely unattributed. The channel looks far more efficient than it is.

Detection: cost_to_serve_calculator.py flags partner_enablement_time and certification_investment when left at $0.

Source: Jay McBain (Canalys), State of the Channel research; Joe Hessling, Partner Program ROI Studies (channeltivity.com). Industry data: time-tracked enablement attribution increases partner channel cost by 15-30% over naive accounting.

---

4. MDF without ROI tracking

Pattern: Market Development Funds disbursed to partners without an attributable pipeline ROI. Partners take the MDF, deliver an event or campaign of dubious value, and no pipeline is traceable to the spend.

Why it kills: MDF without attribution is just a partner discount in disguise — and undisciplined. Industry-median MDF-to-pipeline ratio is 3.5:1; best-in-class is >7:1. If yours is <3:1 (or untracked), you have an unbudgeted discount line.

Detection: require MDF requests to commit to attributable pipeline targets BEFORE disbursement. Reconcile quarterly.

Source: Jay McBain (Canalys), MDF discipline research. SiriusDecisions (now Forrester) MDF benchmarks: 60% of MDF spend has no attributable pipeline tracking at all.

---

5. Channel-mix dogma ("we don't sell direct") blocks profitable segments

Pattern: A founder or CRO has a strong belief — "we're a partner-first company", "we don't sell direct in SMB", "we never sell direct in EMEA" — that overrides the segment-level economics. Profitable segments get starved because the strategy slogan doesn't allow direct motion there.

Why it kills: Mix should follow the math. Industry data shows dogmatic single-channel strategies forfeit 15-25% of TAM in mid-market specifically.

Detection: force the explicit articulation of the dogma in the planning conversation. "What's the segment we DON'T sell into, and why?"

Source: MIT Sloan Management Review, When Channel Conflict Means Growth, Frazier & Lassar (1996, updated 2019). Also: HBR on channel-conflict mismanagement, Cespedes (2014).

---

6. Treating influenced as sourced

Pattern: Partner is involved somewhere in a deal cycle — sometimes only at signature — and the deal is reported as "channel-sourced." Influence and source get conflated.

Why it kills: Inflates partner contribution by 25-40%. Drives mis-allocation of channel investment. Channel-program ROI becomes uninterpretable.

Detection: require strict first-touch + qualified-source criteria. Channel-sourced = partner originated the opportunity AND brought it to your team unqualified.

Source: SiriusDecisions (now Forrester), Channel Attribution Models, 2018-2022 research. Single most-cited source-vs-influence taxonomy in B2B SaaS.

---

7. No cost-attribution for channel-manager headcount

Pattern: Channel manager salary ($150-$250k loaded) is bucketed under "G&A" or "Sales Overhead" rather than attributed to the channel they manage. The channel reports better economics because its biggest cost line is hidden.

Why it kills: A $200k channel manager managing $4M of partner ARR is $50 of channel-manager cost per $1k ARR — material to the channel verdict. Hiding it is the most common single-line distortion in channel economics.

Detection: cost_to_serve_calculator.py flags channel_manager_attribution at $0 as a hidden-cost line.

Source: Gartner, Service Delivery Cost Allocation in Multi-Channel Technology Vendors, 2022. McKinsey CTS research.

---

8. Channel ROI computed without retention differential

Pattern: Channel ROI calculation uses pooled retention assumption (e.g., 90% across all channels) when in fact partner-sourced customers retain at 84% and direct-sourced retain at 92%. LTV calculation is inflated for the partner channel.

Why it kills: A 5-point retention gap moves LTV by 30-50%. Most channel investment decisions are made on LTV, so the wrong retention assumption produces the wrong investment decision.

Detection: require per-channel retention as mandatory input. channel_mix_optimizer.py will not compute effective LTV without a per-channel retention number.

Source: David Skok (For Entrepreneurs — SaaS Metrics 2.0). LTV = (ARPA × Gross Margin) / Churn — channel-blind churn is the most common source of false channel ROI.

---

Bonus anti-pattern: the "we'll figure out attribution later" trap

Pattern: Channel program launches without an attribution model. Six quarters later, no one can answer "did this work?" because the data was never structured.

Why it kills: Attribution must be designed at program-launch, not retrofit. Retroactive attribution is always contested.

Detection: force the attribution model to be in writing BEFORE the channel program is launched.

Source: HBR, Why Channel Programs Fail (Cespedes, 2014). Also: Tomasz Tunguz on channel-trap analyses.

---

How this skill detects the anti-patterns

Channel Economics Canon

The authoritative reference set for direct-vs-partner economics, channel ROI computation, and channel-mix decision-making. Use this when validating the assumptions inside cost_to_serve_calculator.py, channel_roi_analyzer.py, and channel_mix_optimizer.py.

---

1. David Skok — For Entrepreneurs: SaaS Metrics 2.0

Skok's framework gives the LTV / CAC equation the industry treats as canonical:

• LTV = (ARPA × Gross Margin %) / Churn Rate
• LTV / CAC ≥ 3.0 is the floor for sustainable channel investment
• CAC Payback ≤ 12 months is the SaaS target (longer for enterprise)

The channel-economics application: per-channel LTV/CAC and per-channel payback, never pooled. Pooled metrics hide the fact that one channel is funding another.

Source: forentrepreneurs.com — SaaS Metrics 2.0 — A Guide to Measuring and Improving What Matters (2014, updated 2018).

---

2. Bessemer Venture Partners — State of the Cloud (annual)

BVP's annual benchmark report is the single most-cited source for channel mix and CAC benchmarks across public + private SaaS:

• Public SaaS gross margins cluster 70-80%; partner-led channels typically run 5-10pts lower after load
• Sales efficiency (Magic Number) ≥ 0.7 is the funding bar; channel inefficiency drags this below the bar fastest
• Partner-led companies that scale past $100M ARR almost universally have <40% partner concentration — single-partner risk dominates above this line

Source: Bessemer Venture Partners, State of the Cloud report series, 2014-2024 editions.

---

3. Tomasz Tunguz — Channel CAC analyses

Tunguz's blog has the most rigorous public series on channel CAC and the diminishing-returns curve specifically. Key findings replicated across cohorts:

• Marginal CAC rises non-linearly with investment scale. The first $1M in channel program returns ~3x; the next $1M returns ~1.5x; the next $1M often <1.0x.
• Average ROI is a vanity metric. Investment decisions must be made on marginal ROI.
• Channel programs that "work on paper" but fail in practice usually fail because the team funded them past the marginal-ROI inflection point without realizing it.

Source: tomtunguz.com — channel CAC posts including The Channel CAC Premium, Diminishing Returns in SaaS Sales.

---

4. Pacific Crest / KeyBanc Capital Markets — Annual SaaS Survey

The Pacific Crest survey (continued by KeyBanc) is the longest-running channel-economics benchmark — 350+ private SaaS companies surveyed annually since 2008. The channel-specific findings used in this skill:

• Median direct CAC payback: 14 months. Partner-led: 11 months (lower nominal but understates loaded cost).
• Channel-led companies with <70% true (loaded) gross margin in partner channel materially underperform direct-led peers on Rule of 40
• Mixed-motion companies (40-60% direct, balance partner) outperform single-motion peers on growth efficiency by ~15-20%

Source: KeyBanc Capital Markets, SaaS Survey annual report (most recent 2024).

---

5. Madhavan Ramanujam — Monetizing Innovation — channel chapter

Ramanujam's channel chapter introduces the "value-flow" framework:

• Every channel splits economic value between vendor, partner, and customer
• The partner-cut must be earned by partner-delivered value (lead gen, technical sale, implementation, support) — not granted by program-tier convention
• Channels where the partner-cut exceeds the value the partner delivers are economic transfers, not channel programs

Source: Madhavan Ramanujam and Georg Tacke, Monetizing Innovation (Wiley, 2016) — Chapter 8 on channel & pricing alignment.

---

6. Jay McBain (Canalys) — Channel research

McBain is the most-cited channel analyst working today. The Canalys research the skill draws on:

• MDF discipline. Industry median MDF-to-attributable-pipeline ratio is 3.5:1; best-in-class >7:1. Anything below 3:1 is undisciplined.
• Influence vs. source. Channel-influenced ≠ channel-sourced. Industry conflation overstates partner contribution by 25-40% on average.
• Channel-conflict overhead is a real and measurable cost; mature channel programs allocate 5-8% of channel-team time to conflict resolution and surface it as a P&L line.

Source: Canalys research notes by Jay McBain (formerly Forrester), 2020-2024 — see also McBain's LinkedIn newsletter Channel Insights.

---

7. KeyBanc + OpenView — Joint Channel Maturity Benchmark

Joint research between KeyBanc Capital Markets and OpenView Partners (2022-2024) establishing the channel maturity scale used in this skill's verdict logic:

• Stage 1 (Discovery): channel < 15% of revenue, <2x LTV/CAC — DEFUND or EXIT verdict
• Stage 2 (Scale): channel 15-35% of revenue, 2-3x LTV/CAC — MAINTAIN verdict
• Stage 3 (Optimization): channel 35-50% of revenue, 3-5x LTV/CAC — DOUBLE-DOWN verdict candidate
• Stage 4 (Mature): channel >50%, but check single-partner concentration — risk verdict

Source: OpenView Partners + KeyBanc Capital Markets, Channel Maturity Benchmark 2023.

---

How this skill uses the canon

• `channel_roi_analyzer.py` verdict thresholds derive from Skok (LTV/CAC ≥ 3.0 floor) and BVP cash-ROI target ranges
• `channel_mix_optimizer.py` payback targets per profile follow KeyBanc/Pacific Crest survey medians
• Diminishing-returns curve in the marginal-ROI computation traces directly to Tunguz's channel-CAC posts
• Influence-vs-source discipline in the forcing-question library comes from McBain (Canalys) and SiriusDecisions

When the user's data contradicts these benchmarks, the data wins — these are reference anchors, not rules.

Cost-to-Serve Canon

The authoritative reference set for fully-loaded cost-to-serve methodology. Use this when validating cost categories, allocation methodology, and the "hidden costs" cost_to_serve_calculator.py surfaces.

The core principle across every source below: without consistent overhead allocation, every cross-channel margin comparison is contaminated.

---

1. Robert Kaplan & Robin Cooper — Measure Costs Right: Make the Right Decisions (HBR, 1988)

The foundational paper for Activity-Based Costing (ABC). Kaplan & Cooper observed that traditional cost-allocation methods systematically distort channel and product margins:

• High-volume, low-complexity channels appear unprofitable under traditional allocation (they over-absorb overhead)
• Low-volume, high-complexity channels appear profitable (they under-absorb)
• The fix: allocate overhead by activity driver, not by revenue share

For channel economics: partner-led channels typically appear higher-margin under naïve allocation precisely because they're lower-volume + higher-complexity. ABC corrects this.

Source: Kaplan, R.S. & Cooper, R., Measure Costs Right: Make the Right Decisions, Harvard Business Review, September-October 1988.

---

2. Charles Horngren — Cost Accounting: A Managerial Emphasis

The canonical textbook (now in 16th edition, Pearson). The chapters this skill draws on:

• Chapter 14 (Cost allocation): the rule of allocation consistency — same methodology, same denominator, every comparable segment. Inconsistent allocation invalidates downstream comparison.
• Chapter 15 (Customer-profitability analysis): the channel-economics application — customer (and channel) profitability is a function of both revenue and fully-loaded cost-to-serve, never just gross margin.

The most common channel-economics error this textbook anchors: allocating overhead at 25% to direct and 5% to partner "because the partner handles the overhead." The partner does not, in fact, handle the channel manager, the partner program, the certification, the MDF, the conflict resolution — all of which sit in YOUR P&L.

Source: Horngren, Datar & Rajan, Cost Accounting: A Managerial Emphasis, 16th ed., Pearson.

---

3. Jeremy Hope — Beyond Budgeting + channel-allocation writings

Hope's Beyond Budgeting movement contributed the framework for rolling channel-cost allocation rather than annual fixed allocation. Key principle:

• Channel cost allocation must update at the same cadence as channel investment decisions (quarterly minimum)
• Annual fixed allocations lock in last year's channel mix and prevent learning
• Use rolling 4-quarter cost-to-serve for forward decisions

Source: Hope, J. & Fraser, R., Beyond Budgeting (Harvard Business School Press, 2003); BBRT (Beyond Budgeting Round Table) channel-allocation guidance papers.

---

4. IBM Cost-to-Serve transformation case studies

IBM Institute for Business Value has published a sequence of cost-to-serve transformation case studies (2010-2022). Findings replicated across cases:

• 5-15% of "gross margin" at large enterprises evaporates when partner-channel overhead is loaded honestly
• The single largest unattributed cost is technical-sale resource time (sales engineering / solution architects co-selling with partners)
• Companies that move from naive to ABC-style channel allocation typically defund 1-2 channels within 6 months — and grow the remaining channels faster

Source: IBM Institute for Business Value, Cost-to-Serve Transformation case study series.

---

5. McKinsey & Company — Cost-to-Serve research

McKinsey's go-to-market practice publishes regular CTS research. The findings this skill leans on:

• Customer-level CTS variance within a single channel is often 5-10x — meaning a channel-average CTS hides material per-customer variance
• The hidden-cost line items most teams omit, in order of impact: technical-sale time, channel-manager attribution, partner enablement time, certification investment, conflict-resolution overhead
• McKinsey's recommended cadence: refresh CTS quarterly minimum, annually at the customer level, continuously for top-decile accounts

Source: McKinsey & Company, Cost-to-Serve: Reducing complexity and increasing profitability (operations practice white papers).

---

6. Gartner — Service Delivery Cost research

Gartner's research on service-delivery cost allocation, particularly for technology vendors with mixed direct + partner motion:

• The service-delivery overhead (customer success, support, professional services) often differs by 30-50% between direct-sourced and partner-sourced customers
• Reasons: partner-sourced customers often arrive less qualified, requiring more onboarding; partner-sourced customers expand less, reducing CS leverage; partner-sourced customers escalate to vendor support faster because the partner offloads tier-2 support back
• Gartner's recommendation: instrument support-ticket-volume-per-customer by sourcing channel, not by customer size

Source: Gartner, Service Delivery Cost Allocation in Multi-Channel Technology Vendors research notes, 2021-2024.

---

7. Boston Consulting Group — Channel allocation methodology

BCG's channel-allocation methodology (from their TMT and software practices) introduces the dual-axis cost framework this skill implements:

• Direct costs: incurred specifically because of this channel (channel manager headcount, MDF, partner discount, certification spend)
• Allocated overhead: shared costs apportioned by activity driver (revenue share, deal count, or time-tracked attribution)
• The two must always be reported separately so executives can see the lever they control directly

This is the framework cost_to_serve_calculator.py enforces by breaking out direct cost lines from allocated overhead — and validating overhead-% consistency across channels.

Source: BCG, Channel Economics in Software & Subscription Businesses practitioner publications.

---

How this skill uses the canon

• Direct-cost line items in cost_to_serve_calculator.py follow BCG's dual-axis framework
• Hidden-cost surfacing (the HIDDEN_COST_KEYS list flagged when $0) follows McKinsey's most-forgotten-cost ranking
• Allocation consistency validation (warns when partner channel has <5% overhead while direct has >20%) implements Horngren's allocation-consistency rule
• Per-channel retention differential (used in channel_roi_analyzer.py) follows Gartner's service-delivery findings — channel-blind retention is the most common source of wrong channel ROI