Converge - Plans in AccountsMerchants with multiple accounts need a way to keep subscriptions organized and make changes across all accounts
About

Multiple accounts within one account, we’ll call them ‘subaccounts’ need a logical way to create plans and subscriptions.

We’ll use Schitt’s Creek to help me explain. Let’s say David decides that his business, Rose Apothecary, will start selling a subscription to offer monthly astrological readings. Customers can sign up for this subscription and get their monthly reading, and Rose Apothecary will automatically charge them. Now, let’s say David wants to expand his mercantile shop and starts selling some of their best-selling products out of ROSEBUD Motel (shh Johnny still doesn’t know). He’ll want a way to offer that same subscription to guests coming and going from the hotel, but his business manager, Patrick, would never let him sign customers up from the same account.

To help Patrick out, we developed a new way to create plans and sell subscriptions across various accounts and manage them all from the account manager.

  • ClientElavon
  • RoleLead Product Designer
  • Timeline5 weeks
Accounts... subaccounts... account manager... plans... subscriptions... confused yet?
So was I.
Understanding the merchant's needs was the first step.

Thinking like a merchant helped me to understand what was required from a user experience perspective. I mapped-out flows for each need and discovered that they all actually overlapped in several areas. These provided me with the opportunity to make the merchant’s experience a little more streamlined and a lot less convoluted.

  • Create a plan in the account manager
  • Create a plan in a subaccount
  • Add a subscription from the account manager to a plan
  • Add a subscription from a subaccount to a plan
Whether you have a couple accounts or hundreds, plans should be consistent + easy to consume
Using my trusty whiteboard, I set out to create some reusable components across the account manager and subaccount pages to connect the experience. Using familiar components allows the merchant to recall less steps while also speeding up development timelines.
A complex user flow requires consistent components + subtle messaging to keep the user on track