Atlassian 2015: Building a Software Giant With No Sales Team
Situation
It is 2015. Atlassian, founded in Sydney in 2002 by Mike Cannon-Brookes and Scott Farquhar (famously bootstrapped on credit-card debt), makes software development and collaboration tools — Jira (issue tracking), Confluence (wikis/docs), and Bitbucket (code hosting). The products are used by hundreds of thousands of teams around the world.
What makes Atlassian remarkable isn't the products — it's how they're sold, which is to say barely sold at all. Enterprise software's iron law is "big software is sold, not bought": you need a large, expensive, quota-carrying sales force, field engineers, and a long high-touch cycle, especially to land big accounts. That sales machine routinely consumes half or more of revenue.
Atlassian inverted the model:
- Low, transparent prices published on the website.
- Self-serve purchase — a developer can download, try, and buy with a credit card, no sales call.
- Bottom-up adoption — one team adopts Jira, likes it, and it spreads team-to-team inside the company until IT eventually standardises on it.
- No traditional sales reps. The money that competitors spend on sales, Atlassian spends on R&D and the product.
Now the founders are preparing to list on NASDAQ. The entire investment thesis rests on a heretical claim: that you can build — and keep scaling — a global enterprise-software company without the sales force everyone insists is mandatory.
The decision moment
It is 2015, approaching the IPO. The founders must decide how to scale from here:
- Stay the course — double down on product-led growth. Keep prices low and self-serve, pour the sales savings into R&D and acquisitions, and let word-of-mouth and bottom-up adoption keep compounding. Bet that the model that got Atlassian here keeps working at enterprise scale. The risk: large enterprises increasingly demand security, governance, and a throat to choke — things a no-sales model may not deliver.
- Bolt on a traditional enterprise sales force. Hire quota-carrying reps to chase big accounts directly, accelerating large-deal revenue. The risk: it inflates cost, dilutes the capital-efficient model investors are buying, and can corrode the developer-first culture.
- Hybrid — keep self-serve, add a thin "enterprise success" layer. Preserve product-led growth as the engine, but add solution engineers, partner channels, and enterprise features/support to convert and expand accounts that adopted bottom-up — without a classic outbound sales army. Captures big-account value while protecting the model and margins.
You are Mike Cannon-Brookes and Scott Farquhar.
Key datapoints (for reference)
| Metric | Value |
|---|---|
| Founded | 2002, Sydney (bootstrapped) |
| Flagship products | Jira, Confluence, Bitbucket |
| Go-to-market | Self-serve, low price, no traditional sales force |
| Sales & marketing as % of revenue | Far below enterprise-software norms |
| R&D spend | Unusually high share of revenue (the sales savings, reinvested) |
| Customers | Hundreds of thousands of teams globally |
| IPO | December 2015, NASDAQ |
| Growth engine | Bottom-up adoption + word-of-mouth + acquisitions (e.g. Trello later) |
Frameworks invoked
- Product-Led Growth (PLG). The product is the primary acquisition and conversion channel: try → adopt → expand, driven by the user's experience rather than a rep's pitch. Works best when the buyer is also the user (developers) and the product delivers value before any purchase decision.
- Low-Touch Distribution & Unit Economics. Removing the sales force doesn't just cut cost — it changes the unit economics. Low customer-acquisition cost means Atlassian can profitably serve small teams that no enterprise rep would ever call, vastly widening the funnel and seeding future enterprise expansion.
- Reinvestment Flywheel. The money saved on sales goes into R&D → a better product → more organic adoption → more revenue → more R&D. Competitors spending half their revenue on sales can't match that product investment without breaking their own model.
- Bottom-Up vs Top-Down Selling. Traditional enterprise sales lands the CIO first. PLG lands the practitioner first and rises to the CIO after the tool is already entrenched — turning "rip this out" into an organisational fight the incumbent can't easily win.
Discussion questions
- The "big software is sold, not bought" rule was treated as law. What conditions made it wrong for Atlassian — and where does the rule still hold?
- Atlassian reinvested its sales savings into R&D. Why is that flywheel so hard for a sales-led incumbent to copy, even if it wanted to?
- PLG works when the user is the buyer. As Atlassian moves up-market to large enterprises, the buyer becomes IT/procurement. How does that strain the model?
- Atlassian eventually added enterprise features, channels, and acquisitions (Trello, Opsgenie). At what point does a "no sales team" company have to compromise the purity of its model — and how do you do it without breaking the culture?
- Bottom-up adoption made Atlassian sticky inside companies before IT noticed. Is that a durable moat, or just a head start a determined incumbent can erase?
The real outcome (revealed at session end)
December 2015: Atlassian IPOs on NASDAQ to strong demand, validating the model — a highly profitable, capital-efficient enterprise-software company built largely without a traditional sales force, spending an unusually small share of revenue on sales and an unusually large share on R&D.
Following years: Atlassian keeps the product-led engine central while pragmatically adding an enterprise layer — enterprise editions, security/governance features, a partner/solution-partner channel, and acquisitions (Trello, Opsgenie, later Loom) — to capture and expand large accounts without building a classic outbound sales army. Revenue compounds for years; Atlassian becomes one of the most valuable software companies in the world and a defining case study for product-led growth.
The lesson: A "rule" that everyone in an industry accepts can be the biggest opportunity to break it. Atlassian proved that for the right product and buyer, self-serve and word-of-mouth beat a sales force — and that the cost saved on selling, reinvested into the product, compounds into an advantage incumbents structurally can't match. But maturity required nuance: the company didn't reject enterprise needs, it added a thin enterprise layer on top of the PLG engine rather than replacing it. The discipline was knowing which parts of the heresy to keep.
Sources
- Atlassian S-1 / IPO prospectus (2015) and subsequent annual reports.
- Interviews with Mike Cannon-Brookes and Scott Farquhar on Atlassian's no-sales model.
- Coverage in the Financial Times, Forbes, and tech press of Atlassian's IPO and PLG strategy.
- Product-led growth literature and case discussions citing Atlassian as a canonical example.