Claude Code for startups: 15 companies, 5 rules, and a roll-out checklist

Key takeaways

• Let the person who owns the problem build the 0→1. Marketers, legal, sales, and doctors can produce working prototypes; engineering, design, security, and compliance review and productize them.
• Automate mechanical tasks with checkable results first. PR review, bug triage, test fixes, coverage completion, incident triage, and batch data analysis all have clear inputs and verifiable outputs.
• Agent permissions should be gated by validation capability. CLAUDE.md stores rules, Loops handle repeatable execution, Hooks provide hard gates, and evals plus human escalation catch drift and block regressions.
• Keep the cost of rebuilding low. Worktrees isolate old and new versions, Plan Mode reviews the approach first, the same evals gate the merge, and the old path is deleted after migration.
• Productize only after internal validation. Teams run internal agents on real data, permissions, and workflows first; then decide what to expose to customers based on the failure record.

How 15 companies put Claude Code to work

The same tool landed in very different places across these 15 companies: some let lawyers and marketers build products directly, some handed testing, code review, and on-call to agents, some rebuilt their eval systems, and others used Claude Code to design their own AI products.

15 companies

5 RULES / 15 TEAMS

15 companies, five rules in action

Click a company to see details; click a rule to filter matching teams. All 15 companies are shown by default.

All 15 01 Everyone ships 02 Automate 03 Verify 04 Rebuild 05 Productize

Artemis Security02 · 03 Cainex03 Clay01 · 02 · 04 ClickHouse02 · 05 Cognition04 Commure02 · 04 Crosby01 · 02 Emergent01 · 02 · 05 Harvey04 Heidi01 · 02 Higgsfield03 Omni01 · 02 · 05 Parahelp01 Translucent01 · 02 Zingage03

02 · 05ClickHouse

30% more features shipped

Two test agents are the repo's 2nd and 3rd largest contributors; the team also uses Claude Code to iterate on the SQL console agent and AI SRE.

1. Artemis Security6,000+ PRs / week。Offload mechanical work to agents, while using test infrastructure, codebase organization, and team knowledge systems to support end-to-end delivery.
2. CainexMedical coding verification loop。Auditors check coding and reasoning, log corrections by error type; Claude Code revises general principles, then runs the golden set and random samples.
3. Clay100% automated bug triage。Quarterly reviews move non-technical employees' prototypes into the roadmap; the Bug Agent handles initial screening through code change suggestions, and repeatedly rebuilds the same feature.
4. ClickHouse30% more features shipped。Two test agents are the repo's 2nd and 3rd largest contributors; the team also uses Claude Code to iterate on the SQL console agent and AI SRE.
5. Cognition6–12 month system lifespan。Assume today's AI systems may be obsolete within half a year to a year, and design architecture ahead of future model capabilities.
6. Commure~13 tickets in parallel。Subagents own tickets and PRs; another Skill automatically scans and deletes feature flags and old code that have been fully released.
7. CrosbyThousands of legal docs summarized in parallel。Integrate Claude Code into tools lawyers already use, let lawyers prototype products directly, and use subagents to batch-process legal materials.
8. EmergentMarkdown completes first-day environment setup。New hires have Claude read a Markdown file to set up the environment; a shared Skills repo stores database, schema, and company context.
9. HarveyPlatform architecture redone for new model capabilities。Each wave of reasoning, automation, planning, and orchestration improvements triggers a platform redesign; discard old architecture when needed.
10. HeidiDomain experts PR directly + compliance review。Those who know the problem best submit the first PR; automated review then checks against established technical and compliance frameworks, flags critical issues, and routes them to specialized reviewers.
11. HiggsfieldModel integration: days → hours。New video and image models need Skills, evals, routing, and tests before production; Claude Code compresses this integration into the same working session.
12. Omni2–3× engineering productivity。Show prototypes to the whole team in Slack, let engineers join customer interviews; the product side borrows file-based context and parallel harnesses.
13. ParahelpNon-technical roles ship UI directly。While engineers accelerate, non-technical co-founders also start submitting UI changes and other product improvements directly.
14. TranslucentMulti-perspective code review + agent marketplace。Internal review agents check the same change in parallel and merge conclusions; engineering, delivery, and sales each use dedicated agents.
15. Zingage567 lines of team invariants。When Claude's code looks plausible but strays from the architecture, the team writes down the problem framework, invariants, and proof methods to constrain every session.

Rule One: hand the 0→1 to the people who know the problem best

“Everyone ships” opens the door to working prototypes and first-pass PRs. Marketers, legal, sales, and doctors can turn their domain knowledge into a runnable approach; designers, engineers, security, and compliance handle their own specialties.

Thomas Kelly, co-founder of Heidi, calls the old process a “game of telephone”: the person with the idea tells the product manager, who tells the designer, who passes it to the engineer. Weeks later, the delivered result can drift far from the original problem. With Claude Code, the problem owner creates the PR first, then brings in design and engineering for experience, architecture, and production readiness.