Recipes / Weekly partner co-sell digest to Slack

Weekly partner co-sell digest to Slack

Crossbeam + PartnerStack + Slack

Who it's for

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.

What you get

Weekly digest drafted for #partners. Sample output: every company and person in it is 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.

Time and cost

Estimate About 10 minutes once it's set up, most of it reading the draft.

Assumptions: One weekly run with about 5 active partners and a few dozen PartnerStack leads, deals and rewards.

• Crossbeam: A few reads: account overlaps and ecosystem signals for the week. These requests can draw from your Crossbeam Credits balance. Some tools use credits. MCP calls draw from a pooled annual Crossbeam Credits balance (Free 50, Connector 500, Supernode 2,500, Enterprise 5,000 per year); best-practice, own-account-context and product-knowledge requests are free. Extra packs ($0.10/credit) for Supernode and Enterprise only. Source: help.crossbeam.com, checked 2026-10-16
• PartnerStack: Reads only: leads, deals, transactions and rewards for the last 7 days. No exports, invites or messages. Credit use not confirmed by PartnerStack.
• Slack: One channel message after you approve it. Credit use not confirmed by Slack.

Exact credit costs depend on your plan with each vendor. Check the tool pages before a large run.

MCP servers

Every server is confirmed in: ClaudeCursor

• Crossbeam Up · auth
  ClaudeChatGPTCursorRead onlySome tools use credits
  https://mcp.crossbeam.com/mcp
• PartnerStack Up · auth
  ClaudeChatGPTClaude CodeCursorCopilotRead + writeCredits not confirmed
  https://mcp.partnerstack.com/mcp
• Slack Up · auth
  ClaudeClaude CodeCursorRead + writeCredits not confirmedNeeds admin or IT
  https://mcp.slack.com/mcp

Set up in a chat app

Every server in this recipe is confirmed for Claude. Connect each one, then paste the prompts below into one conversation.

• Connect Crossbeam without code (Claude, ChatGPT)
• Connect PartnerStack without code (Claude, ChatGPT)
• Connect Slack without code (Claude)

Developer setup

{
  "mcpServers": {
    "crossbeam": {
      "url": "https://mcp.crossbeam.com/mcp"
    },
    "partnerstack": {
      "url": "https://mcp.partnerstack.com/mcp"
    },
    "slack": {
      "url": "https://mcp.slack.com/mcp"
    }
  }
}

Step-by-step prompts

Copy all prompts

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.

Run it on a schedule (optional)

• Run it weekly, for example Monday morning before the partner or pipeline meeting.
• In a scheduled run, stop at the draft: send it to yourself and post to the channel only after you approve it.
• Save each week's overlap list somewhere the next run can read (a pinned message, a canvas or a file). Without it, 'new' overlaps can't be told apart from old ones.
• Crossbeam, PartnerStack and Slack all use OAuth, and Slack needs a workspace admin to approve the integration. Test one manual run before you schedule it.

Where this goes wrong

• 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.

Gotchas

• Crossbeam's MCP server is read-only. PartnerStack's is read and write, so the read-only rule has to come from your prompt.
• PartnerStack connects to one PartnerStack instance at a time. If you run more than one program, run the digest once per instance.
• In Claude, PartnerStack is added as a custom connector while its directory listing is pending review. In ChatGPT it needs Developer Mode, and on Business only admins can use it.
• PartnerStack's help center says it uses OAuth with no API key, but a PartnerStack blog post mentions an API key. Follow the help center steps.
• Crossbeam needs a Full Access or Sales seat, and its MCP calls draw from a pooled annual Crossbeam Credits balance.

Download

Get the prompts, guardrails and expected output as one Markdown file. Paste it into a Claude Project or ChatGPT project's instructions, or save it as CLAUDE.md for Claude Code.

Download partner-cosell-digest.md

Vendor sites: Slack. If we join an affiliate program, these links will be labeled as affiliate links.