RFC-46: App Editions for Marketplace

Hello @SarahAllen, @PremankuChakraborty, @SeanBourke, and thank you for a thorough RFC plus quick turnaround to questions from the Marketplace Partners!

I appreciate we’re all going on a journey here, exploring this space and learning together. With that in mind here are a few of the questions and thoughts that Easy Agile are reflecting on at present:

  • Should our DC subscriptions contain all of the features of the Advanced edition? How would we communicate differences in functionality between DC and the two Editions on Cloud on our website, Marketplace, etc?
  • How does a DC customer migrate to Cloud? Presumably they need to migrate to an Advanced Edition based on the above. For example, we would likely accept the data from DC via JCMA and it would be stored in Cloud, yet if they are on the Standard edition then they would lose access to that functionality and data.
  • How do we enable end users to experience functionality of an Advanced edition when they do not have administrator permissions? Ideally we can surface additional functionality in product and enable end users to request Advanced from their administrator.
  • What would the revenue implications be of an uncapped user tier for the Free edition? How would we model with the information we have today? Our preference at this stage is to continue with the Free Starter Tier to avoid changing too many things at one time, as with lots of changes at once it hinders our ability to ascertain attribution on financial metrics.
  • A Free Edition adds friction to the buying process as it is different from Atlassian’s existing pricing structure. For example, Atlassian uses a Free Starter Tier for their products, so introducing something different requires someone (Atlassian? Marketplace Partners? Solution Partners?) to educate customers, and that all takes time.
  • Is this a precursor to Atlassian offering an uncapped user tier Free edition for their products too?
  • Will we be able to apply different promotion codes to each edition separately, so we can promote the Advanced edition without the promo code being used on Standard?
  • What are the implications of app editions with respect to license decoupling?
  • What does Atlassian’s GA / comms plan look like? Does this get announced at TEAM '25? How does Easy Agile tell a good news story around App Editions?
  • Can we get a commitment to be notified of the GA timeframe and comms at least 2 months in advance so we can prepare our own messaging?
  • Can Atlassian provide a pricing calculator tool to enable us to plan, model and then communicate pricing for each edition at each tier? This would be an exact copy of the pricing tool you will create for setting the pricing ahead of it being live in the admin portal. Without this we will not be able to accurately plan, model and communicate pricing changes and options.
  • How does Easy Agile classify an Evaluator if the Free Starter Tier is phased out? Our financial and product metrics currently look at how many Evaluators become paid Customers. Basically, we need to consider the internal reporting / management accounting ramifications and change those reports to reflect the new reality. Again this is something that makes comparing present vs past periods difficult (like pre vs post Server EOS).
  • How do we direct evaluators to the right Edition for them? Is an end user able to request the Advanced edition? Can we deep link to the Marketplace so an end user can start or request an evaluation of an Advanced edition?

If you have thoughts around any of these we’d love to hear them.

Thanks so much, have a great day,
Nick Muldoon
CEO, Easy Agile

4 Likes