646: How We’re Using Claude Code To Get Back 30 Hours A Week

Podcast: Download (Duration: 41:00 — 47.2MB)

Claude Code is the terminal-based version of Anthropic’s Claude that runs on your computer, reads and writes your files, and executes scripts for you. On this episode of the My Wife Quit Her Job podcast, my co-host Toni and I break down exactly how we are using it to save around 30 hours a week between our ecommerce and consulting businesses. She uses it heavily for data analysis, Klaviyo audits, and email drafting; I use it for content generation, custom scripts, and fixing broken WordPress plugins.

The name “Claude Code” is misleading, because it has almost nothing to do with coding. It is essentially Claude with access to your computer, and the best use cases for ecommerce sellers involve zero code writing at all.

If you are already using regular Claude or ChatGPT in a browser, Claude Code is the next step and it is where the real time savings happen.

Below is the full breakdown: the specific workflows we automated first, how to install it if you have never opened a terminal, the mistakes we made, and the limitations we hit that are worth knowing before you spend hours going down a dead end.

Get My Free Mini Course On How To Start A Successful Ecommerce Store

If you are interested in starting an ecommerce business, I put together a comprehensive package of resources that will help you launch your own online store from complete scratch. Be sure to grab it before you leave!

Click Here To Download

Key takeaways

• Claude Code is Claude with permission to read, write, and modify files on your computer. It runs in your terminal. Despite the name, most of the highest-value ecommerce use cases involve no code writing at all.
• The highest-ROI workflows to automate first: Klaviyo flow audits, editorial calendar folder creation, customer-support email drafting, review-mining for short-form video scripts, and repurposing one piece of content into 10 platform-specific variants.
• The skill that matters most is articulating what you want in plain English. Traditional coding skills are becoming less valuable; specification and prompting are becoming more valuable.
• Skip Claude Cowork. Everything Cowork does, Claude Code does better and with fewer limits.
• You do NOT need to know how to code or how to open a terminal. Ask Claude in a browser to walk you through installing Claude Code step by step; it will.
• Always double-check what it writes. Especially when it touches Klaviyo segments (terminology mismatch), gives permissions (“yes, yes, yes”), or edits files outside the project directory.

What is Claude Code and how is it different from Claude and Claude Cowork?

Claude Code is a terminal application that gives Claude direct access to read, write, and execute files on your computer. Regular Claude runs in a browser and can only see what you paste in; Claude Code can open your Klaviyo export from the folder you saved it in, analyze it, and write the summary chart to disk without you copy-pasting anything. Claude Cowork is a middle option that sits between them, and you should skip it entirely because Claude Code is more versatile.

The three tiers, in order of power and setup effort:

1. Claude (browser): paste text in, read text out. Fine for one-off analysis but you export from every tool by hand and paste it into the chat.
2. Claude Cowork: a browser-based intermediate step. Not worth learning; anything it does, Claude Code does with fewer limits.
3. Claude Code (terminal): Claude with file-system access. Runs on your Mac or PC via the terminal. This is where the 30-hour-a-week time savings actually live.

The name causes confusion. The word “Code” makes people who do not write code assume this tool is not for them, and it is not a coding tool.

Toni is not a coder and gets the highest-value use out of it in our team. If the tool were renamed “Claude Desktop” it would probably have 10x the users.

Do you need to know how to code to use Claude Code?

You do not need to know how to code, and you do not need to have ever opened a terminal before. Toni had to Google “where is the terminal on a Mac” the first time. The trick is to use regular Claude (in the browser) to walk you through the Claude Code install, step by step, and to keep asking dumb questions until you understand each step.

The pattern that works for non-technical users:

1. Open regular Claude in your browser (or ChatGPT if you are managing Claude API credits).
2. Ask: “I have a Mac (or Windows PC). Walk me through installing Claude Code step by step. Show me what to click and what to type.”
3. When you get stuck, paste the error message back and say “explain this to me like I have never used a terminal.”
4. Keep asking until you understand. It never tells you you are dumb. In fact it tends to inflate your ego, which is a separate problem worth double-checking against.

The classic “help me, my Mac died and I do not know where the terminal is” moment happens to everyone the first time. You are not behind if you have to Google that.

What ecommerce workflows should I automate with Claude Code first?

The highest-ROI ecommerce workflows to automate first are Klaviyo flow audits, editorial-calendar folder auto-creation, customer support triage, review-to-short-form-video-script generation, and one-piece-of-content-into-ten-platform-variants repurposing. Each of these takes a task that used to eat multiple hours per week and reduces it to a single “run this” command.

Ranked by how quickly a normal ecommerce store will see time savings:

1. Klaviyo flow audits. Any store with more than 10 flows should be auditing them monthly. Nobody does because the export is a mess. Claude Code pulls flows, sorts by activity, color-codes stale ones, and hands you a “delete these, fix these, ignore these” summary chart.
2. Customer-support email triage. A morning script scans Gorgias tickets, marks obvious sponsor/spam solicitations for review, and drafts replies to the real support questions. Saves an hour of inbox digging.
3. Editorial-calendar folder creation. Add a row to a Google Sheets editorial calendar, and Claude Code auto-creates the matching Google Drive folder with a marketing brief, launch plan, and graphics sub-folders using your naming convention. Saves the entire job that used to be a person’s task.
4. Review-to-short-form-video-scripts. Export your product reviews from a plugin like Judge.me, feed them to Claude Code, and get back 50+ short-form video scripts that handle the most common objections. 15 minutes of your time, weeks of content queued.
5. Content repurposing. One YouTube script becomes a LinkedIn post, a Twitter thread, a Facebook post, a TikTok script, and a full SEO-optimized blog post that embeds the video. All in Steve’s voice because Claude Code was trained on his prior writing.

How do you use Claude Code to audit a Klaviyo account?

You use Claude Code to audit a Klaviyo account by giving it access to your Klaviyo export folder and a prompt that spells out how to evaluate each flow (age, active subscribers, open rate, revenue per recipient). It reads the export, sorts and aggregates the data, and returns a color-coded chart telling you which flows to delete, fix, or ignore.

The workflow that Toni uses for a client with 187 Klaviyo flows:

1. Export flows from Klaviyo, aggregated by month.
2. Save the export into a folder Claude Code has access to.
3. Prompt: “Analyze these flows. For each one, tell me the age, how many subscribers are actively in it, and flag any flow that has had zero recipients in 6+ months. Color-code the output: green (healthy), yellow (needs review), red (delete or archive).”
4. Claude Code reads the sheet, produces the summary chart, and calls out flows that need immediate attention.

This is the workflow that turned monthly audits from “impossible with 187 flows” into “runs in three minutes.” Trying the same thing with browser Claude requires exporting, uploading, waiting for it to process, and dealing with truncation on the larger accounts.

Can Claude Code check whether contractors are actually doing their work?

Yes, and it is one of the more underrated uses. If you have hired someone to manage your Klaviyo or Meta ads, Claude Code can dump the account’s actual state and check it against what the contractor said they were going to deliver. “You said you would create 10 flows this month. Here are the 4 you actually created.”

This is legitimately useful for stores that outsource to agencies or freelancers. You do not need to know Klaviyo or Meta yourself; Claude Code reads the account state and translates it into “here is what actually happened this month vs. what was promised.”

The natural extension is having Claude Code do the work directly once you have trained it on the past patterns. Hire a contractor to build the first 10 flows, feed those into Claude Code as reference, and have it generate the next 10 following the same conventions. Then check the work before it goes out.

What are the biggest mistakes to avoid when starting with Claude Code?

The three biggest mistakes when starting with Claude Code are giving blanket permissions that let it modify files outside your project directory, not double-checking its output on tools with weird terminology (like Klaviyo segments), and expecting it to be right the first time on complex workflows. All three are recoverable, but each has burned real users badly.

The permission trap: Claude Code asks “can I do X?” many times per session, and it is tempting to click “yes, yes, don’t ask me again” and move on. I did this on a whim once and Claude Code started modifying files outside the project directory.

Nothing terrible happened in my case, but the news has recent stories about users who accidentally gave permission and Claude deleted an inbox. Do not blanket-permission the whole disk; give per-project permissions instead.

The terminology gap: on tools like Klaviyo, Claude Code can tell you exactly what segments you need to build, but sometimes uses terminology that does not match the tool’s actual UI. It will describe a segment condition perfectly and then you go to Klaviyo and cannot find where to click.

This deficiency will probably close over time. For now, expect to do a small amount of manual translation on Klaviyo segment builders.

The first-try expectation: complex workflows almost never work on the first prompt. Expect three rounds of “this is 85% there, now fix these five specific things.” That last 15% is why you double-check every output.

How do you keep Claude Code from touching files it shouldn’t?

You keep Claude Code from touching files it should not by scoping permissions per project rather than blanket-approving with “yes, don’t ask me again,” and by starting each project in its own dedicated folder so the permission scope is that folder only. If you are cautious, run it on a virtual private server (VPS) instead of your main machine so any accident is contained to a disposable environment.

The VPS pattern is worth considering for anything experimental. You install Claude Code on a $10/month cloud server, give it whatever permissions you want, and if something goes wrong the blast radius is that server, not your laptop with your family photos and your business records on it. Steve is planning to move team-shared Claude Code work onto a VPS for exactly this reason.

For most solo users, scoped-per-project permissions on your normal machine are fine. Just resist the muscle-memory habit of hitting “yes” without reading what the permission is for.

What are Claude Code’s current limitations for ecommerce work?

Claude Code’s current limitations for ecommerce work include some rough edges on Klaviyo segment building (right logic, wrong terminology), the fact that it is tied to your specific machine (not shared across a team by default), and the general AI risk of confident-sounding wrong answers on any complex tool it has not been trained deeply on. None of these are dealbreakers, and most will close within a year.

The machine-tied problem: my Claude Code project on my desktop is not automatically available on my laptop. If you swap between computers, you either sync the project folder manually, use git, or set up on a VPS that both machines connect to.

The over-confidence problem: Claude Code will produce a beautifully formatted answer that is subtly wrong. This is the classic AI failure mode. The countermeasure is to always double-check load-bearing outputs, especially anything that will get sent to customers, spent as ad budget, or executed as a segment.

The Klaviyo segment issue specifically: Toni hit this last week analyzing a 300,000-subscriber list. Claude Code correctly identified the buckets to segment (unengaged, problem children, etc.), but the segment conditions it suggested did not map cleanly to Klaviyo’s actual UI terminology. Expected in the current version; expect improvement.

Frequently asked questions

What is Claude Code and how is it different from regular Claude?

Claude Code is a terminal application that gives Claude direct read, write, and execute access to files on your computer, while regular Claude runs in a browser and only sees what you paste in. The name is misleading because most of the highest-value ecommerce use cases involve no code writing at all. If you are already using regular Claude for data analysis, Claude Code eliminates the export-upload-wait-download cycle.

Do I need to know how to code to use Claude Code?

No. Toni is not technical and gets the highest-value use of Claude Code on our team, because the core skill is articulating what you want in plain English. If you get stuck on setup, ask regular Claude in your browser to walk you through the install step by step, and keep asking dumb questions until each step makes sense.

Which Claude Code workflows save the most time for an ecommerce store?

The five highest-ROI workflows to start with are Klaviyo flow audits (especially if you have 30+ flows), customer-support email triage, editorial-calendar folder auto-creation, generating short-form video scripts from your product reviews, and repurposing one piece of long-form content into 10 platform-specific variants. Between those five, most stores will save 20-30 hours per month in the first month.

Should I use Claude Cowork instead of Claude Code?

Skip Claude Cowork. Everything Cowork does, Claude Code does better and with fewer limits. The extra intermediate step is not worth learning, especially since installing Claude Code takes maybe 20 minutes if you use browser Claude to walk you through it.

What is the biggest risk of using Claude Code?

The biggest risk is giving blanket permissions (“yes, yes, don’t ask me again”) that let Claude Code modify files outside your project directory. There have been real news stories about accidents where users approved a permission chain and Claude deleted their emails. Scope permissions per project, do not blanket-approve, and consider running experimental work on a VPS so any accident is contained to a disposable machine.

How much time can Claude Code realistically save an ecommerce operator?

Toni and I both estimate around 30 hours a week saved between our businesses once the initial workflows are set up. The setup cost is real; each workflow typically takes an hour or two of prompting to get to a state where you trust it. The payoff compounds because every subsequent run is essentially free time.

Ready To Get Serious About Starting An Online Business?

If you are really considering starting your own online business, then you have to check out my free mini course on How To Create A Niche Online Store In 5 Easy Steps.

In this 6 day mini course, I reveal the steps that my wife and I took to earn 100 thousand dollars in the span of just a year. Best of all, it's absolutely free!