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

> Auto-detect partners from your CRM, keep them in sync both ways, and organize them into lifecycle phases - one partner list, always the CRM's.

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 Management turns the partners you already track in your CRM into a live, organized program, with no second list to maintain and nothing that drifts out of sync.

## What it does

Partner Management detects your partners directly from the companies or records you keep in HubSpot or Salesforce. You tell Introw how partners are stored, which records count as partners, and what to link to them, and it builds your partner list from there. New partners that match your criteria can flow in automatically, and changes sync both ways so the CRM stays the source of truth.

Once partners are in, you organize them. A visual list shows the properties that matter to your team, and lifecycle phases (from first contact to signed and active) let you see at a glance where every partner sits. Each partner has a detail view with their people, deals, tasks, assets, and goals in one place, so a partner manager never has to leave Introw to understand a relationship or jump into the CRM to keep it current.

## The problem it solves

Most programs run on a partner list that started in the CRM and quietly diverged into spreadsheets:

* **Recruiting partners is guesswork** → Detect partners straight from the CRM records you already qualify, so your program is built on real accounts instead of a parallel list.
* **The partner list drifts from the CRM** → Two-way sync keeps one partner record, owned by the CRM, so partner ops stops reconciling duplicates by hand.
* **No clear view of where each partner stands** → Lifecycle phases show every partner's stage at a glance, so partner managers know who to push and who to celebrate.
* **Adding a partner means manual data entry** → New matching partners sync in automatically and a manual create pulls company data from the CRM, so onboarding starts with clean data.

## From problem to solution

Partner Management makes the CRM do the heavy lifting. Instead of maintaining a partner database, you point Introw at your existing records and it keeps a single, synced partner list organized into the phases your program runs on. Partner ops gets clean data without reconciliation, and partner managers get one place to see and move every relationship.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  crm["Point at CRM records"] --> list["Single synced partner list"]
  list --> phases["Organized into phases"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Detect partners from the CRM" icon="circle-check">
    Build your partner list from the companies or partner records you already manage.
  </Card>

  <Card title="Keep one synced list" icon="circle-check">
    Let new matching partners flow in and changes sync back, so nothing drifts.
  </Card>

  <Card title="Run a lifecycle" icon="circle-check">
    Move partners through phases from potential to signed and active.
  </Card>

  <Card title="Work a partner in one view" icon="circle-check">
    See a partner's people, deals, tasks, and goals together on their detail page.
  </Card>
</CardGroup>

## Impact

* **CRM-native** - One partner list, owned by the CRM and synced both ways, so there is no second source of truth to maintain.
* **Time to value** - Detection builds your partner list from CRM records the moment you connect, so the program starts populated instead of as an empty database you have to fill.
* **Low total cost of ownership** - Partner ops configures detection, phases, and views with no-code, without involving engineering.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Manager (CAM / PAM)" icon="user">
    Works the relationship and tracks each partner's stage without leaving Introw.
  </Card>

  <Card title="Partner Operations" icon="user">
    Configures detection and phases and keeps partner data reconciled to the CRM.
  </Card>
</CardGroup>

## Works with

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

<CardGroup cols={2}>
  <Card title="CRM" icon="plug" href="/features/integrations/crm">
    Partners are detected from your CRM.
  </Card>

  <Card title="Partner Team" icon="users" href="/features/partners/team">
    Assign an owner to each partner.
  </Card>

  <Card title="Tiers" icon="users" href="/features/partners/tiers">
    Organize partners into tiers.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"Show partners in EMEA with no activity in the last 60 days.",
"Change Acme's partner manager to me.",
"Update Globex's lifecycle phase to active.",
]}
/>

## 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">
    Integration surface and code.
  </Card>
</CardGroup>
