Five Real Workflows for SMB Owners

You've got Cowork open. You know the layout. You understand the paradigm shift and when chat is still the right tool. Now what do you actually run?

Below are five workflows you can copy, adapt, and run today. Each represents a different shape of automation — schedule something recurring, batch-process a folder, synthesize across many emails, generate from a template, or kick off a task from your phone while you're between meetings. Treat them as starting templates, not an exhaustive list.

The prompts below are the actual prompts. Adapt the paths and conditions to your business, then run them. If a workflow doesn't apply to your work, skip it — these aren't a checklist, they're a sample of patterns.

Workflow 1: The Friday client wrap-up

Shape: scheduled, recurring, folder → multiple deliverables.

Who this is for: consultants, agencies, freelancers — anyone who touches multiple clients in a week and ends up reconstructing what happened every Friday afternoon.

Your prompt:

"Every Friday at 4pm, read every note in /Client-Notes/this-week and produce a one-page status update for each client. Each update should cover: what we worked on this week, decisions made, blockers, next steps. Save them in /Client-Updates/[client-name]-2026-05-16.docx using this Friday's date in the filename."

What's happening: as long as the Claude Desktop app is running and your computer is awake at the time, Cowork's scheduler fires this task automatically every Friday at 4pm — no manual trigger needed from you. Cowork reads the notes folder, groups by client, and uses the built-in Word skill to produce a formatted document per client.

What you get back: a folder of Word docs on your desktop, ready to skim Monday morning before sending out the wrap-ups.

On creating the schedule itself: two paths work. You can fill in Cowork's manual scheduled-task form (name, description, instruction, target folder — folder is selected explicitly). Or you can type /schedule in a regular Cowork chat and let Claude walk you through it conversationally. Useful nuance: the Claude-assisted path inherits the folder from your current chat session by default, so if you're already in the right folder it's fine — but if not, swap to the manual form so you can pick the folder explicitly.

One thing to watch: the scheduled run only fires if your laptop is awake and the Claude Desktop app is open. Enable "Keep computer awake" in Settings → Desktop app → General. Remember a closed laptop lid still puts the machine to sleep — this works for desk-bound laptops, not the one you take home.

Workflow 2: Resume triage to scored shortlist

Shape: read a folder of unstructured documents, produce a sortable spreadsheet.

Who this is for: any SMB hiring even one role per year. Especially solo founders or small ops teams without a recruiter.

Your prompt:

"Read every PDF resume in /Applicants and produce an Excel called shortlist.xlsx saved to the same folder. Columns: filename, candidate name, total years of relevant experience, top 3 skills as listed on the resume, and a 1–5 fit score against the job description in /Applicants/jd.txt. Sort by fit score, highest first. For each candidate, also include a single sentence explaining the score."

What's happening: Cowork reads each PDF, extracts the relevant fields, scores them against your JD, and produces a spreadsheet with working sort. The built-in Excel skill creates the file directly in your folder.

What you get back: an Excel ranked by fit score with a one-sentence explanation per candidate, ready to share with whoever's joining the first interview round.

One thing to watch: Cowork can hallucinate experience years or invent skills that aren't actually on a resume. Spot-check the top three candidates before sharing the shortlist, and treat the fit score as a starting point — not a verdict.

Workflow 3: Customer feedback themes from your Gmail

Shape: synthesis across many emails → one structured deliverable.

Who this is for: any business that gets customer feedback by email — service businesses, e-commerce stores, anyone with a support inbox.

Your prompt:

"Search my Gmail for every email labeled 'Customer Feedback' from the last 90 days. Produce a Word doc summarizing the top 5 themes that come up most often, with 1–2 anonymized example quotes for each. Add a final section flagging any urgent issues that should be addressed first. Save as /Reports/Q2-feedback-summary.docx."

What's happening: Cowork queries Gmail through the Google Workspace connector, reads the matched emails, and synthesizes patterns across them. The built-in Word skill produces the report locally.

What you get back: a Word doc summarizing what your customers have been saying, with quoted examples (anonymized — but re-check before sharing externally), saved where you can find it.

One thing to watch: the quality of this output depends heavily on how disciplined your Gmail labels are. If "Customer Feedback" is applied inconsistently, the synthesis misses real feedback. Also: the Gmail connector reads email content and metadata, but attachment content is not accessible — if customers send screenshots or PDFs of issues, those won't be in the analysis.

Workflow 4: Custom proposal from your template

Shape: combine a static template with a dynamic brief → polished output.

Who this is for: service businesses that respond to inquiries — consultants, agencies, contractors, freelancers, web designers. If you write the same proposal structure over and over and just swap content, this one's for you.

Your prompt:

"Use /Proposal-Template.docx as the structural template, and the inquiry brief at /New-Inquiries/[client-name].md as the content source. Produce a customized proposal that follows the template's section order, headings, and tone — but with content tailored to this specific brief. Match my voice as it shows up in the template. Save as /Proposals/[client-name]-proposal-2026-05-14.docx."

What's happening: Cowork opens your template, reads the brief, and fills in the structural skeleton with content tailored to the specific inquiry. The built-in Word skill handles the formatting.

What you get back: a draft proposal in the same shape as your template, on your desktop, ready to review.

One thing to watch: the draft can drift from your tone if the brief is short. Always read the draft end-to-end before sending — never let a Cowork-generated proposal go straight to a prospect without your eyes on it. That discipline is the difference between "Cowork saved me 90 minutes" and "Cowork sent the client a generic-sounding doc."

Workflow 5: Mid-day mobile dispatch with Gmail

Shape: kick off from your phone, work runs on your desktop, result waiting when you return.

Who this is for: owners who are out of the office during business hours — trades crews on job sites, owners running between meetings, agency leads on client calls. Anyone whose laptop is at the desk while they're not.

Your prompt (sent from the Claude mobile app, between meetings):

"Pull every email I received this morning from existing clients via Gmail, group by sender, and flag anything urgent. Save a brief to /Daily-Briefings/2026-05-14.docx so I can review it when I get back. Text me a one-line summary when done."

What's happening: you dispatch the task from your phone. Cowork executes on your desktop computer (which is awake at the office), uses the Gmail connector to pull this morning's client emails, synthesizes a brief, saves it locally, and pings you back with a summary.

What you get back: a Word doc on your desktop named with today's date, ready to read when you return. Plus a one-line preview on your phone.

One thing to watch: Dispatch only works if your desktop is awake and the Claude Desktop app is open. The "Keep computer awake" toggle in Settings → Desktop app → General is the simplest way to ensure the desktop doesn't drift to sleep while you're out. If you close the laptop lid and take it with you, Dispatch can't fire — the lid puts the machine to sleep even with the toggle on. This is the mid-day pattern, not the end-of-day pattern — for "the laptop is at the office while you're away from it."

What's next

These five aren't a complete list — the universe of what you can automate in your business is effectively limitless. They're a representative sample of different shapes of Cowork automation: schedule, batch process, synthesize, generate from template, mobile dispatch. Take any of them as a starting template, swap in your own inputs, and adapt to whatever your business actually needs.

When you adapt a prompt:

• Replace folder paths with your actual paths
• Replace the JD, template, or label names with your real ones
• Run in "Ask before acting" mode the first few times so you can see Cowork's plan before it executes
• Spot-check the output before you trust it — for the first dozen runs, treat Cowork's output as a draft, not a final

Module 5 covers the Business Onboarder Skill — context about your voice, your business, and your customers, packaged so Cowork can use it across tasks. Install it once; future workflows that need your voice or context get sharper without you re-explaining who you are.

Module 6 covers when not to run these workflows. Some are clearly Build territory. Others might be Buy or Skip. The framework matters.