> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Co-branded Collateral Generator

> Use when a Partner Marketing Manager wants to turn a vendor template into fully co-branded collateral for every partner, generating per-partner PDF, DOCX, or JPEG versions and publishing them to the portal…

*Vendor skill for [Through-Channel Marketing](/headless/agentic-use-cases/through-channel-marketing).*

**Skill ID:** `vendor-cobranded-collateral-generator`

Use when a Partner Marketing Manager wants to turn a vendor template into fully co-branded collateral for every partner, generating per-partner PDF, DOCX, or JPEG versions and publishing them to the portal and asset hub. Trigger phrases include "co-brand this for our partners", "generate co-branded collateral", "make a partner-branded version", "co-brand the campaign one-pager", "roll out co-branded assets", "generate branded PDFs for all partners".

**Built for:** Partner Marketing Manager · Vendor Marketing

**Workflow:** Pick template + audience → Merge partner branding per format → Generate PDF/DOCX/JPEG per partner → Publish to portal + log

```md SKILL.md theme={"theme":{"light":"github-light","dark":"github-dark"}}
---
name: vendor-cobranded-collateral-generator
description: Use when a Partner Marketing Manager wants to turn a vendor template into fully co-branded collateral for every partner, generating per-partner PDF, DOCX, or JPEG versions and publishing them to the portal and asset hub. Trigger phrases include "co-brand this for our partners", "generate co-branded collateral", "make a partner-branded version", "co-brand the campaign one-pager", "roll out co-branded assets", "generate branded PDFs for all partners".
---

# Co-branded Collateral Generator (Vendor)

**Audience**: Vendor — **claude.ai Introw** MCP.
**Use case**: Through-Channel Marketing (TCMA).

## When to use this skill

Use when a Partner Marketing Manager wants to produce fully co-branded collateral — not a logo stitched onto a deck, but on-brand documents carrying both the vendor's and the partner's branding — for one partner, a segment, or the whole partner base, and publish them where partners can self-serve.

**Sample prompts that fire this skill:**
- "co-brand this for our partners"
- "generate co-branded collateral"
- "make a partner-branded version of the campaign one-pager"
- "roll out co-branded assets to Gold partners"
- "generate branded PDFs for all partners"

## Why this matters
Co-marketing stalls when every co-branded asset is a one-off design request. Most channel partners have **zero dedicated marketing or design staff**, so collateral that isn't ready-to-use simply never ships. Generating fully co-branded assets from a governed template — in whatever format the partner needs (PDF, DOCX, JPEG) — removes the design bottleneck and lets co-marketing scale to hundreds of partners while staying on-brand for both sides.

## Inputs to gather
- **Source template** — the base asset with vendor branding and placeholders for partner name / logo / details (a PDF with named form fields, or an equivalent template).
- **Target audience** — all partners, a segment (tier / region / vertical), or a named list.
- **Output format(s)** — PDF, DOCX, JPEG, or several.
- **Distribution target** — which portal experience / asset hub the copies should surface in.

## Process

### Step 1 — Confirm the template and its editable areas
- Confirm which parts of the template are locked (stay as vendor branding) and which are co-branding fields (partner name, logo, contact details). Locked areas protect brand consistency; only the co-branding fields change per partner.

### Step 2 — Resolve the audience
- `Introw:search_partners` — pull the target roster with tier / region / vertical.
- Confirm each partner has branding captured (logo + details). Flag partners missing a logo: they will get a copy generated **without** their brand unless fixed first.

### Step 3 — Generate per-partner, per-format
- For each partner, merge their branding into the template and generate the requested format(s). Produce one co-branded copy per partner, saved as a partner-specific asset that belongs to that partner only.
- Report any partner whose copy could not be produced (missing branding, template error) so the source can be fixed and re-run.

### Step 4 — Publish and surface
- Surface each partner's copy through a partner-specific asset hub in a portal experience, so each partner finds only their own co-branded version.

### Step 5 — Log
- `Introw:add_comment` on the relevant partner or campaign record to log which collateral was generated and distributed, for audit trail.

## Output format
- **Generation summary**: template used, audience size, formats produced.
- **Per-partner result**: partner, formats generated, distribution target, status (done / skipped-missing-branding / error).
- **Fix list**: partners missing branding that need attention before a re-run.
- **Distribution note**: where each partner will find their copy.

## Guardrails & PRM best practice
- **Lock the brand.** Anything that must stay on-brand is locked in the template, not left editable.
- **No brand, no fake brand.** A partner missing a logo gets a vendor-only copy or is skipped — never fabricate partner branding.
- **Partner-scoped assets.** Each generated copy belongs to one partner; never expose one partner's co-branded asset to another.
- **Format fidelity.** Confirm the output format renders correctly (fonts, image resolution for JPEG) before broad rollout — generate one sample and review.
- **Human review on new templates.** For a template's first run, review one generated copy before generating for the whole base.
- **Cross-skill handoff.**
  - Bundle the generated collateral into a campaign via `vendor-campaign-kit-builder`.
  - Partners can self-generate their own versions via `partner-cobrand-my-collateral`.
```

<Note>
  Drop this file into `.claude/skills/vendor-cobranded-collateral-generator/SKILL.md` in your repo and Claude Code triggers it on the prompts in its `description`. Or run the same play in plain language from Claude, ChatGPT, Slack, Teams, or your CRM through [Introw's MCP server](/features/developer/mcp): every action writes back to your CRM source of truth.
</Note>