Atlassian · Go-to-market · Senior · 45 to 60 minutes

How should Jira enter the market?

Atlassian builds software that helps teams plan, track, and collaborate on work, including the issue tracking product Jira. Answer this product management case and get it graded line by line against a weighted rubric.

GTM strategy
Segmentation
Prioritization
Channel design
Metric design

The situation

It is 2002. Mike Cannon-Brooks and Scott Farquhar have turned an internal support tool into the first version of Jira, a software product for tracking issues and coordinating work. They are based in Australia, far from major tech hubs, and they do not have venture funding or an established sales team. Their earlier support business proved hard to scale, so this product launch needs to create a repeatable path to revenue, not just a few custom deals. The founders are asking you, their first product leader, to recommend how Jira should enter the market. They need clarity on who to target first, how those users should discover and buy the product, and what kind of go-to-market motion the company can actually sustain with limited cash and headcount. Assume Atlassian has enough budget for only a small number of hires over the next two quarters. The hard part is balancing short term survival against building a durable growth engine that could later expand inside larger companies.

What to produce

A 3 page go-to-market strategy memo for Jira.

Your answer must

Recommend a specific initial customer segment and explain why it is the best beachhead, compared with at least one credible alternative.
Describe the acquisition and buying motion for the next 12 months, including the role of self-serve, sales, support, and any content or community tactics.
Propose pricing and packaging principles that fit an early product and Atlassian's resource constraints.
Define a metric set that covers acquisition, activation, adoption, expansion, and go-to-market efficiency, and identify the most important leading indicator.
Lay out a phased plan with major risks and second order effects, including impact on support load, product priorities, and future enterprise expansion.

Constraints

Atlassian cannot assume a large field sales team or significant outside capital in the near term.
The product is early, so the plan must work with low brand awareness and limited feature breadth.
Do not rely on acquisitions, marketplace effects, or brand strength that Atlassian does not yet have.

Format

Use sections titled beachhead customer, reach and buy motion, pricing and packaging, scale plan, metrics, and risks.

How Atlassian actually played it

Covers how Atlassian began, its low-touch sales approach, and its go-to-market playbook.

Skip heavy sales early
Find a specific who
Build a growth machine around adoption

Built from How Atlassian Grows by Jaryd Hermann (How They Grow).