How I Run My Business With Claude Code: The 5 Jobs It Handles

My day starts with a briefing I didn't write.

Every morning, Claude Code shows me my day. Not just the meetings. Who I'm meeting, why we're meeting, and what happened the last time we spoke. I don't walk into calls unprepared anymore.

That briefing is one small part of how I run my business now. Claude Code is known as a coding tool. In my business it works more like a team member. It manages my tasks, sorts my email, drafts replies in my voice, builds automations and keeps sales moving.

Not a chatbot. Not a prompt library. Something that does the work and remembers why.

Here's how it's set up, what it does, what changed, and what it costs.

What changed when I gave Claude Code a memory?

For a long time, automation meant connecting tools. One trigger here. One workflow there.

Helpful, but fragile. Everything still depended on me remembering the context. Which client is this? What project? What stage are we in? What did we decide last time?

That's where things always broke. The tools could move data around. They couldn't know my business.

So I stopped adding tools and started building memory.

My setup knows:

• my products
• my clients
• my processes
• how I work
• how I make decisions

Not because I repeat myself. Because it's written down, and Claude Code reads it before it starts. I never explain the same thing twice. That one change made everything else possible.

What the memory looks like

It's less technical than it sounds. The memory is a handful of plain notes, split by area of the business: a business profile, sales, marketing, finance and operations. I keep them in Obsidian.

Before a task, Claude Code reads the notes that matter. A sales reply pulls in the sales notes and the business profile, so it knows what we offer and who it's talking to. A LinkedIn post pulls in the marketing notes, so it sounds like me.

Then it gets access to the tools where the work actually happens: my Trello board, my inbox, my calendar, n8n. Claude Code connects to those through MCP servers, small connectors that let it read and act inside each tool.

Memory first, tools second. Tools without memory just give you generic output, faster.

What does Claude Code actually do in my business?

Five jobs. Each one used to take a slice of my attention every single day.

1. Tasks: it runs my Trello board

It manages my entire Trello board. It updates cards, tracks progress and knows what's urgent and what isn't.

I don't manage tasks anymore. I get a clear overview and decide what to work on.

2. Calendar: context before every meeting

That's the morning briefing from the top. My calendar already tells me when a meeting is. What it never told me was the context: who this person is, why we're talking and where we left off.

Now I start client conversations where the last one ended. Better prepared calls make for better conversations. That's the whole point.

3. Email: triage and replies in my voice

This one surprised me.

It reads every message, labels it and understands the intent. Sales, support or operations. Then it drafts a reply in my voice.

Real replies. Not generic text. It knows the client and the history, so the draft does too.

Sometimes I send it as it is. Sometimes I tweak one line. Either way, email stopped draining my energy.

4. Automation: n8n workflows from a description

When I need a new workflow, I don't open n8n and start dragging nodes around. I explain what I want.

Claude Code builds it, logic included, and pushes it to my n8n instance where I review it. No manual setup. No staring at screens. Automation feels simple again.

5. Sales: leads don't wait for me

Leads get replies while I sleep. They get qualified. Calls get booked.

Deals move forward without me chasing them. For a small business, that's the difference between a lead that cools off in someone's inbox and a booked call.

None of this is about replacing people. It's about removing friction: the small lookups, handoffs and "what did we agree again?" moments that eat a day without anyone noticing. It's also what we build for other companies at Arcgent. Digital team members that actually work inside a business, not another tool on the pile.

What changed in my week, before and after?

I was skeptical at the start. Giving an AI access to my files, my clients and my email sounded risky. So I tested it on something small.

I asked Claude Code to write a cold email to a prospect. Normally I'd spend 30 to 45 minutes researching the company and writing something personal. This took 2 minutes. And the email was better than what I usually write. More personal. More specific. More relevant.

I figured it was a lucky shot. So I gave it another task. And another. And another.

But speed isn't what changed my business. Headspace did.

I'm not stuck in execution mode anymore. I think about strategy. I have conversations with clients instead of staring at a blank screen. Follow-up happens faster because it doesn't wait for a free hour in my calendar. I run the business instead of drowning in busywork.

The hours are the mechanism. What you do with them is the result.

Can Claude Code build more than workflows?

Yes. The five jobs above are about running a business day to day. Claude Code can also build complete systems.

One example: I built an automated affiliate website generator with it. The system finds a niche by checking competition, search volume and real product data. It writes product reviews, comparisons, buying guides and how-to articles. It builds a Next.js site, deploys it to Vercel, then buys a domain and connects it. After that it keeps running: a new niche site every Monday and new articles every day at 06:00 UTC, with monitoring in the background.

The point isn't the affiliate site. It's that Claude Code doesn't just write code. You describe an outcome and it builds the system around it. The same thing happens, on a smaller scale, every time I describe a new n8n workflow.

What does it cost, and what should you watch out for?

This setup has costs, and they aren't all in the subscription.

You're giving an AI access to your business. Files, clients, email, calendar. That should make you think twice. It made me think twice. Decide on purpose what it can read, what it can change and what it can send. Start with read access and drafts. Widen it only when the output has earned it.

You still review what goes out. The email drafts are good, often good enough to send unchanged. But they go out under my name, so I read them first. Same for proposals and new workflows. Claude Code does the heavy lifting. I make the final call.

Setup takes real effort. Installing Claude Code is the easy part. Connecting your tools, writing the memory notes and testing the first tasks takes time. The payoff comes after that, not on day one.

Memory has to be built and maintained. The output is only as good as what's in the notes. When an offer changes, a process changes or a client relationship shifts, the memory has to change with it. Outdated memory produces confident drafts that are wrong. I update the notes as the business moves, the same way I'd brief a colleague.

It doesn't replace judgment. It knows my business because I wrote it down. Which deals to chase, what to say no to and where the company goes next still sit with me. It removes the friction around those decisions. It doesn't make them.

How do you start using Claude Code for your business?

You don't need to be a developer. You don't need to understand how it works under the hood. You need to start small and stick with it for a few weeks. The learning curve is shorter than you think.

Here's the order I'd follow:

1. Pick one recurring task that needs context. Writing emails, researching prospects or drafting content are good first picks. They come back every week, so you'll see the difference fast.
2. Write one memory note. One page on what you sell, who you sell to and how you write. In Claude Code, this can live in a CLAUDE.md file in your project folder, which it reads at the start of every session.
3. Run it side by side for a week. Do the task with Claude Code, compare it with your own version and correct what's off.
4. Turn every correction into memory. If you explain something twice, it belongs in the notes.
5. Connect one tool. Once the drafts are trustworthy, give it access to one system, like your task board or your inbox. Keep it on drafts, and review before anything is sent.
6. Add the next job. Calendar briefings, email triage, workflows, sales follow-up. One at a time.

That's how mine grew. Not as one big project. One task, then another, then another, until it knew the business well enough to run real parts of it.

Start with the memory. The tools get easier after that.