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

# Roll out Partner Connect at scale

> Sequence a Partner Connect rollout across hundreds of partners: read the adoption funnel, target nudges by segment, and pick the right surface per partner type.

Partner Connect adoption is not a broadcast. With a large partner base, the thing that decides whether it lands is sequencing: which partners you ask, in what order, for which surface, and at what moment. This guide is the playbook.

One thing to have straight before you start asking, because it is the question every partner comes back with: **everything you are asking them to do happens at [partners.introw.io](https://partners.introw.io)**, their own Introw account, not inside your portal. It is free, it takes a minute to create, and it covers every vendor they work with - so a partner already connected to another vendor is most of the way done with you. [Get started as a partner](./get-started-at-partners-introw-io) is the link to put in your own words when you ask.

## What you'll achieve

A rollout you can run from the partner list instead of an inbox: partners sorted by exactly where they are stuck, nudges targeted by segment, and the ask matched to each partner type, so you spend your time on the partners where a connected CRM changes revenue.

## Before you start

<Steps>
  <Step title="Partner Connect is enabled">
    Partner Connect is a module on your plan. If you do not see the Partner Connect column in your partner list, contact Introw to have it turned on.
  </Step>

  <Step title="Deals are attributed to partners">
    A partner can only link to deals you have attributed and exposed to them. Without that there is nothing on the other side to connect to. See [Set up a shared pipeline](/features/co-selling/shared-pipelines/guides/set-up-a-shared-pipeline).
  </Step>

  <Step title="The right contacts have portal access">
    Nudges only reach active portal contacts. A partner with no active contact cannot be nudged, and will be reported back to you as skipped.
  </Step>
</Steps>

## Read the funnel before you send anything

Introw scores every partner into one of four stages, shown as a **Partner Connect** column in [Partners](https://app.introw.io/partners) and on each partner's detail page. Sort by it and your rollout list writes itself.

| Stage       | Shown as          | What it means                                                          | The ask                                            | Where the nudge lands them             |
| ----------- | ----------------- | ---------------------------------------------------------------------- | -------------------------------------------------- | -------------------------------------- |
| Onboard     | **Not onboarded** | Nobody from this partner has an Introw account yet                     | Get one person signed up                           | The signup page at partners.introw\.io |
| Connect     | **Stalled**       | They have an account but have connected neither a CRM nor an assistant | Connect one surface, whichever is easiest for them | Their Integrations page                |
| Attach deal | **Connected**     | Their tools are connected, but this specific deal is not linked        | Link this deal                                     | Their Partner Connect home             |
| Done        | **Connected**     | Connected and this deal is linked                                      | Nothing, leave them alone                          | n/a                                    |

Two things to notice, because they change how you work the list:

* **The Connect stage counts either surface.** A partner who connected only an AI assistant already counts as connected. That matters: for many partners the assistant is the realistic first step, and it moves the funnel on its own.
* **Attach deal is deal-scoped.** The same partner can be Done on one deal and Attach deal on another, so this stage is a per-deal to-do list, not a partner property.

## Sequence it: three waves, not one campaign

Resist the mass email. A partner who has no live deal with you has no reason to install anything today, and a nudge they ignore is harder to repeat.

<Steps>
  <Step title="Wave 1: partners with live co-sell pipeline">
    Filter to partners who currently have attributed open deals, and start with them. The conversation is concrete ("this deal, on your own record, no more status emails") and the payoff is immediate on both sides. This wave produces your reference stories.
  </Step>

  <Step title="Wave 2: the rest of your active partners, assistant first">
    Ask for the lowest-effort surface, not the deepest. Connecting an assistant takes any rep about two minutes and needs no admin, so it converts far better than a CRM install as an opening ask. It also moves them to Connected, which means the next nudge they get is the deal-linking one.
  </Step>

  <Step title="Wave 3: deal-triggered, forever">
    Stop campaigning and let the co-sell moment do the work. When you are working a deal with an unconnected partner, the nudge is right there on the deal. This is the highest-intent moment you will ever get, because the partner gains something today, and it scales without you running anything.
  </Step>
</Steps>

## Target the nudge

The nudge is a stage-aware email with a **Set up Partner Connect** button that drops the partner on the exact page at partners.introw\.io they need next: signup, Integrations, or their home screen, depending on their stage. You never have to explain which step they are on, and they never have to find the address themselves.

Targeting controls, in the order you will reach for them:

* **Segment** picks which partners are in scope, and it respects the contact-level filters inside that segment. So you can nudge, for example, only the primary partner contacts of tier-1 resellers in EMEA, rather than everyone attached to those accounts. This is the control to use when you want granularity over who hears about Partner Connect. See [Segments](/features/partners/segments).
* **Connected filter** hides partners who are already done, so you are only ever looking at partners worth asking.
* **Contact selection** is per (contact, partner) pair, so you choose the individual people, not just the company.
* **Personal message** is prefilled and editable. Replace the default with one line about the specific deal or relationship; it is the difference between a product announcement and a request from a person.

<Info>
  Sending is deliberately partial-success. Partners who are already connected, or who have no active portal contact, are skipped and reported back with the reason ("Already connected", "No portal contact to nudge") rather than silently dropped. Treat the skipped list as your data-hygiene queue: a partner with no portal contact is a partner you cannot reach through any surface.
</Info>

## Match the ask to the partner type

The surfaces are identical for every partner. What differs is which one to ask for first, and how hard to push.

| Partner type       | Ask for first                   | Notes                                                                                                                                                                                                           |
| ------------------ | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Reseller**       | Their CRM                       | The strongest fit. Resellers running real sales ops want registration and margin protection from their own record, and typically pin the card near the top of the deal view. Expect enthusiasm, not resistance. |
| **Co-sell**        | Their CRM, on a live deal       | Lead with the specific shared deal. Both AEs stop chasing status, which is an easy yes when there is pipeline on the table.                                                                                     |
| **Referral**       | Chat or assistant, CRM optional | The win is sharing a lead from their own CRM the moment it comes up. They are usually happy to connect, and they do not need the card high in the sidebar. Do not open with a CRM-install ask.                  |
| **Distributor**    | Assistant                       | Roll-ups of sub-partner status and sell-through from their own stack are the draw. Pair with a channel per relationship rather than a portal seat per rep.                                                      |
| **Implementation** | Assistant                       | Technical self-serve, 24/7, in their own workspace. A CRM connection is rarely the point.                                                                                                                       |

<Warning>
  Deal linking from the partner's own CRM is HubSpot-only today. For partners on Salesforce or any other CRM, do not include the CRM ask in your sequence. Point them at the assistant and chat surfaces, and have them register deals instead of linking. See [Register instead of link](./register-instead-of-link).
</Warning>

## Give partners something to forward

The person you nudge is usually not the person who has to approve the CRM install. Assume your message gets forwarded to a CRM ops or security reviewer who has never heard of Introw, and give them a link that answers them without you in the loop.

Send [Introw for partners](./introw-for-partners). It covers what each surface takes, the exact HubSpot permissions and why they are requested, the fact that nothing about a deal reaches you until the partner links or registers it, what their sellers will see, and how to reverse everything. Pair it with the click-throughs in [Connect HubSpot](./connect-hubspot) so their admin can see the whole install before agreeing to it, and with [Get started as a partner](./get-started-at-partners-introw-io) for whoever actually has to create the account and find the screens.

Two objections worth pre-empting rather than waiting for:

* **"An unknown app in our CRM."** Name it up front: the app is Introw Connect, it is installed at account level, and support is [support@introw.io](mailto:support@introw.io). Offer to put your Introw contact on a call with their CRM team. Partners who have to discover the app name themselves get more suspicious, not less.
* **"It will clutter our sellers' view."** True and controllable: the card is a sidebar card, its position is entirely the partner's choice, and sellers with no vendor access see a single small tile. Say so before they raise it.

## Measure it

* **Funnel movement** in the partner list is the primary metric. Count partners in each stage weekly and watch Stalled shrink.
* **Linked deals** are the outcome metric. A connected partner who never links a deal has not changed anything about how you work together.
* **Per-partner status** on the partner detail page tells you whether a specific relationship is actually live, so you know before promising a colleague that they can read the partner's side off the record.

Expect a long tail. A large partner base will not converge, and it does not need to: the partners who matter are the ones with pipeline, and Wave 3 keeps catching the rest as deals appear.

## Related

<CardGroup cols={2}>
  <Card title="Get started as a partner" icon="door-open" href="./get-started-at-partners-introw-io">
    The front door at partners.introw\.io. Forward it to whoever has to do the setup.
  </Card>

  <Card title="Introw for partners" icon="share-nodes" href="./introw-for-partners">
    The page to forward to a partner's CRM or security team.
  </Card>

  <Card title="Enable Partner Connect and link a deal" icon="link" href="./enable-partner-connect-and-link-a-deal">
    The end-to-end flow across both sides.
  </Card>

  <Card title="Segments" icon="filter" href="/features/partners/segments">
    Build the audiences you target nudges with.
  </Card>

  <Card title="Set up a shared pipeline" icon="diagram-project" href="/features/co-selling/shared-pipelines/guides/set-up-a-shared-pipeline">
    Attribute and expose the deals partners link to.
  </Card>
</CardGroup>
