Most “how to use Claude Cowork” guides on the open web are either Anthropic’s own setup walkthrough or a six-month-old generic overview that predates everything Cowork can actually do today. This one is different. It’s a workflow library — twelve specific recipes you can paste into Cowork tonight and run before Monday morning.
The selection is biased toward two things: workflows that have been validated in public by people running real businesses (with the X posts and like counts to prove it), and workflows that pay back the time spent setting them up within the first week. Anything that takes more than 30 minutes to set up has a payoff column explaining why.
If you’re new to Cowork entirely, the Claude Cowork starter guide covers what Cowork is and how to get it installed. This post assumes you have it open and you’re looking for the next thing to do with it.
Quick refresher on the four building blocks
Every workflow below uses some combination of four pieces. If you remember nothing else, remember these:
| Block | What it is | Where you set it up |
|---|---|---|
| Connectors | OAuth integrations with apps (Gmail, QuickBooks, HubSpot, Slack, Notion) | Cowork sidebar → Connect apps |
| Skills | Reusable instructions that wrap a specific task (e.g., “summarize a meeting transcript”) | Skills panel inside the project |
| Plugins | Bundled skills + connectors for a domain (Small Business plugin, Legal plugin) | Cowork toggle area |
| Scheduled Tasks / Routines | Tasks that run on a schedule, even when your laptop is asleep (Routines) | Schedule tab on a task |
The interesting part of Cowork — the part that’s different from ChatGPT or generic Claude — is that workflows can chain these together. A scheduled task can call a skill that uses a connector that pulls data from another app and saves the result as a file in your project folder. That’s where the time savings come from.
OK, the workflows.
Workflow 1: The Monday Morning Brief
Where it shines: founders, ops leads, agency owners. You open your laptop on Monday and a one-page brief is already sitting in your project folder, summarizing cash position, pipeline movement, last week’s metrics, and this week’s commitments.
Setup: Connect QuickBooks (or your accounting tool), HubSpot (or your CRM), Google Calendar, and your team Slack. Create a project called “Monday Brief.” Add this as a scheduled task that runs every Sunday at 7 PM:
Generate this week's Monday brief and save as monday-brief-{date}.md in this project.
Include:
1. Cash position from QuickBooks (current balance, net last 7 days, vs same week last year)
2. Sales pipeline summary from HubSpot (opportunities created, opportunities closed, total pipeline value)
3. Calendar overview for the next 5 days (recurring meetings excluded, surfacing only "decision-required" items)
4. Three things that would change my Tuesday-Thursday focus if I knew them now (look at unread Slack from #leadership and #ops)
5. One question to bring to my exec team meeting
Keep it under 400 words. Plain bullets. No corporate language.
Payoff: 15-20 minutes of Sunday-night anxiety becomes 0 minutes. The post that made this workflow famous is from Mike Futia (@mikefutia on X) showing a Meta Ads version with 613 likes — the principle generalizes to whatever data sources you actually run on.
Workflow 2: Bookkeeping + Tax Prep with a Context.md File
Where it shines: solo founders, freelancers, small business owners who spend 6-8 hours a year doing bookkeeping for taxes.
JJ Englert (@JJEnglert, 495 likes) shared the cleanest version of this on X earlier this year. The trick is the Context.md file — a briefing doc that lives in the project folder and tells Claude everything it needs to know without you re-explaining each time.
Setup: Create a folder called “Taxes-2026,” dump in your W-2s, 1099s, bank statements, mortgage docs, business P&L. Point Cowork at the folder. Then run this prompt:
Help me set up a bookkeeping workspace for my taxes. Organize the documents I've uploaded into a logical folder structure.
Then create a Context.md file by reading through my documents and pulling out my filing status, income sources, business entities, tax preparer info, key numbers, and open questions.
After that, help me build a plan for what documents I still need to gather and what working documents we should create together to prepare for filing. Include a CSV file showing my P&L for the year, with an expenses tab categorizing all my write-offs and an income tab showing my income sources.
Cowork will sort the documents, build the Context.md, generate the spreadsheet, and flag the docs you’re missing. Save 6-8 hours of work and walk into your accountant appointment with a one-page brief instead of a pile of paper.
Workflow 3: Month-End Close
Where it shines: solo CPAs, bookkeepers, controllers at small companies.
This is the operationally heaviest workflow on the list, but the payoff is the largest — for many small finance teams, month-end close is two solid days of work that this workflow compresses to about three hours of supervision.
Setup: Connect QuickBooks, your bank accounts (via Plaid or direct), and PayPal/Stripe. Create a project called “Close-{Month}.” Run:
Run the close for {month}. Steps:
1. Reconcile QuickBooks bank feed against actual bank statement. Surface any line items that don't match (amount, date, or category). Create reconciliation-issues.csv with one row per discrepancy.
2. Reconcile QuickBooks against PayPal settlement reports. Same output format.
3. Categorize uncategorized transactions using the rules in close-rules.md (which I've added to this project). Surface any transaction over $500 that doesn't match a rule for my manual review.
4. Generate the P&L for the month. Compare against the prior month and surface any line item that moved more than 25%. Write a 2-paragraph plain-English explanation of what changed.
5. Generate the accountant packet PDF: P&L + balance sheet + cash flow + notes on flagged items.
Pause after step 1 for me to approve the reconciliation issues before fixing.
The pause-for-approval is doing real work here — Cowork won’t auto-fix discrepancies you haven’t seen. The approval gate is the only reason this is safe to run on real client books.
Workflow 4: Invoice Chaser
Where it shines: anyone who invoices clients and watches money sit in “overdue” for too long.
Setup: Connect QuickBooks (or Stripe, or your invoicing tool) and Gmail. Add to a Cowork project as a scheduled task running every Tuesday morning:
Pull every overdue invoice from QuickBooks. For each:
1. Calculate days overdue
2. Check Gmail for any reply from the client about payment in the last 14 days
3. Categorize the invoice into: 0-7 days late (gentle nudge), 8-21 days (firmer follow-up), 22+ days (escalation)
4. Draft a follow-up email in my voice (read past sent invoices to learn my tone) but DO NOT SEND. Save each draft as a .md file in the chase-{date}/ folder.
For invoices over 30 days late, also draft a one-paragraph internal note about whether to escalate to a collections call.
Payoff: typical small-business owner saves 1-2 hours a week on collection follow-ups and recovers about 8-15% more of their AR within 60 days because the chase actually happens consistently.
Workflow 5: Meta Ads Creative Brief
Where it shines: DTC brands, performance marketing teams, agencies running paid social.
This is the second Mike Futia workflow (different post, 707 likes). It runs Cowork against Meta Ads Manager + the public Meta Ad Library to produce a weekly creative brief.
Setup: Connect Meta Business (via the Meta connector) and a Google Drive folder for creative briefs. Add scheduled task running every Friday afternoon:
Run the weekly creative brief.
1. From Meta Ads Manager, pull this week's performance for every active creative. Identify the top 3 by ROAS and the bottom 3 by CTR (excluding any creative live less than 5 days).
2. For each top creative, write a 2-sentence analysis: what's the hook, what angle is it leaning on, what's the CTA pattern.
3. Open the Meta Ad Library and check 5 named competitors (list in /context/competitors.md). For each, screenshot any new creative shipped in the last 7 days and note the angle.
4. Write 5 fresh hook variations for the top 1 winning creative, segmented by buyer awareness (cold, warm, retargeting).
5. Save everything as creative-brief-{week}.md in this project. Include a "ship by Tuesday" priority list at the bottom.
Payoff: a typical 3-person agency creative team gets 4-6 hours back per week. The brief that used to require pulling reports, opening Ad Library tabs, screenshotting, and writing from scratch is just done.
Workflow 6: Flight + Hotel Booking
Where it shines: anyone who travels for work more than three times a year.
This one made the rounds in early May after Boris Cherny (@bcherny, 3,016 likes) showed Claude Opus 4.7 booking 8 flights and 5 hotels for him in one Cowork session while he worked on something else.
Setup: Save your flight + hotel preferences as travel-prefs.md in a Cowork project. Include things like: preferred airlines, status numbers, seat preferences, hotel chains you have status with, baseline budget per night, deal-breakers (no red-eyes from EWR, etc.).
Book the following trips. Use travel-prefs.md for my preferences. Pause for my approval before each purchase confirmation:
1. SF → Austin, June 14-18, 2 nights at downtown property
2. Austin → NYC, June 18-21, near East Village
3. NYC → SF, June 21 evening
For each: present 3 flight options (cheapest, fastest, best on schedule), 3 hotel options, then your pick with a 1-sentence reason. After I approve, complete the booking and save the confirmation PDFs to /trips/june-2026/.
The “pause for approval before each purchase” is the only thing standing between you and an unintended $4K charge. Don’t remove it. Anthropic has been clear that purchases without confirmation are not the design, but the agent will optimize toward speed if you let it.
Workflow 7: Inbox Triage
Where it shines: anyone with a noisy inbox and bad email habits.
Setup: Connect Gmail. Save common email categories to email-rules.md in the Cowork project. Add a scheduled task running every weekday morning at 7 AM:
Triage my inbox for the last 24 hours. For each unread email:
1. Categorize into: needs-reply-today, needs-reply-this-week, FYI, spam-or-marketing, newsletter
2. For "needs-reply-today" — draft a reply in my voice and save the draft to the Gmail draft folder. Do not send.
3. Archive everything in the FYI and spam categories without my review.
4. Build a 5-bullet morning summary: how many emails came in, how many got drafted replies, anything urgent I should know about, anything from a specific sender list (in email-rules.md → "always-flag").
Save the summary as inbox-{date}.md in this project.
This is the workflow most readers will start with because it has the lowest activation cost (one connector, one rules file) and the daily payoff is immediately visible.
Workflow 8: Sales Lead Triage
Where it shines: solo founders running their own outbound, small sales teams without a full SDR layer.
Setup: Connect HubSpot (or your CRM) and Gmail. Add as a scheduled task every Monday and Thursday morning:
Triage new inbound leads from the last 4 days.
1. Pull every new contact from HubSpot with a last-touch in the past 4 days
2. For each, score on three dimensions: company fit (using ICP.md), buying signal strength (using signal-rules.md), and engagement (last 7 days of email opens + meetings)
3. Categorize into: hot (book this week), warm (sequence), cold (nurture), disqualify
4. For "hot" — draft a personalized outreach email in my voice. Save as draft in HubSpot. Do not send.
5. Update the CRM stage for any contact whose stage hasn't moved in 14 days, based on the most recent engagement signal.
Surface the top 5 hot leads as a one-page brief at lead-brief-{date}.md.
The pause-and-draft pattern is doing real work here too. You’re getting an SDR’s worth of triage and a draft library; you’re not getting auto-sent emails to your prospects without your eyes on them.
Workflow 9: Content Brief from Competitor Scrape
Where it shines: content marketing managers, SEO teams, agency content leads.
Setup: Save a list of competitors and their blog URLs in competitors.md. Connect Google Drive. Run as needed:
Generate this week's content brief.
1. Visit each blog URL in competitors.md and pull every post published in the last 14 days
2. Bucket the topics by theme. Surface any theme that 3+ competitors have covered (signals search demand)
3. For each theme, check if we have an existing post on the topic (search /content-archive/). If yes, surface as a refresh candidate. If no, surface as a net-new candidate.
4. For the top 3 net-new candidates, draft a brief with: target keyword, suggested angle, 5 H2s, 3 sources to cite, internal links to add.
5. Save as content-brief-{week}.md in /briefs/.
This is the workflow that most clearly replaces a junior team member’s research week. Use the time you save to actually write better posts, not to do more triage.
Workflow 10: Slack Decision Log
Where it shines: distributed teams where decisions get buried in channels and nobody can find them later.
Setup: Connect Slack. Add as a scheduled task every Friday afternoon:
Build this week's decision log from Slack.
1. Scan #leadership, #product, #engineering for any thread that contains a decision (look for words like "we decided," "going with," "approving," "let's ship," explicit acceptance of a proposal)
2. For each, extract: the decision, the people involved, the date, the trade-off if mentioned, the link to the source thread
3. Append to /decisions/decisions-log.md (don't overwrite)
4. Cross-reference against any existing decisions and flag any contradictions for human review
Output a one-page weekly summary as decisions-week-{date}.md.
Payoff: less catastrophic than the others, but the long-tail value is real — six months from now, when somebody asks “why did we choose Postgres over MySQL?”, the answer is searchable.
Workflow 11: Contract Review Against Your Playbook
Where it shines: solo lawyers, in-house legal at small companies, anyone who reviews vendor contracts on a recurring basis.
Setup: Save your firm or company’s playbook as playbook.md in the project folder (clauses you require, clauses you reject, fallback positions). Connect DocuSign (or whatever contract system you use).
Review the attached vendor contract against playbook.md.
For each clause in the contract:
1. Identify which playbook section applies (or none)
2. Score: green (matches our standard), yellow (deviates but acceptable), red (must be changed)
3. For yellow and red, draft the markup language we'd send back, in our standard contract voice
4. Generate a one-page summary memo for my partner review
Save as contract-review-{vendor}-{date}.md. Do not auto-send anything to the vendor.
This is the workflow that maps almost 1:1 to the new Claude for Legal “playbook ingestion” agents that shipped this week. If you’re a Pro user, you can run this now without the legal plugins. If you toggle on the legal plugins, you get a more domain-tuned version of the same prompt.
Workflow 12: Personal Project File Cleanup
Where it shines: anyone whose Documents folder is a graveyard of “untitled (3).docx” and screenshots from 2023.
Setup: Point Cowork at your ~/Downloads, ~/Desktop, or ~/Documents folder. Run as a Friday-afternoon scheduled task:
Clean up my Downloads folder.
1. Move screenshots into ~/Documents/Screenshots/ organized by month
2. Move PDFs into ~/Documents/PDFs/ if they're documents I might need to find later. Trash any obvious one-time-use PDFs (boarding passes from past trips, receipts I've already processed).
3. Move any installer (.dmg, .pkg, .exe) older than 30 days to trash
4. For everything that's been in Downloads more than 60 days and is not a screenshot, PDF, or installer, ask me one yes/no question: "Move to /Archive or trash?"
5. Log everything you moved or trashed to cleanup-log-{date}.md so I can recover anything if needed
Pause before trashing anything. Show me a 5-line summary of what you're about to do and wait for "yes."
The pause + 60-day buffer + log are the safety nets. The first time you run this, supervise it. After that, set it as a recurring scheduled task and forget it.
A few patterns the workflows have in common
You’ll notice these by now:
- They use Context.md / playbook.md / rules.md files. Cowork is much smarter when you give it project-level memory. Spend 15 minutes writing a Context file before you start running workflows; it’s the highest-leverage setup work you’ll do.
- They pause for human approval at the irreversible step. Drafting an email is fine to automate. Sending it isn’t, until you’ve watched the workflow run cleanly for two weeks.
- They save outputs as files, not as chat replies. This is the key Cowork advantage over chat-only Claude. Files stack up over time and become a searchable archive of what was decided and what was sent.
- They use scheduled tasks for anything recurring. If you find yourself running a workflow more than once a week, schedule it. Cowork’s Routines tier (April 2026) runs scheduled tasks even when your laptop is closed, so you don’t need to keep your machine on.
The bottom line
Most people who try Cowork run one or two manual queries, decide it’s “just Claude with file access,” and never come back. The workflow library is what changes the experience — once you have 3-4 of these running on a schedule, Cowork stops being “an AI app I sometimes use” and starts being “the layer that runs my Friday close-out work.”
Pick one workflow above. Just one. The Monday Brief is the highest-impact starter for most readers; the Bookkeeping + Tax Prep is the highest single-event time saver. Set it up tonight. Run it once with supervision this week. Then schedule it.
Three of our courses go deeper on the patterns above:
- Claude Cowork Essentials — the foundation course covering connectors, skills, plugins, and scheduled tasks
- Cowork Skills & Plugins — for when the prebuilt 15 aren’t enough and you want to write your own skills
- Claude Dispatch — for the remote-control angle where you trigger workflows from your phone while Cowork runs them on your laptop
We’ll keep updating this post as new workflows hit the X feeds. If there’s one we missed, drop us a note.
Sources
- Anthropic: Get started with Claude Cowork
- Anthropic: Custom connectors using remote MCP
- Geeky Gadgets: Ultimate Cowork Guide — Are You Using Claude to Its Full Potential?
- Pluginsforcowork: Claude Cowork Connectors & Integrations (2026) — Complete List
- Mike Futia on X: Claude Cowork + Meta Ads creative system (707 likes)
- JJ Englert on X: Bookkeeping + tax prep workflow with Context.md (495 likes)
- Boris Cherny on X: Cowork booked 8 flights and 5 hotels (3,016 likes)
- Anthropic: Introducing Claude for Small Business (the prebuilt-workflow approach)
