Remote and Distributed Teams
Building and managing teams that aren’t in the same office. Once a contrarian stance (Fried’s 37signals pioneered it), remote-first is now the default for most startups — accelerated by COVID and cemented by the AI era where solo founders and tiny teams build at scale.
The Case For Remote
Fried’s 37signals proved the model: 80 people, distributed globally, tens of millions in profit.
- Wider talent pool: Hire the best person, not the best person within commuting distance
- Lower costs: No office lease (often a startup’s biggest expense after payroll)
- Deep work by default: Fewer interruptions, more focused time
- Async communication: Forces written clarity, creates documentation naturally
- Diversity: Teams span time zones, cultures, and backgrounds
- Sustainability: Fried’s “It Doesn’t Have to Be Crazy at Work” — remote enables calm culture
The Case Against (When Co-Location Wins)
Altman: “Keep everyone in the same office when possible (especially early).”
- Early-stage intensity: Pre-PMF, speed of iteration matters more than work-life balance. Sitting together enables instant communication.
- Culture formation: The first 10 hires set cultural DNA — harder to transmit remotely
- Serendipity: Hallway conversations, whiteboard sessions, overhearing problems
- Trust building: Relationships form faster in person, especially between cofounders
- Wartime operations: When in wartime mode, coordination overhead of remote is costly
The Hybrid Reality
Most startups in 2026 are hybrid — some combination of:
| Model | How It Works | Best For |
|---|---|---|
| Remote-first | Everyone remote; office optional | Bootstrapped, distributed talent needs |
| Office-first | Everyone in office; remote exceptions | Pre-PMF, intense collaboration phase |
| Hub + remote | Core team in one city; others remote | Post-PMF scaling with cultural anchor |
| Async-first | Work happens on own schedule; few meetings | Global teams across many time zones |
Making Remote Work: Tactical Advice
Communication
- Write it down: If it’s not written, it didn’t happen. Memos > meetings.
- Default to async: Not everything needs a real-time response. Use Slack/email for updates; reserve calls for decisions.
- Over-communicate context: Remote workers miss hallway context. Share more than feels necessary.
- Rabois’ transparency principle: Everyone accesses board decks, meeting notes, dashboards. Even more critical when remote.
Meetings
- Fewer, shorter, structured: Every meeting needs an agenda and a decision to make
- Record everything: Absent team members catch up via recording, not a second meeting
- Timezone fairness: Rotate meeting times so the same team isn’t always at 6am
- No “hybrid meetings”: If one person is remote, everyone joins from their own screen (levels the playing field)
Culture
- Rituals replace proximity: Weekly all-hands, monthly retrospectives, quarterly offsites
- In-person offsites: 2-4x per year, invest heavily in face time for relationship building
- Social channels: Non-work Slack channels, virtual coffee chats, shared interests
- Onboarding matters more: New remote hires need structured onboarding since they can’t learn by osmosis
Management
- Output over hours: Measure what people produce, not when they’re online
- Trust by default: Micromanaging remote workers destroys both productivity and morale
- 1:1s are non-negotiable: The remote manager’s primary relationship tool — weekly, never skip
- Rabois’ barrels are even more important: In remote, self-directed people who ship end-to-end are 10x more valuable than those who need constant direction
Remote in the AI Era
AI makes remote teams even more viable:
- AI tools reduce coordination overhead (automated standups, AI-summarized meetings)
- Solo founders + AI stack can build what teams of 10 did — no office needed at all
- Async documentation (the backbone of remote work) is AI-accelerated
- The question shifts from “should we be remote?” to “do we even need to hire?”
Common Remote Mistakes
- Replicating the office online: 8 hours of video calls isn’t remote work — it’s surveillance
- No async culture: If everything requires a meeting, you’ve built a worse version of an office
- Ignoring loneliness: Remote workers get isolated. Build social infrastructure deliberately.
- Same compensation everywhere: Debate exists — pay for role (same everywhere) vs pay for market (adjust by location)
- No in-person time ever: Fully remote + zero offsites = team that doesn’t trust each other
See Also
- hiring
- company-culture
- operations
- execution
- onboarding
- ai-era-entrepreneurship
- bootstrapping
- founder-psychology