Cold outreach that can't email the wrong person: HoMOE for Hot Mess Cleans of Chicago
A local, human-approved outreach engine that sends a few good emails a day and treats 'never email someone who opted out' as its first job.
Hot Mess Cleans of Chicago is a boutique cleaning company working across Chicagoland. Like most small service firms, it wins commercial work through relationships: property managers, offices, contractors who need a post-construction clean. Finding those people is easy. Writing to them one at a time, remembering who to follow up with, and never contacting someone who said no is the part that falls apart in a spreadsheet. Bulk email tools solve the volume problem and create a worse one: they're built to send a lot, and a small business can't afford its domain being flagged as spam.
At a glance
| Client | Hot Mess Cleans of Chicago |
| Industry | Commercial and residential cleaning |
| What we built | A local outreach engine: import prospects, write a three-step sequence, approve it, and let it send a small number of personal emails a day |
| Where AI fits | Optional. When switched on, it drafts one short, personal opening line per prospect, which the owner sees before anything sends. It never blocks a send. |
| Stack | A desktop web app that runs only on the owner's computer, talking to Gmail and Google Sheets |
| Status | A local, human-approved outreach engine for a Chicago cleaning company |
The old way
- Keep prospects in a Google Sheet, with duplicates, three contacts at the same company, and stale rows.
- Copy a template into Gmail, edit the name and the business, send.
- Try to remember who needs a follow-up next Tuesday.
- Notice a reply days later, by which time a follow-up may already have gone out.
- Keep a mental list of who asked to be left alone, and hope the next import doesn't bring them back.
Every step depends on the owner's memory, and the failure that matters most, emailing someone who opted out, is the easiest one to make.
What we built
HoMOE (Hot Mess Outreach Engine) runs entirely on one computer. It has no public website, nothing listening from the internet, and no cloud database. It connects to the company's Google Workspace account, reads prospects from a Sheet or CSV, and sends through the owner's own Gmail, so every message is a real email from a real person, threaded like one.
A campaign is a three-step sequence: an opening email and two follow-ups. Nothing goes out until the owner approves it. Once approved, a separate background worker sends on a paced schedule inside a set daily window, under hard daily caps. It reads the inbox for replies, bounces and opt-outs, and stops each sequence on its own.
How the workflow changes
| Step | Before | After |
|---|---|---|
| Importing prospects | Paste rows and hope they're clean | An import preview explains every row it holds back: duplicates, missing fields, already suppressed |
| Writing | Edit each email by hand | Write the sequence once; HoMOE fills in each prospect and shows the finished email before activation |
| Approving | Implicit: you sent it, so it was approved | An explicit checklist: every template approved, sender verified, postal address set, and every prospect test-rendered so no "Hi {first_name}" ever leaves |
| Following up | Calendar reminders and memory | Follow-ups thread into the original conversation on schedule, and stop the moment anyone at that business replies |
| Opting out | A mental list | A permanent suppression list that no future import can undo, fed by replies that say "unsubscribe" and by Gmail's native unsubscribe button |
| Pausing | Stop sending, and hope nothing is queued | One switch pauses everything instantly, and the dashboard shows exactly what is scheduled |
Inside the build
The worker is the only process that can send, and only one may run at a time.
Under the hood
- A step can only send once. Each send is claimed in the database under a unique key before Gmail is called. If the computer dies mid-send, recovery asks Gmail whether the message actually went out instead of guessing, because guessing is how someone gets emailed twice.
- One contact per business. Emailing three people at one property management company on the same morning reads as spam. HoMOE contacts one, and closes the whole business the moment anyone there replies or opts out.
- Offline is not failure. Losing Wi-Fi pauses the queue; it never marks anyone as bounced. A day the computer was asleep is simply a day with no sends, and nothing bursts out on startup to catch up.
- Out-of-office replies are recognized by their headers. They don't count as replies and don't stop the sequence, but a real reply always does.
- Portable, without sending twice. The whole system exports to one file. Moving to a new computer "retires" the old one, so two machines can never email the same person.
By the numbers
- 616 unit tests and 34 end-to-end tests passing in the project's last recorded verification (August 2026), plus a full rehearsal of the sending engine.
- Six latent bugs found by a deliberate defect hunt after the first build, each fixed with a regression test.
- A rehearsal mode writes every message to a local outbox, so the owner can run a campaign end to end and read exactly what would go out.
- A built-in setup checklist checks the domain's email-authentication records (SPF, DKIM and DMARC) live, so the owner can see what's configured without asking anyone.
- 37 commits.
Example scenario
Example scenario (illustrative): A two-van cleaning company wants twenty new commercial accounts this year. The owner imports a list of 300 local property managers on Monday morning. The preview drops 41 duplicates and 6 people who opted out last spring. They write one opening email and two follow-ups, previews ten of them, approves the campaign, and closes the laptop. Over the next three weeks HoMOE sends twelve emails a day. When a manager replies "we're locked in until June", that whole company drops out of the sequence automatically, and the owner answers the reply personally in Gmail.
What this means for your business
The pattern here is outreach automation that is built around restraint: a human approves the message, the machine handles timing, and compliance is the first rule rather than an afterthought. It fits:
- Local service businesses (cleaning, landscaping, trades) selling to commercial accounts
- B2B firms where every prospect is worth a personal email, not a blast
- Teams that need CAN-SPAM-conscious sending without a marketing platform subscription
- Anyone who has been burned by a bulk tool hurting their domain reputation
Second Voyage builds AI systems that are held to a standard you can check. Talk to us about yours.