Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better handling for single plans (but offers multiple site tiers) #12

Open
bfintal opened this issue Oct 31, 2020 · 2 comments
Open

Better handling for single plans (but offers multiple site tiers) #12

bfintal opened this issue Oct 31, 2020 · 2 comments

Comments

@bfintal
Copy link

bfintal commented Oct 31, 2020

Here's my current pricing. I only have 1 product plan but available in different number of sites. My plans are annual only.

image

When I try out the new pricing page, I'm getting this:

image

A few things:

  1. Both tiers say "Professional", is there a way to change this?
  2. For annual plans, is there a way to display an annual price instead of the monthly price? (per year instead of per month)
  3. Maybe it's better to add some default colors to the heading and button
  4. Is there a way to note a "Most popular" plan?

For 1 and 2, the pricing can end up like this:

image

@bfintal bfintal changed the title Differences from the old pricing page and new pricing page Better handling for single plans (but offers multiple site tiers) Oct 31, 2020
@vovafeldman
Copy link
Collaborator

@bfintal:

  1. The adjustment of the title is already implemented in this PR, it is still in code review, but it would be great if you can check if it works on your end as expected.
  2. In this design we decided to default to monthly increments, to show smaller numbers, even if you don't sell monthly. It is better from a CRO perspective since it's easier to commit when seeing smaller numbers. Would you still want to show in annual increments? We don't have that flag/option but we can add it if there's a need.
  3. If you can share a mockup of what colors would you like to tweak, that would be helpful.
  4. That's something that we won't be able to support right away since it requires adjustments of the storage, etc.

@vovafeldman
Copy link
Collaborator

1st bullet address here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants