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

# Introduction

You've built an app. You've tested it as a client. The hard part now is getting real clients to use it. This section covers what happens after launch — the practical work of bringing clients into the Portal and getting them to stay.

## Why rollout matters more than build

An app that works perfectly and that no one uses is the same as no app at all. Most adoption failures in client portals trace to one of three places:

* Clients never found out the app exists
* The first session was confusing and they didn't come back
* The friction to use the app was higher than the friction to email you

Rollout is how you avoid all three.

## The pre-rollout checklist (recap)

If you skipped this earlier, do it now. From [Launching apps](/docs/building-new-apps/launching-apps):

<Check>
  You've used the app as both an internal user and a test client
</Check>

<Check>
  Empty states look intentional
</Check>

<Check>
  Notifications fire correctly for both audiences
</Check>

<Check>
  Visibility is set right — for internal users and for clients
</Check>

<Check>
  External integrations are connected and tested
</Check>

## What's in this section

<CardGroup cols={2}>
  <Card title="Inviting clients" icon="user-plus" href="/docs/rolling-out-to-clients/inviting-clients">
    The different invite paths and when to use each.
  </Card>

  <Card title="The client's first session" icon="door-open" href="/docs/rolling-out-to-clients/the-clients-first-session">
    What new clients see when they sign in, and how to set them up for success.
  </Card>

  <Card title="Driving adoption" icon="chart-line" href="/docs/rolling-out-to-clients/driving-adoption">
    What works after the first week, and how to learn what's not landing.
  </Card>
</CardGroup>