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

# Implementation track

> Stand up the implementation motion in Introw: a clean sales-to-delivery handoff on the CRM deal, scoped access so delivery teams see only their accounts, onboarding and go-live tracking, and certification that gates who can deliver.

> An [implementation partner](/partner-types#implementation) does not close the deal - it delivers the outcome after someone else wins it. This track sets up the three things that make delivery work in Introw: a clean handoff that attaches the implementation partner to the won deal, scoped access so consultants see only the accounts they deliver on, and certification that gates who is authorised to deliver. Then it adds the onboarding, enablement, and health tracking that drive go-live.

<Note>
  **Time to first value:** an implementation partner working a handed-off deal on the CRM record within a few days. **Owned by:** Partner Operations and the Partner Manager, with Partner Marketing on certification and enablement.
</Note>

<Warning>
  An implementation partner is measured on go-live and adoption, not on the signature. This track configures delivery on the same CRM record the deal closed on - not a separate services system - so the vendor keeps visibility from close through go-live.
</Warning>

## What an implementation partner actually needs

An implementation partner is a delivery organisation: a practice lead owns the vendor relationship and certification standing, while consultants own scoping, configuration, and go-live for each customer. There is rarely a quota-carrying rep, because the deal is closed elsewhere. The partner needs a clean handoff with full deal and account context, scoped access to only the accounts they deliver on, onboarding and go-live tracking on the record, and certification to be authorised to deliver. The single most useful thing you configure is the handoff onto the CRM deal.

## Set up the foundation

<Steps>
  <Step title="Connect your CRM">
    **Why it matters.** Delivery has to happen on the same record the deal closed on, or the vendor loses sight of the customer between close and go-live. Connecting the CRM first means the implementation partner works the won deal and its context directly, with nothing to reconcile later.

    Connect HubSpot or Salesforce as the system of record.

    **Time:** 20 to 30 min  ·  **Who:** CRM Administrator, Revenue Operations

    <CardGroup cols={2}>
      <Card title="Connect your CRM" icon="plug" href="/features/integrations/crm/guides/connect-salesforce">
        Two-way sync with Salesforce or HubSpot.
      </Card>

      <Card title="Choose how partners are stored" icon="database" href="/features/integrations/crm/guides/connect-hubspot">
        Decide how implementation-partner records map into the CRM.
      </Card>
    </CardGroup>
  </Step>

  <Step title="Import partners and their contacts">
    **Why it matters.** An implementation partner brings a practice lead facing you and consultants facing the customer. Importing the partner with its contacts is what lets you scope the right people's access in the next step.

    Detect implementation partners from the CRM and bring their contacts in.

    **Time:** 30 to 60 min  ·  **Who:** Partner Operations

    <CardGroup cols={2}>
      <Card title="Auto-sync new partners" icon="arrows-rotate" href="/features/partners/partner-management/guides/detect-partners-from-your-crm">
        Detect implementation partners automatically from the CRM.
      </Card>

      <Card title="Manage partner contacts" icon="address-book" href="/features/partners/partner-management/guides/work-a-partner-record">
        Bring in the partner's consultants as contacts.
      </Card>
    </CardGroup>
  </Step>

  <Step title="Hand off the won deal to the implementation partner">
    **Why it matters.** This is the defining setup for implementation. Attaching the implementation partner to the closed deal, and letting them collaborate on the record without a CRM seat, is what turns a forwarded email into a clean handoff with full context. Without it, delivery starts blind and the vendor loses the thread between close and go-live.

    Attribute the implementation partner on the deal and let them collaborate on the shared record.

    **Time:** Half a day  ·  **Who:** Partner Operations, Partner Manager

    <CardGroup cols={2}>
      <Card title="Choose attribution options" icon="sitemap" href="/features/integrations/crm/guides/attribution-options">
        Attach the implementation partner to the won deal.
      </Card>

      <Card title="Collaborate on a shared deal" icon="comments" href="/features/co-selling/shared-pipelines/guides/collaborate-on-a-shared-deal">
        Let consultants work the record without a CRM seat.
      </Card>
    </CardGroup>
  </Step>
</Steps>

## Build the delivery motion

<Steps>
  <Step title="Scope access so consultants see only their accounts">
    **Why it matters.** An implementation partner should see the accounts it delivers on and nothing else. Partner team roles and per-user scoping give consultants self-serve access to their own projects while you keep governance over the rest of the program.

    Create partner team roles, assign them, and limit each user to the accounts they deliver on.

    **Time:** Half a day  ·  **Who:** Partner Operations, with the Partner Manager

    <CardGroup cols={2}>
      <Card title="Create a partner team role" icon="shield-halved" href="/features/access/team-management/guides/set-up-partner-team-roles">
        Define what a consultant can see and do.
      </Card>

      <Card title="Limit a user to their partners" icon="user-lock" href="/features/access/team-management/guides/create-an-internal-role">
        Scope each user to their own accounts.
      </Card>
    </CardGroup>
  </Step>

  <Step title="Track onboarding and go-live on the deal">
    **Why it matters.** Delivery is a checklist with owners and dates: configuration, integration, data migration, sign-off. Tracking those steps on the CRM deal keeps the go-live moving without status meetings, and lets the partner self-serve the next step while the vendor sees progress on the record.

    Build an onboarding path and show delivery tasks on the deal.

    **Time:** 2 to 4 hours  ·  **Who:** Partner Operations

    <CardGroup cols={2}>
      <Card title="Build a progressive onboarding path" icon="person-walking-luggage" href="/features/partners/onboarding/guides/build-a-progressive-onboarding-path">
        Turn a closed deal into a go-live journey.
      </Card>

      <Card title="Create and show partner tasks" icon="list-check" href="/features/partners/tasks/guides/create-and-show-partner-tasks">
        Track onboarding and go-live steps on the record.
      </Card>
    </CardGroup>
  </Step>

  <Step title="Certify consultants before they deliver">
    **Why it matters.** Only qualified consultants should deliver, or quality drifts as the team grows. Certification gates who is authorised, and the status syncs back to the CRM so you can trust who is on a project.

    Build delivery courses, enroll consultants, and issue certificates that sync to the CRM.

    **Time:** Half a day  ·  **Who:** Partner Marketing, Partner Operations

    <CardGroup cols={2}>
      <Card title="Build a course" icon="graduation-cap" href="/features/courses/authoring/guides/build-a-course-manually">
        Author the delivery certification.
      </Card>

      <Card title="Create a certificate" icon="award" href="/features/courses/certificates/guides/create-a-certificate">
        Authorise consultants and sync status to the CRM.
      </Card>
    </CardGroup>
  </Step>

  <Step title="Stand up a minimal delivery experience">
    **Why it matters.** An implementation partner needs one place to see its projects, the runbooks it delivers with, and its certification status. A focused delivery experience keeps consultants self-serve without a CRM seat. Experience building can add far more later.

    Publish a delivery experience with the project pipeline, a governed asset library, and certification.

    **Time:** 2 to 4 hours  ·  **Who:** Partner Operations

    <CardGroup cols={2}>
      <Card title="Build a portal experience" icon="browser" href="/features/portal/experiences/guides/build-and-publish-a-portal-experience">
        Assemble the implementation portal.
      </Card>

      <Card title="Build the asset library" icon="folder-open" href="/features/content/asset-library/guides/build-the-asset-library">
        Give consultants governed solution docs and runbooks.
      </Card>
    </CardGroup>
  </Step>
</Steps>

## Go deeper once you are live

Add these once the handoff, access, and certification are working. Delivery health is the highest-value next step, because go-live quality is what protects renewal and expansion.

<Steps>
  <Step title="Delivery health and reporting">
    **Why it matters.** The whole point of an implementation partner is that the customer succeeds. Partner analytics and dashboards built on the delivery data give you the go-live and health view that ties delivery quality back to renewal.

    **Time:** Half a day  ·  **Who:** Revenue Operations, Partner Manager

    <CardGroup cols={2}>
      <Card title="Read partner analytics" icon="chart-line" href="/features/reporting/partner-analytics/guides/read-a-partners-analytics">
        See delivery and health across accounts.
      </Card>

      <Card title="Show a partner dashboard in the portal" icon="chart-simple" href="/features/reporting/partner-analytics/guides/show-a-partner-dashboard-in-the-portal">
        Give partners their own delivery view.
      </Card>
    </CardGroup>
  </Step>

  <Step title="Account services and influence credit">
    **Why it matters.** Implementation partners earn services revenue and often an influence credit for deals they help source during delivery. Commission plans calculated from the source-of-truth deals keep any incentive auditable and reconciled to the CRM.

    **Time:** Half a day  ·  **Who:** Finance, Partner Operations

    <CardGroup cols={2}>
      <Card title="Create a commission plan" icon="hand-holding-dollar" href="/features/commissions/commission-plans/guides/build-and-launch-a-commission-plan">
        Model services or influence incentives.
      </Card>

      <Card title="Choose a data source" icon="database" href="/features/commissions/commission-plans/guides/build-and-launch-a-commission-plan">
        Calculate from the CRM or billing truth.
      </Card>
    </CardGroup>
  </Step>
</Steps>

## You are live

The implementation partner now takes a clean handoff on the won CRM deal, works only the accounts it delivers on, tracks onboarding and go-live on the record, and stays certified to deliver. You keep visibility from close through go-live, and a customer you already won actually succeeds with the product.

<CardGroup cols={2}>
  <Card title="Run a different motion?" icon="users-between-lines" href="/tracks">
    Pick another partner-type track.
  </Card>

  <Card title="Day in the life" icon="calendar-day" href="/days-in-the-life/implementation">
    See the implementation partner's day end to end.
  </Card>
</CardGroup>