# Weekly partner co-sell digest to Slack

Source: https://mcpforgtm.com/recipes/partner-cosell-digest (StackMCP, independent directory of official MCP servers)

## Goal

RevOps and partnership leaders who want one weekly post with new partner overlaps, partner-sourced leads and deals, and what's owed in commissions, without logging into two partner tools. Slack can be swapped for Microsoft 365 (Work IQ) to send the digest as an email.

## Connected tools

- Crossbeam: https://mcp.crossbeam.com/mcp (setup: https://mcpforgtm.com/tools/crossbeam)
- PartnerStack: https://mcp.partnerstack.com/mcp (setup: https://mcpforgtm.com/tools/partnerstack)
- Slack: https://mcp.slack.com/mcp (setup: https://mcpforgtm.com/tools/slack)

## Guardrails

- Read only in Crossbeam and PartnerStack. Never create, convert, approve, message or export anything in PartnerStack.
- The only write is one Slack post to the channel I name, after I approve it.
- If there's no previous snapshot, say this is the baseline and don't report anything as new.
- Say which dates and date fields you used for every PartnerStack number.

## Steps

1. Use Crossbeam to list our account overlaps with each partner and any ecosystem activity signals from the last 7 days. Compare with last week's snapshot in {snapshot location} if there is one; if not, call this the baseline.
2. Read PartnerStack leads, deals, transactions and rewards from the last 7 days, grouped by partner. Tell me which date field you used. Read only: don't create, convert, export or message anything.
3. Draft a short digest for {Slack channel}: new overlaps by partner, notable signals tied to our open deals, partner-sourced leads and deals, and rewards created. End with one thing to decide this week. Show me the draft.
4. Post the digest to {Slack channel} only after I approve it. Then give me this week's overlap list to save as next week's snapshot.

## Expected output

Weekly digest drafted for #partners. Example (all names fictional):

```
Partner co-sell digest, week of Oct 12 (compared with last week's snapshot)

New account overlaps (Crossbeam)
- Brightwell Consulting (fictional): 4 new customer overlaps with our open pipeline, including Quarry Lane Analytics (fictional) and Mossgate Labs (fictional)
- Tallow Systems (fictional): 2 new prospect overlaps

Ecosystem signals (Crossbeam)
- Brightwell Consulting (fictional) flagged new activity at Fernhill Software (fictional), an open deal for us (owner: Alex Rivera).

Partner-sourced (PartnerStack, last 7 days)
- Leads: 7 new, 5 from Kestrel Referral Group (fictional)
- Deals: 2 new, 1 converted to a customer
- Rewards: 3 commissions created, all pending

One thing to decide: Kestrel Referral Group sent 5 leads this week and has no co-sell plan. Worth a call?

No changes were made in PartnerStack. Reply 'post' to send this to #partners.
```

## Watch for

- Old overlaps reported as new: The first run has nothing to compare against. It must say 'baseline' and list totals only. From week two, compare with the saved snapshot and count only accounts that weren't there before.
- Wrong week in PartnerStack numbers: Leads, deals and rewards each have their own dates. Have it state which date field and which 7 days it used, and check one partner's count against the PartnerStack dashboard once.
- An accidental PartnerStack write: PartnerStack's MCP server can create rewards, convert deals, send partner messages and trigger exports. Keep the guardrail that it only reads, and stop the run if it asks to approve anything in PartnerStack.
- Partner or commission details in the wrong channel: Commission amounts and partner customer names may not be meant for a wide channel. Name a private channel, or post counts only and keep the detail in a canvas or DM for the partner team.