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

# Deal Coaching

> Put an AI coach in every partner deal - segment-specific stage guidance, objection handling, and the right enablement, surfaced on the deal and through the agent.

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>}
    </>;
};

> You cannot put a partner development manager on every deal, but you can put a coach. Deal coaching gives partners segment-specific guidance on every deal - what to do at each stage, how to handle objections, and which content to use.

## What it does

Deal coaching is a set of playbooks that guide partners through deals. You build a coach scoped to a
pipeline and to specific deals, partners, or segments, and define its content: instructions for each
stage, objection handling, enablement assets to surface, and rules of engagement. When a partner
works a matching deal, the coaching appears right on the deal record and through the partner support
agent when they ask "what should I do here?".

AI helps you build the playbook quickly when you create a coach, generating a first draft you refine.
Because coaches are scoped by pipeline, deal, partner, and segment, each partner gets advice that
fits their motion, referral, co-selling, or reselling, rather than generic tips.

## The problem it solves

Partners stall on deals because they are not your sales team:

* **Partners lack deal know-how** → Stage instructions guide them step by step.
* **Objections go unhandled** → Objection handling equips them with responses.
* **The right content is hard to find** → Enablement assets surface on the deal.
* **Coaching does not scale** → Every matching deal gets coached automatically.

## From problem to solution

Deal coaching scales your best sales guidance across every partner deal. Build playbooks once, scope
them to the right motions, and partners get expert, contextual advice on the deal and through the
agent, lifting win rates without adding headcount.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  playbooks["Build playbooks"] --> scope["Scope to the right motions"]
  scope --> surface["Surfaced on the deal and agent"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Coach every deal" icon="circle-check">
    Guidance on each partner deal.
  </Card>

  <Card title="Handle objections" icon="circle-check">
    Equip partners for pushback.
  </Card>

  <Card title="Surface enablement" icon="circle-check">
    Put the right content in reach.
  </Card>

  <Card title="Fit each motion" icon="circle-check">
    Scope coaching by segment and pipeline.
  </Card>
</CardGroup>

## Impact

* **AI-native** - AI drafts playbooks and surfaces coaching in context.
* **CRM-native** - Coaching attaches to deals in your CRM.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Operations" icon="user">
    Builds and scopes coaching playbooks.
  </Card>

  <Card title="Sales Leadership" icon="user">
    Defines the guidance partners receive.
  </Card>
</CardGroup>

## Works with

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

<CardGroup cols={2}>
  <Card title="Shared Pipelines" icon="handshake" href="/features/co-selling/shared-pipelines">
    Coach partners on deals in the shared pipeline.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"Coach me on the Acme deal: what are the risks and next steps?",
"Which of my deals need attention this week?",
"What should I do to move the Globex deal forward?",
]}
/>

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