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

> Partners see the vendor and live deal status on their own CRM opportunity, and register, co-sell, coach, and reach the right rep from inside HubSpot or Salesforce.

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 CRM brings the vendor to the partner's own record: on their open opportunity in HubSpot or Salesforce, a partner sees which vendor is involved, where the deal stands on the vendor side, and can register, co-sell, get coaching, and reach the right rep - without leaving their CRM.

## What it does

A partner rep lives in their own CRM. Partner CRM meets them there: an Introw card on their opportunity shows the vendor on the deal and the live status from the vendor's side, so the partner always knows where things stand without asking. From that same record they register the deal or share a lead, get stage-specific deal coaching in context, and message the right seller on the vendor's team directly - no portal, no hunting for the deal, no email chain.

Because everything writes back to both systems of record, the partner and the vendor work one shared reality. The partner never logs in to a portal to check status or take action, and the vendor never chases the partner for an update. The result is the deepest form of off-portal co-selling: the partner's CRM becomes a full window into the partnership.

## The problem it solves

* **A partner can't see where the vendor's side of the deal stands** → The Introw card shows live vendor status right on the partner's opportunity, so no one waits on an email to know what's happening.
* **Registering or updating a deal means leaving the CRM for a portal** → The partner registers, shares leads, and co-sells from the record they already have open, cutting the busywork that kills partner adoption.
* **Reaching the right rep is slow and manual** → The partner messages the correct seller from the deal itself, so joint deals move faster.
* **Reps have no in-context selling help** → Deal coaching surfaces on the record, so a partner rep gets vendor-grade guidance without training on a new tool.
* **The vendor loses visibility once a deal is with the partner** → Two-way sync keeps the vendor's CRM current, so partner-attached pipeline stays trustworthy and attributed.

## From problem to solution

Before, a partner rep had to leave their CRM, log in to a portal, find the deal, and still email the vendor for status. Now the deal, the status, the actions, and the right rep all live on the record they already work. The partner acts in seconds where they already are, and the vendor gets a real-time, attributed view of every partner-attached deal - more joint pipeline, less friction, and no forced portal.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  ownCrm["Partner's own CRM"] --> context["Vendor and deal status on the record"]
  context --> act["Register and act in seconds"]
  act --> vendor["Vendor gets an attributed view"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="See vendor status in the CRM" icon="circle-check">
    Know which vendor is on the deal and where it stands, on your own opportunity.
  </Card>

  <Card title="Register and co-sell in place" icon="circle-check">
    Register deals, share leads, and collaborate without leaving HubSpot or Salesforce.
  </Card>

  <Card title="Coach the deal in context" icon="circle-check">
    Get stage-specific AI selling guidance right on the record.
  </Card>

  <Card title="Reach the right rep" icon="circle-check">
    Message the correct seller on the vendor's team from the deal itself.
  </Card>
</CardGroup>

## Impact

* **Work where you already are** - The partner works entirely from their own CRM; the portal is never the entry point.
* **CRM-native** - Both sides work their system of record, kept in sync two ways.
* **AI-native** - Coaching and context come to the partner where they sell.
* **Partner self-serve** - The partner registers, updates, and gets help without waiting on the vendor.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner - Sales & Marketing" icon="user">
    Registers, co-sells, and reaches the right rep from the CRM they already use.
  </Card>

  <Card title="Partner - Vendor/Alliance Manager" icon="user">
    Connects the partner's CRM and keeps shared deals aligned with the vendor.
  </Card>

  <Card title="Sales Rep / AE" icon="user">
    Co-sells with the partner on the shared record without leaving the CRM.
  </Card>
</CardGroup>

## Works with

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

<CardGroup cols={2}>
  <Card title="Connected Deals" icon="circle-nodes" href="/features/partner-connect/connected-deals">
    Link the partner deal to the vendor's and keep both in sync.
  </Card>

  <Card title="CRM" icon="plug" href="/features/integrations/crm">
    The Introw card renders vendor context on the partner's CRM record.
  </Card>

  <Card title="Deal Coaching" icon="robot" href="/features/ai/deal-coaching">
    Coach the deal in context on the record.
  </Card>

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

## Headless

<Headless
  prompts={[
"Show the vendor's live status on my open opportunity.",
"Register this deal with the vendor without leaving my CRM.",
"What next steps did the vendor's rep leave on our deal?",
]}
/>

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