How high-performing distributed companies actually operate.
Not theory. Not tips. Real operating systems from the companies that figured out distributed execution — how they communicate, plan, decide, and scale without falling apart. Applies whether your team is fully remote, hybrid, or reluctantly back in offices.
Companies
Company profiles. Distinct operating models.
Deep profiles of distributed companies that have published how they actually work — handbook-first, async-first, founder-as-system, mixed sync + async, and publicly transparent.
Handbook-first
Automattic
Automattic stewards WordPress, the CMS behind ~42% of all websites, and runs WordPress.com with a fully distributed team across 81 countries — P2 blogs replace email, everyone does customer support, and new hires trial before they're hired.
Read profileAsync-first
Basecamp / 37signals
37signals built the definitive async operating system — 6-week cycles, zero full-time managers, and 98% of all communication in one tool.
Read profilePublicly transparent
Buffer
Buffer has been fully remote since 2012 (last office closed late 2015) with 75 teammates across multiple continents, publishes all salaries on a public formula, runs profit share for the whole team, and explicitly documents that remote does not mean async-first.
Read profileAsync-first
Doist
Doist builds Todoist and Twist with ~93 employees across 39 countries, no VC funding, no meetings by default, and Slack deliberately excluded — the most extreme async-first operating system in use at a real software company.
Read profileAsync-first
GitHub
GitHub built developer culture around 'optimize for happiness,' no managers, no meetings, and pull-request-as-artifact — and ran for 12 years that way before being acquired by Microsoft. The PR survived. The manifesto mostly didn't.
Read profileHandbook-first
GitLab
GitLab has 2,500+ team members across 65+ countries with no offices and a public handbook that runs well over 2,000 pages — radical documentation, async-first communication, and results over activity.
Read profileHandbook-first
Linear
Linear is the rare small distributed company that publishes its operating handbook — the Linear Method — and runs the entire product on it. Cycles, taste-as-hiring-filter, quality-as-binary, and async-first by default at exactly the scale most readers actually operate at.
Read profileMixed sync + async
Shopify
Shopify pivoted to digital-by-default in May 2020 and held it through the post-COVID RTO wave. In January 2023 they cancelled every recurring meeting >2 attendees, eliminated ~76,500 hours of meeting time, and built an internal calendar tool that surfaces the dollar cost of meetings. The most public post-RTO operating-model case study in software.
Read profileFounder-as-system
Wolfram
Wolfram Research has been distributed since the early 1990s with Stephen Wolfram as a remote CEO since 1991 — one of the longest-running distributed-CEO cases in software, running ~700 people across 29+ countries on audio-only meetings, livestreamed design reviews (975+ episodes), and no outside money.
Read profileMixed sync + async
Zapier
Zapier has been fully remote since 2011 and scaled to 800+ employees without a single office on two rules — default to action, default to transparency — plus a DRI system, single-page specs, and customer-centered annual summits.
Read profilePractices
The systems that separate strong distributed teams from struggling ones.
Each practice covers what it is, why it works, where it fails, and what founders can actually copy.
Frameworks
Original frameworks built from cross-company patterns.
Synthesized from real evidence across multiple companies — not opinion, not theory.
Framework
The 20-30 Person Fracture Point
Companies that scaled distributed work successfully — at least in this dataset — built explicit operating infrastructure before reaching 20–30 people. Companies that struggled at that scale hit a recurring set of failure modes: invisible ownership, fragmented communication, lost institutional knowledge, cultural drift. This framework states the pattern as a working hypothesis and lays out what to build before you hit it.
Read frameworkFramework
Scrum in Distributed Companies: What Survives, What Breaks, What to Adapt
A source-backed audit of which Scrum elements strengthen distributed execution, which conflict with it, and how distributed-native companies (GitLab, 37signals, Linear, Doist) achieve Scrum's intended outcomes through adapted mechanisms. Triangulates the Scrum Guide 2020, Scrum.org and Scrum Alliance distributed guidance, the Scrum@Scale Guide, LeSS principles, and peer-reviewed empirical research.
Read frameworkFramework
Sync vs Async Decision Matrix
A practical decision matrix for choosing between synchronous and asynchronous communication — built from the operating practices of 37signals, GitLab, Doist, Buffer, and Zapier. Includes symptom checklist, situation-by-situation guidance, and a framework for setting team-level communication norms.
Read frameworkWhy it matters
Most distributed teams don't fail because of the wrong tools.
They fail because of the wrong operating model. Meetings as default. No written culture. Decisions without owners. Planning without rhythm.
This site documents what the companies that got it right actually did — with sources, not summaries.
- Every claim is sourced or labeled Inference
- Founder takeaways on every page
- Tradeoffs and failure modes included
- No generic best-practices content
Consulting
If your company is hitting these issues, Alex helps leadership teams fix them.
Execution systems for distributed companies. Planning, communication, decision-making — designed for your context, not a generic framework.
See how Alex works