Partner Referral System

Sharing Leads and Profits

Project Context

Project Context

Registered Investment Advisors (RIA's) are a class of financial advisor with a fiduciary duty to provide sound advice. Amplify sought to partner with groups of RIA's as an additional channel to promote Indexed Universal Life (IUL) insurance policies. An RIA could either recommend an IUL policy to clients and let Amplify handle the sale, or share leads who were not a good fit for the rest of the RIA's services. Amplify could handle the details of an IUL sale and share the revenue with the referring partner.

Registered Investment Advisors (RIA's) are a class of financial advisor with a fiduciary duty to provide sound advice. Amplify sought to partner with groups of RIA's as an additional channel to promote Indexed Universal Life (IUL) insurance policies. An RIA could either recommend an IUL policy to clients and let Amplify handle the sale, or share leads who were not a good fit for the rest of the RIA's services. Amplify could handle the details of an IUL sale and share the revenue with the referring partner.

Task & Constraints

Task & Constraints

I was tasked with creating a portal for Registered Investment Advisors to send leads to Amplify. Their time is precious and they are reluctant to send leads to third parties, so the portal needed to be easy to use, and generate trust. Generating trust often involved displaying more relevant information, which required more input, which increased the cognitive load of the interface. Thus, a design challenge emerged.

I was tasked with creating a portal for Registered Investment Advisors to send leads to Amplify. Their time is precious and they are reluctant to send leads to third parties, so the portal needed to be easy to use, and generate trust. Generating trust often involved displaying more relevant information, which required more input, which increased the cognitive load of the interface. Thus, a design challenge emerged.

My Role

My Role

I interviewed RIAs to gain a picture of their needs, tools, and appetite for this type of product. I determined that there was little inherent desire to share leads, and in fact there was marginal opposition. The project was a priority for the company, so I created an interface to overcome as much opposition as possible, offering both a low-speed/high-reward path, and a high-speed/low reward path for sharing leads.

I interviewed RIAs to gain a picture of their needs, tools, and appetite for this type of product. I determined that there was little inherent desire to share leads, and in fact there was marginal opposition. The project was a priority for the company, so I created an interface to overcome as much opposition as possible, offering both a low-speed/high-reward path, and a high-speed/low reward path for sharing leads.

Outcome

Outcome

We launched the portal, allowing Registered Investment Advisors to send qualified leads to Amplify. They were protective of their clients and remained reluctant to share many leads, but this planted the seeds for cultivating long-term partnerships. It also set a precedent for industry partnerships in other areas, particularly white-labeling insurance sales administration software.

We launched the portal, allowing Registered Investment Advisors to send qualified leads to Amplify. They were protective of their clients and remained reluctant to share many leads, but this planted the seeds for cultivating long-term partnerships. It also set a precedent for industry partnerships in other areas, particularly white-labeling insurance sales administration software.

Partner Referral System

Sharing leads and profits

Success

Our partnered Registered Investment Advisors gained lead-sharing and profit-sharing, clients gained coverage, and Amplify set a precedent for itself in white-labeled software.

Success

Our partnered Registered Investment Advisors gained lead-sharing and profit-sharing, clients gained coverage, and Amplify set a precedent for itself in white-labeled software.

Below you will find a detailed breakdown of the RIA Partner Referral project, from beginning to end. The demo to the right shows the full prototype, based on the deliverable.

Research & Discovery

Research & Discovery

I interviewed several 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 with custodians or to or to become a white-labeled partner.

I interviewed several 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 with custodians or to 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 an RIA). 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

The more information an RIA provided about a lead, the higher the chance of a sale, and thus a mutually beneficial profit-share. But they needed to trust us first and see the effort as worthwhile. Some interviewees 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.

The more information an RIA provided about a lead, the higher the chance of a sale, and thus a mutually beneficial profit-share. But they needed to trust us first and see the effort as worthwhile. Some interviewees 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

An RIA would potentially spend time sending leads for a chance at extra income, but not if the process was too time-intensive. Still, the more information Amplify had about incoming leads, the greater the chance of closing the deal. I needed to design an interface that helped RIA's understand the payoff and spend their time efficiently.

An RIA would potentially spend time sending leads for a chance at extra income, but not if the process was too time-intensive. Still, the more information Amplify had about incoming leads, the greater the chance of closing the deal. I needed to design an interface that helped RIA's understand the payoff and spend their time 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.

true partnership

I needed to design an interface that helped RIA's understand the payoff and spend their time efficiently.

true partnership

I needed to design an interface that helped RIA's understand the payoff and spend their time efficiently.

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, 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, so I opted for a page progression instead. Additionally, with the large number of proposed questions, I advocated for a "quick referral" path 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, 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, so I opted for a page progression instead. Additionally, with the large number of proposed questions, I advocated for a "quick referral" path 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, as the number of questions would exceed reasonable capacity for a modal experience.

Updated Draft Based on Stakeholder Input

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

Client-Side: Patterns and Collaboration

Client-Side: Patterns and Collaboration

Client-Side Experience

Client-Side Experience

The workflow needed to include not only RIA's, but the clients they referred to Amplify. Our goals were to build trust with RIA's through a positive client experience, and for clients to complete the application process, leading to a sale. I designed the client experience as a streamlined version of our application, and encouraged engagement by customizing the screen with their name, as well as displaying a partially-filled progress bar.

The workflow needed to include not only RIA's, but the clients they referred to Amplify. Our goals were to build trust with RIA's through a positive client experience, and for clients to complete the application process, leading to a sale. I designed the client experience as a streamlined version of our application, and encouraged engagement by customizing the screen with their name, as well as displaying a partially-filled progress bar.

Partner Transparency

Partner Transparency

To help RIA's trust Amplify with their leads, we provided them with a timeline and a preview of the client experience. It was important for our partner advisors to know that we would contact their leads quickly and that we had a plan for the sales process.

To help RIA's trust Amplify with their leads, we provided them with a timeline and a preview of the client experience. It was important for our partner advisors to know that we would contact their leads quickly and that we had a plan for the sales 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. After clicking through from an email, they are quickly 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. Providing such "inherited progress" encourages users to complete labor-intensive processes.

In order to incentivize clients to follow through with applications, I incorporated both a rapid value-feedback-loop and inherited progress. After clicking through from an email, they are quickly 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. Providing such "inherited progress" encourages users to complete labor-intensive processes.

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 page load.

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.

focus on engagement

I promoted engagement by including the client's name and utilizing inherited progress.

focus on engagement

I promoted engagement by including the client's name and utilizing inherited progress.

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 as 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 all 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 as 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 all 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.