Popular use cases

In this section, we share seven of the most common ways knowledge workers use Cowork, from research synthesis and meeting prep to inbox triage and catching up after time away. Each follows the same shape: the situation, what to ask Cowork, what you'll get back, and tips to get better results. The named roles are illustrative, but the patterns generalize across a wide range of work.

Turning a messy folder of research into a synthesized brief

A competitive intelligence analyst at a mid-market SaaS company has spent three weeks collecting articles, PDFs, screenshots, and notes about the competitive landscape. She needs a two-page brief for the product leadership meeting tomorrow.

What to ask Claude Cowork

I've connected the ~/Research/competitive-landscape folder. Read everything in it, then write a two-page brief for our product leads covering: (1) the three most important trends, (2) what each competitor is doing differently, (3) where we have the biggest gaps, and (4) two recommendations. Cite the source file for each claim. Save as competitive-brief.md in the same folder.

What you'll get back

A structured markdown brief in the folder you specified, with inline citations tying each point back to a source file. Claude Cowork will usually ask a clarifying question or two — about audience, length, or which sources to prioritize — before starting.

Tips

Tell Claude Cowork the reader and the decision the brief should support, not just the topic. Ask for citations from the start; retrofitting them is painful. If the folder is large, ask Claude Cowork to share its plan before diving in so you can correct course early.

Preparing for a meeting using scattered context

A partnerships lead has a quarterly review with a customer in 90 minutes. The relevant context is spread across a Gmail thread, two Slack DMs, a co-edited Google Doc, and her notes from the last meeting.

What to ask Claude Cowork

I have a meeting at 2pm with Sarah Chen from Acme about the Q3 partnership review. Pull together: (1) the most recent thread with her in Gmail, (2) our last two Slack exchanges, (3) the shared doc titled "Acme partnership Q3," and (4) my calendar notes from our previous meeting. Give me a one-page prep doc with the three things I should go in knowing and the two open questions to raise.

What you'll get back

A prep doc that threads together the relevant context from each source, with links back to the originals. Claude Cowork will tell you if any source was inaccessible — for example, if Gmail isn't connected yet.

Tips

Name the people, the topic, and the timebox. The more specific you are about what decision the meeting is about, the more useful the synthesis. Asking for the "top three" rather than a dump forces better prioritization.

Drafting a recurring report from source files

An engineering manager writes a weekly update every Friday. The content comes from the same places each time: an Asana board, a metrics CSV the data team publishes, and a blockers channel in Slack.

What to ask Claude Cowork

Draft this week's eng update in the format of ~/Reports/weekly-template.md. Pull shipped items from my Asana "Done this week" section, key metrics from the CSV at ~/Reports/metrics.csv, and blockers from the #eng-blockers Slack channel since Monday. Save as weekly-update-2026-04-10.md.

What you'll get back

A filled-in draft matching your template's structure, grounded in real files and real messages.

Tips

Build the template once and reuse it every week. Use scheduled tasks (opens in new tab) to have Claude Cowork start the draft automatically every Friday morning so it's waiting for you.

Inbox triage with context

A chief of staff returns from a long weekend to 120 unread emails. Some need immediate responses, some can wait, some can be archived, and a few need to be escalated.

What to ask Claude Cowork

Go through my unread Gmail from the last 72 hours. Categorize each thread as "needs a response today," "can wait a week," "FYI only," or "escalate to [exec]." For each "needs a response today," draft a two-sentence reply in a separate file I can review before sending. Don't send anything — just draft.

What you'll get back

A triage summary plus a file of draft replies. Claude Cowork will never send email on your behalf without explicit confirmation on each send.

Tips

Give Claude Cowork a quick rundown of the people and projects that matter before it starts triaging. A line like "anything from the board or referencing a sales pipeline dashboard should escalate to me first" helps it sort signal from noise far more accurately than category rules alone. Without that context, Claude has to guess at importance from sender domains and subject lines, which works for obvious cases but misses the nuance.

Building a project plan from a kickoff doc

A marketing ops lead just finished a website-redesign kickoff. The notes are messy, the scope is half-defined, and she needs a plan by tomorrow morning.

What to ask Claude Cowork

Read ~/Projects/website-redesign/kickoff-notes.md. Turn it into a project plan with milestones, task breakdown under each milestone, owners (use the names mentioned in the notes), a rough timeline assuming a six-week delivery, and a risks section. Output as both a markdown doc and a CSV.

What you'll get back

Two files: a readable plan for humans and a structured CSV for your tracker. Claude Cowork will flag anywhere the kickoff notes were ambiguous rather than inventing details.

Tips

Ask for the ambiguity list explicitly ("flag anything you had to guess"). Resolving five clarifying questions up front is faster than catching invented details later.

Comparing options across documents

A finance analyst has five vendor proposals for a new analytics tool. She needs a head-to-head comparison and a short recommendation for her director.

What to ask Claude Cowork

In ~/Vendors/proposals there are five PDFs from different analytics vendors. Extract from each: price, implementation timeline, what's included, what's extra, SLAs, and references. Produce a comparison table as an .xlsx file and a short written recommendation explaining which two I should shortlist and why.

What you'll get back

A spreadsheet with one row per option and one column per criterion, plus a written rationale. Claude Cowork will note where a proposal was silent on a criterion rather than guessing.

Tips

Define your criteria up front. If you don't, Claude Cowork will pick reasonable ones—but they may not be your reasonable ones.