Atlassian app name brand first and product second
Name the Marketplace app with your brand first and the Atlassian product second, so the listing reads like a third-party product instead of an in-house Atlassian feature.
Why this can grow a startup
A lot of Marketplace traffic starts with a buyer comparing a short list under time pressure. The name has to do two jobs at once: say what the product is and avoid implying Atlassian made it. Atlassian's own naming rules push partners away from host-product-first naming because that creates attribution confusion. A clearer brand-first name makes the listing easier to trust, easier to remember, and less likely to stall in review.
Source guidance
Atlassian's brand guidelines allow names like 'Bug Fixer for Jira' and reject names like 'Jira Bug Fixer' because Atlassian app names should not appear at the beginning.
Source-reported evidence
Source: Atlassian Docs: Brand guidelines for Marketplace Partners
Marketplace app names must be 60 characters or less, and host-product-first examples like 'Jira Bug Fixer' are listed as not allowed.
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, SEO is relevant to naming, brand trust, review readiness and you can run a bounded test with a free 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: Brand guidelines for Marketplace Partners as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the 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
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.