Chat vs. Cowork vs. Claude Code: which one, when

Founders often assume Chat, Cowork, and Claude Code are different products with different capabilities. They’re the same Claude — the difference is how much of the work happens in one step versus several, and how much you review along the way.

Chat — you ask, it answers, you decide what happens next, every single time. This is where most of a founder’s actual judgment calls belong: sensitive communication, strategy, anything where you want to stay in the loop at every step.

Cowork — for anything that needs more than one step, needs to remember context across a Project, or needs to touch a connected tool like your inbox or calendar. More power than chat. Earn it by working in Chat first, until you’ve watched Claude get things right a few times.

Claude Code — for anything that touches real files: your codebase, a landing page, a folder of documents on your machine. It remembers your project via a CLAUDE.md file and edits files in place with a diff you review, instead of handing you a new blob of text.

The practical rule: start in Chat. Move to Cowork once a task needs to run more than once or reach into another tool. Move to Claude Code once a task actually needs to touch files. You don’t need to pick one forever — most founders end up using all three, for different jobs.

The 90-day roadmap walks through exactly when to cross each bridge.