AdvicePay
The only billing and payment solution designed for fee-for-service financial planning.
ABOUT
As the only Product Designer at AdvicePay, I was responsible for the entire UX process, from early-stage user interviews to high-fidelity mockups. I worked directly with all types of users, including Enterprise administrators and solo Financial Advisors. Through interviews, user-testing and beta-testing, I was able to provide valuable feedback and recommendations to the team on some of our new features and integrations.
The Deliverables feature I worked on at AdvicePay allows users of the platform to create, track and submit Financial Plans, which could otherwise slip through the cracks and lose the firm money and credibility. This feature was specifically designed for Enterprise use. See below for a detailed outline of my work on this project, as well as a quick redesign of the Pricing page of advicepay.com
Deliverables
Research
“Deliverables” is the term that many Financial Planners and their Home Offices (administrators) use to refer to any financial plan or another service that is to be handed off to a client within a certain amount of time in exchange for a fee. This is a feature many of our Enterprise clients had been requesting, and I wanted to make sure that I fully understood the pain points of their existing process, and what would be needed to solve their problems.
I started by asking pretty broad questions, like:
What does your current deliverables process look like?
How many deliverables are due each year?
Who is responsible for tracking deliverables?
What software do you use for each piece of the process and do they integrate?
It became clear that most Enterprises have a team of 2-3 people responsible for tracking and approving thousands of deliverables a year, and most were using a combination of Excel, email, snail-mail, and software used to create financial plans. Many Enterprises knew there were dozens of overdue financial plans that their advisors hadn’t completed, but didn’t have the capacity to follow up with the advisor about it.
Determining the MVP
I worked with my PM and went through several design revisions to determine what should be included in the MVP. At first, it looked something like this:
Home Office determines when an open deliverable will be created: upon invoice paid by client or agreement signed by client
Open deliverable is automatically created and is assigned to the correct Advisor
Advisor is alerted via email when deliverable is near overdue or overdue
Home Office can track Open, Overdue, and Completed deliverables
Home Office can review, accept or decline the deliverable once it is submitted
A new deliverable is automatically opened and assigned to Advisor if the client is on a subscription
After scoping with the dev team, a lot of back and forth with my PM, and some more user interviews and testing, we cut the MVP down to the following:
Home Office and Advisors can track Open, Overdue, and Complete deliverables
Home Office can create deliverables for Advisors
Email notifications are sent to remind Home Office and Advisors when deliverables are overdue or almost overdue
Final Designs
Here are some screens of the final designs for the MVP of Deliverables!
The Home Office view of the Deliverables page.
Filters for Home Office
Settings for Home Office, to determine the due date for the Deliverable.
Home Office creating a Deliverable for an Advisor.
Advisor view for submitting a deliverable.
Successful completion of a Deliverable for an Advisor.
PRICING PAGE REDESIGN
The very last project I worked on at AdvicePay, and the content was given to me by our marketing team in the order it should appear. Not a ton of research on my end went into this, but it was fun!
Here is the existing pricing page:
A couple of wireframes and the final design!