# 6,000+ PRs a Week, Automated! 15 Fast-Growing Startups Share Their 5 Rules for Claude Code

Hi, it's me, Shiichan! Today I've got some genuinely practical know-how from the Claude blog.

## What was announced?

The Claude blog published "The Claude Code Guide for Startups," distilled from interviews with 15+ fast-growing startups building their products with Claude Code. These companies are described as shipping at roughly 10x the pace you'd expect for their size.

## Why it matters

The guide boils down five operating principles these companies share:

- Everyone ships: connecting Claude to existing tools via MCP (Model Context Protocol) and sharing skills across teams lets non-engineers build features too. Domain experts like lawyers or clinicians can prototype directly, without going through an intermediary
- Automate the tedium: running agents across the entire development lifecycle to automate code review, testing, and CI/CD — the idea being that "agents own the mechanical 80% so engineers spend time on judgment calls"
- Trust, but verify: agents propose fixes, subject matter experts review them with the reasoning visible, corrections get fed back as principles rather than one-off patches, and backtesting guards against regressions
- Build for rebuilding: since model capabilities keep shifting, code isn't treated as permanent — teams embrace continuous rebuilding, using git worktrees for parallel versions and plan mode to get team sign-off on a rebuild approach before implementation
- Prototype, dogfood, productionize: the experience of building with AI feeds directly into designing products for AI — the more internal know-how a team builds using agentic tools, the better their customer-facing agent design becomes

## What changes

The guide backs this up with concrete results:

- ClickHouse: shipped 30% more features, with Claude's agents becoming the #2 and #3 contributors to the repo
- Omni: 2-3x engineering productivity
- Clay: 100% of bug triage automated
- Artemis Security: 6,000+ PRs processed weekly

## Dive Deep

The guide also includes a practical checklist:

- Connections: use MCP or the CLI to connect Claude directly to databases and tools, instead of copy-pasting
- Automation: deploy Code Review (research preview) on repositories and integrate Claude Tag into CI/CD on-call response
- Verification: encode architectural invariants in a root CLAUDE.md, use loops that iterate until a stop condition is met, and maintain a "golden set" evaluation dataset
- Rebuilding: isolate parallel versions with git worktrees, and catch architectural drift early with plan mode
- Spreading it: use Skills as an internal plugin marketplace for sharing best practices across the company

## Wrap-up

- A guide distilled from interviews with 15+ fast-growing startups building on Claude Code has been published.
- It covers five principles: everyone ships, automate the tedium, trust but verify, build for rebuilding, and prototype/dogfood/productionize.
- It's backed by concrete numbers, like ClickHouse's 30% jump in shipped features and Artemis Security's 6,000+ weekly PRs.
- A checklist covers connections, automation, verification, rebuilding, and spreading best practices.
- A ready-to-use practical guide for startup engineers who want to seriously weave Claude Code into their development workflow.