RIA Client Referral

RIA Client Referral

Goal: Design a robust B2B sales administration portal to manage arbitrarily large life insurance sales teams.

User Requirements

Create and edit Roles (e.g. Business Development Specialist, Sales Agent, Case Manager, etc.)

Add and remove Users, both internal and external to the company (in the case of contractors)

Create and edit Group configurations

Late Requirement: Integrate with third party systems like Hubspot

Business Requirements

Must be an attractive product for brokerages who might purchase it

Must be absolutely future-proof, affording feature expansion in almost every capacity

Context

Amplify explored the possibility of licensing their internal Agent Portal software as a white-labeled product.

Until this point, sales administration within the company had taken place using ad-hoc third party software.

To prepare for external licensing, they sought to unify the Agent Portal with strong native administration capabilities.

Project Requirements

empty road
empty road
empty road

Sneak Peak

Sneak Peak

A snippet of an engineering sanity check here displays the core flow, affording Registered Financial Advisors the ability to qualify and send leads to Amplify. This generates additional income for the advisor, with more information leading to greater likelihood of closing a deal.

A snippet of an engineering sanity check here displays the core flow, affording Registered Financial Advisors the ability to qualify and send leads to Amplify. This generates additional income for the advisor, with more information leading to greater likelihood of closing a deal.

Research & Discovery

Research & Discovery

I interviewed 5 RIAs to understand their needs, tools, and appetite for a lead-share feature like this. Additionally, I was tasked with researching the field of "custodians" (effectively brokerages who work with RIA's to sell policies), to understand who the major players were and what features they offered. This project had the potential to compete directly or to become a white-labeled partner.

I interviewed 5 RIAs to understand their needs, tools, and appetite for a lead-share feature like this. Additionally, I was tasked with researching the field of "custodians" (effectively brokerages who work with RIA's to sell policies), to understand who the major players were and what features they offered. This project had the potential to compete directly or to become a white-labeled partner.

User Journey

Incorporating all of our research, the PMs and I built a user journey map, seen from the perspective of the user (in this case, RIA's). The first section was ultimately delegated to Marketing. The rest of the scope was massive, and progressively broken into smaller pieces. The first phase tackled sections 2-4 ("Begin with Amplify" through "Administer Clients") and for this porfolio I am focusing on "Create Applications".

Goals and Incentives

Goals and Incentives

Low Trust

Low Trust

Some interviewee's expressed unwillingness to recommend IUL as a product. In order to positively influence these potential partners, the interface needed to be transparent, clearly displaying the policy details and any benefits to their clients. Above all, Amplify needed to preserve their reputation as advisors.

Some interviewee's expressed unwillingness to recommend IUL as a product. In order to positively influence these potential partners, the interface needed to be transparent, clearly displaying the policy details and any benefits to their clients. Above all, Amplify needed to preserve their reputation as advisors.

Low Time

Low Time

RIA would potentially spend time sending leads for a chance at extra income, but not if if took much time. Still, the more information Amplify had about incoming leads, the greater the chance of closing the deal. I needed to design the interface in a way that helped RIA's to feel like their time was being spent efficiently.

RIA would potentially spend time sending leads for a chance at extra income, but not if if took much time. Still, the more information Amplify had about incoming leads, the greater the chance of closing the deal. I needed to design the interface in a way that helped RIA's to feel like their time was being spent efficiently.

Concentric Target Model

Illustrates that higher chances of obtaining value also require higher workloads as input.

Linear Model

Illustrates the progressive nature of information and thus lead types, and helps classify categories of lead.

RIA Side: Patterns & Collaboration

Patterns &
Cross-Team Collaboration

RIA Side: Patterns & Collaboration

The goal here was to encourage RIA's to send as many leads as possible, with as much information about each lead as possible. There was a limit to how much we could expect, but the interface could help. We needed to walk a line between asking for information versus making the process feel swift and efficient.

The goal here was to encourage RIA's to send as many leads as possible, with as much information about each lead as possible. There was a limit to how much we could expect, but the interface could help. We needed to walk a line between asking for information versus making the process feel swift and efficient.

Pattern: Modal

Pattern: Modal

Initially I explored modals as a means of making the interface feel "quick". Modals are associated with temporary activity, so placing the questionnaire within one could lead an RIA to feel that it was more lightweight.

Initially I explored modals as a means of making the interface feel "quick". Modals are associated with temporary activity, so placing the questionnaire within one could lead an RIA to feel that it was more lightweight.

Pattern: Page Progression

Pattern: Page Progression

After getting feedback from stakeholders in leadership (shown below), it became apparent that we were going to ask for as much information as possible. A modal would feel too heavy if a user needed to scroll to use it. I opted for a page progression instead. Additionally, with the large number of questions stakeholders were asking for, I advocated for a "quick referral" to be included in the design, which would include a subset of questions for those in a hurry.

After getting feedback from stakeholders in leadership (shown below), it became apparent that we were going to ask for as much information as possible. A modal would feel too heavy if a user needed to scroll to use it. I opted for a page progression instead. Additionally, with the large number of questions stakeholders were asking for, I advocated for a "quick referral" to be included in the design, which would include a subset of questions for those in a hurry.

User Journey Becomes Workflow

Here I have used the User Journey Map to begin building a workflow for the RIA and the referred client, including prototype connectors.

Draft of Combination Coverage

Notes for engineering are working to catch edge cases and provide clear specs.

Draft of IUL Coverage

Does not include the "Term" portion, slightly simplifying a complex page.

Early Draft: Modal

I explored using a modal, but decided to progress with pages instead (explained below).


Updated Draft Based on Stakeholder Input

After additional communication, I incorporated Hanna's input to create a more comprehensive questionnaire. The benefits section would have its own dedicated page.

CEO Stakeholder Input

I incorporated stakeholder input throughout the process, from our CEO (shown here), VP of Product, PMs, and Engineers.

Client Side: Patterns and Collaboration

Client Side: Patterns and Collaboration

RIAs: Transparency Please

RIAs: Transparency Please

In order for RIA's to trust Amplify with their leads, they needed to know that we would provide the clients with a positive experience. In order to facilitate transparency, we provided them with a timeline and a preview of the client experience.

In order for RIA's to trust Amplify with their leads, they needed to know that we would provide the clients with a positive experience. In order to facilitate transparency, we provided them with a timeline and a preview of the client experience.

Client-Side Experience

Client-Side Experience

The workflow needed to include not only RIA's, but the clients whom they referred to Amplify. Our goals were: to build trust with RIA's through a positive client experience, and for as many referred clients as possible to complete the application process.

The workflow needed to include not only RIA's, but the clients whom they referred to Amplify. Our goals were: to build trust with RIA's through a positive client experience, and for as many referred clients as possible to complete the application process.

Patterns: Rapid Value and Inherited Progress

Patterns: Rapid Value and Inherited Progress

In order to incentivize clients to follow through with applications, I incorporated both a rapid value feedback loop and inherited progress. Rapid Value: After clicking through from email, they are immediately presented with value in the form of policy details. After completing a few additional questions, they receive a quote. Additionally, the CTA reads "Complete My Application" (rather than "Begin"), and the progress indicator displays "20% complete" from the very start.

In order to incentivize clients to follow through with applications, I incorporated both a rapid value feedback loop and inherited progress. Rapid Value: After clicking through from email, they are immediately presented with value in the form of policy details. After completing a few additional questions, they receive a quote. Additionally, the CTA reads "Complete My Application" (rather than "Begin"), and the progress indicator displays "20% complete" from the very start.

Draft A: RIA Preview of Client Experience

To build trust, we wanted the entire process to be transparent.

Draft B: RIA Preview of Client Experience

Stakeholders asked for more of the client experience timeline.

Client Side: Initial Clickthrough

Displaying both immediate value and inherited progress.

Client Side: Completing Application

Progress indicator fills to 20% on first click.

Engineering Sanity Check

I created this Figma prototype as a way to help engineers understand one of the primary flows, and to check for blind spots early in the process.

Delivery & Meta

Delivery & Meta

Delivery

Delivery

Deliverable Format: Figma link.


Structure: I designed the interface largely using the Style and Component library that I created and maintained for the Product team (pulling in many contributions from others), which is based on the atomic framework. Engineering maintains a copy on their end.

Deliverable Format: Figma link.

Structure: I designed the interface largely using the Style and Component library that I created and maintained for the Product team (pulling in many contributions from others), which is based on the atomic framework. Engineering maintains a copy on their end.

Specs and Instructions

Specs and Instructions

Reducing engineering lift and helping with clean execution means not just designing with modularity, but leaving clear instructions. I left annotations throughout the deliverable to assist engineers in execution. The metric of success here is to have as few questions as possible after delivery. Where necessary, I mocked up animations to demo behavior.

Examples:

  • In the "education" section of the project (scope not covered above), I included a micro-interaction to provide feedback on copying an article.

  • In the "client administration" section of the project (scope not covered above), I included detailed dropdowns and overlays for speedy execution.

Reducing engineering lift and helping with clean execution means not just designing with modularity, but leaving clear instructions. I left annotations throughout the deliverable to assist engineers in execution. The metric of success here is to have as few questions as possible after delivery. Where necessary, I mocked up animations to demo behavior.

Examples:

  • In the "education" section of the project (scope not covered above), I included a micro-interaction to provide feedback on copying an article.

  • In the "client administration" section of the project (scope not covered above), I included detailed dropdowns and overlays for speedy execution.

Microinteraction

Takes into account the feedback experience in copying an article link.

Complete Specs

Providing engineers with complete specs increases efficiency.

Final Outcome

Final Outcome

The end result allows RIA's to partner with Amplify, sharing leads and generating extra (largely passive) profits. The scope of this project started out massive and was reduced to merely enormous. I am proud of how user research led to a User Journey Map, which led directly to workflows in the interface. We provided our partners with an intuitive interface that nevertheless displays complex data. And it provides referred clients with a clear and easy path to apply for life insurance.

The end result allows RIA's to partner with Amplify, sharing leads and generating extra (largely passive) profits. The scope of this project started out massive and was reduced to merely enormous. I am proud of how user research led to a User Journey Map, which led directly to workflows in the interface. We provided our partners with an intuitive interface that nevertheless displays complex data. And it provides referred clients with a clear and easy path to apply for life insurance.

Figma Deliverable

This is a section of the final deliverable, covering the complex "Quoting" functionality.

Future Opportunities

Future Opportunities

Odds and Predictions

Odds and Predictions

It would have been interesting to include live-updating "odds of closing a deal" and "predicted income over time" metrics that increased as an RIA provided higher amounts of information about each lead.

It would have been interesting to include live-updating "odds of closing a deal" and "predicted income over time" metrics that increased as an RIA provided higher amounts of information about each lead.

Client Path Updates

Client Path Updates

I liked the aesthetic of the client path in this project, and I would consider A/B testing it in the main walkthrough to see if it increased conversion.

I liked the aesthetic of the client path in this project, and I would consider A/B testing it in the main walkthrough to see if it increased conversion.