Projects, Artifacts, Research, Cowork, and Code

Think of Claude as one building. Chat is the lobby: everyone arrives there, and plenty of work finishes there too. But the building has five more rooms, and each exists because the lobby is bad at exactly one thing. Chat forgets, so there is a records room. Chat cannot cite what it has not read, so there is a library. Chat produces messages, not deliverables, so there is a showroom. Chat needs you present, so there is a studio that works alone. And chat cannot ship software, so there is a workshop.

Walk the floor

Click into each room. You are not learning features, you are learning which kind of work goes through which door.

Every room is reachable from the lobby’s message box. Nothing here is a separate product to log into. It is the same account, the same building, one click apart.

One deliverable, whole building

Rooms make sense in isolation, but real work uses several at once. Here is a quarterly competitive brief passing through the building.

Project: Q3 competitive brief

Research gathers

A cited report on what the four competitors changed this quarter lands in the project.

Chat shapes

You argue with the findings, cut what does not matter, and settle the storyline.

Artifact ships

The brief becomes a polished document with a share link the leadership team can open.

Cowork

Next quarter, the whole pipeline runs as a scheduled task while you are in meetings. You review instead of assemble.

Code

If the brief needs a live data pull from your systems, the workshop builds the tool once and it works forever.

The project is the floor everything sits on. Because the research, the argument, and the artifact all live in one workspace, nothing gets re-explained, and the next brief starts smarter than the last one.

Prove you can route

Eight jobs are about to hit your desk. Send each one to the right room. First instinct, no overthinking.

If you misrouted one or two, look at which direction you missed. Sending chat-sized work to heavyweight surfaces wastes minutes. Sending heavyweight work to chat wastes the surface: you become the project memory, the file mover, and the scheduler that Claude would have been.

Where the deep dives live

Each room gets a full section of its own later in this course.