# Atlassian partner brand assets stay distinct from Atlassian

> Keep your logo, colors, screenshots, and captions unmistakably yours, while using Marketplace media slots to explain the workflow instead of imitating Atlassian's brand.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/atlassian-partner-brand-assets-stay-distinct-from-atlassian/
- Source: [developer.atlassian.com](https://developer.atlassian.com/platform/marketplace/building-your-presence-on-marketplace/)
- GrowthDex source hub: [Atlassian Docs: Building your presence on Marketplace](/sources/atlassian-docs-building-your-presence-on-marketplace-developer-atlassian/)
- Last checked: 2026-06-06T04:05:00Z
- Rarity: rare
- Budget: low
- Channels: Marketplace, Brand, Conversion
- Stages: brand trust, screenshots, positioning, creative


## Why this can grow

Marketplace buyers use visual shortcuts. If the page looks like a blurred copy of Atlassian, it raises attribution and trust questions instead of answering them. Atlassian tells partners to look and sound like their own company, avoid unsubstantiated claims, and use screenshots plus captions to explain the app. The growth move is to treat every media slot as a teaching surface, not as decorative brand camouflage.

## 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 partner brand assets stay distinct from atlassian can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplace and Brand 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 brand guidelines tell partners to make it clear they are third-party vendors, while the Marketplace presence guide requires highlight screenshots, cropped screenshots, and screenshot captions that explain what the buyer is seeing.

## Adjacent tactics in the same lane

- [Miro Marketplace visuals teach the workflow not the logo](/growth-ideas/miro-marketplace-visuals-teach-the-workflow-not-the-logo/) - 3 shared channels, 2 shared stages
- [Atlassian app name brand first and product second](/growth-ideas/atlassian-app-name-brand-first-and-product-second/) - 2 shared channels, 2 shared stages
- [Framer template gallery proof images before submit](/growth-ideas/framer-template-gallery-proof-images-before-submit/) - 2 shared channels, 1 shared stage
- [Miro Marketplace profile as second proof surface](/growth-ideas/miro-marketplace-profile-as-second-proof-surface/) - 2 shared channels, 1 shared stage

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