How Todoist Runs a Distributed Company With Async Communication and Deliberate Meetings

Snapshot

Todoist’s current About Us page dates its remote and async working model to 2011, and its company history places the first hire in that year. The history records a transition from Doist to Todoist in July 2026. The current footprint is 108 team members in 38 countries. (About Us, company history)

The company behind Todoist and Twist remains the subject of this profile under its existing Doist URL. Its current privacy policy identifies Todoist Inc. as registered in Delaware, United States; the policy does not establish a legal name-change date. (Privacy policy)

The operating model combines written communication with planned support meetings and a public handbook. The earlier Doist sources below remain useful evidence of how that model developed; dated practices are not automatically current mandates.

Core Philosophy

Doist’s founder Amir Salihefendić designed the company explicitly around deep work. The operating principle: coordination should not interrupt creation.

Research relevant to the model:

• About 60% of knowledge-worker time goes to work about work — coordination, status updates, and information-hunting — leaving roughly 40% for the skilled work people are actually paid for. (Source: Asana, Anatomy of Work Index)
• Time spent in meetings per Microsoft Teams user rose roughly 252% between February 2020 and February 2022. (Source: Microsoft, 2022 Work Trend Index — Great Expectations: Making Hybrid Work Work)
• Interrupted tasks can be completed faster while increasing stress, frustration, time pressure, and effort. (Source: Mark, Gudith and Klocke — The Cost of Interrupted Work: More Speed and Stress, CHI 2008)

Salihefendić discusses the costs of coordination and interruptions when explaining Doist’s focus on uninterrupted work. (Source)

The response emphasizes writing and fewer interruptions. Recurring meetings still have a place, as the onboarding and accountability practices below demonstrate.

Doist treats headcount as a “vanity number” — they hire slowly and deliberately, prioritizing culture fit over speed. (Source)

Communication Model

Twist is the primary communication tool. Twist is a threaded async communication app — like Slack, but organized around topics and threads rather than chronological channels. Conversations are persistent, searchable, and not expected to produce real-time replies.

Why not Slack: Doist explicitly built Twist because they found that Slack’s real-time channel structure created ambient anxiety and interrupted deep work even when used “async.” The design of the tool shapes the communication norms. (Source)

Meetings are replaced with async alternatives by default:

• Status updates → Twist threads
• Brainstorms → written proposals in Twist
• Feedback sessions → async written reviews
• Announcements → Twist broadcasts

(Source)

Meetings are deliberate and include recurring support. The current onboarding guide schedules weekly mentor and team-head check-ins. Doist’s published accountability model also describes regular manager 1:1s. (Onboarding, accountability)

Communication norms:

• Default to writing
• No immediate response expected; 24 hours is the general response window
• Async conversations become permanent documentation
• Respect for off-hours and disconnected time

(Source)

Planning and Cadence

Doist has published a DO (Doist Objectives) planning system; its details have evolved over time.

• Heroes and housekeeping. A system designed to minimize context switching — some time is protected for deep “hero” work (shipping features, solving hard problems), and other time is dedicated to “housekeeping” (bug fixes, maintenance, admin). This prevents the typical problem where support load constantly interrupts feature development. (Source)
• DO squads connect objectives to execution. A September 2022 company article described 1–5-person squads, DO cycles lasting one to six months, monthly reflection and end-project async retrospectives. The current onboarding guide still references DOs, squads and cycle planning; the exact current cadence is not established by the publicly readable pages. (Accountability, onboarding)
• Bootstrapped = long-term thinking. No investor pressure for quarterly results. Doist consistently prioritizes sustainable pace over growth sprints. (Source)

Decision-Making Model

Amir Salihefendić (CEO/founder) is the ultimate decision-maker. As a bootstrapped company with a strong founder, strategic decisions centralize with him.

Below the founder level, the model follows the async-first principle: decisions are written up, discussed in Twist threads, and made visible to the relevant people. The lack of real-time communication means decisions cannot be rushed — someone raising a question on a Friday afternoon will get a considered reply, not a hasty Slack reaction.

Hiring decisions are deliberately slow. Cover letters are required. Applications without a cover letter are rejected without reading the resume. The thinking: someone who cannot write a clear, motivated cover letter for an async-first company is probably not right for this environment. (Source)

The bar for hiring is deliberately high — Doist’s published approach emphasizes test tasks, multiple interview rounds, and explicit values alignment, with hiring slowed to protect cultural fit at the cost of headcount growth. (Source)

Org Structure

• 108 team members across 38 countries (checked September 12, 2026). (Source)
• Bootstrapped — no outside investors, no board pressure.
• Relatively flat structure for its size, but specific org chart is not published.
• Founder remains deeply involved operationally.
• Cultural homogeneity is a deliberate choice. Doist hires slowly to ensure each new person fits the async-first communication culture — they treat every new hire as a cultural integration challenge, not just a skills acquisition.

Tools and Stack

Notably absent: Slack. (Source)

The current handbook and onboarding guide supply the documentation and recurring-check-in examples. (Handbook, onboarding)

Rituals

Two organization gatherings per year. Todoist’s current About Us page says the organization meets twice yearly. This describes the company cadence, not a guarantee of individual attendance. (About Us)

Doist’s historical 20/30/50 retreat rule:

• 20% work sessions
• 30% planned social and entertainment activities
• 50% rest, relaxation, and free time

This published agenda emphasizes relationships and downtime. It is a historical design example; the current About Us page does not establish it as a mandatory agenda. (Historical source, current gathering statement)

AI

DoistOS is a company-wide shared workspace. On April 10, 2026, Chase Warrington, who led the squad that took it from prototype to launch, described DoistOS as a shared AI workspace that connects internal tools and is available in plain language to anyone at the company. The same day, Dominique Jost said it had been rolled out to every Doister. The stated purpose is shared context across tools, so people who are not building personal agents can work from the same company context. These are employee posts, not a handbook chapter. They do not establish usage, output quality, or time saved. (Warrington, Jost)

Hiring allows AI if the candidate says so. The hiring FAQ says candidates may use AI to organize their thinking, asks them to disclose it, and says Todoist interviews humans rather than an LLM. Screening calls are with a person. New-hire onboarding includes an item to explore AI at Doist. (Hiring FAQ, onboarding)

What They Do Well

• Explicit support for async work. The public handbook combines written guidance with scheduled onboarding support. Inference: this makes an async-first model easier to learn than relying on unwritten norms. (Source)
• Building your own tools to enforce your own norms. Twist exists because Doist decided that the best-available tool (Slack) was architecturally incompatible with their values. Most companies accept the tools available and then complain that their culture does not match what they wanted. Doist chose a different path.
• The 20/30/50 retreat rule is actionable. Most companies plan retreats as either productivity-first (too exhausting) or social-first (too disconnected from work). The 20/30/50 split is a specific, testable framework for what makes in-person time valuable.
• Bootstrapped = calibrated incentives. Without investor pressure, Doist optimizes for employee wellbeing and product quality rather than ARR growth. That alignment between ownership structure and operating model is rare.

Tradeoffs and Weaknesses

Delayed replies can slow coordination. Inference: decisions spanning time zones may take longer without a live discussion. This is a design tradeoff, not a measured Todoist decision-time statistic or evidence that its model excludes calls.

Culture requires explicit maintenance. Inference: a geographically dispersed team benefits from deliberate relationship-building. Todoist’s twice-yearly organization gatherings supply one mechanism. (Source)

Not everyone thrives in this environment. Doist is explicit that their model requires specific personal qualities — the ability to structure your own day, high written communication skill, tolerance for delayed feedback, comfort with ambiguity. These are not universal. (Source)

A public handbook now documents the operating system. Todoist publishes onboarding, compensation, career development, feedback, performance-review and retreat material. Some linked internal pages remain unavailable publicly. (Public handbook)

What Founders Can Copy

Todoist is a bootstrapped company with 108 team members at this review. Inference: the practices below are useful design options; their fit depends on team size, growth and coordination needs.

1. Budget explicitly for retreats. Doist’s historical 20/30/50 rule provides a concrete agenda to evaluate, while the current company statement specifies two organization gatherings per year. (Historical example, current cadence)
2. Require cover letters. A mandatory cover letter filters for written communication ability before you ever review a resume. For async-first roles, writing skill is table stakes. (Applies at any scale; pays back fastest at 10–100 where every hire is a culture-shaping addition.)
3. High-bar, slow hiring. Every person you add to an async team is a cultural integration event, not just a skills addition. The quality bar should reflect that — Doist uses test tasks, multi-round interviews, and explicit values alignment to enforce it. (Applies most cleanly at 10–100; harder above 200, where hiring volume and cycle pressure typically force compromises.)
4. Make planning and maintenance responsibilities explicit. Doist’s published DO example connects small squads to objectives. Use a documented planning system while protecting feature work from unplanned maintenance; the evidence here does not establish Todoist’s current sprint length.
5. Design retreat agendas against productivity. Counter-intuitive but correct: in-person time for a distributed team should be mostly rest and social, not work. You already have the async infrastructure for work. Use the expensive in-person time for what async cannot do. (Applies at any scale; gets harder above ~150 where leadership feels pressure to “use the gathering” for planning that should have stayed async.)

Where This Model Breaks

• When urgent coordination lacks an escalation path. Inference: written discussion can become a bottleneck if a team never switches to a call when needed. Todoist’s deliberate meetings mean its model should not be read as a prohibition on synchronous work.
• When trust breaks down. Async-first communication requires high levels of trust — that messages will be answered, that commitments will be kept, that work is happening even when you cannot see it. One reliable bad actor can poison the well for an entire team.
• Below 15 people. At very small scale, the overhead of maintaining async discipline exceeds the benefit. A 5-person team in similar time zones should just talk to each other.
• Roles requiring real-time customer interaction. Sales, customer success, and support roles inherently require synchronous availability windows. Doist routes around this by keeping those functions minimal or structured differently from the engineering and design teams.

Related Practices

• Async Communication — written defaults with deliberate synchronous support
• Retreats — the 20/30/50 framework is directly Doist-derived
• Written-First Culture — Doist is the model case for communication-by-writing

Related Frameworks

• Sync vs Async Decision Matrix — choosing written discussion or a deliberate meeting

Sources

1. How Doist Works Remote: https://doist.com/how-we-work/how-doist-works-remote
2. How We Work — Doist: https://doist.com/how-we-work
3. How Remote Teams Win With Retention: https://doist.com/how-we-work/remote-teams-retention
4. Doist Careers — company-wide and team retreats: https://doist.com/careers
5. How Amir Salihefendić Scaled Doist with Async Work (Business of Software, 2025): https://businessofsoftware.org/2025/08/how-amir-salihefendic-scaled-doist-with-asynchronous-work
6. Asana, Anatomy of Work Index (primary source for the ~60% “work about work” figure): https://asana.com/resources/anatomy-of-work-index
7. Microsoft, 2022 Work Trend Index — Great Expectations (primary source for the 252% meeting-volume figure): https://www.microsoft.com/en-us/worklab/work-trend-index/great-expectations-making-hybrid-work-work
8. Mark, Gudith and Klocke — The Cost of Interrupted Work: More Speed and Stress, CHI 2008 (interruption effects on speed and stress; does not establish a 23-minute recovery estimate): https://ics.uci.edu/~gmark/chi08-mark.pdf
9. Replace Meetings with Twist (Doist blog): https://blog.doist.com/replace-meetings-twist/
10. Todoist, About Us (live, checked September 12, 2026): https://www.todoist.com/about-us
11. Todoist, Public Handbook (live, checked September 12, 2026): https://www.todoist.com/handbook
12. Todoist, Privacy Policy (current entity clause; displayed effective date is not a name-change date): https://www.todoist.com/privacy
13. Todoist handbook, Our History (includes July 2026 transition): https://handbook.todoist.net/s/a772e0a3-2196-4568-b08d-c5b939653b7c/doc/our-history-5X74kRZbMT
14. Todoist handbook, Your First 90 Days (live): https://handbook.todoist.net/s/6ca6f66e-2d02-4e05-b629-b1c772f5ff23
15. Becky Kane, 3 time-tested systems for creating accountability on a remote team (September 21, 2022): https://async.twist.com/accountability-remote-workers/
16. Chase Warrington, DoistOS launch (April 10, 2026): https://www.linkedin.com/posts/chase-warrington_introducing-duist-os-an-ai-powered-workspace-activity-7448354236540612608-JSGz
17. Dominique Jost, DoistOS rollout (April 10, 2026): https://www.linkedin.com/posts/dominiquejost_introducing-duist-os-an-ai-powered-workspace-activity-7448401315896033280-hnWr
18. Hiring FAQ (living page; AI-use answer accessed October 5, 2026): https://handbook.doist.com/s/e4006490-4bd7-40dd-9209-f17903efb6f9/doc/hiring-frequently-asked-questions-dmZBKLmwD3

Inferences

• Doist’s decision to build Twist instead of using Slack was not primarily a product strategy — it was a culture strategy. The tool architecture of real-time chat channels creates norms that contradict the behavior you want in an async-first company. Most companies try to impose async norms on synchronous-by-design tools. Doist built the tool to enforce the norm architecturally.
• Doist’s historical retreat design treats in-person time as relationship infrastructure. The current async-first model also includes recurring meetings; gathering twice yearly complements that support rather than replacing every live conversation.
• The cover-letter-required hiring policy is a proxy test for the most critical skill in an async company: clear written communication under no time pressure. If someone cannot write a motivated, clear cover letter when they have unlimited time, they will not write clear async messages when they are busy.
• DoistOS extends the same written-context habit into an AI workspace: the value, if it holds, is that colleagues share one connected environment rather than each starting a private chat from zero. The launch posts do not measure whether that happened.

Work with Alex

If you are trying to reduce meeting load and shift your company toward more focused async work, Alex helps leadership teams redesign their communication infrastructure and cadence.