> ## 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
> Partner Connect brings your whole partnership into the three places partners already work - their AI assistant, their chat tools, and their own CRM.
export const Headless = ({children, intro = true}) => {
const [copied, setCopied] = useState(null);
const copy = event => {
const row = event.target.closest("li");
if (!row) return;
const text = row.textContent.trim();
try {
navigator.clipboard?.writeText(text);
} catch {}
setCopied(text);
setTimeout(() => setCopied(null), 1600);
};
return <>
{intro ?
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.
: null}
{children ? :
The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
Claude, ChatGPT, Slack, and your CRM.
}
;
};
export const Rail = ({children}) =>
{children}
;
export const Impact = ({children}) =>
{children}
;
export const Personas = ({children}) =>
{children}
;
export const Pains = ({children}) =>
{children}
;
> Your portal is where partners spend most of their time with you, and it should never be the only way in. Partner Connect brings the same partnership, under the same rules your portal defines, to the three places partner teams also work - their AI assistant, their communication tools, and their own CRM. More adoption. More revenue. Zero friction.
## The problem it solves
| Without Introw | With Introw |
| - | - |
| A busy partner skips the portal login | The program also comes to where they work |
| A busy rep will not hunt for a deal | The deal is on their own record |
| Registering means stopping to log in | One sentence in their assistant |
| You lose sight once it is theirs | Both CRMs stay in sync |
## Impact
This is the whole argument. A partner who never has to leave their assistant, their channel or their CRM to work with you will work with you more than with the vendor who sends them a login.
for your business
* **No new tool**
Partners act from their assistant, their shared Slack or Teams channel, and their own CRM, so a portal login is never the price of entry
* **In your CRM**
Both sides work their own system of record and the shared deal stays synced across the two, with no CRM seat for the partner
* **AI, not admin**
The partner brings their own LLM and reaches deal registration, coaching, enablement and support from inside it
for your partners
* **Self-serve**
Registration, coaching, enablement and support all arrive on the surface they chose, with no login to remember
* **Enabled**
Deal coaching and vendor-grade guidance land on the record they already have open
* **Efficient**
One sentence in the thread where the deal came up, instead of a form in a second system
[A day in the life of your partners](/days-in-the-life)
* **Partner sales teams** - register from chat, co-sell from CRM
* **Partner alliance managers** - tier and earnings from the assistant
* **Partner technical teams** - answers 24/7, without waiting
* **Your own reps** - co-selling from the CRM they use
## How this area works
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.
**Where this sits in a setup.** For partners who run their own CRM. The [co-sell](/tracks/co-sell) and [reseller](/tracks/reseller) tracks bring it in once your own side is live, since it is the partner's setup rather than yours.
* 
[**Partner AI**](./partner-ai)
Their own Claude, GPT or Gemini, connected to your program.
[How to · 3 guides](./partner-ai/technical)
* 
[**Communication Tools**](./communication-tools)
A shared Slack or Teams channel, and WhatsApp.
[How to · 1 guide](./communication-tools/technical)
* 
[**Partner CRM**](./partner-crm)
An Introw card on the partner's own opportunity.
[How to · 8 guides](./partner-crm/technical)
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 by meeting partners on the three surfaces where they already spend their day:
1. **Their AI assistant** - Claude, ChatGPT, Gemini, or any MCP client. The partner asks, the program answers. Introw sits next to the partner's other connectors, so any system they have connected can exchange data with the portal, both directions. 2. **Their communication tools** - Slack, Microsoft Teams, and WhatsApp. The same agent in shared channels and messaging, built for the fast commercial moves: *"@Introw, share this \$20k deal for me."* 3. **Their own CRM** - an Introw card on the partner's own HubSpot record. One click from there opens the full co-sell view, deal coaching included, or the entire portal, signed in automatically.
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 what changes the partner experience, and with it the numbers: more adoption, more registered revenue, zero friction.
Three surfaces, one shared deal that stays synced with yours.
### Where partners start: partners.introw\.io
The three surfaces are where partners *work*. [partners.introw.io](https://partners.introw.io) is where they *set it up* - and the point most easily missed is that it is **theirs, not yours: one account per partner company, spanning every vendor they work with**. A partner who sells three products connects their CRM once and it serves all three. A vendor portal, by contrast, belongs to one vendor and holds that vendor's program.
There a partner signs up with Google, Microsoft, or a six-digit code sent to their email. No password, and no cost to them. They connect HubSpot once, at company level, and install the MCP connector per person. They invite their own colleagues and give each one access to specific vendor portals, without you provisioning anyone. And they open every vendor portal they can reach, signed in automatically. Everything that powers Partner Connect is turned on there.
Two consequences on your side. Portals appear for a partner automatically once you invite their address or allow their email domain, so there is no code to send and no access to request. And your nudge lands them at the point that matches their stage: signup, Integrations, or their home screen. The nudge email always labels that button **Set up Partner Connect**. The banner on the deal uses the stage's own wording - **Get started**, **Connect now**, or **Open Partner Connect**.
The partner front door end to end: create the account, connect the tools, reach every vendor portal. Written to the partner, so you can forward it as the first link.
Two details are worth knowing about the surfaces themselves.
In the assistant, Introw is one connector **among the partner's others** - their CRM, inbox, docs, data warehouse. That makes the assistant the integration layer. A partner can pull the opportunities from their own systems that mention your product and register them in one prompt. Data moves between those systems and the portal with no integration project and no middleware.
In their own CRM, the Introw card opens the full co-sell view, or the entire portal, in one click and already signed in. Everything beyond the deal is one hop away. That is real estate inside your partner's CRM, in front of their sellers every time they open a record - not a portal they forgot the password to. The card works in the partner's own HubSpot and Salesforce alike.
### What it takes from your partners
The usual question is not what Partner Connect does, it is what it costs the partner. Nothing, and no seat in your CRM. Each surface is independent - a partner can take one, two or all three, and none is a prerequisite for another.
| Surface | Partner effort | Who at the partner |
| - | - | - |
| Their AI assistant | About 2 minutes, once per person | Any of their users, no admin rights needed |
| Chat | Nothing to set up | Nobody |
| Their own CRM | About 10 minutes, once | A HubSpot admin who can also manage their Introw integrations |
Four pages carry this end to end, written to the partner so you can forward them:
The front door: create the account, connect the tools, reach every vendor portal.
The forwardable page: permissions, what their sellers see, how to reverse it.
Sequencing across hundreds of partners, by type and by stage.
What a partner rep actually does, day to day.
### What it unlocks, by partner type
The surfaces are the same for every partner; the move that matters differs by [partner type](/partner-types):
* **Referral** - lives in email and chat, not portals. Shares a lead in one sentence from Slack or WhatsApp, and asks their assistant what it will earn. The intro happens when it comes up, not after a login they will never do.
* **Co-sell** - both sales teams work one [linked deal](./partner-crm) from their own CRM. The partner's AE sees your side's status on their own record; your AE never chases for an update.
* **Reseller** - registers from their own CRM the moment an opportunity appears, locking in margin and conflict protection early. Their reps ask the assistant about tier progress, certification gaps and pending commission rather than emailing their alliance manager.
* **Distributor** - queries the network from the assistant (sub-partner status, sell-through, commission roll-ups) and uses its own connectors to move that data into the systems the distribution business already runs on.
* **Implementation** - consultants self-serve technical answers 24/7 and pull your solution docs into their own workspace, so delivery never blocks on the vendor.
## Run it from your AI assistant
Partner Connect is the partner-side half of [Introw's headless motion](/headless). The agentic use cases show it end to end:
Partners register conversationally in 90 seconds - from Claude, Slack, email, or CRM.
Every partner deal gets segment-specific guidance, delivered in the partner's own workspace.
Partner questions answered 24/7 in every language, in chat or the assistant.
Partners query commission status and tier progress in seconds - no portal, no finance ticket.
* What do I still need to close to reach the next tier with this vendor?
* @Introw, share this \$20k deal for me.
* Register the opportunities from my own CRM that mention the vendor's product.
* Check my pending commission and the vendor-side status of my deals.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.