Most marketing teams waste 12 to 15 hours a week on tasks that follow the same pattern every time. Email drafts, LinkedIn captions, segmentation logic, calendar builds. None of it requires judgment. All of it eats time that should go toward thinking.
Lilach Bullock, an AI implementation consultant, has spent the past five years systematizing her own marketing operation. She estimates the result at 15 to 18 hours saved per week. At her hourly rate, she calculates that at £3,600 to £4,320 per week in reclaimed time, or £187,000 to £225,000 annually. The tools she used: Claude and ChatGPT API calls, Zapier or Make for connecting systems, Google Sheets with AppSheet for data automation, and ConvertKit’s native sequence templates. No expensive platform required.
Here is what she automated, what it saved, and the one mistake that cost her 12 weeks of metric recovery.
️ The four workflows worth automating first
1. Email nurture sequences
Writing a seven-email nurture sequence manually takes 8 to 10 hours: roughly one hour per email plus editing and QA. With an AI-assisted workflow, the same sequence drafts in 45 minutes, then gets a 90-minute human pass for voice and specificity.
Net saved: 5.75 hours per nurture sequence. At two sequences per month, that’s 11.5 hours per month, or 138 hours per year. The human work shifts from blank-page writing to editorial review.
2. LinkedIn captions from blog posts
Taking a 1,500-word blog post and turning it into five LinkedIn variations takes 2 to 3 hours done manually. With Claude, the workflow looks like this: feed the blog URL plus a style guide prompt, receive five versions in 3 minutes, pick the two strongest, tweak for 15 minutes total.
Saved per post: 2.5 hours. Across 12 blog posts per year, that’s 30 hours.
3. Audience segmentation and tagging
Building behavioral segmentation rules manually inside an email tool (opened five times, clicked three times, never purchased) takes 4 to 5 hours and is error-prone. With an API integration, feeding user data and scoring rules to an AI model returns a clean segmented list in 20 minutes.
This one doesn’t run weekly, but when it does, it saves a full day of work.
4. Scheduling, formatting, and calendar creation
Bullock draws a clear line here: she does not automate the writing of social content. She writes the thinking and the voice herself. What she does automate is the scheduling, formatting, hashtag research, and calendar building. That saves about 90 minutes per week, or roughly 78 hours per year, without touching the content quality.

⚠️ What happened when she automated too much at once
In Q3 of last year, Bullock automated email sequences, LinkedIn captions, ad copy approval, and newsletter drafts all in the same month. She projected 25 hours per week in savings. Six weeks later, email open rates dropped 8 percent, LinkedIn engagement dropped 12 percent, and newsletter unsubscribes doubled.
The cause wasn’t bad AI output. It was a broken feedback loop. The content was flowing out so fast that she stopped reading replies, stopped checking which posts sparked conversations, and stopped noticing what wasn’t landing. The system became a content pump with no listening attached.
She rolled back two of the four automations. Then she added one manual step: every Thursday, she spends 90 minutes reading one week of sent emails and LinkedIn posts, reviewing replies, and noting what worked. That 90-minute session feeds directly into the next brief she gives the AI tool. Her metrics recovered within three weeks.
Automation isn’t about doing more things. It’s about doing the same important things faster so you have time to think about them.
How to start: a four-week rollout
Week one: pick one specific task
Not a category. One task. “Email sequences” is too broad. “Draft the nurture sequence for my bottom-of-funnel audience” is the right size. Before you automate it, time yourself doing it the old way. Write down the hours. That number is your baseline.
Week two: build the workflow in a document first
Don’t touch a no-code tool yet. Write a Google Doc with the exact prompt, the exact output you expect, and the exact human editing steps that follow. Test it twice. Revise the prompt based on what came back.
Bullock’s email sequence prompt runs about 400 words. It includes: the audience, the email goal, three examples of her best previous emails for tone, the key points to hit, and the required format (subject line, three paragraphs, one CTA).
Week three: measure for two weeks
Run the workflow four times. Time each run. Average them. Compare to your baseline. If you’ve saved more than 50 percent of the original time, keep it. If you’ve saved less, refine the prompt and try again.
Her email sequences went from 8 hours per sequence to 2 hours per sequence. That’s 75 percent. She kept it.
Week four: add it to your calendar, then stop
Once one workflow is winning, make it a recurring calendar task. Do not move to the second automation yet. Run the first one for a full month. Document every step. Only then pick your next task.

Real example: client onboarding emails via webhook
Bullock works with 8 to 10 new clients per quarter. Each previously received a five-email welcome sequence written manually at about 3 hours per client.
The current workflow: when a new client is added to her CRM, a webhook triggers an automation that pulls their name, industry, and company size into a Claude API call. The prompt instructs Claude to write a five-email welcome sequence for a company of that industry and size, in her attached tone. Claude returns five emails in about 45 seconds.
A human (Bullock or someone on her team) then spends 45 minutes personalizing, adding specific case studies, and adjusting timelines. Total work: 2 hours per client instead of 3. Saved per year: about 16 hours. The more important outcome: every client gets a welcome sequence within hours of signing, not days.
What to never automate
Strategy decisions, tone-of-voice choices, offer decisions, customer complaint responses, crisis communication, and anything that requires reading the unspoken need underneath what a customer is actually asking. AI is fast. It is not good at judgment.
Bullock’s specific warning: automating customer service emails. The AI answers the question the customer asked but misses the emotion underneath it. The customer feels replied to by a machine, not heard by a person. That distinction costs brands more than the time saved.
️ The tools (listed without recommendation)
- Claude or ChatGPT API calls for text generation
- Zapier or Make for connecting systems
- Google Sheets with AppSheet for data automation
- Native automation in ConvertKit for email sequence templates
The pattern is always the same: define the input, define the AI step, define the human review step, define the output. One operator she mentions spent £800 on a SaaS platform for something a £20/mo API subscription and a Google Sheet would have handled. Start with what you already have.
The team change-management problem
Solo operators own the feedback loop automatically. They see what worked and adjust. Teams don’t work that way.
Bullock built an automation, told her team to use it without sitting down with them, and two weeks later only one person was using it. The fix: show each person the time saved in their specific role, ask what’s hard about the new workflow, and iterate based on their input.
She also found that after automating the drafting work, her team got bored. They missed the creative writing. The solution was to shift what they owned: instead of writing emails, they now own customer research and tone development. They listen to calls, read feedback, write the brief that goes into the AI tool, and do the editorial pass. The work got more interesting because it moved up a level.
If you automate and your team gets more bored, you did it wrong.
How to audit your own tasks
The framework Bullock uses with clients:
- List every task you or your team do each week that is the same or very similar each time.
- Estimate the time each task takes.
- Multiply by 52 to get the annual hours cost.
- Rank by hours spent, not by difficulty to automate.
- Start with the task that costs the most hours and can be described in a clear prompt. Not the one that seems easiest.
Pick one task this week. Time it. Build a prompt. Test it twice. Compare the time. That’s the whole start.


