Partner marketing co-op asset pack blueprint for integration launches
Views
3.9K
Copies
859
Likes
703
Comments
0
Copy rate
22.0%
Prompt
You are a partner marketing lead who has launched 30+ co-op campaigns between SaaS companies. Design a complete asset pack for a joint launch between [brand_a] and [brand_b] announcing [integration_name]. The combined reach is [audience_size].
Deliver:
1. Launch narrative and positioning (what wins customers, not just features)
2. Asset inventory list (every asset both sides need)
3. Content distribution calendar (8 weeks)
4. Channel coordination rules
5. Attribution and deal-split model
6. Success metrics by stageCustomise this prompt
Fill in 4 variables to personalise this prompt
Preview
You are a partner marketing lead who has launched 30+ co-op campaigns between SaaS companies. Design a complete asset pack for a joint launch between [brand_a] and [brand_b] announcing [integration_name]. The combined reach is [audience_size].
Deliver:
1. Launch narrative and positioning (what wins customers, not just features)
2. Asset inventory list (every asset both sides need)
3. Content distribution calendar (8 weeks)
4. Channel coordination rules
5. Attribution and deal-split model
6. Success metrics by stage
Example output
# Partner Co-Launch Asset Pack — Stacks × Slack
**Integration:** Native Stacks-in-Slack — turn any message into a project task
**Combined reach:** Stacks 28k email list + Slack's partner marketplace (6M+ monthly actives)
**Timeline:** 8-week buildup to launch, 4 weeks of amplification after
---
## 1. Launch Narrative
**Positioning:** "Stop losing client requests in Slack threads."
Not "Stacks and Slack integrate." That's feature-speak. Instead: a specific pain (requests buried in Slack) and a specific outcome (every request becomes a tracked task).
**Supporting proof points:**
- 71% of agency requests start in a Slack message, per our pre-launch survey
- Average agency loses 4.2 hrs/week reconstructing what was promised where
- Beta users saw 34% faster task turnaround vs. manual entry
**Tone:** Confident, specific, problem-aware. Both brands speak like an operations lead, not a product marketer.
---
## 2. Asset Inventory
### Owned by Stacks
- Landing page: /slack (anchor URL for all campaigns)
- 90-second explainer video
- Case study: 1 joint customer already using the integration
- Email #1: announcement to Stacks list
- Email #2: "how to set it up in 5 minutes"
- Blog post: "How we built native Slack integration (engineering story)"
- Docs: installation + troubleshooting
- Slack app directory listing copy + screenshots
### Owned by Slack
- Featured placement in Slack App Directory (week 1)
- Co-branded email to Slack's marketing partner list
- Social push from @SlackHQ (2 posts)
- Inclusion in monthly "new apps" newsletter
- Partner blog mention
### Co-owned (joint sign-off required)
- Press release
- Joint webinar + landing page
- Co-branded one-pager (PDF for sales)
- Comparison chart: "Before vs. With Stacks-in-Slack"
- Customer testimonial video
---
## 3. 8-Week Calendar
**Weeks -8 to -5 (Build phase)**
- Finalize integration QA with 5 beta customers
- Draft all assets, legal review, joint sign-off
- Agree on exact launch date
**Week -4**
- Soft-launch to existing shared customers for testimonials
- Record case study video
- Align PR timing with both comms teams
**Week -2**
- Pre-launch teaser: both brands post "something big coming with @Slack" / "with @Stacks"
- Brief both sales teams with battle cards
- Schedule launch-day content
**Week 0 (Launch week)**
- Monday: joint press release hits
- Monday: landing page live, app directory live
- Tuesday: founder posts from both companies on LinkedIn
- Wednesday: joint webinar live
- Thursday: case study drops
- Friday: behind-the-scenes engineering blog
**Weeks +1 to +4 (Amplify)**
- Week 1: customer testimonials, usage stats
- Week 2: "5 workflows we didn't expect" blog
- Week 3: webinar replay + bonus content
- Week 4: 30-day results recap, benchmark data
---
## 4. Channel Coordination Rules
1. **Shared content calendar:** Notion doc with locked dates, both sides can comment
2. **24-hour embargo:** no public mention before Monday 9am ET on launch week
3. **Hashtag alignment:** #StacksInSlack used by both brands — drives searchable conversation
4. **@mention rule:** every social post tags the partner account
5. **Reply SLAs:** both brands commit to replying to comments within 2 hours on launch day
6. **No channel conflict:** if one brand schedules a post, the other waits 3 hours before same-channel post
---
## 5. Attribution + Deal Split
- **Lead source tracking:** UTM parameter utm_partner=slack on all Slack-originated links
- **CRM field:** new account source "Slack Partnership"
- **Commission:** Stacks pays Slack no direct commission (Slack benefits from ecosystem value)
- **Future deals:** any joint enterprise deal with ACV >\$100k splits co-marketing budget 50/50 for case study
- **Lead sharing:** quarterly account review between partner managers
---
## 6. Success Metrics by Stage
| Stage | Metric | Target |
|---|---|---|
| Awareness | Joint press coverage | 8+ tier-1 outlets |
| Interest | Landing page visits | 45k in 30 days |
| Consideration | App directory installs | 3,200 in 30 days |
| Activation | Completed integration setup | 1,800 in 30 days |
| Revenue | Sourced ARR in 90 days | \$340k |
**Overall target:** 12% lift in Stacks new-logo acquisition in Q2, attributable to partnership channel.