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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Atlassian Docs: Building your presence on Marketplace
Atlassian provides three highlight slots, each with a screenshot, cropped screenshot, and caption, and tells partners to stay visually distinct from Atlassian.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Marketplace, Brand, Conversion is relevant to brand trust, screenshots, positioning and you can run a bounded test with a low 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplace and Brand, using evidence from Atlassian Docs: Building your presence on Marketplace as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose the first market, local proof, partners, and distribution sequence with operator context.