One Calendar for Every Vendor Launch and Webinar (Claude Skill)

‍

Vendors want their channel partners to sell more. According to the benchmark survey cited in Introw's campaigns and announcements playbook, 96% of B2B marketers expect to increase revenue attributable to channel partners. So every vendor in your portfolio is shipping launches, webinars, campaign kits and incentive programs at you, each in its own portal and on its own schedule.

Here's how that plays out on a Monday. Vendor A announced a new security module two weeks ago, and you only spot it when a customer asks about it. Vendor B's MDF window for Q1 closes on Friday. Vendor C has a cobranded webinar next Thursday that would be perfect for your healthcare accounts, if anyone on your team had seen the invite. Multiply that by five to ten vendors and you're always playing catch up.

What if you had one partner content calendar that pulled all of it together, ranked it by what matters for your customers, and told you which three things to do this week?

This guide covers why a partner content calendar matters when you work with multiple vendors, how to plan around MDF windows and launches, the Claude skill that builds the calendar for you, the full SKILL.md you can copy, how to install and run it, and how to stay in control of what goes out.

Why channel partners need one partner content calendar across vendors

Vendors plan their marketing initiatives around their own quarter. You plan yours around your customers. Those two calendars rarely line up, and the gap is where good opportunities slip.

A product launch is a perfect reason to call your installed base. A webinar is an easy invite for potential customers you've been nurturing. An MDF window is free budget for the demand generation you were going to run anyway. But only if you see them early enough to act.

Most partners don't, for a few reasons:

• Every vendor announces differently: one posts in the partner portal, one emails, one drops it in a Slack channel, and one tells your account manager on a call.
• Timing is scattered: launches, certification cohorts, MDF programs and tier reviews all run on different cycles, so there's no natural moment to review them together.
• Most of it isn't relevant: a vendor might announce twelve things this month, and only two apply to the products you actually sell and the segments you serve.
• Capacity is finite: even if you saw everything, your marketing and sales teams can't act on a dozen launches in two weeks.

For a channel partner, a missed launch isn't just a missed email. It's lost market reach, a weaker market presence with the vendor, and one less chance to drive sales while the vendor is putting its own resources behind the moment.

A good partner content calendar fixes all four. It puts every vendor's upcoming activity in one place, filters it to what fits your business, and makes the trade offs visible, so you choose your focus instead of reacting to whoever emailed last. The best ones also balance promotional and educational content, so customers hear about launches and get useful guidance, and they give every item a clear escalation path when a vendor approval stalls. Jointly promoted content tends to carry more weight with buyers too, because it comes from two names they already trust.

Here's how a reactive approach compares with a planned one:

That's the core of strategic planning for every channel partner. It isn't about doing more. It's about lining your own marketing efforts up with vendor moments that already have budget, content and attention behind them.

How to plan your partner marketing around MDF windows and launches

Of everything on a vendor calendar, two items move the most money: product launches and market development funds. They also work best together. A launch gives you a reason to reach out, and market development funds pay for the reach.

What market development funds are, and how they differ from co op funds

Market development funds, sometimes called marketing development funds or MDF funds, are budgets a vendor sets aside to help channel partners run marketing activities that generate demand for the vendor's products. The vendor reimburses approved spend, or pays it upfront, as long as the activity fits the program's MDF guidelines. Introw's glossary has a short primer on market development funds.

Co op funds are related but different. Here's the quick version:

Most MDF programs start with a proposal: what you'll run, for which audience, with what budget and expected results. Once the activity runs, you submit proof of performance, like event photos, attendee lists, campaign results or the number of qualified leads, and the vendor reimburses you through its usual payment processing. Each market development fund program has its own rules, so read the MDF guidelines before you plan.

Both kinds of funds are easy to leave on the table. MDF utilization is a known problem in partner programs, and it's rarely because partners don't want the money. It's because the MDF process has deadlines, eligible activities and paperwork, and the window closes before anyone gets round to it. When the right person sees the window too late, the MDF support the vendor offered goes to someone else.

Eligible activities that generate demand around a launch

Most MDF programs fund a familiar set of marketing activities. When you can line one up with a vendor launch, your proposal gets stronger and your results get better:

• Cobranded webinar: host a session on the new release for your customers and prospects, with a vendor speaker. Attendee lists become qualified leads for your sales teams.
• Digital campaigns: digital ads and social media content aimed at your target audience, timed to launch week, to build brand recognition for you and the vendor's products.
• Local events and trade show presence: a lunch and learn or a booth at a regional trade show where you can demo what's new.
• Email and lead generation campaigns: a short sequence to your installed base about the upgrade, using the vendor's campaign kit.
• Training and certification: some programs fund certifications, which matters when a launch requires them.

The common thread is strategic alignment. A proposal that says "we'll run a cobranded webinar for 40 mid market healthcare accounts the week the healthcare module launches" is far easier to approve than "we'd like budget for marketing."

Budget allocation across vendors

If you work with several vendors, your marketing budget and each vendor's MDF budget need to work together. A few habits help:

• Know every window: list each vendor's MDF programs, program eligibility rules, application deadlines and claim deadlines in one place.
• Co invest where you're strongest: put your own budget next to allocated funds in the verticals where you already win, so every dollar reaches further.
• Don't spread too thin: three well run campaigns beat eight half finished ones, especially for smaller partners with lean teams.
• Track results per vendor: show each vendor the pipeline their funds created. It builds strong relationships and makes the next approval faster.
• Mix quick wins with longer term campaigns: a launch week push helps you generate leads now, while a quarterly webinar series builds the long term success that vendors reward with bigger allocations.

Vendors notice partners who plan this way. Many weigh partner productivity when they decide where next year's funds go, so a partner that applies early, runs the activity well and reports results puts itself in a strong position for more.

This is a lot to keep in your head across five vendors, which is exactly why a calendar that ranks it for you is useful. For the vendor's side of the same story, see Introw's market development funds product and our guide to channel partner marketing strategy.

The skill to use: Cross Vendor Content and Activity Calendar

Cross Vendor Content and Activity Calendar is a partner side skill from Introw's free Claude skill library. It runs from your side of the relationship, as a reseller, agency, SI or MSP, and reads every vendor portal you have access to through Introw's MCP server. Then it builds one ranked calendar of what's coming, and drafts the moves worth making.

It fires on prompts like "what's coming up", "vendor calendar across all my vendors", "upcoming launches", "MDF windows", "what should I plan around" and "vendor activity calendar".

The key difference from a shared spreadsheet is relevance. The skill doesn't just list everything. It scores each item against what you sell and who you sell to, and keeps the top five to ten. That gives your sales and marketing people one shared view of the market moments worth chasing, instead of each team working from a different inbox.

How the skill works, step by step

The skill follows six steps. You don't need to run them yourself, but knowing what happens helps you trust the output.

Step 1: Find every vendor portal you can access

The skill starts by listing every vendor portal connected to your Introw account. If you work with six vendors on Introw, it sees six portals, each kept separate.

Step 2: Pull upcoming activity from each portal

For each vendor, it reads the campaigns and announcements you've been invited to, open MDF program windows, cobranded marketing proposals and application deadlines, vendor assigned tasks with due dates that hint at something coming, and knowledge base content where launch or event details are published.

Step 3: Classify each event

Every item gets a type (product launch, feature release, webinar, certification cohort, MDF window, campaign template release, tier review window, executive event or training drop), a date or window, the audience it applies to, the action you'd need to take, and the economic stake for you, such as a product you sell, a vertical you serve or a tier you're close to.

Step 4: Score relevance to your business

This is the step that turns a feed into a plan. Each event is ranked on four things:

To ground the scoring, the skill looks at your deals and customers, so an enterprise launch doesn't get flagged as urgent if your book is mid market services.

Step 5: Build the unified calendar

Everything lands in four buckets: this week (deadlines, registrations, opt ins), the next 30 days (things to pre stage, like outreach and SE time), strategic windows 30 to 90 days out, and FYI items that are worth knowing but not acting on.

Step 6: Recommend your moves

For the top scored events, the skill drafts the next step: which customers and prospects to contact and when, which campaign assets to use and for which segment, a drafted MDF application aligned to the program, and prep work like certifications to finish or demos to book with the vendor's SE before the launch lands.

Get the skill: the full SKILL.md

Here's the complete skill file. Copy it as is, or adjust the scoring factors, buckets and cadence to match how your team plans.

---
name: partner-cross-vendor-content-calendar
description: Use when a partner wants a unified calendar of upcoming product launches, webinars, MDF programs, campaigns, and tier-promotion windows across all the vendors they work with, so they can plan their own outreach, sales motions, and customer communications around vendor activity. Trigger phrases include "what's coming up", "vendor calendar across all my vendors", "upcoming launches", "MDF windows", "what should I plan around", "vendor activity calendar".
---

# Cross-Vendor Content & Activity Calendar (Partner)

**Audience**: Partner user, uses **Introw Partner Connect** MCP across **all portals** the partner has access to.
**Use case**: 07, Campaigns & Announcements (partner-side, multi-vendor).

## When to use this skill

Use when a partner wants a unified calendar of upcoming product launches, webinars, MDF programs, campaigns, and tier-promotion windows across all the vendors they work with, so they can plan their own outreach, sales motions, and customer communications around vendor activity.

**Sample prompts that fire this skill:**
- "what's coming up"
- "vendor calendar across all my vendors"
- "upcoming launches"
- "MDF windows"
- "what should I plan around"
- "vendor activity calendar"

## Why this matters
Every vendor runs its own roadmap of launches, campaigns, MDF cycles, webinars, and incentive programs, and announces them in its own portal, on its own cadence. The partner who could capitalize on a Vendor X launch with their installed base often misses it because they didn't see the announcement until two weeks later. Multiplied across 5 to 10 vendors, the partner is constantly playing catch-up on vendor activity.

This skill aggregates: every vendor's announced upcoming activity, in one calendar, ranked by what's most leverageable for the partner's actual customer base. Plan outreach around launches; pre-stage campaigns; book SE time before the wave hits.

## Process

### Step 1: Enumerate vendor portals
- `Introw_Partner_Connect:partners`: get all portals.

### Step 2: Pull upcoming activity per portal
For each `roomId`:
- `Introw_Partner_Connect:search_partner_engagement`: recent and upcoming campaign / announcement events the partner has been invited to.
- `Introw_Partner_Connect:search_form_submissions`: open MDF program windows, co-marketing proposals, partner application deadlines.
- `Introw_Partner_Connect:search_tasks`: vendor-assigned tasks with due dates that hint at upcoming activity.
- Knowledge-base content where launch / event metadata is published.

### Step 3: Classify each event
For each upcoming activity across vendors, capture:
- **Type**: product launch, feature release, webinar, certification cohort, MDF window, campaign template release, tier-review window, executive event, training drop.
- **Date / window**.
- **Audience** (which segments / verticals / regions does this apply to).
- **Partner action required** (read-only, register to attend, opt-in, MDF apply, campaign deploy).
- **Economic stake** (related to a SKU the partner sells, a vertical the partner serves, a tier the partner is approaching).
- **Vendor + portal**.

### Step 4: Score relevance to this partner
Rank each event by:
- **Customer-base fit**: does the partner have prospects/customers in segments where this matters?
- **Partner motion fit**: does it apply to what the partner actually sells (avoid noise from products outside the partner's portfolio)?
- **Effort vs. impact**: a MDF window with 1-week deadline + low fit ranks lower than a launch in the partner's strongest vertical.
- **Vendor-relationship leverage**: high-value when it's a vendor where the partner is pacing for a tier promotion or activation.

### Step 5: Build the unified calendar
- **This week**: items that need action now (deadlines, registrations, opt-ins).
- **Next 30 days**: items to plan around, pre-stage outreach, book SE time, queue campaigns.
- **Strategic 30 to 90 days**: bigger windows worth shaping the partner's quarter around.
- **FYI**: vendor activity not directly leverageable but worth knowing.

### Step 6: Recommend partner moves per high-relevance item
For top-scored events:
- **Outreach plan**: which customers / prospects to contact when, framed around the launch.
- **Campaign queueing**: which assets to use, what segment to send to.
- **MDF application**: drafted proposal aligned to the program.
- **Pre-event prep**: certifications to complete before a launch hits, demos to schedule with vendor SE.

## Output format
- **Calendar across vendors**: table by date with vendor, event, type, action required, fit score.
- **This-week action queue**: anything time-sensitive.
- **30-day plan**: moves the partner should pre-stage now.
- **Strategic windows**: bigger opportunities worth shaping the quarter around.
- **Drafted outreach / MDF apps**: copy-pasteable per top-relevance item.

## Guardrails & PRM best practice
- **Strictly scoped per portal.** Each vendor's calendar data is only fetched with its own `roomId`. No cross-portal leakage in any partner-facing or vendor-facing output.
- **Vendor-confidential roadmap data stays internal.** Some vendor announcements are partner-confidential (e.g., advance notice on a launch). Don't surface those to customer-facing outreach or campaigns until embargo lifts.
- **Don't pre-announce.** If a vendor has shared advance launch info under embargo, the calendar can show it to the partner, but the partner's drafted customer outreach must respect the embargo date.
- **Relevance discipline.** Surface 5 to 10 high-fit events per cycle, not 50 generic vendor events. Generic feeds train the partner to ignore the calendar.
- **Honor capacity.** A partner can't action 12 launches in 2 weeks. Recommend a focused 3 to 5 priority moves; the rest is FYI.
- **Match to actual customer base.** If the partner's customer base skews mid-market services, an enterprise launch is FYI not action. Use deal/customer signals (`search_crm_objects`) to ground relevance.
- **Don't auto-deploy campaigns.** Campaign queueing means drafted + ready-for-review, not pushed to customers automatically.
- **Capture commitments.** When the partner commits to apply for MDF or attend an event, log via `add_task` on the relevant vendor portal.
- **Run on cadence.** Weekly default. Daily during heavy launch periods.
- **Cross-skill handoff.** Outreach plan → individual customer-level coaching via `partner-deal-war-room`. Cert pre-reqs for upcoming launches → `partner-cross-vendor-cert-tracker`. MDF program windows → drafted apps stay with this skill until applied.

How to install and run the skill

This is a partner side skill, so you run it as the partner: the reseller, agency or SI that has access to one or more vendor portals on Introw. You've got two ways to use it.

Option 1: Claude Code

Create a folder called partner-cross-vendor-content-calendar inside .claude/skills/ in your repo, and save the file above as SKILL.md inside it. Claude Code picks it up automatically and runs it whenever your prompt matches one of the trigger phrases in the description.

Option 2: Claude (or any MCP client) with the Introw connector

You don't need to be technical for this. Connect Claude to Introw once, sign in with the account you use for your vendors' partner portals, and Claude can see every portal you have access to. Introw is listed in Claude's connector directory, so it's one click plus a sign in. Here's how connecting looks:

‍

The Connect Claude guide walks through it step by step, and the Claude integration page covers what else you can do once you're connected.

Prompts to try

Once the skill is installed or Claude is connected, try any of these:

• "What's coming up across all my vendors?" Builds the full calendar with this week, next 30 days, strategic windows and FYI.
• "Which MDF windows are open right now, and which should I apply for?" Focuses on market development funds and drafts applications for the best fits.
• "Upcoming launches that matter for our healthcare customers." Narrows the calendar to one vertical.
• "What should I plan around next quarter? Give me three priority moves." Gets you a short, focused plan instead of a long list.
• "Draft outreach for the top launch, but don't send anything." Gives you copy to review before anyone sees it.

What you'll get back

A typical run returns five things:

• Calendar across vendors: a table by date with vendor, event, type, action required and fit score.
• This week action queue: anything with a deadline, registration or opt in coming up.
• 30 day plan: moves to pre stage now, like outreach, SE bookings and campaign queues.
• Strategic windows: bigger opportunities worth shaping your quarter around.
• Drafts: outreach copy and MDF applications for the top items, ready to copy.

Here's an illustrative slice of a calendar for an IT services reseller that works with five vendors and mostly sells to mid market healthcare:

And the top move it would suggest: apply for Vendor A's MDF with a cobranded webinar and short email sequence aimed at your healthcare installed base, timed to Vendor B's launch week, while booking Vendor B's SE for two customer demos.

Staying in control: what Claude can and can't do

A calendar that drafts customer outreach only works if you trust it. Here's what's built in:

• You approve every write: the skill drafts outreach, campaigns and MDF applications, and only logs a task on a vendor portal after you confirm.
• It acts as you: Claude connects to Introw over OAuth with your partner account, so it sees exactly the portals and data you can see, nothing more.
• Vendors stay separate: each vendor's data is fetched only from its own portal. Nothing from one vendor leaks into another vendor's output.
• Embargoes are respected: if a vendor shared advance notice of a launch, you'll see it on your calendar, but drafted customer outreach waits until the embargo date.
• No auto deployed campaigns: campaign queueing means drafted and ready for review, never pushed to customers automatically.
• It keeps the list short: five to ten high fit events per cycle and three to five priority moves, so the calendar stays something you actually read.

Prefer to do this in the Introw app?

The calendar is only as good as what vendors publish. On the vendor side, Introw lets partner marketing teams package a launch as a campaign kit, with emails, posts, a banner and a one pager partners can cobrand, and publish it on a Marketing tab in the partner portal. Here's how vendors set that up:

‍

If you're a vendor reading this, that's the content your partners' calendars will pick up. Introw's partner campaigns and the partner marketing manager page show how the pieces fit, and the glossary entries on campaign in a box, co marketing and through partner marketing cover the basics.

Pair it with other Claude skills

The calendar tells you what to focus on. Other partner side skills help you act on it:

• Cross Vendor Certification Tracker: when a launch requires a certification, it shows what's required, optional or expiring across every vendor.
• Deal War Room: turns launch outreach into deal specific coaching with playbooks, past wins and battle cards.
• Drip Campaign from Assets: turns a vendor's campaign kit into a scheduled drip in your own email tool, with cobranding applied.
• Incentive Maximizer: shows which actions this quarter unlock the next bonus tier or accelerator.

You'll find all of them in Introw's skill library, and our roundup of Claude skills for partner teams explains how they work together.

Run your multi vendor partner marketing from Claude with Introw

Introw is a CRM first partner relationship management platform, which means it builds on top of your existing HubSpot or Salesforce setup rather than replacing it. It's also headless by design: the partner portal is one surface, but partners and vendors can run the same work in plain language from Claude, ChatGPT, Slack or Teams through Introw's MCP server, with every action written back to the CRM.

That's what makes a cross vendor calendar possible. If you're a reseller partner working with several vendors on Introw, one sign in gives Claude access to all of their portals, each kept separate, so you can plan your quarter around their launches, MDF windows and webinars without logging into five places.

See every vendor launch, webinar and MDF window in one place. Connect Claude or book a demo.