FM-06 // OPERATIONS
Tools We Use
Updated Jan 15, 2025 · Contributors: nikhil
Table of Contents
Communication
| Tool | Purpose |
|---|---|
| Slack | Real-time messaging, quick questions, social |
| Notion | Long-form docs, specs, meeting notes, knowledge base |
| Loom | Async video walkthroughs and demos |
| Google Meet | Video calls when sync communication is needed |
Engineering
| Tool | Purpose |
|---|---|
| GitHub | Code, PRs, issues, CI/CD (Actions), project tracking |
| VS Code / Cursor | Primary code editors |
| Linear | Issue tracking and sprint planning |
| Figma | Design files and prototypes |
Infrastructure
| Tool | Purpose |
|---|---|
| AWS | Cloud infrastructure (ECS, RDS, S3, Lambda) |
| Terraform | Infrastructure as code |
| Datadog | Infrastructure monitoring and APM |
| PagerDuty | On-call alerting and incident management |
Business
| Tool | Purpose |
|---|---|
| HubSpot | CRM, marketing automation, forms |
| Stripe | Payments and billing |
| Deel | Payroll and contractor management |
| Google Workspace | Email, calendar, drive |
Adding New Tools
Before adding a new tool:
- Check if an existing tool can solve the problem
- Consider the security and compliance implications
- Discuss with the team - others may have experience with alternatives
- Prefer tools with SSO/SAML support for security
- Document the tool’s purpose and admin ownership in this page
We avoid tool sprawl. Every new tool adds cognitive overhead, another login to manage, and another vendor to evaluate for security. The bar for adding something new is intentionally high.