> ## Documentation Index
> Fetch the complete documentation index at: https://assembly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduce Assembly in manageable groups

> Invite clients in phases, and explain the value clearly before the first invitation goes out.

A phased rollout allows you to learn and make adjustments without creating confusion across your entire client base.

## Recommended rollout sequence

<Steps>
  <Step title="Internal pilot">
    Run the complete experience with your team and test users.
  </Step>

  <Step title="Friendly client pilot">
    Invite a small group representing your most common client types, and ask for candid feedback.
  </Step>

  <Step title="Adjust">
    Correct confusing language, missing content, notification volume, access issues, and process gaps.
  </Step>

  <Step title="Phased launch">
    Invite clients in groups your team can actively support.
  </Step>

  <Step title="Standardize">
    Make the validated experience your default process for net-new clients.
  </Step>
</Steps>

## Explain the value clearly

Before sending an invitation, tell clients:

* What Assembly is
* Why your business is introducing it
* What they will be able to do there
* What will become easier
* What they should do first

Avoid positioning Assembly as simply another tool they must learn. Frame it around the work clients already do with your business: communicating, finding files, completing requests, reviewing next steps, accessing resources, or making payments in one place.

## Give clients one clear first action

Your launch communication should provide one clear first action, such as logging in, reviewing a welcome page, completing a short request, or confirming account information. A specific action helps clients begin building the habit of returning to Assembly.