[blog] Polish Upcoming changes to MUI X pricing in 2024#43438
[blog] Polish Upcoming changes to MUI X pricing in 2024#43438oliviertassinari merged 2 commits intomui:masterfrom
Conversation
oliviertassinari
force-pushed
the
pricing-change-edits
branch
from
3205cb2 to
5294cbf
Compare
Netlify deploy previewhttps://deploy-preview-43438--material-ui.netlify.app/ @material-ui/core: parsed: +Infinity% , gzip: +Infinity% Bundle size reportDetails of bundle changes (Toolpad) |
oliviertassinari
force-pushed
the
pricing-change-edits
branch
from
5294cbf to
fb1763c
Compare
oliviertassinari
force-pushed
the
pricing-change-edits
branch
from
fb1763c to
eab5361
Compare
| description: Check out the new pricing updates and how to transition to the new model. | ||
| date: 2024-08-01T08:00:00.000Z | ||
| authors: ['josefreitas'] | ||
| authors: ['josefreitas', 'oliviertassinari'] |
There was a problem hiding this comment.
Showing my face on the blog post to take accountability for them.
| ## Changes to the Pro plan | ||
|
|
||
| ### Current Pricing | ||
| ### Current pricing |
| manualCard: true | ||
| --- | ||
|
|
||
| We're excited to share some important updates to our product offerings and pricing structure. This change reflects the expanded feature set and helps us continue delivering high-quality components to you and your users. |
There was a problem hiding this comment.
Wasn't sure about "excited". It's mostly about pricing and an increase, not sure exactly that users would be excited.
| ### Current Pricing | ||
| ### Current pricing | ||
|
|
||
| Under our current pricing model, if you licensed the Pro plan for 50 developers, you only paid for 10 seats. This concept was introduced when we offered only the Data Grid Pro with a much smaller feature set. |
There was a problem hiding this comment.
Removed the notion of "seat", I believe we banned it in the legal an pricing page.
There was a problem hiding this comment.
Hmm, okay. I guess I missed that discussion.
There was a problem hiding this comment.
Why though? Shouldn't we have separate terms for the license (permission to use the software) and the number of devs that a single license covers?
There was a problem hiding this comment.
regarding banning "seats", I'm not sure if mixing "licenses" in plural with "license" in singular doesn't make it more confusing (and maybe even legally ambiguous)
It's borderline confusing, I agree, to get a project licensed, each developer needs to be licensed. One word for two different concepts. I think we should address this a whole though. Same issue on the EULA, /pricing page, store page, etc.
| ### Pricing for small teams | ||
|
|
||
| The price is the same for customers with 10 developers or fewer. | ||
| Actually, we are making this pricing change to be able to keep the price affordable for small teams. |
There was a problem hiding this comment.
Not sure it's super relevant, but it's pretty much why we do this, to lower price for smaller teams, and increase for larger team who get more value.
|
|
||
| The price is essentially the same for customers with 10 developers or fewer, but you still need a new license key to use the Pro versions of Charts or Tree View. If that's the case, we recommend you contact our sales team and get a discount to renew your license earlier. | ||
| However, if you want to use the new features, you will need a new license key to use the Pro versions of Charts or Tree View. | ||
| You can [contact](https://support.mui.com/hc/en-us/requests/new) our support team to receive a new license key. |
There was a problem hiding this comment.
Added a link to take action.
|
|
||
| ## Changes to the Premium plan | ||
|
|
||
| ### New Pro components |
There was a problem hiding this comment.
In case people missed this.
|
|
||
| However, we want to ensure that our valued early customers continue to enjoy the benefits of an earlier purchase. | ||
| Current customers will still benefit from a 20% renewal discount. | ||
| Current customers will still benefit from a 20% renewal discount (vs. 25% early bird discount before). |
There was a problem hiding this comment.
To help appreciate it's a small increase.
|
|
||
| After two years since the [introduction of our Premium plan](/blog/premium-plan-release/), we've added numerous features and are on the verge of releasing the Pivot mode for the Data Grid. We consider the product mature and battle tested enough and as a result, the early bird discount for the Premium plan finally reaches its end. | ||
| After two years since the [introduction of our Premium plan](/blog/premium-plan-release/), we've added numerous features and are on the verge of releasing the Pivot mode for the Data Grid. | ||
| We consider the product mature and battle-tested enough and as a result, the early bird discount for the Premium plan finally reaches its end. |
There was a problem hiding this comment.
Line break for easier comments
joserodolfofreitas
left a comment
joserodolfofreitas
left a comment
There was a problem hiding this comment.
Thanks for the update!
| ### Current Pricing | ||
| ### Current pricing | ||
|
|
||
| Under our current pricing model, if you licensed the Pro plan for 50 developers, you only paid for 10 seats. This concept was introduced when we offered only the Data Grid Pro with a much smaller feature set. |
There was a problem hiding this comment.
Hmm, okay. I guess I missed that discussion.
Co-authored-by: José Rodolfo Freitas <joserodolfo.freitas@gmail.com> Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com>
Signed-off-by: Olivier Tassinari <olivier.tassinari@gmail.com> Co-authored-by: José Rodolfo Freitas <joserodolfo.freitas@gmail.com>
4 participants
A continuation of #43061. I tweaked a bit the content, trying to anticipate what people could be confused about. I didn't look at the support tickets, there is likely more that we could learn to reflect on this blog post but 🤷♂️ no time. It looks solid otherwise.
Preview: https://deploy-preview-43438--material-ui.netlify.app/blog/mui-x-sep-2024-price-update/
In the email we sent, I wish we kept it shorter and linked the blog post, I think it's better because it helps people share the content with their team (rather than forwarding an email).