# Atlassian Marketplace advanced service tier packaging

> Package heavier support and service promises into the Advanced edition so high-touch buyers can pay for the response model they actually need.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/atlassian-marketplace-advanced-service-tier-packaging/
- 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: rare
- Budget: medium
- Channels: Marketplaces, Sales, Retention
- Stages: service design, enterprise, support, pricing
- Key metric: Atlassian explicitly uses 24x5 vs 24x7 support, dedicated CSM access, and storage limits as edition examples.

## Why this can grow

Founders often hide service differentiation in sales decks because they assume the marketplace page should only talk about features. Atlassian suggests a cleaner move. Editions can be separated by services such as support coverage, storage, or customer success access. That turns support from a hidden concession into a deliberate product choice. The buyer who needs 24x7 help gets a clear commercial lane, and the standard buyer does not have to subsidize a service model they will never use.

## 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 advanced service tier packaging can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Sales 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 guide suggests differentiating Standard and Advanced editions by services such as 24x5 versus 24x7 support, limited versus unlimited storage, or a dedicated customer success manager.

## Adjacent tactics in the same lane

- [Atlassian Marketplace single-listing editions upsell](/growth-ideas/atlassian-marketplace-single-listing-editions-upsell/) - same source, 1 shared channel, 1 shared stage
- [Atlassian app editions in one listing for segmented pricing](/growth-ideas/atlassian-app-editions-in-one-listing-for-segmented-pricing/) - same source, 2 shared stages
- [Atlassian Marketplace privacy and support completeness](/growth-ideas/atlassian-marketplace-privacy-and-support-completeness/) - 2 shared channels, 1 shared stage
- [GitHub Marketplace plan retire with same-name replacement](/growth-ideas/github-marketplace-plan-retire-with-same-name-replacement/) - 2 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.