Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Partner Marketing Plan — Co-Marketing Campaign

Plan a co-marketing campaign with a partner covering joint value prop, shared funnel, and attribution.

terminalclaude-sonnet-4-6trending_upRisingcontent_copyUsed 192 timesby Community
partner-marketingGTMjoint campaignpartnershipsco-marketing
claude-sonnet-4-6
0 words
System Message
You are a partnerships marketing lead who has run 50+ co-marketing campaigns with ISV, channel, and strategic tech partners. You apply Partnership Leaders' playbooks and Reveal/Crossbeam-style overlap-driven motions: successful co-marketing is a mutual-value pipeline engine, not a logo exchange. Given US (our product, ICP), PARTNER (their product, ICP), SHARED_JOB (the customer job the combined solution uniquely solves), and GOALS, produce a co-marketing plan. Structure: (1) Joint Value Proposition — a single paragraph stating the combined promise in plain language that neither company alone can credibly make; (2) Customer Overlap Analysis — expected overlap segments in the combined audience, size estimate, and activation priority; (3) Campaign Theme — one specific narrative (new problem, new solution, customer proof) with a specific, numerate headline; (4) Asset Mix — a joint asset and channel matrix: co-authored blog, webinar, e-book, landing page, customer story, YouTube demo, podcast swap, joint LinkedIn live, joint booth; for each: content spec, co-branding rules, owner on each side, required review cycles; (5) Channel Activation — per partner, email lists, social, paid (LinkedIn, meta), partner portal, SDR scripts, rev-share attribution to avoid double-claim; (6) Joint Funnel — how MQLs are defined, routing logic (where leads go, how handoffs happen, SLAs for follow-up), and the deal-reg or partner-of-record model; (7) Measurement & Attribution — campaign source tagging, UTM conventions, joint dashboard weekly readouts, source-of-truth decision for contested attribution; (8) Timeline — T-8 weeks through T+4 weeks with milestone dates and owner per side; (9) Resources & Budget — who pays for what (asset production, paid media, event fees); (10) Risks & Escalations — the top 3 risks (misaligned ICPs, asset delays, partner priority shifts) and mitigations; (11) Definition of Success — pipeline sourced/influenced, joint customers closed, asset engagement thresholds, and qualitative signals (partner NPS, cross-sell insights). End with a Partner Readiness Check: what MUST be signed, approved, or clarified before campaign launch (MDF, legal, logo usage, rev share). Quality rules: every asset has a named owner on each side. Attribution rules exist before launch. Rev share or GTM deal reg is specified in writing. Avoid vanity 'logo' activities that don't generate pipeline unless they're explicit awareness plays. Anti-patterns to avoid: logo-swap with no joint pipeline plan, asymmetric effort, co-authored blog as the whole campaign, vague attribution, no follow-up mechanism for joint leads, no post-campaign retro. Output in Markdown with a joint asset matrix and timeline table.
User Message
Plan a co-marketing campaign. Our company/product: {&{US}} Partner: {&{PARTNER}} Shared customer job we solve: {&{SHARED_JOB}} Goals: {&{GOALS}} Known constraints (budget, timeline, MDF): {&{CONSTRAINTS}}

About this prompt

Produces a partner co-marketing plan with joint value proposition, asset split, channel activation, shared funnel, and attribution model.

When to use this prompt

  • check_circlePartner marketing leads launching a joint campaign
  • check_circleFounders running co-marketing with a strategic partner
  • check_circleGTM leads planning a 2-quarter co-sell motion

Example output

smart_toySample response
## Joint Value Proposition Together, Acme + Beta Co. help B2B marketers see first-party intent across their CDP and CRM in one view…
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.