Make it really clear how users can buy GitLab from the group billing page
Problem
When you visit the group billing page whilst on the Free plan, there is nowhere to purchase GitLab. You can click the Free
link but that's not a clear pathway to purchase. You can only start a trial. This causes users to either have to visit the user settings billing page or find the pricing page on about.gitlab.com (or they might already know to go to the portal, but that's doubtful).
I've created a separate issue to discuss increasing visibility to buy GitLab on the homepage.
We should make it really easy for people to buy GitLab via this page and reach the checkout page in very few clicks.
Original Proposal
Could we add a green CTA that simply says Buy Now
that takes them to the pricing page either next to or instead of the Start your Free Trial
CTA? I'm not sure what's the best user experience here.
Design Proposal
Upgrade (No Current Plan) | Upgrade (Active Current Plan) |
---|---|
**Upgrade (No Current Plan)**
We should create a 3 column Card component layout to showcase Upgrade opportunities, displaying short, informative and easily digestible information. The Card would contain three top features, with a link to learn more about each Plan. This seems like a reasonable bitesize amount of information for our users to make an informed choice.
**Upgrade (Active Current Plan)**
If a user is already on a Plan (i.e. Bronze) we should display the "Active" Plan with a disabled styling, including a note next to the Title with the text Current Plan
. We should also disable the Upgrade Button.
URLs
-
All of the "See All {Plan} features" links = https://about.gitlab.com/pricing/#gitlab-com
-
Since downgrading is currently a manual process via support I've also included some text "Please contact Customer Support if you would like to downgrade your Plan." to inform users of this process.
"Customer Support" link =https://support.gitlab.com
Design Specs
Result
Less confusion for our users, an improved user experience and a potential increase in GitLab.com subscription revenue.
Next steps (if any)
-
@tipyn to investigate data behind the potential improvements -
@timnoah to review and add a design MVC - We could consider this as a first stepping stone to making the portal invisible to users. -
@jameslopez to add a weight -
@dennis for your visibility and input (although, this may mostly be frontend - if you could confirm that'd be great)