What ClickHouse, Omni, and Clay Actually Changed to Ship Like a Bigger Company

Anthropic’s new startup guide, drawn from interviews with more than a dozen fast-growing companies including ClickHouse, Omni, Clay, and Artemis Security, names five operating principles behind teams it says are “shipping like organizations ten times their size.” ClickHouse reports shipping 30% more features; Omni reports a 2-3x engineering productivity gain; Clay says it has automated 100% of its bug triage. The five principles: “everyone ships” — lowering the bar for non-engineers to contribute code directly; “automate the tedium,” letting agents absorb the mechanical bulk of engineering work; “trust but verify,” building monitoring around agent output instead of assuming it’s correct; “build for rebuilding,” treating code as more disposable given how fast coding-agent capability is moving; and a prototype-dogfood-productionize development cycle.

That last principle — code as disposable — isn’t a hypothetical. Anthropic’s own case study from July describes Bun co-founder Jarred Sumner using Claude Code to migrate roughly a million lines of Bun from Zig to Rust in under two weeks, with 100% of Bun’s existing test suite passing before merge and only 19 post-merge regressions, all since fixed. Separately, Anthropic Labs co-lead Mike Krieger migrated a Python codebase to 165,000 lines of TypeScript over a weekend; the payoff showed up in build times, with per-platform compile dropping from roughly 8 minutes to about 2 seconds. Migrations that used to be multi-year, career-risk bets are now weekend-scale decisions.

Gartner is already putting a structural number on where this heads: Principal Analyst Aliyah Camacho projects 60% of organizations will run smaller software engineering teams by 2029, up from roughly 15% today, as routine execution shifts to AI and engineers concentrate on architecture and judgment calls. Camacho frames it as a redesign of team composition, not primarily a cost cut.

For consulting engagements advising engineering leadership on agentic-coding adoption, the throughline across all three sources is the same: the tooling is the easy purchase. The organizational redesign — who ships, what gets automated, how output gets verified — is the actual engagement.