Atlassian free listing external account and paid dependency clear
If a free listing still needs a separate paid account, make that dependency obvious on the page instead of forcing the buyer to discover it during setup.
Why this can grow a startup
A 'free' label attracts the wrong click when the useful part of the product is locked behind another subscription. Atlassian's approval rules are direct here: the app should provide some useful function as is, and any third-party account or payment dependency must be clear. That kind of clarity does not just protect approval. It keeps the install intent clean by filtering out buyers who are not actually eligible.
Company example
Atlassian's approval guidelines say a free listing must make any separate third-party account and any related payments or licensing clear, and in many cases such apps should be paid-via-vendor instead.
Source and metric
Source: Atlassian Docs: App approval guidelines
Atlassian explicitly recommends paid-via-vendor for many apps that require a separate paid third-party account.
When to use it
Use this when Marketplace, Pricing, Conversion is relevant to pricing clarity, qualification, review readiness and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Atlassian Docs: App approval guidelines and identify what is directly supported.
- Choose one channel context: Marketplace, Pricing, Conversion.
- Define the test around Atlassian explicitly recommends paid-via-vendor for many apps that require a separate paid third-party account..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.