Atlassian’s Rise: Lessons from Australia’s Software Giant

Atlassian is routinely called Australia’s most successful software company, and the description is defensible. Two people, a small debt and a product idea turned into a business that now sells to software teams worldwide. What makes the story worth reading is the handful of decisions under the scale, because some of those can be copied and some genuinely cannot.

The founding, as the founders tell it

Mike Cannon-Brookes and Scott Farquhar started the company in Sydney in 2002, two university friends with no customers and no outside money. The story they tell about the start involves a ten thousand dollar credit card debt, and the number is less important than what it bought: time to sell something before answering to investors. The company ran without venture funding for its first eight years.

Its first product was also its most ordinary-looking: Jira tracked bugs for software teams. That was a small, unglamorous and extremely common job, and the company sold into it directly, online, at prices a team could approve without a procurement department. Confluence followed, for the documents and wikis that teams keep. The strategy, in hindsight, was to own the daily tools of software work rather than anything that could be called a platform.

Sell directly, to the person with the problem

For most of its first decade, Atlassian did not run an enterprise sales army. It published prices, sold online, and let the tool spread from team to team. That is a harder model than it sounds, because it forces the product to explain itself and the price to survive daylight. It also means the growth is made of people who chose the software rather than people who were sold it, which is a more durable kind of base.

Once the base existed, buying made sense. Bitbucket and Trello were absorbed into the range, each one a tool sitting near the same daily work. The acquisitions did not create a new strategy. They thickened the old one.

The culture was a decision, not a vibe

Atlassian states its culture in writing, including the famous instruction to be an open company with no bullshit. The famous part is the wording. The useful part is that the company has kept spending on the practices that make the wording true, like the internal days where staff stop their normal work and ship an idea they chose themselves.

Culture at scale is what an organisation keeps doing when it would be easier to stop. Hiring practices, how decisions get published, and what founders visibly reward all show up in the product eventually. Atlassian’s version of this has been stable enough to be a recruiting asset, which is the commercial test most culture statements fail.

Sydney was a fact, not an excuse

Sydney remains the company’s headquarters, and it built a global software business from there in an era when the conventional advice said not to try. Being remote from Silicon Valley changed the hiring pool and the investor list. It clearly did not cap the outcome. Founders elsewhere read the story as permission, and the honest reading is narrower: the location removed some options and added others, and the company used what it had.

Australian software now covers more ground than workplace tools. The same years that produced Atlassian also produced a wave of health technology, and what mental health apps and wearables can and cannot do is its own question, judged by different rules than a work tool is.

The giving, structured like the business

Atlassian was among the founding companies behind Pledge 1%, a program that asks companies to commit one per cent of equity, profit, product and employee time to their communities. The structure has framed the company’s giving since. The detail worth noticing as a business lesson is that the commitment is engineered rather than charitable in the moment: it is written into the company’s design, so it survives a bad year and a change of management.

What other founders can take

• Solve a common, unglamorous problem. Bug tracking was nobody’s dream market. It was everybody’s daily chore, which is better.
• Sell to the person who feels the pain. A price a team can approve removes an entire layer of friction from growth.
• Let one product earn the next. Confluence, Bitbucket and Trello each arrived to a base that was already there, rather than to a cold market.
• Write the culture down and keep funding it. A value that survives the busy quarter is the only kind that counts.
• Build from where you actually live. Distance from the usual capital is a cost. It is not a ceiling.

Copy the method, not the myth

The parts of the story that cannot be copied are the parts most often quoted: two founders with unusual endurance, timing that placed the company in front of a once-in-a-generation shift to internet-delivered work tools, and a list of decisions that look obvious only after they worked. The parts that can be copied are duller and more useful: pick a real problem, sell directly to the person holding it, reinvest in the product before the market forces you to, and keep the promises you wrote down. Carry that out of the story, and leave the swagger on the shelf.

Sources: Atlassian’s company history and investor relations pages (atlassian.com); the Nasdaq listing record for the company’s 2015 float; Pledge 1% program information (pledge1percent.org).