> ## 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 Assets
> Let partners generate marketing assets that carry both your brand and theirs, so co-marketing scales without your team designing one-offs.
export const Headless = ({prompts = []}) => {
const PromptRow = ({prompt}) => {
const [copied, setCopied] = useState(false);
const copy = () => {
try {
navigator.clipboard?.writeText(prompt);
} catch {}
setCopied(true);
setTimeout(() => setCopied(false), 1600);
};
return ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> Co-marketing stalls when every asset needs your design team, and a logo stitched on a deck was never really co-branding. Partners, and their AI agents, pull your enablement and generate fully co-branded versions themselves, in any format, in minutes.
## What it does
Co-branded assets are templates that automatically combine your branding with each partner's, so a partner can take a one-pager, a slide, or a campaign asset and have it personalized with their logo and details without design work. You create the template once and control what partners can change; partners generate their own co-branded version and use it to sell.
Co-branding goes well beyond dropping in a logo. Partners can pull an asset into their own AI assistant over Introw's [MCP server](/features/developer/mcp) and generate a fully co-branded version, recomposed with their branding, details, and voice, and exported in whatever format they need (PDF, DOCX, JPEG). You still control what stays locked, so both brands remain consistent no matter how the asset is generated.
The assets live in the same library that powers the rest of your enablement, so they are governed, versioned, and easy to distribute.
## The problem it solves
* **Every co-branded asset is a design request** → Partners generate their own from a template, freeing your team.
* **A logo stitched on a deck isn't real co-branding** → Fully recomposed, on-brand documents in any format partners actually use.
* **Partners go off-brand making their own materials** → Templates keep both brands consistent.
* **Co-marketing does not scale** → Hundreds of partners can self-serve on-brand assets.
* **Partners lack ready materials to sell** → They grab a co-branded asset, or generate one from their LLM, and go.
## From problem to solution
Instead of your team producing a custom asset for each partner, you publish a co-branded template and let partners generate their own version, from the portal or straight from their own AI assistant. Co-marketing scales to the whole program, the output is a fully co-branded document in the format the partner needs, and your locked areas keep both brands consistent.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
template["Publish a co-branded template"] --> pull["Partner or AI agent pulls it"]
pull --> generate["Generate co-branded version (any format)"]
generate --> launch["Download and launch"]
```
## Use cases
Every partner self-serves on-brand assets.
Templates control both brands.
No more one-off co-branded requests.
Ready co-branded materials on demand.
Partners recompose assets from their own LLM.
Export co-branded PDF, DOCX, or JPEG.
## Impact
* **Low total cost of ownership** - marketing builds templates with no per-partner work.
* **Partner self-serve** - partners create their own co-branded assets.
* **Work where you already are** - partners generate co-branded assets from their own AI tools, not only the portal.
* **AI-native** - partner AI agents recompose assets into fully co-branded versions, well beyond logo placement.
## Who it's for
Builds and governs co-branded templates.
Generates co-branded materials to sell with.
## Works with
{/* CONNECTS:START - generated content goes here */}
Co-brand straight from the library.
Apply partner and vendor branding.
Co-brand certificates the same way.
Distribute co-branded assets in partner campaigns.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Endpoints and code.