> ## 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.
# Partner Connect
> Introw's headless, AI-native way of working, extended to your partners - they stay in their own CRM, chat, and AI assistant and reach everything you offer without ever logging into a portal.
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.
}
;
};
> Introw is already headless and AI-native for the vendor - your team runs partnerships inside their CRM with agents doing the busywork. Partner Connect brings that same way of working to the partner: they stay in the systems they already live in - their own CRM, Slack or Teams, and their own AI assistant - and everything you offer reaches them there, without a portal login.
## What this area does
Headless is how Introw works, not a single feature. The vendor already runs the whole program inside HubSpot or Salesforce with agents handling the mechanical work. Partner Connect closes the other half of the loop: it extends that headless, agentic, CRM-first model to the partner, so the partnership is two-way and AI-native for **both** sides, not just the vendor.
Partner portals have always had an adoption problem, and the reason is simple: they ask a busy partner rep to leave the tools they work in, remember another login, and go hunt for the right deal before they can do anything. Most never do. Partner Connect removes that friction - the portal becomes optional, and the work comes to the partner instead.
A partner running their own HubSpot or Salesforce sees, right on their open opportunity, which vendor is involved and exactly where the deal stands on the vendor side. They register deals and share leads from their CRM, get deal coaching in context, and reach the right seller on the vendor's team without logging into anything. A partner who lives in Slack or Teams gets the same. And a partner who works through an AI assistant can connect their own LLM - Claude, GPT, Gemini - and reach your resources from there.
The result is a single shared reality both organizations work from wherever they already are. Meeting partners where they work - instead of overloading them with one more portal - is how programs actually drive adoption, visibility, and revenue.
## Why it matters
* **Work where you already are** - Partners act from their own CRM, chat, and AI assistant; the portal is one surface among many, not the entry gate.
* **CRM-native** - Both sides work their own system of record, and the shared deal stays synced across the two - no reconciliation, no CRM seat.
* **AI-native** - The experience is AI-native for both sides: the partner brings their own LLM and reaches deal reg, coaching, enablement, and support from it.
* **Partner self-serve** - Deal registration, coaching, enablement, training, and support all come to the partner where they work, so they never wait on the vendor or a login.
* **Composability** - CRM embeds, chat, and MCP are building blocks partners combine, so each partner chooses where they work and finds everything there.
## How it fits together
The partner works from their own tools on a deal that stays synced with yours:
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
partner["Partner: own CRM, chat, AI"] --> connect["Partner Connect"]
connect --> deal["Connected deal"]
deal <-->|"kept in sync"| vendor["Vendor CRM"]
```
## Capabilities
Link a partner's own CRM deal to yours so both sides work one shared opportunity, each from their own CRM, kept in sync.
Partners see the vendor and live deal status on their own opportunity, and register, co-sell, and reach the right rep from inside their CRM.
Partners connect their own LLM - Claude, GPT, Gemini - and reach deal reg, coaching, enablement, and support from the assistant they already use.
## Meet partners where they work
The Introw card that renders shared deal context and actions on HubSpot and Salesforce records.
Register deals, get notified, and collaborate from the chat tools partners already live in.
Connect any MCP client - Claude, ChatGPT, Cursor - to reach Introw from a partner's own assistant.
Stage-specific AI selling guidance, surfaced in context on the deal.
The register-and-protect motion partners run from a link, embed, email, chat, or AI.
## Who works in this area
Registers deals, co-sells, and reaches the right rep from their own CRM, chat, or AI assistant.
Connects the partner's CRM and AI, and keeps shared opportunities aligned with the vendor.
Invites partners into the headless experience and keeps joint deals moving without a portal push.
Co-sells with partners on the shared deal from inside the CRM they already use.
## Headless
## All guides
{/* ROLLUP:START - generated content goes here */}
Turn on Partner Connect, have a partner connect their own HubSpot, and link their deal to the matching deal in your CRM so both sides co-sell on one shared opportunity.
When a partner has an opportunity that does not yet exist in your CRM, register it as a new shared deal instead of linking, so co-selling can still start.
Disconnect a linked partner deal from the matching deal in your CRM when the link was wrong or the opportunity is no longer joint.
As a partner, connect any MCP-capable client - Cursor, Gemini, Windsurf, Notion AI, and more - to your Introw partner data with the partner MCP connector.
As a partner, connect ChatGPT to Introw over MCP so you can query and act on your own partner data - deals, commissions, tasks - from inside ChatGPT.
As a partner, connect Claude to Introw over MCP so you can query and act on your own partner data - deals, commissions, tasks - from inside Claude.
As a partner, connect your own HubSpot, add the Introw card to your deals, and verify it so vendor context and actions appear on your own CRM records.