How Doist Runs a 90-Person Bootstrapped Company With No Meetings and No Slack

Snapshot

Doist has been async- and remote-first since 2010, with the company’s first remote hire (David, providing customer support from Poland) in 2011. About 93 employees across 39 countries today (per their own About page). They make Todoist (one of the world’s most popular task managers) and Twist (an async team communication app built to replace Slack). They are bootstrapped — no outside investors — which means they optimize for sustainable work, not growth-at-all-costs.

What makes Doist unusual is not just that they are remote. It is that they have the most extreme async-first stance of any company this size in the industry. They built their own communication tool specifically because they believed Slack was damaging to the kind of focused work they wanted to enable. They eat their own cooking — and have done it for 15+ years.

Core Philosophy

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

The statistics that shaped their 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)
• Resuming full focus on a task after an interruption takes around 23 minutes. (Source: Gloria Mark, UC Irvine — research on attention and interruption)

Salihefendić cites this cluster of research in his interview with Business of Software when explaining why Doist designs around uninterrupted work. (Source)

The response: eliminate most meetings by default. Use Twist (their own product) instead of Slack because threaded async conversations have lower ambient noise than real-time channels. Hire people who thrive in low-interruption environments and explicitly do not want to be in constant contact.

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)

When meetings happen: synchronous calls are used only when async would genuinely be less efficient — complex technical decisions, crisis response, or situations requiring real-time emotional attunement. They are exceptions, not scheduled defaults.

Communication norms:

• No expected real-time response to any message
• No @channel or @here interruptions
• Respect for off-hours — no expectation of after-hours responsiveness
• Clear, high-context messages that minimize back-and-forth

(Source)

Planning and Cadence

Doist does not publish the full details of their planning cadence publicly. What is confirmed:

• 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)
• Work is project-based and async. Teams work in Twist threads organized around projects. There is no company-wide sprint or cycle cadence published externally.
• 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

• ~93 employees across 39 countries (per Doist’s About page, 2026).
• 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)

Rituals

Company-wide retreat, once per year. The full company gathers in person for one week. (Source)

Team retreats, once per year. Each team gathers separately. Total: two in-person gatherings per employee per year — company-wide and team-level.

Doist follows the 20/30/50 retreat rule:

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

The philosophy: in-person time at Doist is primarily for relationship-building, not for replicating office productivity. The work gets done async. The in-person time maintains the human connections that make async work sustainable. (Source)

Doist spends ~$350,000 annually on retreats. That is a substantial commitment for a sub-100-person bootstrapped company — well over $3,000 per person per year on in-person time. (Source)

What They Do Well

• The deepest async discipline of any company at this scale. No meetings by default is not an aspiration — it is an operational reality maintained over 15 years. That longevity is evidence that it is sustainable, not just a temporary experiment.
• 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

Coordination velocity is slower. A decision that requires input from three people who are in different time zones and checking messages once or twice a day can take 24–48 hours to close. At Basecamp, the same decision might take a few hours of async messages. For fast-moving markets, this is a real cost.

Culture requires explicit maintenance. When the team never meets in real-time and works from 30 countries, shared culture requires constant investment. Doist invests $350,000/year in retreats specifically because async culture erodes without periodic in-person repair. (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)

Limited public documentation. Doist does not have a public handbook on the scale of GitLab’s or 37signals’. The operating model is known primarily through blog posts and founder interviews, not codified operational documentation. Some details remain undocumented publicly.

What Founders Can Copy

Doist is a sub-100-person bootstrapped case. The async-first practices below are most operationally faithful when copied at similar scale; transferring them to faster-growing or larger companies usually requires adaptation, not direct copy.

1. Budget explicitly for retreats. If you are fully distributed, the question is not whether to spend on in-person time — it is how much and how to design it. Doist’s 20/30/50 rule (50% rest, 30% social, 20% work) is the most operationally specific retreat framework available. (Applies at 10–150 cleanly; above ~150 retreats split into team-level and divisional formats and the per-person budget shape changes.)
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. Separate hero time from housekeeping time. Define which part of the sprint is for deep feature work and which part is for maintenance. Not doing this means maintenance load continuously bleeds into creative work. (Applies at any scale; especially valuable at 20–200 where small teams own multiple production surfaces.)
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

• In fast-moving competitive markets. Pure async-first becomes a liability when your competitor ships weekly and you need organizational velocity. Doist’s bootstrapped products compete in a market (productivity software) where pace is important but not existential. A startup racing a better-funded competitor cannot afford 48-hour decision cycles.
• 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 — the most fully realized example of async-first in practice
• 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 — when is pure async not enough?

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 to Build Human Connections in an Async Workplace: https://async.twist.com/remote-team-culture/
4. The 20/30/50 Rule for Remote Team Retreats: https://async.twist.com/20-30-50-rule-remote-team-retreats/
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
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. Gloria Mark, UC Irvine — research on attention and interruption (primary source for the 23-minute recovery figure): https://www.ics.uci.edu/~gmark/

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.
• The $350,000 annual retreat spend is not a perk — it is an operational cost of running a no-meetings async company. The relationship capital that colocated employees build by proximity must be built at retreats for fully distributed companies. Doist has simply made this explicit in their budget. Most distributed companies underinvest in retreats and then wonder why async communication breaks down.
• 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.

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.