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

# Visibility & collaboration

> Give partners a live view of shared deals and CRM records with no CRM seat - register, comment, update, complete tasks, and stay in sync automatically.

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 ? <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> : null}

      {children ? <div className="not-prose" data-prompts="block">
          <div data-prompts="head">
            <span>{copied ? "Copied" : "Try it from your LLM"}</span>
          </div>
          <div data-prompts="rows" onClick={copy}>
            {children}
          </div>
          <a href="/headless/prompts" data-prompts="more">
            See all prompts
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
          Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

export const Rail = ({children}) => <div className="not-prose" data-overview="rail">
    {children}
  </div>;

export const Impact = ({children}) => <div className="not-prose" data-overview="impact">
    {children}
  </div>;

export const Personas = ({children}) => <div className="not-prose" data-overview="personas">
    {children}
  </div>;

export const Pains = ({children}) => <div className="not-prose" data-overview="pains">
    {children}
  </div>;

> This is where partners **see and act on** the CRM records that involve them. Every partner - referral, reseller, distributor, implementation, or affiliate - gets a live, transparent view of their deals and records, is nudged automatically when something changes, and can self-serve on each one, while everything writes back to your CRM and no partner ever needs a seat in it.

## The problem it solves

<Pains>
  | Without Introw | With Introw |
  | - | - |
  | Partners cannot see what happened | They see their own deals live |
  | You reconcile status over email | Both sides read one record |
  | Partners would need CRM seats | Scoped views, and no seat |
  | Attribution is argued afterwards | Registration settles it up front |
</Pains>

## Impact

Opacity is what kills a channel. A partner who can see what happened to the lead they sent, without asking, refers again; the one who had to chase you does not.

<Impact>
  for your business

  * **In your CRM**
    Everything happens on the CRM record and writes back to it, so there is one pipeline rather than two to reconcile
  * **No new tool**
    Your reps stay in HubSpot or Salesforce and partners stay in the portal or their own CRM, on the same record
  * **Trustworthy**
    Attribution, conflict detection and approvals decide credit before the deal moves, not after it closes

  for your partners

  * **Self-serve**
    They comment, update the fields you expose and complete tasks on the deal, without a seat in your CRM
  * **Enabled**
    An automatic nudge when a stage changes, which for a referral partner is most of the value they wanted
  * **Efficient**
    Nobody emails to ask where a deal stands, because the answer is already on the record

  [A day in the life of a co-sell partner](/days-in-the-life/co-sell-partner)
</Impact>

<Personas>
  * **Partner Managers** - records that move without chasing
  * **Your own reps** - collaboration inside the CRM
  * **Partners of every type** - their deals, visible and actionable
</Personas>

## How this area works

Partnerships stall on opacity. The partner can't see what happened to the lead they sent, the vendor can't see the partner's work, and both sides reconcile status over email. This area closes that gap. Partners get a **transparent, scoped window into your CRM** and can **self-serve** on the records that involve them. They see the deal, get nudged when its stage changes, comment, update the fields you allow, and complete tasks. It all writes back to HubSpot or Salesforce, and none of it needs a CRM seat.

**Where this sits in a setup.** The [co-sell track](/tracks/co-sell) sequences this end to end, and the [distributor track](/tracks/distributor) adds the multi-tier case where two partners are credited on one deal.

<Rail>
  * ![A registered deal on its submission thread: the fields the partner submitted, the deal it created, and the partner that registered it.](https://assets.introw.io/docs/features/co-selling/deal-lead-registration/shots/submission.png)

    [**Deal & Lead Registration**](./deal-lead-registration)

    Let partners register deals and leads, with channel-conflict checks and approvals, synced to your CRM.

    [How to · 17 guides](./deal-lead-registration/technical)

  * ![A deal opened from the shared board, with its CRM properties, the partner attributed to it and the conversation both companies work in.](https://assets.introw.io/docs/features/co-selling/shared-pipelines/shots/deal.png)

    [**Shared Pipelines**](./shared-pipelines)

    A scoped view of their attributed deals and records: you set what they see, edit and how it is labelled, with auto-nudges on every change.

    [How to · 7 guides](./shared-pipelines/technical)

  * ![The Tasks tab of a partner record, with each task's status, due date, assignee, and the action the partner takes to close it.](https://assets.introw.io/docs/features/co-selling/tasks/shots/tasks.png)

    [**Tasks**](./tasks)

    The next step on the shared deal, with an owner.

    [How to · 1 guide](./tasks/technical)
</Rail>

That transparency-and-self-service value is **not** limited to co-selling - it matters for every partner type:

* **Referral partners** - transparency into what happened to their lead, and an automatic nudge when the deal moves, is often the entire value they want.
* **Resellers & distributors** - one scoped, shared pipeline of their attributed deals, collaborated on in context.
* **Implementation partners** - a clean handoff on the won deal, worked without a CRM seat.
* **Affiliates** - visibility into the conversions and deals their referrals became.

Co-selling is simply the motion where both sides push a deal to close together; it rides on the same shared records. When a partner runs their own CRM, [Partner Connect](/features/partner-connect) links the two systems on one deal.

## Run it from your AI assistant

<Headless>
  * Which shared deals are closing this quarter and what stage are they in?
  * Add a comment on the Globex deal asking the rep for next steps.
  * Create a task on the Acme deal to send the security questionnaire.
</Headless>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.