Skip to main content
Before importing data or inviting clients, map the experience you want clients and your internal team to have. Start with the moments that repeat across most client relationships, then account for meaningful differences based on factors such as service, client type, location, account owner, or lifecycle stage.

​
Questions to answer

  • What should every client see immediately after logging in?
  • What is the first action you want a client to take?
  • Which information, requests, resources, files, messages, or next steps are part of the standard client journey?
  • Which parts of the experience vary by client segment, service, location, or internal owner?
  • What should your internal team do before, during, and after a client is invited?
  • Which system will be the source of truth after launch?
  • Which existing communication or workflow channels should Assembly replace?
Best practice: keep the initial experience focused. A smaller number of clearly named apps and one obvious next step will usually create more confidence than an experience containing every possible resource on day one.