# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/atlassian-free-listing-external-account-and-paid-dependency-clear/
- Source: [developer.atlassian.com](https://developer.atlassian.com/platform/marketplace/app-approval-guidelines/)
- GrowthDex source hub: [Atlassian Docs: App approval guidelines](/sources/atlassian-docs-app-approval-guidelines-developer-atlassian-com/)
- Last checked: 2026-06-06T04:05:00Z
- Rarity: rare
- Budget: free
- Channels: Marketplace, Pricing, Conversion
- Stages: pricing clarity, qualification, review readiness, setup friction


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where atlassian free listing external account and paid dependency clear can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplace and Pricing channel.
3. Use the evidence from developer.atlassian.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed 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.

## Adjacent tactics in the same lane

- [Webflow Marketplace pricing and policies before review loop](/growth-ideas/webflow-marketplace-pricing-and-policies-before-review-loop/) - 2 shared channels, 1 shared stage
- [Shopify pricing details own every charge and free-plan flag](/growth-ideas/shopify-pricing-details-own-every-charge-and-free-plan-flag/) - 2 shared channels, 1 shared stage
- [Miro Marketplace pricing copy stays synced with the listing](/growth-ideas/miro-marketplace-pricing-copy-stays-synced-with-the-listing/) - 3 shared channels
- [HubSpot marketplace pricing only for integration-enabled plans](/growth-ideas/hubspot-marketplace-pricing-only-for-integration-enabled-plans/) - 1 shared channel, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Atlassian Marketplace page should answer the admin before the demo](/blog/the-atlassian-marketplace-page-should-answer-the-admin-before-the-demo/) - marketplaces, SEO, conversion

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.