The Twenty Minute VCScott Farquhar: Founding Atlassian; How We Scaled to a $50B Valuation; The 4 Jobs of a CEO | E1070
CHAPTERS
- 0:00 – 3:08
From college grads to Jira: Atlassian’s bootstrapped origin story
Scott and Harry rewind to Atlassian’s founding right after college, when Scott and Mike Cannon-Brookes tried multiple ideas before landing on Jira. Scott explains why passion matters, but also how founders often learn to love a problem as they get good at it—and how the mission evolved into “unleash the potential of every team.”
- •Atlassian started in the 2001 post–dot-com crash environment, which pushed them toward bootstrapping
- •Early experimentation before product-market fit (support work, then Jira)
- •Passion as a competitive advantage; skill-building can deepen passion over time
- •Jira’s roots in bug tracking vs. Atlassian’s broader modern mission
- •Scale outcome: hundreds of thousands of customers and thousands of employees
- 3:08 – 4:53
Bootstrapping vs. venture capital: how the era shaped Atlassian’s path
Scott describes why Atlassian could bootstrap for so long and how company-building is often “symbiotic” with the funding environment. He contrasts their era with today’s AI startups, where capital needs can be structurally higher, and discusses when bootstrapping is still viable.
- •2001–era ‘nuclear winter’ made fundraising rare and bootstrapping normal
- •Atlassian waited ~10 years to add VCs and didn’t add cash to the balance sheet for ~15 years
- •Business feasibility depends on competitive intensity and market niche
- •Bootstrapping remains possible in small, niche vertical software categories
- •AI startups today often can’t bootstrap due to compute/data costs
- 4:53 – 6:34
The biggest myth about startups: glamour vs. survivor bias
Scott pushes back on the idea that startups are glamorous, arguing most are brutally hard and often fail. He shares how “startup” used to be synonymous with being unemployed and how cultural narratives have shifted despite the reality staying difficult.
- •Survivor bias distorts how people perceive startup life
- •Most startups are ‘really freaking hard’ and many fail
- •Early-era stigma: founders seen as unemployed rather than ambitious
- •Why modern hype can mislead founders about day-to-day reality
- •Hardness is normal—not a signal you’re doing it wrong
- 6:34 – 11:19
Honeymoon crisis: the 2010 hack and Atlassian’s near-death moment
Scott recounts a high-stakes incident while on his honeymoon: a security breach hits as he’s about to fly to the U.S. to raise Atlassian’s first VC money. He explains the operational scramble, the personal cost of cutting the honeymoon short, and why transparency with VCs and customers mattered.
- •Urgent message routing to reach Scott in remote Botswana
- •A solo hacker accessed one of Atlassian’s systems—security awareness was lower in 2010
- •Company-wide incident response: all-hands, people sleeping at the office, rapid containment
- •Scott cuts honeymoon short; leadership trade-offs and partner support
- •Proactive disclosure to VCs/customers; investors respond that hacks happen more than people admit
- 11:19 – 16:02
Raising capital on their terms: sealed-bid VC process and valuation outcomes
Scott explains Atlassian’s unconventional fundraising approach: a one-shot, closed-envelope bid to reduce signaling and “collusion” dynamics. He shares the company’s financial profile at the time, the spread of bids, why Accel won, and how the same method worked again pre-IPO.
- •Atlassian was ~sub-$100M revenue run-rate with strong profit margins when raising
- •Sealed-bid structure to force ‘best offer’ upfront; internal debate with CFO
- •Bid dispersion: several in $200–300M range; Accel at ~$405M with $60M invested
- •Relationship-building happened before the process via years of VC outreach and meetings
- •They repeated the method later (pre-IPO liquidity round) with similar ‘outlier’ dynamics
- 16:02 – 18:01
Scott’s biggest regret: not betting hard enough on breakout opportunities
Scott distinguishes early-company mistakes (commission) from later-stage mistakes (omission). He argues Atlassian had strong products in markets like source control and chat, but failed to invest aggressively enough to win the category—shaping how he thinks about resource trade-offs today.
- •Small-company errors: doing the wrong things; big-company errors: not doing the right things
- •Examples: Bitbucket vs. GitHub and a Slack competitor—good products, insufficient investment
- •The cost of under-investing when timing and product quality are there
- •How missed chances change CEO mindset about commitment and urgency
- •Resource allocation requires starving something else to fund the new bet
- 18:01 – 19:15
The 4 jobs of a CEO—and why resource allocation is quarterly, not daily
Scott outlines his framework for CEO responsibilities: build the leadership team, set vision, set culture, and allocate resources. He explains how he audits his calendar against these priorities and why Atlassian shifted from annual to quarterly resource allocation to steer faster at scale.
- •Four CEO jobs: hire/fire leadership, set vision, set culture, allocate resources
- •Using the framework as an annual self-check against time spent
- •Resource allocation cadence: quarterly beats daily to avoid losing the ‘forest for the trees’
- •Scaling challenge: big-company inertia makes steering harder
- •Atlassian’s shift from annual planning to quarterly allocation
- 19:15 – 20:58
Systems thinking as a superpower—and prioritization as the weakness
Scott describes his strength as systems thinking across disciplines, driven by deep curiosity. He also admits curiosity can become a liability: he gets excited by too many things, so he needs strong partners and structures to help prioritize.
- •Systems thinking: understanding second- and third-order effects across a whole business
- •Curiosity across disciplines (physics to psychology) as the raw input
- •Business as an unusually dynamic, complex ‘system’ worth studying
- •Leadership challenge: curiosity fights focus; prioritization becomes the constraint
- •Practical mitigation: surrounding himself with people who help prioritize
- 20:58 – 27:03
Atlassian’s AI strategy: beyond ‘parlor tricks’ to workflow-and-data leverage
Scott frames AI as a platform shift that can reorder the tech leaderboard, making an AI strategy non-optional. He argues the first wave is commodity features (summaries, bullet points), while durable advantage comes from connecting unique datasets and workflows—where Atlassian’s customer footprint helps it experiment at scale.
- •Tech history lens: major platform shifts reshape winners; AI is the next discontinuity
- •Phase one: bolting AI onto existing products; many features are becoming commoditized
- •Differentiation comes from combining datasets + end-to-end workflows (e.g., support, bugs, logs, code ownership)
- •Atlassian invests hundreds of engineers in AI but doesn’t need to build a base LLM
- •Scale advantage: experimentation with 250,000 customers and deep historical datasets
- 27:03 – 34:39
Team Anywhere: how Atlassian structures remote work with ‘intentional togetherness’
Scott explains why Atlassian chose a deliberate, permanent remote stance to keep hiring globally, rather than drifting into hybrid by default. He shares research showing in-person gatherings boost team connection sharply—and that the benefit lasts months—suggesting a few purposeful meetups per year can rival daily office presence.
- •Remote decision made early in COVID with a hiring-first mindset; ‘never required’ return to office
- •Benefits: access to broader talent, lower attrition, high employee-reported productivity support
- •‘COVID remote’ is not the same as healthy remote: you still need human connection
- •Internal research: intentional meetups increase connectedness ~30%, with 4–5 month decay to baseline
- •Open questions: best formats for bonding (office time vs. hikes vs. philanthropy)
- 34:39 – 39:27
Competition, product complexity, and AI-era pricing pressure
Scott addresses how Atlassian balances competitor awareness with customer-led differentiation, including critiques that Jira has grown complex for new users. He then explores how AI will pressure per-seat pricing—especially in high-cost enterprise seats—and why the industry is still searching for the next pricing proxy for value.
- •Competition matters, but copying competitors is rarely the path to winning
- •Jira’s trade-off: power and scalability vs. perceived complexity; configuration often drives pain (e.g., too many required fields)
- •Continual simplification efforts while preserving ‘never grow out of it’ scalability and integrations
- •AI pressure on per-seat pricing: agents and automation break the ‘seat = value’ proxy
- •Likely outcome: pricing evolves (augmentation vs. replacement), but software won’t simply become free
- 39:27 – 52:03
Money, parenting, marriage, and quick-fire reflections on life after scale
Scott shares how wealth changes the time–money trade-off and how he’s learning to ‘buy back time,’ especially for family. He discusses the challenge of raising kids with wealth, his view on a strong marriage (idealization + fast apologies), and closes with rapid reflections on philanthropy, calm under pressure, and co-founder partnership.
- •Wealth shifts the time–money slider; learning to spend for reclaimed time
- •Parenting challenge: teaching values and humility when kids inevitably notice wealth
- •Marriage principles: ‘put your partner on a pedestal’ and say sorry quickly
- •Serenity tools: consistent exercise and prioritizing sleep
- •Co-founder dynamics: complementary differences and long-term relationship intensity
