How I Use Claude Cowork to Run My Own IT Business

I run Claude Cowork on a dedicated, isolated machine to handle the back-office work of running an IT business: backups, security alerts, expenses, and mileage.

For years, my mornings all started the same way. Coffee in hand, I'd sit down and start working through the list. Log into one client's backup portal and check it. Log into the next one. Open the email alerts. Pull up a NAS dashboard. Check Microsoft 365. One system at a time, until I finally had a picture of whether everything was healthy across all my clients.

By then the coffee was cold and half the morning was gone.

These days I sit down, open one machine, and the whole picture is already there waiting for me. The coffee actually gets finished.

That change came from a machine I built out of a PC that was headed for the recycling pile, and how I set it up matters as much as what it does. So here is the whole story.

The Machine Started Life in a Recycling Pile

A while back, a client was clearing out old equipment, and one of the PCs was headed for the recycler. It was a perfectly capable machine that just was not needed anymore. I took it, rebuilt it, and gave it a new job.

That machine is now the dedicated computer that runs my automation. Not my daily work laptop. Its own box, doing its own thing.

That was a deliberate choice, and it is the first thing I would tell anyone thinking about this. I did not want this running on the laptop I use for everything else. I wanted it isolated, on a machine with one purpose, so whatever it is doing stays in its own lane. More on why that matters in a minute.

I will admit I also just like that it used to be e-waste. A machine somebody was about to throw away is now doing real work for my business. That is the kind of get-your-money's-worth thing I bring to everything.

What Claude Cowork Actually Is

Most people know AI as a chat window. You type a question, it types back. Useful, but that is not this.

To understand Cowork, start with the Claude desktop app. It is a program you install on your computer, and it has different modes. One mode is regular Chat, the same kind of conversation you would have in your browser, tied back to your usual Claude work. Another mode is Cowork. Same app, different job.

Cowork is the one that does work instead of just talking. You point it at a task, and it runs through the steps on its own, reading and writing real files in the folders you give it access to, the way a capable assistant would if you handed them a folder and a checklist. You can set it to run tasks on a schedule, which is the part that makes a morning dashboard possible.

Now the part that matters for safety, and the reason the dedicated machine is not overkill. When Cowork carries out a task, the heavy lifting does not run loose on your computer. The app spins up a sealed, isolated environment, a virtual machine, and the actual commands run inside that walled-off space, separate from the rest of your system. When the task is done, that environment is wiped. You do not set any of this up yourself. The app creates it the first time you use Cowork and tears it down after each session.

That isolation is a real boundary. If something ever went sideways, it stays contained instead of reaching the rest of the computer. Think of it as letting an assistant work in a separate room with the door closed, rather than giving them the run of your whole house.

So I put it on its own machine on top of that. The tool already isolates its work, and I isolated the whole machine around it. Belt and suspenders. That is how I treat anything that touches my business or my clients.

There is a practical reason for the separate machine too. For Cowork to run a task, especially a scheduled one, the desktop app has to be open and the computer awake. I did not want my daily laptop tied up and running around the clock to keep an automation alive. A dedicated box that stays on and does only this is the natural fit. It just sits there and does its job.

My Morning, In One Screen

Three things happen on that machine before I have finished my first cup.

It monitors my clients' backups. I am responsible for backups across their servers, their NAS file servers, and their Microsoft 365 data. Cowork checks all of it overnight and lays it out in a spreadsheet. Did every backup run? Did any fail? Are the hard drives in the servers healthy? Were there errors I need to know about? Instead of logging into a dozen places to assemble that picture, the picture is built and waiting. I read it, and I act on anything that needs me.

It also watches security. I set up a shared mailbox where alerts from my clients' security portals all flow in. Cowork monitors that mailbox and turns it into a report, the same way it does the backups. Any viruses, any breaches, anything that looks wrong. If there is something I need to jump on right away, it flags it and tells me so I see it first thing, not three days later. I review that every morning alongside the backups.

That is the whole point. It is the difference between walking into a kitchen where the coffee is already made and standing there grinding beans half awake. My backups and my security alerts. The two things I absolutely cannot let slip. They used to be scattered across portals and inboxes I had to chase down one at a time. Now they are sitting there waiting. Nothing slips because I got busy or a tab got buried.

It Does Not Just Help Me. It Helps My Clients Hear From Me.

This is the part I did not expect to like as much as I do.

On the first of every month, Cowork has already drafted a backup recap email for each client, sitting in my drafts. I open them, read them, make any tweaks, and send. Each client gets a plain-language monthly note telling them their backups are running and being monitored. They know it is working because I tell them, every month, without it eating my morning to write each one from scratch.

I am building the same thing for security. A monthly note on each client's security posture, even when there is nothing wrong. Especially when there is nothing wrong, honestly, because no alerts means things are working, and clients should hear that instead of assuming silence means nothing is happening. I have it leave a space where I drop in a snapshot of their security score, so they can see a starting point and watch me improve it over the months. That part is still a work in progress, and the score snapshot is something I add by hand, because a client-facing number is worth a human set of eyes before it goes out.

Both work the same way. Cowork drafts it, I read it, I send it. A client never gets an email I have not looked at myself. It does the assembly and the rough draft, and I stay the one deciding what actually goes out.

The Receipt Pile I Used To Avoid

Now the part of the business I actually hate.

Tracking receipts and gas is tedious, so for a long time I did what a lot of small business owners do. I put it off. Every business has that junk drawer, the one you keep throwing stuff into and slamming shut, telling yourself you will sort it out later. Mine was receipts. It just kept piling up.

This past tax season, it caught up with me. So I decided to let Claude dig me out. I had it pull my receipts from the email accounts I keep for that, and it worked, mostly. Amazon was the holdout, it could not pull those directly, so I downloaded them, zipped them into one folder, and handed the whole thing over to sort. Days of manual sorting turned into an afternoon.

That was the moment it clicked. If it could dig me out of the drawer at tax time, it could keep me from ever filling it up again.

So now it runs on its own. Every week and every month, Cowork pulls my receipts from email and from a folder where I drop anything I buy, and sorts them into a spreadsheet by date, type, and amount, broken into categories. No more drawer. When tax time comes around again, the work is already done.

The Mileage Trick I Am Most Proud Of

The mileage piece is where it got clever, and it is my favorite thing I have built so far.

I keep my calendar color-coded by client. Cowork knows that. So when it works through my mileage, it does not just log miles, it reads my calendar, sees which client I was with, and logs which site I drove to right alongside the trip. Then it matches my mileage against my gas receipts and flags anything that does not add up, so I can review it.

It is not just listing miles in one column and gas in another. It is checking whether the two tell the same story, and waving a hand when they do not. Some days I fill up twice, which would look like a mistake to a dumber tool, so I built in caveats based on how many miles I actually drove that day. It uses the calendar to work that out. It knows the difference between a weird-looking day and an actual error.

That is the difference between a tool that records and a tool that pays attention.

How It Knows What It Can Touch

None of this happens on its own, which is the part I would want to know about. I had to explicitly grant Cowork access to the specific folders and the mailbox where this data lives, and once I built the scheduled tasks, I had to approve them before they would run. It does not quietly reach into my files or start working without permission. I decide exactly what it can touch and sign off on what it runs. For a tool this capable, I would not have it any other way.

Why It Is All the Boring Stuff, On Purpose

Look again at what I put on this machine. My backups report. My security alert summaries. My receipts. My mileage. My monthly client drafts. All back-office work, and all mine to begin with.

What I did not do is turn it loose on regulated client data. The security piece is a good example. Cowork reads the alert emails landing in a mailbox I set up and summarizes them. It is not reaching into anyone's protected systems or handling regulated records.

I drew that line on purpose. Because Cowork is autonomous and works on local files, its activity is not captured the way a managed, audited business tool's is. So anything regulated, CUI under CMMC, protected health information under HIPAA, stays in the systems built and authorized for it. Figuring out which tasks belong on a tool like this and which absolutely do not is most of the job. The technology is the easy part. Knowing where to point it is what takes experience.

Claude Cowork Versus Claude Teams: Two Different Jobs

If you read my last post about setting up Claude Teams for a construction company, you might wonder how these two fit together. They are different tools for different jobs.

Claude Teams is the shared, cloud-based workspace. It is where a team collaborates, with admin oversight and a record of how it is being used. It is built for a group of people doing everyday work together, safely. That is what I set up for clients.

Claude Cowork is the agent that runs on a machine and works through tasks on its own. It is more powerful in what it can do unattended, and because of that, it carries a different risk profile and lives in a more controlled spot. For me, that spot is a dedicated, isolated machine running only my own back-office work.

So one is built for a team working together, and the other for the heavy automation you keep on a short leash and run yourself. I use both, each for what it is actually good at.

Why I Built This Before Offering It

I work with small businesses across Columbia, MD, and the DMV, and farther out into Pennsylvania, West Virginia, and Delaware. A lot of them are buried in the same back-office work I just described. So the fair question is whether I would build something like this for them. And because this kind of setup can be done remotely, that question is not limited to businesses near me. If you are buried in the same work, where you are located does not really matter.

The honest answer is maybe, and it depends on the business and the task. But I would never put a client on something I had not run myself first. This machine is me being my own first client. I learn exactly where this tool shines, where it needs a short leash, and where it does not belong at all, on my own operation, where the only risk is mine to carry.

That is the whole reason it exists. It is not a gimmick, it is the test bench that lets me tell a client, with a straight face, that I know how this behaves because I have been living with it in my own business.

What This Could Mean for Your Business

Every small business owner I know has a version of my receipt pile. The reports nobody has time to pull. The reconciliation you keep meaning to get to. The nagging worry that something important is sitting in an inbox you have not opened. It is real time, and it is real peace of mind, and most owners are short on both.

AI automation can take a serious bite out of that. But the lesson from my own setup is the same one I give every client. The tool is the easy part. Where you run it, how you isolate it, and which tasks you trust it with are what separate a smart setup from a risky one.

Think of it this way. A powerful AI tool with no boundaries around it is a steel door with no lock installed. It looks like security, but anyone can still walk right through it. The door was never the hard part. The lock is, and making sure it only opens for the right things. That is the part I actually do.

That is what I help with. Not just handing someone a tool, but working out the right tool for the right task, set up so it saves time without opening a door you did not mean to open.

My Services Include

At SNL-Tech Services, I help small businesses use AI and automation to save real time without creating new risk. My related services include:

• AI automation planning for back-office and reporting tasks

• Claude Cowork and Claude Teams setup, with honest guidance on which fits each job

• Backup monitoring and monthly client reporting across servers, NAS, and Microsoft 365

• Security alert monitoring and posture reporting for managed clients

• AI governance and risk assessment, including which tasks should never go on an autonomous tool

• Ongoing managed IT and security for businesses across the DMV and remotely across the United States.

Frequently Asked Questions

What is Claude Cowork?

Claude Cowork is a mode inside the Claude desktop app. The app has a regular Chat mode, like the AI conversations you may already use, and a Cowork mode that does hands-on work instead of just talking. In Cowork, it carries out multi-step tasks on its own, reading and writing files in folders you give it access to, and it can run tasks on a schedule. The actual work runs inside an isolated virtual machine that the app creates automatically and wipes after each task, which keeps that activity walled off from the rest of your computer. It is built for things like organizing files, building reports, and processing documents.

Does Claude Cowork run on my computer or in the cloud?

Both, in a sense, and the split is the important part. You install the Claude desktop app on your computer, and its everyday chat side connects to Claude the way the web version does. But when you run a Cowork task, the actual work happens locally, inside a virtual machine the app creates right on your computer. That is different from regular AI chat, where nothing touches your machine. It is why Cowork can work with your real files, and also why running it on a dedicated, isolated machine is the smart way to keep that local activity contained.

Is Claude Cowork safe to use for business?

It is, when you respect what it is. Because it works on local files and runs fairly autonomously, the smart approach is to run it on a controlled or dedicated machine and point it only at tasks you are comfortable letting it handle. Its activity is not captured the way a managed, audited business tool's is, so it is not the right place for regulated or highly sensitive data. For back-office automation on a properly isolated machine, it is a strong fit.

Can Claude Cowork access my files and email without my permission?

No. You have to explicitly grant it access to specific folders and mailboxes, and it can only read and write where you connect it. Scheduled or automated tasks also need your approval before they run. In my own setup, I granted access only to the folders and the shared mailbox holding the data I wanted it to work with, and I signed off on each scheduled task before it would run. It does not quietly reach into your system on its own, which is exactly the control you want on a tool this capable.

Why run Claude Cowork on a separate computer?

Isolation, and practicality. Cowork already runs its work in a contained environment, and putting the whole thing on a dedicated machine adds a second layer of separation from your everyday computer and data. It also needs to stay open and awake to run scheduled tasks, so a dedicated machine means your daily laptop is not tied up keeping an automation alive. For anything touching a business, that separation is worth it.

Can AI really help with bookkeeping, receipts, and mileage?

For the organizing and sorting side, yes, and it can save serious time. My setup pulls receipts from email and a drop folder, then sorts them into a spreadsheet by date, type, and amount. For mileage, it reads my client-color-coded calendar to log which site I drove to, matches the trip against my gas receipts, and flags anything that does not line up for me to review. It does not replace your accountant, but it clears the manual grind so your records are organized and accurate before they ever get there. At tax time one year, this approach saved me days of work.

Can Claude Cowork monitor backups or security alerts for a managed IT provider?

It can assemble and report on them, which is how I use it. It checks my clients' backup results across servers, NAS, and Microsoft 365 and builds a daily status report, and it summarizes the security alerts that flow into a shared mailbox so I see anything urgent first thing each morning. It even drafts the monthly client recap emails for my review. The key is that it reports and drafts, while a human still reviews and acts. It is an assistant for the busywork, not a replacement for the technician.

What kind of computer do I need to run an AI automation like this?

Less than you might think. I built mine from a capable PC a client was about to recycle, rebuilt as a dedicated machine for the job. The point is not raw power, it is having a separate, isolated machine with a single purpose rather than running automation on your daily work computer. Reusing solid hardware that would otherwise be thrown out is a practical way to do it.

Should I use Claude Cowork for my regulated or sensitive data?

No. Tasks involving regulated data, like CUI under CMMC or protected health information under HIPAA, should not go on an autonomous tool whose activity is not captured in audit logs. That data belongs in systems built and authorized for it. The right use for a tool like Cowork is non-sensitive, back-office automation, and knowing where that line sits is exactly the kind of thing worth getting professional guidance on.

How much time can automating back-office tasks actually save?

It depends on the tasks, but the savings come from the repetitive work you do over and over: pulling reports, sorting receipts, reconciling numbers, checking systems one by one. My morning backup and security review used to mean logging into a dozen portals and inboxes. Now it is one spreadsheet and a coffee. Sorting a year of receipts at tax time went from days to an afternoon. The real win is not just hours, it is that nothing slips because I got busy.

Do you set up AI automation for businesses near Columbia, MD, or do you work remotely? Both. I am based in Columbia, MD, and I work with small businesses across the DMV, including Maryland, Northern Virginia, Washington DC, Pennsylvania, West Virginia, and Delaware. But this kind of work does not require me to be in the room. Setting up and managing AI automation can be done remotely, so I am not limited to my local area. If you are a small business anywhere and the back-office grind is eating your time, distance is not the obstacle. I help plan and set up the automation for the right tasks, on the right tools, with the isolation and judgment that keeps it safe.

Ready to talk?

If the administrative side of your business is eating time you do not have, there is probably a smarter way to handle it. I will give you an honest read on what could be automated safely and what should stay exactly where it is.

Based in Columbia, MD, and serving small businesses across the DMV, Pennsylvania, West Virginia, and Delaware and beyond. I help owners use AI and automation without creating new risk. Contact me today.