Growth idea action plan
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.
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. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. 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
- Define one narrow startup segment where atlassian app name brand first and product second can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Marketplace and Brand channel.
- Use the evidence from developer.atlassian.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- 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 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: Atlassian Docs: Brand guidelines for Marketplace Partners (developer.atlassian.com)
GrowthDex source hub: Atlassian Docs: Brand guidelines for Marketplace Partners
Last checked: 2026-06-06T04:05:00Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Atlassian partner brand assets stay distinct from Atlassian 2 shared channels · 2 shared stages
- Miro Marketplace name matches the board job 2 shared channels · 2 shared stages
- Help center social share image for article links 2 shared channels · 1 shared stage
- Help center footer columns for next-step navigation 2 shared channels · 1 shared stage
Related GrowthDex essays
- The Atlassian Marketplace page should answer the admin before the demo marketplaces, SEO, conversion
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory