Skip to main content
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:
You’ve used the app as both an internal user and a test client
Empty states look intentional
Notifications fire correctly for both audiences
Visibility is set right — for internal users and for clients
External integrations are connected and tested

​
What’s in this section

Inviting clients

The different invite paths and when to use each.

The client's first session

What new clients see when they sign in, and how to set them up for success.

Driving adoption

What works after the first week, and how to learn what’s not landing.