# Atlassian Marketplace single-listing editions upsell

> Use Atlassian app editions to show Standard and Advanced packaging under one listing so upsell happens on the same buying surface instead of on a separate pricing detour.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/atlassian-marketplace-single-listing-editions-upsell/
- Source: [developer.atlassian.com](https://developer.atlassian.com/platform/marketplace/listing-app-editions/)
- GrowthDex source hub: [Atlassian Docs: Listing app editions](/sources/atlassian-docs-listing-app-editions-developer-atlassian-com/)
- Last checked: 2026-05-29
- Rarity: epic
- Budget: medium
- Channels: Marketplaces, Pricing, Conversion
- Stages: upsell, enterprise, packaging, cloud apps


## Why this can grow

A lot of add-on vendors split packaging logic across landing pages, sales calls, and docs, which makes the upgrade story harder to trust. Atlassian's editions model keeps the ladder in one place. The same listing can show multiple options, and buyers across all parent-plan segments can still choose the app edition that fits them. That means the listing can do more of the selling job on its own. A buyer on a free Jira plan can still see what the advanced app tier looks like without waiting for a rep to explain the route.

## 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 marketplace single-listing editions upsell can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces 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 editions docs say you can display multiple packaging options for a cloud app within a single Marketplace listing, and customers across all segments can purchase Marketplace app editions regardless of their parent Atlassian app edition.

## Adjacent tactics in the same lane

- [Atlassian app editions in one listing for segmented pricing](/growth-ideas/atlassian-app-editions-in-one-listing-for-segmented-pricing/) - same source, 1 shared channel, 3 shared stages
- [Atlassian Marketplace advanced service tier packaging](/growth-ideas/atlassian-marketplace-advanced-service-tier-packaging/) - same source, 1 shared channel, 1 shared stage
- [G2 Profile pricing section before demand capture](/growth-ideas/g2-profile-pricing-section-before-demand-capture/) - 3 shared channels
- [Shopify pricing details own every charge and free-plan flag](/growth-ideas/shopify-pricing-details-own-every-charge-and-free-plan-flag/) - 3 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Atlassian Marketplace page should close the diligence gap](/blog/the-atlassian-marketplace-page-should-close-the-diligence-gap/) - marketplaces, brand trust, pricing

## Advisory

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