What small teams actually do with Claude Cowork
Updated August 10, 2026 · 5 min read
What do small teams actually use Claude Cowork for?
The Claude Cowork workflows worth setting up first in a small team are the ones that repeat: a morning brief pulled from the inbox and Slack, month-end reporting, routine email drafts, file organization, answers from the company handbook, and saved tasks that rerun the same way every time. The pattern holds across industries: documents and messages go in, drafts and summaries come out, and a person reviews before anything leaves. The workflows worth keeping are the weekly ones, not the one-off experiments.
What does every team set up first?
Six workflows fit nearly every office, whatever it sells, and they are where we start an engagement: each repeats weekly and is cheap to review, so the day-30 check has something real to measure. Each row ends with a person reviewing.
| Workflow | What goes in | What comes out |
|---|---|---|
| The morning brief | Overnight inbox, Slack or Teams | One briefing: what needs you, what to follow up, what waits for review |
| Reporting and data | Month-end exports and spreadsheets | One readable summary, delivered where the team already reads |
| Email and admin | The routine replies you write again and again | Drafts in your voice, held for a person to send |
| File organization | A shared drive of inconsistent names | Files sorted and renamed by rules you set once |
| Handbook answers | Your policies, handbook, and FAQ | Instant answers in Slack for staff or customers |
| Repeatable tasks | The Monday report from the same three systems | Saved once, rerun on demand, the same way every time |
If none of these six lands for a given office, the honest conclusion is that AI is not its bottleneck yet, and we say that on the call rather than sell around it.
What do law firms run?
In a law firm, Cowork gets pointed at the nonbillable admin around every matter, always with a lawyer reviewing. The recurring seven we set up:
| Workflow | What goes in | What comes out |
|---|---|---|
| Client intake | The first email or call notes | A matter summary in firm format, follow-ups drafted |
| Conflict checks | New party names | Flags against the matter list, for a person to confirm |
| Document and contract review | A long agreement | Clauses and dates pulled, risks flagged |
| Research summaries | Case law and long records | Plain memos, cites left for the lawyer to check |
| Deliverable drafting | The matter file | First drafts of letters and routine filings, held for review |
| Records and discovery prep | The records stack | Organized, summarized material so review starts ahead |
| Client updates | The matter file | A plain-language status draft, sent by the lawyer |
Firms carry duties the other industries do not, and the governance half of the answer matters as much as the workflow half; it is worked through in Claude for law firms.
What does a real estate office run?
Speed and paperwork are the two real estate problems worth aiming at, because leads cool overnight and deals outrun their documents. The set we set up:
| Workflow | What goes in | What comes out |
|---|---|---|
| After-hours leads | The inquiry that lands at nine on a Saturday | An answer with qualifying questions, instead of silence until Monday |
| Listing descriptions | Property facts | Listing copy in the office voice, pasted to the MLS after a read |
| Transaction coordination | Deal timelines and contingencies | Tracked deadlines, reminder drafts each morning |
| Comp summaries | Comparable sales | A client-ready market summary the same day |
| Disclosure prep | The document stack | Packets checked against the office checklist, gaps flagged |
| Client follow-ups | Showing notes | Same-day follow-up drafts, approved before sending |
What do sales teams run?
For a sales team the target is a pipeline that reflects reality without the reps doing data entry. The set we set up:
| Workflow | What goes in | What comes out |
|---|---|---|
| Call notes to next steps | Call notes | CRM updates and tasks, filed before the next call |
| Stage-aware follow-ups | Where each deal sits | Follow-up drafts matched to the stage, not a generic sequence |
| Proposals and RFPs | Requirements and past responses | A first-pass response ready for the rep to shape |
| Pipeline reporting | The CRM export | A Monday summary: what moved, what stalled, what needs a call |
What do marketing teams run?
Marketing in a small business is usually one or two people covering every channel, so the setups hold the brand voice and kill the rebuild work. The set we set up:
| Workflow | What goes in | What comes out |
|---|---|---|
| Content first drafts | A brief | A draft in the brand voice, so the voice survives across writers |
| Repurposing | One long piece | Email drafts, posts, and a summary, each sized to its channel |
| Campaign reporting | Exports from every platform | One plain-English report, delivered where the team reads |
| Research and briefs | Scattered notes and research | A tight brief a writer can execute without re-research |
How do you pick the first workflow?
Pick the task that repeats at least weekly, has a clear input and output, and is cheap to review when the draft is wrong. That filter rules out the flashy one-off demo and rules in the boring report everyone dreads, which is the correct answer. It also tends to rule out a custom build, for reasons set out in When is an AI agent worth it for a small business?.
- 01List the three tasks the team complains about most.
- 02Keep the ones that repeat and have a definable "done".
- 03Capture how long the task takes today, before any AI touches it, so day 30 has a baseline to beat.
- 04Set it up, train the people who own it, and put the review rule in writing.
That sequencing, baseline first, is how our engagements are structured, and it is why the day-30 conversation is about a measured number. What the seats themselves cost sits in What Claude actually costs a small business; what Cowork is, if you arrived here first, is in Claude Cowork, explained for small business; and the setup itself is walked through in How to set up Claude Cowork, step by step.
Straight questions
How many workflows should a team start with?
Three. Enough that the tool shows up in daily work, few enough that training sticks and review stays real. Justo’s roadmaps pick the first three by time saved.
Do these workflows need custom software?
Mostly no. Files, folders, and standard connectors cover the sets above. A custom connection gets built only where an assessment justifies it, scoped to exactly what it may reach.
How long until a team sees value?
Justo’s engagements run two weeks of setup and training, with at least one workflow running and controls confirmed by the end of week two, and time saved measured against the baseline at day 30.
What stays human in all of this?
Judgment, relationships, and signoff. Every workflow above ends with a person reviewing, and anything client-facing goes out under a person’s name after a person’s read.