When you need practitioner-tested principles for calm, sustainable company building
Scanned 9/20/2026
Install to Claude Code
npx -y skills add lev-os/agents --skill basecamp-handbook --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Basecamp Handbook?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lev-os-basecamp-handbook)More formats (shields.io, HTML) on the badges page.
---
name: basecamp-handbook
description: When you need practitioner-tested principles for calm, sustainable company building
tags: [management, company-culture, remote-work, productivity, philosophy]
---
# Basecamp Handbook
## Overview
The publicly documented management philosophy and operational practices of Basecamp (formerly 37signals), codified through their books, blog (Signal v. Noise/Rework), and company handbook. Represents a counter-narrative to Silicon Valley's growth-at-all-costs culture, emphasizing profitability, sustainability, work-life balance, and intentional constraints. Key tenets include remote-first work, asynchronous communication, shipping early and often, and saying no by default.
## Core Principles
### 1. Calm Company Philosophy
**Reject the "always-on" hustle culture**
- 40-hour workweeks as the standard, not minimum
- No all-nighters, death marches, or crunch time
- Sustainable pace prevents burnout and preserves creativity
- "Work can wait" mentality for non-emergencies
### 2. Constraints Breed Creativity
**Fixed time, variable scope (not vice versa)**
- 6-week cycles with built-in cooldown periods
- No overtime to finish features—cut scope instead
- Deadlines force prioritization and focus
- Small teams (3 people or fewer per project)
### 3. Asynchronous by Default
**Real-time communication is the exception**
- Long-form writing over meetings
- Basecamp (the product) over Slack-style chat
- Expected response time: hours/days, not minutes
- "Office hours" for synchronous collaboration
### 4. Remote-First Since 2000s
**Hire the best people, wherever they are**
- No geographic constraints on talent
- Trust-based autonomy over surveillance
- Over-communicate in writing
- In-person meetups 2-3x per year
### 5. Profitable & Independent
**Bootstrapped, no VC funding**
- Revenue-funded growth
- No obligation to exit or scale infinitely
- Make decisions for long-term health, not short-term metrics
- "Enough" as a valid business goal
## Key Operational Practices
### Product Development
- **Shape Up**: 6-week cycles, 2-week cooldown
- **Hill Charts**: Visual progress tracking (uphill = figuring out, downhill = executing)
- **Appetite-driven**: Start with time budget, not feature spec
- **Circuit breaker**: Auto-kill projects that exceed time budget
### Communication
- **Write it down**: Decisions documented in Basecamp
- **No shoulder taps**: Respect focus time
- **JOMO (Joy of Missing Out)**: Not every conversation is critical
- **Library Rule**: Keep virtual workspace quiet
### Hiring & Culture
- **Hire writers**: Communication skills essential for remote work
- **Async interviews**: Written questions before video calls
- **Work-life balance**: Judge output, not hours logged
- **Benefits library**: Choose your own perks
### Decision-Making
- **Disagree and commit**: Voice opinion, then support decision
- **Default to no**: New features add complexity (cost > benefit)
- **Kill features**: Remove more than you add
- **Small is beautiful**: Stay small intentionally
## Execution Steps (Adopting Basecamp Principles)
### 1. Audit Current Practices
- Measure actual work hours (including "nights and weekends")
- Count meetings per week
- Assess synchronous vs. asynchronous communication ratio
- Identify sources of urgency/interruption
### 2. Implement Constraints
- Set cycle length (e.g., 6 weeks)
- Cap team sizes (≤3 people)
- Define "done" as what fits in the cycle
- No overtime allowed—cut scope instead
### 3. Shift Communication Norms
- Default to writing over talking
- Ban "quick question" IMs (use email/Basecamp)
- Establish async-first response expectations
- Schedule "office hours" for sync collaboration
### 4. Measure Calmness
- Weekly hour tracking (aim for 40, not 60+)
- Employee stress/satisfaction surveys
- Turnover rate (calm = retention)
- Profitability per employee (not just revenue growth)
### 5. Resist Growth Pressure
- Define "enough" (revenue, team size, market share)
- Say no to features, customers, opportunities
- Maintain profitability over hypergrowth
- Optimize for sustainability, not exit
## Anti-Patterns
**Async Theater**: Calling meetings "async" but expecting instant responses
**Scope Creep**: Extending cycles when features aren't done (defeats the constraint)
**Remote Surveillance**: Tracking keystrokes/screenshots (antithesis of trust)
**Infinite Growth Mindset**: Adopting practices but chasing VC-style scale
**Cherry-Picking**: Taking "remote work" but ignoring "calm company" foundation
## Quality Indicators
**High Signal**:
- 40-hour weeks are norm, not aspiration
- Profitability without external funding
- Low turnover (people stay 5+ years)
- Shipping regularly without burnout
- Decisions documented in writing
**Low Signal**:
- "Flexible hours" means "always available"
- Async tools used for synchronous pestering
- Growth rate prioritized over profitability
- Constant firefighting and urgency
- Undocumented tribal knowledge
## Related Frameworks
- **Shape Up**: Basecamp's product development methodology
- **Getting Real**: Earlier 37signals book on product development
- **Remote**: Basecamp book on remote work practices
- **It Doesn't Have to Be Crazy at Work**: Calm company philosophy
- **ROWE (Results-Only Work Environment)**: Similar autonomy-focused approach
## Scoring (42/50)
- **Practitioner Weight** (9/10): 20+ years of actual practice at Basecamp
- **Clarity** (9/10): Extensively documented in books and blog
- **Proven ROI** (8/10): Profitable, sustainable company for decades
- **Novelty** (6/10): Counter-cultural but increasingly recognized
- **Applicability** (10/10): Applicable to any knowledge work company
## Sources
- Jason Fried & David Heinemeier Hansson: Rework (2010)
- Jason Fried & DHH: Remote (2013)
- Jason Fried & DHH: It Doesn't Have to Be Crazy at Work (2018)
- Ryan Singer: Shape Up (2019) - Product development methodology
- Signal v. Noise / HEY World blog (ongoing)
- Basecamp public handbook
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!