You finished the course. You know what Cowork is, what it does, how skills work, what workflows it shines at. Now what?
The honest answer: not every AI problem in your business needs Cowork. Or any custom build. Sometimes the right move is to buy something off-the-shelf for $30 a month. Sometimes the right move is to do nothing at all. Most AI courses won't tell you that — they have one tool to sell.
Here's a framework that doesn't.
Four options for every AI decision
For any workflow in your business — customer follow-up, proposals, reports, lead qualification, anything — there are four possible answers. Most people only consider one.
The deciding question across all four is structural: where does this workflow's center of gravity sit? Center of gravity is whatever the workflow can't run without — the thing that, if it disappeared tomorrow, would kill the workflow. That structural answer puts every workflow into one of four buckets.
Buy. The workflow's center of gravity is inside a vendor's product. You adopt the vendor's solution; they own the workflow logic, the data model, the maintenance. AI may be present, but it's the vendor's AI, not yours. Sometimes it's a paid subscription (Klaviyo for email, NiceJob for reviews, QuickBooks for bookkeeping). Sometimes it comes bundled with something you already pay for — Anthropic's Claude for Small Business ships 15 pre-built workflows you install rather than purchase separately, included with paid Claude plans. The key is someone else built it, you adopt it. If the workflow is standard and an off-the-shelf option fits your stack, Buy is the right answer.
Bridge. The workflow's center of gravity is inside SaaS you already run, and AI sits beside it doing what the SaaS can't. Remove the AI, the SaaS keeps running, and the workflow degrades but doesn't die. AI here is doing what traditional automation (Zapier, Make) genuinely can't: writing in your voice, applying judgment, reading unstructured input. Example: every Square sale, you want a personalized thank-you that mentions what the customer bought and feels like you wrote it — not a Mailchimp template with a {first_name} placeholder. Zapier can move the data from Square to your inbox; only AI can write the note. The Bridge is small: Square keeps doing what it's good at, and the AI piece in between handles what neither does on its own.
The honest test: if Zapier alone could solve it, that's not a Bridge — it's Buy a Zapier subscription. Bridge earns the AI label only when the gap needs thinking, not just data movement.
Build. The workflow's center of gravity is an artifact you assembled — a Cowork skill, a script, a scheduled job, an agent. Even if the artifact pulls data from vendor SaaS, the assembled artifact is what defines the workflow. Remove the artifact and the workflow ceases to exist. This is where Cowork lives. The bar for Build has dropped sharply — vibe-coding turns what used to be a $5K engagement into an afternoon. The real Build-vs-Buy line is now maintenance: will you (or someone you trust) keep it running when something breaks? If yes, Build is in play more than ever. If no, lean Buy — because you're not buying just the software, you're buying the vendor's ongoing existence.
Skip. No workflow worth a center of gravity. The work is low-volume, unstable, or just doesn't matter enough. Automating it costs more than just doing it. Leave it alone; revisit in 12 months.
The default in the wider AI conversation is "Build everything custom." That's wrong for most workflows. Most workflows are Buy or Skip. Knowing the difference is the entire skill.
This isn't new thinking. Joel Spolsky said it twenty years ago in "Strategy Letter V": "Smart companies try to commoditize their products' complements." In plain English: differentiate where you uniquely add value; buy off-the-shelf for everything else. Anthropic's own engineering team says the same thing about AI specifically — "We recommend finding the simplest solution possible, and only increasing complexity when needed." What BBBS adds is a workflow-level decision surface for SMB owner-operators — including the Skip cell that enterprise frameworks tend to omit.
Six questions to find the right answer
Before you decide to automate anything, run it through these six. They map back to the center-of-gravity test, but they're phrased so you can answer each yes/no in your head.
- Does this happen at least twice a month, AND does failure actually cost me something? No → Skip. (Run this gate before any other question. If both halves aren't yes, walk away.)
- Is there a product I can sign up for today that does this out of the box, the way I'd want it done? Yes → Buy.
- Is there a product that does most of it, where the only missing piece is something only a human or AI could do — judgment, voice, reading a messy document? Yes → Bridge.
- If I asked an AI to handle this, would it be reaching into three or more places I already have (folders, my CRM, my calendar, a spreadsheet) and stitching them together into something new? Yes → Build.
- If a vendor disappeared tomorrow, do I still have the workflow? Yes → Build. Partially → Bridge. Not at all → Buy.
- Who do I call when it breaks on a Tuesday morning? A vendor's support → Buy. My software vendor for the data, me for the AI prompt → Bridge. Me, full stop → Build.
Q5 and Q6 are confirmatory cross-checks. If your answers from Q2–Q4 disagree with Q5–Q6, trust Q5–Q6 — they reveal where the center of gravity actually sits once the workflow is running.
Three worked examples
A Calgary plumber wants to follow up with old customers
800 past customers. The plumber wants to send a "we're still here, $50 off your next service call" message.
Run the questions. Twice a month? It's a one-off campaign — but the value is real. Product that does it out of the box? Yes — Mailchimp does this. If Mailchimp disappears, the workflow disappears. Who maintains it? Mailchimp.
Answer: Buy. Mailchimp is the center of gravity. Don't build it in Cowork — Mailchimp keeps it running, handles deliverability, and you don't want to be the one debugging email from your laptop at 2am. Subscribe, run a one-time campaign, move on. Save your AI energy for problems that actually need it.
The same plumber wants every new client to get a personalized welcome note
Every booking creates a record in Housecall Pro. The plumber wants every new client to get a thank-you that mentions the specific service they booked and feels like he wrote it personally — not Housecall Pro's canned "Thank you for booking {service}."
Run the questions. Frequency × cost: daily, and late or canned welcomes lose repeat business. Product that does this the way he'd want it? No — Housecall Pro's templates are generic. Missing piece is judgment + voice? Yes — only AI can write a note that mentions a specific service in his voice. If Housecall Pro disappears, the workflow dies. If the AI prompt disappears, Housecall Pro keeps running.
Answer: Bridge. Housecall Pro stays at the center; AI sits beside it doing the personalization Housecall Pro can't. A small AI workflow watches new bookings, drafts the note, queues it in Gmail for approval. Cheaper than ripping out Housecall Pro for a custom CRM; sharper than the template that loses customers.
The same plumber wants a Friday wrap-up of the week's jobs
Every job has notes in three places: paper invoice scans in /Receipts, customer notes in QuickBooks, follow-up reminders in Calendar. The plumber wants a one-page Friday summary: jobs done, revenue, follow-ups due, supplies running low.
Run the questions. Frequency × cost: weekly, and right now the plumber finds out at year-end how the business actually did. Product that does this end-to-end? No vendor stitches paper invoices + QuickBooks + Calendar into one weekly narrative. Reaching into three or more places and stitching them into something new? Yes. If any single vendor disappears, the workflow degrades but doesn't die — the assembled Cowork skill is the center of gravity, not any one tool.
Answer: Build. This is exactly the kind of workflow Cowork was built for. Schedule it, point it at the three folders, get the Friday doc on the desktop by 5pm.
Same business. Three workflows. Three different answers. The framework discriminates.
Cowork's Skip signals
Even when the framework points to Build, Cowork specifically has three situations where it's the wrong tool. Spot them early or you'll waste time.
Your laptop closes at 5pm and goes home with you. Cowork's scheduled tasks only run while the desktop app is open and the computer is awake. If your work pattern doesn't support a computer left awake on a desk, scheduled tasks won't fire reliably. Change the setup (keep a dedicated computer on, or use a different kind of tool) or Skip.
You're in a regulated industry. Anthropic's own safety guidance is unambiguous: "Do not use Cowork for regulated workloads." Cowork activity is excluded from audit logs and compliance APIs, and as of May 2026, Cowork is also not available on HIPAA-ready Enterprise plans — only Claude chat is covered.
A reasonable question: Anthropic just shipped Claude for Small Business with workflows like Contract Reviewer and Tax-Season Organizer. Doesn't that mean Cowork is fine for legal and accounting practices? Not for client-protected work. Those workflows are useful for an SMB owner's own back-office — your own vendor contracts, your own books — but anything subject to HIPAA, attorney-client privilege, SEC/FINRA, or similar audit requirements still needs to live in Claude chat on Enterprise with a Business Associate Agreement, not in Cowork.
Until Anthropic closes the audit gap for Cowork, the BBBS verdict for regulated client work is: Skip Cowork for that work, Buy Claude chat on Enterprise with BAA for the parts that need compliance coverage.
You need memory that persists across standalone sessions. Cowork's memory works within Projects but not across standalone Cowork sessions. If your work can be scoped inside a Project, you're fine. If you need cross-session memory and don't want to think about Project structure, Skip until that changes.
These aren't reasons to dismiss Cowork. They're reasons to know when for you the answer is something else. That honesty is the framework's job.
What to do next
You now have:
- A framework for any AI decision in your business
- A diagnostic to apply it
- An honest read on where Cowork helps and where it doesn't
If you want to apply this to your actual business — surface the 5–10 workflows that matter most, route each through Buy / Bridge / Build / Skip, walk away with a roadmap — that's exactly what the Workflow Audit does. Two hours of your time, one page of recommendations. [Link to Workflow Audit booking.]
If you'd rather DIY: pick the workflow you do most often this week. Run the six questions. Pick the right option. Ship that one. Then the next.
One last note on how BBBS sits next to Anthropic's own framework. Anthropic teaches a four-step model in their AI Fluency for Small Business curriculum — the 4D Framework: Delegation, Description, Discernment, Diligence. BBBS is essentially a more granular version of the first D, Delegation. Instead of the binary "delegate to AI or not," BBBS gives you four explicit options — Build, Buy, Bridge, Skip — including two paths (Buy a non-AI tool, Skip entirely) that 4D's AI-focused framing leaves implicit. The other three Ds — Description, Discernment, Diligence — cover what BBBS doesn't: how to actually work with AI on the workflows you decided to build or bridge. BBBS picks the path; the rest of 4D walks it.
The discipline isn't AI. It's deciding.