> ## 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 AI

> Partners connect their own LLM - Claude, GPT, Gemini - to reach deal registration, coaching, enablement, training, and support from the assistant they already use.

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 <div className="group flex items-center justify-between gap-3 px-4 py-3 transition-colors hover:bg-[#FD90FF]/[0.06]">
        <span className="text-sm leading-relaxed text-zinc-700 dark:text-zinc-200">{prompt}</span>
        <button type="button" onClick={copy} aria-label={copied ? "Copied to clipboard" : "Copy prompt"} className={`shrink-0 rounded-md p-1.5 transition-all hover:bg-[#FD90FF]/10 focus:opacity-100 focus:outline-none ${copied ? "text-[#FD90FF] opacity-100" : "text-zinc-400 opacity-0 group-hover:opacity-100 dark:text-zinc-500"}`}>
          {copied ? <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M20 6L9 17l-5-5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg> : <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <rect x="9" y="9" width="11" height="11" rx="2" stroke="currentColor" strokeWidth="2" />
              <path d="M5 15V5a2 2 0 0 1 2-2h10" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>}
        </button>
      </div>;
  };
  return <>
      <p>
        Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
        Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
        action written straight back to your CRM source of truth. The portal is one surface, never the only one.
      </p>

      {prompts.length > 0 ? <div className="not-prose my-6 overflow-hidden rounded-2xl border border-zinc-200/80 bg-white shadow-sm dark:border-white/10 dark:bg-white/[0.02]">
          <div className="flex items-center gap-2 border-b border-zinc-200/80 bg-gradient-to-r from-[#FD90FF]/10 via-[#FD90FF]/5 to-transparent px-4 py-2.5 dark:border-white/10">
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4 text-[#FD90FF]" aria-hidden="true">
              <path d="M12 2.5l2 5.5 5.5 2-5.5 2-2 5.5-2-5.5L4.5 10l5.5-2 2-5.5z" fill="currentColor" />
              <path d="M18.5 14l1 2.6 2.6 1-2.6 1-1 2.6-1-2.6-2.6-1 2.6-1 1-2.6z" fill="currentColor" opacity="0.55" />
            </svg>
            <span className="text-xs font-semibold uppercase tracking-wider text-zinc-500 dark:text-zinc-400">
              Try it from your LLM
            </span>
          </div>

          <div className="flex flex-col divide-y divide-zinc-100 dark:divide-white/[0.06]">
            {prompts.map(prompt => <PromptRow key={prompt} prompt={prompt} />)}
          </div>

          <a href="/headless" className="flex items-center justify-between gap-2 border-t border-zinc-200/80 px-4 py-2.5 text-sm font-medium text-zinc-600 no-underline transition-colors hover:text-[#FD90FF] dark:border-white/10 dark:text-zinc-300">
            <span>See the full headless playbook</span>
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M5 12h14M13 6l6 6-6 6" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
          from Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

> Partner AI makes the partnership AI-native on the partner's side: a partner connects their own assistant - Claude, GPT, Gemini, or any MCP client - and reaches everything you offer from it, from registering a deal to getting coached, enabled, trained, and supported.

## What it does

Introw is AI-native for the vendor. Partner AI extends that to the partner. Through MCP, a partner connects the LLM they already use and reaches your resources from inside it: register a deal or share a lead in a sentence, get deal coaching, pull up enablement and training, and get 24/7 answers to support questions - all scoped to what you allow, and all without a portal.

This carries Introw's AI-native model all the way to the partner: the partner does not adopt your tool at all, they bring their own. Every action is permissioned and writes back to the CRM, so the vendor keeps a clean, attributed record even when the partner never touches a portal. Partners who live in an assistant get the full partnership there; partners who live in their CRM or chat get it there. Each partner chooses their surface and finds everything on it.

## The problem it solves

* **Partners won't adopt yet another tool** → The partner uses the assistant they already work in, so there is no new tool to learn and adoption stops being the blocker.
* **Registering, coaching, and support all live behind a portal login** → The partner reaches them from their LLM in a sentence, removing the friction that keeps partners disengaged.
* **Answers to partner questions require the vendor or a search** → An MCP-connected assistant answers 24/7 in the partner's own language, so the partner self-serves and the vendor's team is freed up.
* **The vendor fears losing control or attribution to AI** → Every action is scoped by permissions and writes back to the CRM, so the vendor keeps a clean, auditable, attributed record.

## From problem to solution

Before, "AI-native" stopped at the vendor's edge - the partner still had to log in and click. Now the partner brings their own assistant and reaches deal reg, coaching, enablement, training, and support from it, permissioned and synced to the CRM. Friction drops to near zero, partners engage where they already are, and the vendor gets more partner activity with full visibility - the level of adoption a portal never delivered.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  connect["Connect own assistant"] --> reach["Reach deal reg, coaching, support"]
  reach --> synced["Permissioned and synced to CRM"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Register from your assistant" icon="circle-check">
    Register a deal or share a lead from Claude, GPT, or Gemini in a sentence.
  </Card>

  <Card title="Self-serve support 24/7" icon="circle-check">
    Get answers to partner questions in your own language, any time.
  </Card>

  <Card title="Reach enablement and training" icon="circle-check">
    Pull up the content and courses you need from the assistant.
  </Card>

  <Card title="Coach the deal" icon="circle-check">
    Get selling guidance without opening another tool.
  </Card>
</CardGroup>

## Impact

* **AI-native** - The partnership is AI-native for the partner, not only the vendor.
* **Work where you already are** - The partner acts from their own assistant; the portal is never required.
* **Partner self-serve** - Deal reg, coaching, enablement, training, and support all come to the partner on demand.
* **Composability** - MCP is a building block the partner connects to their own client of choice.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner - Sales & Marketing" icon="user">
    Registers deals and gets coaching and answers from their own assistant.
  </Card>

  <Card title="Partner - Technical / Support" icon="user">
    Self-serves technical answers and enablement without waiting on the vendor.
  </Card>

  <Card title="Partner - Vendor/Alliance Manager" icon="user">
    Connects the partner's AI and manages what it can reach.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="MCP" icon="code" href="/features/developer/mcp">
    Connect any MCP client - Claude, ChatGPT, Cursor - to Introw.
  </Card>

  <Card title="Partner Support Agent" icon="robot" href="/features/ai/partner-support">
    The partner's questions get answered by the support agent.
  </Card>

  <Card title="Partner CRM" icon="circle-nodes" href="/features/partner-connect/partner-crm">
    Pair the AI surface with the partner's own CRM.
  </Card>

  <Card title="Deal Registration" icon="file-signature" href="/features/deal-registration/registration">
    Register and protect deals from the assistant.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"Connect my own LLM and ask for my commission status across the vendor's program.",
"Register a deal with the vendor from Claude.",
"What training or certifications do I still need with this vendor?",
]}
/>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Endpoints and code.
  </Card>
</CardGroup>