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

# Partners

> Auto-detect, organize, and progress partners with your CRM as the single source of truth - management, journeys, tiers, and segments in one place.

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

> Partners is where your program lives: every partner is detected from your CRM, organized into phases, tiers, and segments, and moved through onboarding and activation, all without a second source of truth.

## The problem it solves

<Pains>
  | Without Introw | With Introw |
  | - | - |
  | The partner list drifts to a sheet | One list, owned by the CRM |
  | Onboarding lives in someone's head | A journey every partner runs |
  | Quiet partners surface at review | Stalls are visible early |
  | Tiers are a slide, not a ladder | Requirements and benefits, live |
</Pains>

## Impact

Partners invest where they can see the ladder. A visible stage, a named owner and a next step is most of what separates a program they grow in from a logo they signed with.

<Impact>
  for your business

  * **In your CRM**
    Partners are detected and synced from HubSpot or Salesforce, so there is one partner list and it is the CRM's
  * **Cost to run**
    Phases, tiers, journeys and segments are all configured by partner ops, with no engineering
  * **Live in days**
    The structure of a real program, phases, tiers and onboarding journeys, stands up in an afternoon

  for your partners

  * **Self-serve**
    The portal opens up as they qualify, so nobody grants them access step by step
  * **Enabled**
    A journey gives them the next step, and a tier tells them what the step after that unlocks
  * **Efficient**
    One named owner, one clear stage, and a checklist instead of a monthly catch-up call

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

<Personas>
  * **Partner Managers** - the relationship, without leaving
  * **Partner Operations** - phases, tiers, journeys, segments
  * **VP Partnerships** - activation as a leading indicator
  * **Partners** - a visible ladder and next step
</Personas>

## How this area works

A partner program falls apart when partner data lives in a spreadsheet that drifts from the CRM. Partners keeps your CRM as the system of record and builds the program on top of it. Partners are auto-detected from the companies or records you already manage in HubSpot or Salesforce, and kept in sync both ways. They are organized with the structure a real program needs: lifecycle phases, tiers and targeting segments.

**Where this sits in a setup.** Immediately after the CRM. Every [setup track](/tracks) gets partners and their contacts in before building anything they will see.

<Rail>
  * ![A partner record, with its tier and owner in the header and tabs for analytics, people, deals, tickets, tasks, notes and goals.](https://assets.introw.io/docs/features/partners/partner-management/shots/partner.png)

    [**Partner Management**](./partner-management)

    Detect partners from the CRM, and phase them.

    [How to · 5 guides](./partner-management/technical)

  * ![A journey's configuration, with each task's progress across the partners assigned to it, who owns the task, and whether the partner can see it.](https://assets.introw.io/docs/features/partners/journeys/shots/journey.png)

    [**Journeys**](./journeys)

    Onboarding and activation as a repeatable playbook.

    [How to · 4 guides](./journeys/technical)

  * ![A tier program as a matrix: the requirements a partner meets for Bronze, Silver, Gold or Elite, and the benefits each tier unlocks.](https://assets.introw.io/docs/features/partners/tiers/shots/program.png)

    [**Tiers**](./tiers)

    Requirements and benefits, synced to the CRM.

    [How to · 2 guides](./tiers/technical)

  * ![The default portal permissions every partner inherits - whether contacts may invite their own colleagues, and whether they see every record shared with their company - each with a live preview of the result, and each overridable per segment.](https://assets.introw.io/docs/features/partners/segments/shots/permissions.png)

    [**Segments**](./segments)

    Group partners into dynamic or static segments that target content, notifications, and more.

    [How to · 4 guides](./segments/technical)

  * ![The partner portal with its onboarding tab, the tasks the partner works through and the mutual action plan beside them.](https://assets.introw.io/docs/features/partners/onboarding/shots/portal.png)

    [**Partner Onboarding**](./onboarding)

    Onboard partners progressively, unlocking tabs, assets, and abilities as they qualify.

    [How to · 1 guide](./onboarding/technical)

  * ![The People tab of a partner record, listing every contact on that partner's account and the access each one has.](https://assets.introw.io/docs/features/partners/team/shots/people.png)

    [**Partner Team**](./team)

    Assign your team to each partner and let that ownership drive the program.

    [How to · 1 guide](./team/technical)

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

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

    Clear next steps, shown in the portal.

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

From there, you progress partners deliberately. Onboarding and activation are run as repeatable journeys instead of one-off reminders, so a new partner reaches first deal faster and a quiet partner gets caught before the next review, not after. Tiers set the benefits and requirements that motivate partners to grow, and segments decide who sees what across the rest of the product.

Because everything sits on the CRM, the program stays clean: no rogue objects, no duplicate partner lists, and every status change reconciled to the record your revenue team already trusts.

## The spine the rest of the program hangs off

Partner management is not one stage of the relationship, it is the record every other stage reads from.
Partners arrive through CRM detection or an [intake form](/features/forms) you publish. [Journeys](./journeys)
run onboarding and activation. [Tiers](./tiers) and [goals](/features/reporting/goals) define what growth
looks like and what it earns. [Deal registration](/features/deal-registration) and
[visibility and collaboration](/features/co-selling) carry the business itself.
[Reporting](/features/reporting) and business reviews close the loop and set the next plan. Every one of
those reads the partner's phase, tier, and segments from here, which is why a change made once shows up
everywhere.

## The partner lifecycle, stage by stage

| Stage | What happens | The feature | What runs without a person |
| - | - | - | - |
| Recruit | New partners apply or get found | [Partner application form](/features/forms/form-builder/guides/set-up-a-partner-application-form), [Partner Directory](/features/portal/partner-directory), [Crossbeam](/features/integrations/crossbeam), [scouting from your AI assistant](/headless/agentic-use-cases/partner-acquisition) | A submitted application creates the partner, links it in the CRM, and invites them |
| Onboard | The partner gets set up and signs the paperwork | [Journeys](./journeys), [Partner Onboarding](./onboarding), [agreements](./onboarding/guides/get-partner-agreements-signed) | Tabs, assets, and abilities open up as the partner qualifies |
| Activate | The partner learns the product and takes first steps | [Tasks](./tasks), [Courses](/features/courses), [Content](/features/content), [Engagement](/features/engagement) | Courses assign by segment, and announcements and notifications go out on their own |
| Grow and co-sell | The partner brings and works deals | [Deal registration](/features/deal-registration), [Shared Pipelines](/features/co-selling/shared-pipelines), [Referrals](/features/referrals) | Conflict checks run on submission, and deal updates reach the partner automatically |
| Review | You and the partner look at results and set the next plan | [Reporting](/features/reporting), [Goals](/features/reporting/goals), QBR prep from the [AI copilot](/features/ai/copilot) or [your AI assistant](/headless/agentic-use-cases/qbrs-meeting-prep) | Goal progress and pace status update from the CRM |
| Reward | The partner earns for what they did | [Tiers](./tiers), [Commissions](/features/commissions), [Introw Pay](/features/commissions/introw-pay), [MDF](/features/mdf) | Commission lines book from CRM data, and a workflow updates the tier |

The long tail runs on the same rails. In one [workflow](/features/automation/workflows), a partner
completes a course, a [certificate](/features/courses/certificates) is issued, a one-off commission is
added for the partner, and their tier property is updated. Nobody on your team touches it, and every
step lands in the CRM.

## Every partner gets the attention of a strategic one

Most programs can only give real attention to their top ten partners. Everyone else gets a quarterly email
and a portal they rarely open, and that lack of hours, not lack of intent, is why long-tail partners
underperform. Here, progression is structural rather than remembered: phases and tiers update from the CRM
and from [workflows](/features/automation/workflows), journeys hand each partner their next step, segments
unlock the program as they qualify, and goals say who is off pace this week. The same attention then runs
across the whole base without more headcount. From the partner's side, being one of two hundred is
indistinguishable from being one of ten.

## Run it from your AI assistant

<Headless>
  * Which Gold partners haven't registered a deal this quarter?
  * Move Acme up to the Gold tier.
  * Prepare a QBR for my top partner.
</Headless>


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