How to Automate Your Marketing
in 48 Hours Using Claude Code

Most marketing automation conversations go one of two ways: either someone's trying to sell you a $500/month SaaS tool with a 90-day onboarding, or they're showing you a Zapier flowchart that breaks the moment anything changes.

This post is neither. I'm going to show you exactly how I use Claude Code to build marketing automation from scratch — the kind that runs daily, handles real data, and doesn't require a subscription for every component.

The goal isn't to automate everything. The goal is to automate the one thing that's eating the most of your time and delivering the least creativity. Find that thing first.

Before You Start: Define the One Thing

Claude Code can build almost anything, but "automate my marketing" is too vague. Here's a framework I use with every client:

• What task do you do manually more than 3 times per week?
• What's the outcome of that task? (a spreadsheet, an email, a post, a report)
• What are the inputs? (a URL, a list, a database, an API)

The best automation candidates: responding to reviews, generating weekly reports, researching leads, scheduling social content, sending follow-up emails. Pick one.

The 5-Step Build Process

Step 1 — Define the output first

Before you write a single line of code (or ask Claude Code to), know exactly what the finished automation produces. Is it a Google Sheet row? An email? A file? A Slack message? Being specific here saves hours.

Example: "Every morning, I want a Google Sheet row added with: company name, website, phone number, and estimated revenue — for every new business that opened in my city this week."

Step 2 — Identify your data source

Automations need inputs. Common ones I use:

• Google Maps API (for local business data)
• LinkedIn (public profiles, job listings)
• RSS feeds (news, job boards, competitor blogs)
• Google Sheets (as both input and output)
• Your own website/CRM (form submissions, signups)

Step 3 — Write your Claude Code prompt

This is where most people get stuck. The key is to be specific about the tech stack you want. Here's the actual prompt structure I use:

That level of specificity is what gets you a working script on the first attempt, not a generic skeleton you have to rebuild.

Step 4 — Iterate in sessions

Claude Code builds in layers. First session: get the core script working with test data. Second session: add error handling and scheduling. Third session: add the email summary and deploy.

Don't try to build everything at once. Each session should have one clear goal.

Step 5 — Deploy and schedule

Once it works locally, Claude Code can also write the deployment config. I usually deploy to one of:

• GitHub Actions — free, runs on schedule, great for scripts
• A simple VPS (DigitalOcean, $6/month) — for anything that needs to run continuously
• Vercel serverless functions — for webhook-triggered automations

Real Example: The Lead Generation Pipeline I Built in 4 Hours

A fitness studio owner in Vancouver wanted a list of every new business that opened in her neighbourhood each month — potential B2B clients for her corporate wellness packages.

Here's what I built:

1. A script that queries Google Maps for new businesses by category and postal code
2. Enriches each result with the owner's likely LinkedIn profile (via search)
3. Scores each lead by relevance (employee count, industry, website presence)
4. Drops qualified leads into a Google Sheet with a personalised first-line for outreach
5. Sends a weekly email digest: "Here are your 15 best leads this week"

Total build time: 4 hours. Monthly cost to run: $0 (GitHub Actions free tier). Leads delivered per month: ~60 qualified prospects.

She was spending 6+ hours a week on manual prospecting. Now she spends 20 minutes reviewing and personalising the outreach Claude already drafted.

The Automations Worth Building First

Based on what I've built for clients, here's where Claude Code delivers the fastest ROI:

• Review response drafting — Monitor Google/Yelp, draft branded responses, one-click approve
• Weekly competitor brief — Scrape 10 competitors, summarise changes, email Monday morning
• Lead enrichment — Take a list of company names, add contact info, score by fit
• Social content ideas — Scan trending topics in your niche, generate 5 post angles daily
• Analytics summary — Pull GA4 + social data, write plain-English "what happened last week" email

What Claude Code Can't Do (Yet)

I want to be honest. Claude Code is not good at:

• Building automations that require CAPTCHA bypass or aggressive scraping (and it shouldn't)
• Complex OAuth flows without guidance (doable, but needs more direction)
• Maintaining long-running state without a database (you need to plan the data layer upfront)

None of these are dealbreakers. They just mean you need to think about the architecture before you start building — which is exactly what a session with me helps with.

If you want to see more examples of what's possible, read what I've already built with Claude Code. Or if you're trying to decide whether to build it yourself or hire someone, check out the Claude Code vs hiring a developer post.