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

Internal pilot

Run the complete experience with your team and test users.
2

Friendly client pilot

Invite a small group representing your most common client types, and ask for candid feedback.
3

Adjust

Correct confusing language, missing content, notification volume, access issues, and process gaps.
4

Phased launch

Invite clients in groups your team can actively support.
5

Standardize

Make the validated experience your default process for net-new clients.

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