Twenty emails a morning, zero I wrote
My operator finds twenty leads a day, looks up their work emails, drafts a personalized message for each one, and sends them. I read the replies.
Cold outreach was a task I kept skipping. I knew I needed to reach potential clients every day, but writing twenty individual emails is not how I wanted to spend my mornings.
So I described the job to the operator and asked it to take over.
The search runs at 23:00 UTC, which is 07:00 my time. It pulls fresh leads from a professional contact database: two to fifty employees, a marketing, advertising, or software headline, based in the US, UK, Australia, or Singapore. The cursor saves the last page seen and the IDs already visited, so the same person never appears twice across days. On the first morning dry run it returned twenty-five fresh rows in three pages.
From there it looks up work emails. Each successful lookup costs three credits. Leads without a match are skipped for free. On day one, nine of ten people had a findable address.
The first draft rules were strict. Each message ran between ninety and one hundred forty words. It named one true thing from the person's actual headline, asked one question, and linked to my services page. The prompt required varied openings and no two messages could share the same first sentence. A humanize pass ran on every draft before it was saved. Two days later, after no replies on the first twenty-nine, I cut the messages to sixty to ninety words and took the link out.
The first version posted drafts to a Discord channel, one numbered message each. I read them and approved each one by name. The send hook enforced the exact command format. The first time I used a shorthand form with a shell prefix, the hook refused it.
That step lasted about two hours.
I decided the batch should send on its own. The one condition: every email carries an opt-out line, and a "no" reply adds that address to a blocked file the morning batch checks before touching anyone. No one who said no gets another email.
The eight remaining drafts that afternoon went out from my Gmail account in one minute. I raised the daily count from ten to twenty the same day. The original estimate put the search credits at fifty to sixty days at ten a day.
What I did not expect to spend time on was the deduplication. The search holds a cursor. The send list carries a seen file that grows each day. Without it, the same person would appear on Monday and again on Wednesday. Getting that right before the first run was what made the rest of the system worth trusting.
The part I still handle is the reply. When someone writes back, I read it and decide what to say. On request, the operator can draft a reply, but I send it. Volume is handled. The conversation stays mine.