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

# Introduction

> How to plan, build, test, and launch your Assembly client experience.

<Note>
  **The goal:** give clients a polished, intuitive place to work with your business, while giving your internal team a consistent, scalable way to manage each relationship.
</Note>

This guide is for teams preparing to introduce their client experience to existing or new clients. It focuses on rollout strategy and readiness — not the individual steps required to configure each feature. For those, follow the links to the relevant configuration articles as you go.

## Your rollout at a glance

| Phase                        | Primary goal                                                                 | You're ready to move forward when…                                                  |
| ---------------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| **1. Plan**                  | Define the client journey and your internal process.                         | You know what clients should see, do, and receive.                                  |
| **2. Build and migrate**     | Prepare the experience, workflows, permissions, and existing client data.    | The experience reflects your brand and operating model, and your data is organized. |
| **3. Test and launch**       | Validate the experience and introduce it gradually.                          | Clients understand why they should use Assembly and what to do first.               |
| **4. Reinforce and improve** | Establish Assembly as the primary place your team and clients work together. | Your team has a repeatable process for existing and net-new clients.                |

Each phase depends on the one before it, and skipping ahead is where most rollouts run into trouble. Importing before your contact fields exist means remapping later, and launching before you test means your clients find the gaps first.

## What's in this guide

<CardGroup cols={2}>
  <Card title="Plan the client journey" icon="map" href="/docs/rolling-out-to-clients/plan-the-client-journey">
    Map the experience you want clients and your team to have before you build anything.
  </Card>

  <Card title="Build and migrate" icon="wrench" href="/docs/rolling-out-to-clients/client-facing-foundation">
    Brand, apps, data structure, imports, workflows, and access.
  </Card>

  <Card title="Test and launch" icon="rocket" href="/docs/rolling-out-to-clients/test-before-launch">
    Validate the full experience, then invite clients in manageable groups.
  </Card>

  <Card title="Reinforce adoption" icon="chart-line" href="/docs/rolling-out-to-clients/reinforce-adoption-and-improve">
    Make Assembly the primary place your team and clients work together.
  </Card>
</CardGroup>