Home โ€บ Claude Workflows and Use Cases, Organized by Task

Workflows

Claude Workflows: What to Hand Over First

Ten jobs that eat a working week, and what a configured Claude setup actually does with each one. Written from the task backwards: what the build does, what it takes to stand up, and the point where it has to stop and hand back to you.

10

workflows, each with its limits named

4

full build case studies

20

professions with a setup page

Start with the task, not the tool

Each of these is a job someone was already doing by hand before any of this existed. The question is not whether Claude can do it. It is what is left for you afterwards, and every entry says so.

This page is organized by task. If you would rather see the work organized by job title, read the Claude use cases by profession on Strategized.ai.

Ops01

Clean up and reorganize a Google Drive

Point Claude at the drive and it reads what is actually inside each file rather than guessing from the filename. It proposes a folder structure and a rename batch, and nothing moves until you approve the list. The job that has been on your weekend list for two years becomes a review pass.

Stays with you: Deciding what gets deleted. Claude proposes; it does not empty anything.

Client work02

Turn a client intake form into a project brief

Intake arrives as PDFs, form rows or an email thread. Claude pulls the fields that matter into your standing brief template and flags every question the client left blank, so the gaps are visible before the kickoff call instead of during it.

Stays with you: Scope and price. The brief is assembled from what the client said, not from what the work is worth.

Ops03

Build a file naming convention that survives

Conventions fail because people stop following them by week three. Write yours once into CLAUDE.md and the thing doing the filing is the thing enforcing it, on new files and retrofitted onto the old ones.

Stays with you: The convention itself. Getting the scheme right is a twenty-minute decision that pays for years.

Reporting04

Turn a monthly export into a formatted report

Same three sources, same layout, every month. Configure it once against your template and Claude pulls the data, formats it, and leaves a draft in an output folder before you sit down.

Stays with you: Checking the numbers, and writing the paragraph that says why they moved.

Ops05

Rename a folder of files in bulk

Not pattern-matching on the old filename, which is how bulk renamers usually work and why they usually fail. Claude reads the document: invoices get the vendor and the date, contracts get the counterparty, photos get what is in the frame.

Stays with you: Approving the batch. You see the full before-and-after list first.

Marketing06

Review search terms and build a negative keyword list

Export the search term report and Claude groups the waste by theme rather than handing back a flat list, then formats the negatives with the right match type syntax โ€” quotes for phrase, brackets for exact.

Stays with you: Match type decisions, which need the keyword report too. The search term report alone hides most conversions under Google’s privacy thresholds.

Client work07

Turn a meeting recording into decisions and actions

Transcript in, structured debrief out: what was decided, who owns what, what is still open, and which commitments had no date attached.

Stays with you: Judging what a vague commitment actually meant. Claude will flag the ambiguity rather than resolve it.

Client work08

Write an invoice follow-up that gets paid

A time-tracking export becomes a plain summary of the week’s work and a follow-up note that references the specific things you delivered, which is the difference between a nudge and a reason to pay.

Stays with you: The decision to chase, and the relationship judgment about tone.

Marketing09

Run a competitor content gap analysis

Pull the competitor’s pages, compare them against your own coverage, and get back the topics they cover that you do not โ€” with the pages that would need to exist.

Stays with you: Deciding which gaps are worth filling. Most of them are not.

Ops10

Triage a high-volume inbox

Rules that read meaning rather than sender. Route the routine, summarize the long, draft replies for the predictable, and leave everything else untouched in the inbox.

Stays with you: Anything with money or a relationship attached. Those stay unread by anything but you.

How these are written

Every workflow page follows the same shape, because the thing you actually need to judge is fit, not capability.

The task, answered plainly

How the job works, with or without software.

The manual method

And the specific point where it breaks down.

The build

Real configuration from a working practice, not a demo.

What it took

Setup time and what it costs to keep running.

What it does not do

The limits, named before you ask.

Where this goes next

Full build case studies

Four complete setups described by role, including our own practice. What was built, what it runs on its own, and what the owner still touches.

The full reference library

Every Claude use case, comparison, connector and troubleshooting guide lives in the reference library on CoworkStrategy.com. Start there if you want the whole picture rather than the ten jobs above.

Claude skills library

One repeat job per page, written up as a Claude skill: what goes in, what comes out, and what Claude must never do.

Connect Claude to your tools

Gmail, QuickBooks and more: what Claude can do once connected, and the settings worth checking first.

Setups by profession

Thirty practice types, each with the workflows that matter most for that job and the compliance lines that cannot be crossed.

Have it built for you

Setup, training and rollout. The workflows above, configured against your files and your way of working.

Questions

What can Claude actually do in everyday business workflows?

Claude handles repeatable document and file work: organizing and renaming files by reading their contents, turning intake forms into briefs, building recurring reports from the same sources each month, producing meeting debriefs from transcripts, and drafting routine correspondence. The common thread is a task that repeats in roughly the same shape, configured once and then reused.

Where do I start with Claude workflows if I have never used Claude?

Pick the task on this page that annoys you most, not the most impressive one. A single working workflow teaches you more about configuration than ten demos, and it is the one you will keep using.

Which workflows should never be handed to Claude?

Anything where the judgment is the work. Pricing, scope, hiring decisions, clinical or legal conclusions, and any communication where the relationship matters more than the message. Every workflow on this page names its own version of that line.

Are these Claude workflows different from Claude Code?

Yes. Claude Code is built for developers working in a codebase from a terminal. Claude itself is built for people working with documents, folders and recurring business workflows, and needs no code.

Not sure which one to start with?

Bring one task. Twenty minutes, no charge, and you leave knowing whether it is worth configuring and what it would take.

Book a free 20-minute call