If you’ve ever sat in front of a blank screen inside Mailchimp or SendGrid - trying to build a single newsletter issue from scratch, you know the exact flavor of soul-crushing dread I'm talking about.
You're trying to perform five completely different jobs simultaneously:

This article is the Part 2 of my series The $0 Email Engine: How I tried to Outsmart Email Service Providers. The first article you can read here: The $0 Email Engine: How I Used Notion, GitHub, Amazon SES to Outsmart Email Service Providers
Trying to do all five tasks in one sitting is a recipe for instant procrastination.
As someone who struggles with motivation, gets bored easily, and has a habit of abandoning half-finished projects, attempting to tackle monolithic email campaigns almost killed my newsletter output completely.
My solution wasn't to "work harder" or force myself into some rigid corporate discipline.
My solution was to embrace my natural laziness, split the workflow into microscopic chunks, and delegate the tasks I hated to do to people who were better at them than me.
When I looked at my email production pipeline, two major roadblocks were causing me to abandon drafts:
Here is how I engineered human-powered, micro-tasked solutions for both without breaking the bank.
Let's start(again) with an honest confession: My English isn't perfect.
I didn't go to a traditional English-speaking school, and while my ideas are strong and my tone is sharp(because im really prefect), my raw drafts are littered with grammatical landmines — bad verb tenses, missing articles, and weird sentence structures.
In tech writing, people are unforgiving.
The second a reader sees two grammatical errors in a paragraph, they tune out:
"Well, this guy can't write, fuck off."
Trying to meticulously self-edit my English while simultaneously drafting complex technical concepts drained all my creative energy.
So I stopped trying.
I hired a professional copywriter — a native-level ghostwriting machine.
My job was no longer to write polished final drafts.
My job became being the Architect and Editor-in-Chief.
I dump raw, unfiltered thoughts, technical rants, and bullet points into a clean Notion document.
I pass that raw outline to my copywriter.
She fixes the grammar, smooths out the verbs, cleans up the syntax, and ensures the piece flows effortlessly — all while strictly adhering to my sarcastic, direct, "badass" style guidelines.
By separating ideation from syntactical polishing, writing stopped feeling like homework.
Every high-converting newsletter needs solid external context — relevant tech news, industry debates, or supporting documentation to back up your arguments.
Searching Google, digging through Hacker News, Hackernoon, crypto-related websites and assembling curated links is not hard work.
But it is tedious, repetitive, and mentally draining when you're trying to focus on high-level strategy.
Instead of writing a complex Python scraper script or wasting two hours manually clicking search results, I hired a freelance virtual assistant to act as a human link-scraping engine.
The workflow is dead simple:
Once my core topic is locked in Notion, I create a precise, detailed task:
"Find 5 recent articles discussing AWS SES pricing vs SendGrid, tag them by main takeaway, and put them in a spreadsheet."
My freelancer — working asynchronously on their own time — conducts the research, gathers the URLs, categorizes the metadata, and drops a clean CSV file directly into my workspace.
Was the quality of the scraped links always 100% ideal?
No. NEVER.
But it didn't need to be.
It was cheap, human-executed research that saved me hours of brainpower and gave me a structured foundation to build on.
Here is the secret psychological benefit of micro-tasking:
It forces you to plan ahead.
When you operate as a solo operator doing everything inside an ESP, you default to panic-drafting emails two hours before they are supposed to go out.
The result is always low-quality content and immense personal stress. AND YOU WILL MAKE MISTAKES.
When you rely on freelancers or team members who work asynchronously, you cannot panic-draft.
Because my copywriter and link scraper are contractors working on their own schedules, I am forced to write detailed, structured task briefs days in advance.
+-----------------------------------------------------------------------------------+
| THE ASYNCHRONOUS ENGINE WORKFLOW |
+-----------------------------------------------------------------------------------+
| |
| [YOU] Drafts raw concept & detailed briefs in Notion. |
| │ |
| ├───> [LINK SCRAPER] Scours web, populates CSV with research & tags. |
| │ |
| └───> [GHOSTWRITER] Polishes raw rants, fixes syntax, preserves voice. |
| |
| [YOU] Reviews clean Markdown, commits to GitHub, triggers SES. |
| |
+-----------------------------------------------------------------------------------+
By turning a chaotic, single-sitting chore into an organized, multi-step assembly line, I accidentally cured my own procrastination.
I wasn't staring at a terrifying, complex project anymore.
I was just checking off small, 10-minute manager actions.
Stop trying to be a superhero who writes the code, designs the layout, edits the grammar, gathers the links, and manages the sending server all by yourself.
The most efficient developers and content managers aren't the ones who work 14-hour days doing manual labor.
here is my design of a modular system that simplify the friction**(like i did)**:
Just do it - meme page (@Madafaka21216969)
In Part 3 of these series, I will share what happens when this LEAN, multi-tool engine starts hitting its limits — and how turning those manual friction points into an automated script with it is flaws led directly to the creation of LLazyEmail.
End!