4–7 hours. Then 30 minutes. Same output. Same quality. Same human review at the end.
This isn’t theory. This is what one of our forward-deployed marketing operators achieved rebuilding a weekly newsletter system using AI.
Let me show you exactly how.
The Before State
Weekly newsletter production used to look like this:
Research phase (90–120 minutes):
- Manually browse industry news sites, LinkedIn, Twitter
- Screenshot interesting trends and stories
- Drop them into a running document
- Try to remember what mattered and why
Drafting phase (120–180 minutes):
- Stare at blank document
- Write intro from scratch
- Summarize each story manually
- Try to find a connecting thread
- Rewrite sections that don’t flow
- Edit for voice and tone
Editing and approval loop (60–90 minutes):
- Send draft for review
- Wait for feedback
- Incorporate changes
- Send again if major revisions needed
Formatting and scheduling (30–45 minutes):
- Copy into email platform
- Add images and formatting
- Schedule send
- Export for other channels
Total time: 4–7 hours per issue. Every week. Relentlessly.
One person’s week consumed by one asset.
For a consultant or fractional growth advisor, that’s billable time lost. For a startup marketing team, that’s capacity they don’t have. For an agency, that’s margin erosion.
And here’s the thing: 90% of that time was mechanical labor, not strategic thinking.
The Rebuilt Workflow
Here’s the new system, step by step:
Step 1: Automated Research (Perplexity + Relay)
Every Monday morning, a Relay automation triggers. It sends targeted queries to Perplexity:
- “What are the top 5 stories in [industry] this week?”
- “What funding rounds happened in [sector] in the last 7 days?”
- “What regulatory or market changes are B2B tech companies discussing?”
Perplexity returns summaries with sources. Relay drops them into a structured Notion database.
Time: 0 minutes human effort. Runs automatically.
Step 2: Trend Surfacing and Prioritization (Claude)
The Notion database feeds into Claude with this prompt:
“Review these 15 stories. Identify the 3–5 most relevant for [audience]. Explain why each matters to them. Flag any patterns or themes connecting the stories.”
Claude returns:
- The 3–5 stories that actually matter
- Why they’re relevant to the specific audience
- A potential narrative thread connecting them
Time: 5 minutes to review Claude’s output and make final selections.
Step 3: Draft Generation (Claude + Style Template)
The selected stories feed back into Claude with:
- The newsletter’s style guide
- Previous successful issues as examples
- Audience context and tone requirements
Prompt: “Write this week’s newsletter. Follow the style template. Keep it conversational, not corporate. Lead with the most surprising insight. Connect the stories with a clear throughline.”
Claude generates a full draft in 60 seconds.
Time: 0 minutes human effort.
Step 4: Human Review Pass (Taste, Accuracy, Voice)
This is where the human adds value. The operator reads the draft and asks:
- Does this sound like us?
- Are the insights actually interesting or just obvious?
- Is anything factually wrong or misleading?
- Does the narrative thread work?
They make edits. Adjust tone. Sharpen a headline. Cut a weak paragraph. Add a personal observation.
This is the irreplaceable part. The AI eliminated the mechanical labor. The human focuses on taste, editorial judgment, and quality control.
Time: 30 minutes.
Step 5: Design and Formatting (Designer + Platform)
The approved draft goes to a designer (or design tool) for visuals and final formatting. Images, layout, platform upload.
Time: 30 minutes.
Total time: ~60 minutes. Down from 4–7 hours.
Same newsletter. Same quality. Same human oversight where it matters.
The Critical Design Principle
Here’s what makes this work: the system kept humans in the loop deliberately.
Not because the AI couldn’t do more. It probably could. You could ask Claude to format the email, generate images, schedule the send.
But the quality layer — taste, editorial judgment, fact verification — is where human effort is irreplaceable and worth spending time.
The automation eliminated the mechanical labor. It didn’t eliminate the thinking.
This is the difference between AI leverage and AI replacement.
AI replacement: Remove humans entirely, accept lower quality, hope no one notices.
AI leverage: Remove the mechanical work humans shouldn’t be doing, free them to focus on the work only humans can do well.
Taste. Judgment. Context. Voice.
These don’t automate. But everything around them does.
The takeaway
AI leverage isn't doing the same task faster — it's rebuilding the workflow so 4–7 hours becomes 30 minutes. Find the process you dread each week and redesign it around what AI can own, not what it can assist.
Why This Scales
The operator who built this system now runs two newsletters:
- Her own (3,000 subscribers)
- A client’s (8,000 subscribers)
She uses the same workflow for both. Slight variations in prompts and style templates. But the structure is identical.
And here’s the key: because it’s modular and documented, it can be handed off to a different operator in a day.
It’s not a personal workflow dependent on one person’s knowledge. It’s infrastructure.
That distinction is what makes it commercially valuable.
If she gets sick, someone else can run it. If the client wants to bring it in-house, they can. If we need to replicate it for another client, we already have the blueprint.
Systems scale. Personal workflows don’t.
The Audit Framework
Not every workflow is ripe for this treatment. Here’s how to find your equivalent:
Look for workflows that are:
1. Repeatable on a fixed cadence
Weekly newsletters. Monthly reports. Daily social posts. Quarterly competitive analysis.
If it happens regularly and follows a pattern, it’s automatable.
2. Primarily mechanical rather than requiring original thought
Research and summarization: mechanical.
Drafting from a template: mechanical.
Formatting and scheduling: mechanical.
Deciding what’s interesting: human.
Judging tone and voice: human.
Fact-checking and quality control: human.
If 80% of the task is mechanical, automate the 80%.
3. Consuming senior time on junior tasks
If your fractional CMO, head of growth, or senior strategist is spending hours on newsletter production, social clip creation, or report formatting — that’s the wrong use of their time.
Senior time should go to strategy, judgment, and decision-making. Not mechanical execution.
Real Examples to Audit
Here are workflows I’ve seen rebuilt with AI in fractional growth and consulting engagements:
Newsletter production (covered above)
- Before: 4–7 hours/week
- After: 30 minutes/week
- AI tools: Perplexity, Claude, Relay
Social media clip creation (video → short-form content)
- Before: 3–4 hours per video (transcription, editing, caption writing, thumbnail design)
- After: 45 minutes per video
- AI tools: Descript for transcription, Claude for clip selection and captions, Canva AI for thumbnails
Competitive monitoring (tracking competitors’ messaging, pricing, features)
- Before: 2 hours/week manually checking websites and social
- After: 15 minutes/week reviewing automated reports
- AI tools: Perplexity for research, Relay for scheduling, Claude for synthesis
Sales call briefing (researching prospects before discovery calls)
- Before: 30 minutes per call (LinkedIn stalking, company research, news search)
- After: 5 minutes per call reviewing AI-generated brief
- AI tools: Clay for enrichment, Claude for synthesis, Relay for delivery
Reporting and dashboards (monthly performance summaries for clients or stakeholders)
- Before: 3–4 hours pulling data, building slides, writing narrative
- After: 45 minutes reviewing AI draft and adjusting
- AI tools: API connections to analytics platforms, Claude for narrative generation
The pattern: Mechanical work automated. Human judgment preserved.
What AI Leverage Actually Looks Like
Let me be specific about what changed for the newsletter operator.
Before AI leverage:
- Spending 25–30 hours/month on newsletter production (her own + client)
- That’s 60–75% of her available capacity
- No time for strategic work, client development, or new projects
- Burnout risk high
After AI leverage:
- Spending 4 hours/month on newsletter production
- That’s 10% of her capacity
- Freed up 20+ hours/month for higher-value work
- Can take on 2–3 more clients without increasing hours
This isn’t an abstract productivity promise. It’s a specific before and after with measurable time savings.
And here’s what makes it real: she’s not producing more newsletters. She’s producing the same newsletters in a fraction of the time.
That’s leverage.
Not “do more with AI.” Do the same with less effort, then reallocate that effort to higher-value work.
The Tools That Matter
For anyone wanting to replicate this, here are the tools that actually work:
Relay (relay.app) — Workflow automation and orchestration. Think Zapier, but designed for AI-native workflows. Connects Perplexity, Claude, Notion, email platforms, etc.
Perplexity — AI-powered research. Better than manually browsing news sites. Returns summaries with sources.
Claude (Anthropic) — Content generation and synthesis. Better at following style guides and maintaining voice than GPT-4 in my experience.
Notion — Database for organizing research and drafts. Works well with Relay automations.
Total cost: ~$100/month for all tools combined.
Compare that to 20+ hours saved monthly. The ROI is immediate.
If You Don’t Have This Yet
Here’s the honest truth: AI leverage isn’t an abstract productivity promise.
It looks like a specific before and after. Named tools. A documented process. A number you can measure.
If you don’t have that yet, you don’t have AI leverage — you have AI curiosity.
And curiosity is fine. But it doesn’t free up 20 hours a month.
The companies winning with AI aren’t the ones trying everything. They’re the ones who identified one high-friction workflow, rebuilt it systematically, and documented it so it scales.
Newsletter production. Competitive monitoring. Sales briefings. Reporting.
Pick one. Rebuild it. Measure the time saved. Then move to the next.
That’s how you build AI marketing infrastructure, not just experiment with AI tools.
← Back to all posts