Claude is not one tool — it is four. Cowork for daily operations with files. Chat for reasoning and long conversation. Code for groups with a technical team. Design for visuals with text: slides, prototypes, one-pagers. Open the wrong one and you spend twice the quota for half the result.
The difference between someone who genuinely gets value from AI in hospitality and someone who uses it as decoration is knowing what to ask of which — and which tool to ask nothing of, because it does not do it.
01 — Why choosing well matters
The wrong tool costs you quota, time and outcome
When you start using Claude seriously, the first mistake is usually treating its tools as if they were the same thing with a different interface. They are not. Each has its own limits, its own model underneath and its own way of working.
Design, for example, has a quota separate from Chat and it burns through much faster. In my own experience, a single foundational task — uploading the design system — can take a large share of the weekly allowance.
02 — The four tools
Cowork, Chat, Code and Design
Cowork
Agentic tasks with files and a persistent environment. It is the tool I am writing this post in right now — I write it, but it organises it, lays it out in HTML and drafts it straight into my website. It connects directly to a folder on your computer, reads files, edits them, runs code in a safe box and uploads things to your connected apps. Built for non-developers who want to automate file work.
What it is for in hospitality: organising folders with hundreds of PDF invoices, drafting and publishing a blog post, generating spreadsheet templates for your P&L, filling in a certification PDF with your staff data, producing a monthly report crossing your POS and your booking system. Any flow that touches your actual files.
And above all, for creating skills that automate your life. But that is another subject for another post.
Chat
Conversation and fast reasoning. It is what most people know as «Claude» — the claude.ai tab where you write and it answers. Memory by Project: you can, and should, create spaces where Claude remembers context across different conversations, which lets you build a stable adviser on a specific topic.
What it is for in hospitality: ideating a new menu, drafting an email to a supplier or a partner, preparing notes for an interview, writing a brand brief, ordering the notes from an audit you did by hand. Everything that does not need to touch your files directly.
Code
A command line for developers. If your group has a technical team writing code — your own booking system, custom integrations with your POS, a website built from scratch — this is where it belongs.
What it is for in hospitality: for the average operator with no technology team, it is probably not today’s tool. Although it is not that hard either — I use it the most and I am not a developer. For medium and large groups with developers on staff it is vital, but that chapter is written by your CTO, not by this series.
Design
An Anthropic Labs product, still in research preview. It generates interactive prototypes, presentations, one-pagers and mockups with text. It reads your design system — colours, typography, components — and applies your identity automatically. It accepts text, images, DOCX, PPTX, XLSX, code and screenshots of your own website as input.
What it is for in hospitality: the pitch for a proposal to an investor, the deck presenting a new concept to a client, the one-pager to send a journalist, the design of the new menu before printing, restaurant signage ready to print.
03 — What none of the four does
Images and video from scratch: for that, go outside Claude
This is a structural limitation, not a prompting problem: no Claude tool — Cowork, Chat, Code or Design — generates images or video from scratch as things stand. I tried it in Chat. I tried it in Design. Both failed because they are not built for it, and Claude itself told me so on the first attempt. It will do it, but badly.
That honesty is one of the things I respect most about the tool. When an AI tells you «I am not the tool for this, go to that other one», you can let it work with confidence on what it does do. And it saves you hours of prompting for something that was never going to come out.
04 — The operational map
Which tool for which task on a normal day in hospitality
So that it does not stay theoretical, here is the direct translation: concrete tasks an operator does every week, and which tool to open for each.
- A difficult email to a supplier, partner or the team: Chat, with the Gmail connector — it leaves it ready in your drafts.
- Ideating a new menu or tasting menu: Chat, ideally inside a Project with your context loaded.
- Designing that menu once briefed: Design.
- Reorganising a folder with hundreds of PDF invoices: Cowork.
- Processing your P&L spreadsheet and pulling out analysis: Cowork.
- The monthly report crossing POS, bookings and costs: Cowork, with connectors active.
- A pitch to an investor or client: Design, as a deck or one-pager.
- A mockup of how new printed signage will look: Design.
- A logo or a dish photograph from scratch: outside Claude.
05 — For your restaurant
Three rules of quota and judgement
- Start with Chat. If Chat solves the task, do not open Design or Cowork. Save the quota. Cowork and Design are worth gold — spend them on what only they can do.
- Reserve Design for what only Design does. Any visual with text and identity: investor deck, press one-pager, menu prototype. A single foundational task can take a large share of your weekly allowance, so plan before you start.
- Claude’s honesty is a feature, not a bug. If the tool tells you «I am not the tool for this», believe it and redirect the flow. That is worth more than any magic prompt. Ask it to recommend other tools and it will.
The restaurateur who knows how to choose the tool for the task will get four times the output of the one who always opens the same one. Not by using more AI — by using it with judgement.
