Cold email is still run by hand: build a list, guess the addresses, hope they are right, then spend hours on it. Julian Goldie's opening line is exactly that observation, most people still stitch together five separate tools to find the right people. His answer is a machine managed from one screen, where you write a single sentence , and it finds, verifies and writes to the people you described.
The demo run is short and convincing. He types one line into the interface, SEO agencies interested in link building, and presses find and enrich. The output is real domain names, real email addresses, company size and short descriptions, all sorted into three groups : new, enriched and valid. So the demonstration is not an engine filling a table; it is the machine finding and filtering addresses on your behalf.
The machine runs inside a panel the host calls Agent OS, and beneath it sits Hermes Agent, an open-source project from Nous Research: distributed under the MIT license, not tied to a single model, and able to keep memory across sessions. The hermes-agent.nousresearch.com documentation says that memory lives in two plain text files under a strict character budget, and the skills page on the same site describes skills as separate files that follow progressive disclosure. The repository at github.com/NousResearch/hermes-agent confirms the licence and the model independence. The brain claim is therefore not marketing, it is an architecture you can inspect.
One sentence, or a list you already have
There are two doors in. If you already have a list you paste it and enrichment continues from there. If you start from zero you skip filters, spreadsheets and guessing the email format, and simply describe who you are looking for in plain English. Agencies, e-commerce stores, local services or coaches, the logic is the same and only the words change.
Finding and verification run through Hunter. According to Hunter's own help pages the tool can derive an address from a domain or find one from a name plus domain, assigns a confidence score to each address, and runs a free verification check before returning results. The verifier checks the format, filters disposable and webmail addresses, and contacts the mail server without sending anything to confirm a mailbox really exists. The catch is stated on the same pages: on accept-all domains verification cannot become conclusive, so high-confidence addresses are recommended and invented name variants are filtered out.
From filter to reply: score, write, status
After verification comes a second layer: every candidate receives a fit score out of a hundred and anything below the threshold is dropped rather than kept. Then a personal opening line and a short message are written for each name and company. The panel shows new, enriched, valid, contacted and replied as separate states, so where a campaign stands is readable at a glance. Generated text is still held behind human approval before it goes out.
What the five tabs actually cost
The old method the host compares against is familiar: one tab to find contacts, another to verify, another to write, another to send. Hours disappear and most of the time you reach people who were never a fit. Goldie says he did this work himself in the early years of his agency. seogoldieagency.com dates the company to 2018 and describes a seventy-person team running link building for B2B SaaS and ecommerce clients; juliangoldie.com spells out the workflow, prospecting link-worthy sites and then reaching out by cold email. So the comparison is not exaggeration, it is an observation from someone doing the same job.
His reason for preferring the panel over a plain terminal is a separate argument. Typing commands leaves no durable trace of the workflow, so returning later you cannot see what was done. You could write a skill file, but it becomes messy and hard to read afterwards. In the panel you can see who was contacted and when, how many messages went out, what each setting does; a campaign can be paused and irrelevant records removed. The real difference is not a prettier interface but that the system is reversible.
Shared memory and model choice
The real promise of Agent OS is not the panel but shared memory . In the host's words it is an observable vault of plain text files. When the machine learns who works for you, or when you change the writing style, that knowledge does not disappear; the content agent and research agent read the same files. The model side is equally open: complicated work goes to a strong model, repetitive work goes to a free or local one, and you switch between them with a single command. Hermes' model independence is not a competitive advantage here, it is cost control.
Who it works for
The six steps are collected here: describe, find, verify, score, write personally, send from your own mailbox. Setup is not claimed to be more complex than it is: open the app, add your API key in settings, connect an email address. The host stresses that he is not technical, yet he built it, and he answers the most common fear directly: an approval step exists and nothing is sent without you. The second warning is technical, he recommends a separate email address for sending, apart from personal mail.
The closing section is a sales call that does not weaken the thesis, it only sets the scale. The machine has just been built, the host openly describes it as experimental and says using it is genuinely enjoyable. The package, however, is not only the machine: a thirty-day roadmap, copy-and-paste prompts, four coaching calls a week and a community of more than four thousand members working on the same thing. The value here is the support layer as much as the tool.
| Layer | What it solves |
|---|---|
| Input | One sentence or an existing list, no filters |
| Verification | Confidence score and deliverability check cut bounces |
| Filter | Fit score out of 100 drops what falls below |
Key moments
- The problem: five separate tools stitched together
- Targeting described in a single line
- Running the find and enrich job
- Address discovery running through Hunter
- Confidence score and pre-send verification
- Fit score out of one hundred
- The tab and hour cost of the old way
- Not one boxed model but a panel of them
- Human approval before anything is sent
- Admitting the system is still experimental
AI commentary
"The useful part of the video is not the product pitch but three architectural choices: durable memory lives in a file, model choice stays with the user, and sending sits behind human approval. Get those three right and cold email stops being a pile of tabs and becomes a repeatable process."
AI assessment
The strongest claim in the video is that the real cost of automation is context, not tokens. Panel, memory and model choice only work as a set, and taken together they do solve the five-tool problem. Against that, there is no conversion claim anywhere: the video says addresses are found, never how many replies came back. So the success metric on show is elapsed time, not a reply rate.
The technical criticism belongs to the verification layer. The video is right that verification lowers bounce, but on accept-all domains and disposable email services verification cannot be conclusive, a limit written on the tool's own help pages. The same applies to volume: sending hundreds of messages a day from a newly created mailbox, without a separate sending domain and warm-up, lands in spam within days. Apollo's knowledge base suggests roughly fifty emails per mailbox per day plus SPF, DKIM and DMARC, and its deliverability guidance is worth reading before any automated sequence is switched on.
The legal side matters more. In the United States the FTC guide lists what must be done: no deceptive headers or sender information, label the message as advertising, include a valid physical address, and honour opt-out requests within ten business days. In Europe the work rests on the legitimate interest test the ICO describes, built from purpose, necessity and balance, and written down before processing starts. Which company you write to is therefore the weakest point of the whole system.
My practical take: systems like this accelerate research and sourcing, they do not decide. I would start with one niche and one sending domain, keep approval in the loop, measure non-replies weekly, and write the legitimate interest assessment once and store it. For people who want to run their own agency on their own tooling this is useful; for anyone looking for cover to blast in bulk, the verification step stops nothing.
Sources
12 links; 1 of them also cited by 1 other story. Stories sharing a link do not confirm each other; a source's origin is not inferred from how often it is cited.
- @youtube Julian Goldie SEO — I Built a Lead Generation Machine With Hermes
- @hunter.io Hunter — Email Verification FAQs
- @hunter.io Hunter — Email Verifier kontrolleri
- @ftc.gov FTC — CAN-SPAM Act uyum rehberi
- @ico.org.uk ICO — Meşru menfaat değerlendirmesi
- @knowledge.apollo.io Apollo — E-posta ulaşılabilirlik önerileri
- @hermes-agent.nousresearch.com Hermes Agent — Kalıcı hafıza dokümantasyonu
- @hermes-agent.nousresearch.com Hermes Agent — Beceri sistemi
Also cited by: Building with Hermes Agent: Persistent Memory, Skills, and Multi-Channel Automation
- @github.com NousResearch — hermes-agent deposu
- @seogoldieagency.com Goldie Agency — Julian Goldie hakkında
- @juliangoldie.com Julian Goldie — Link building uzmanlığı
- @ico.org.uk ICO — B2B pazarlama kuralları
hermes · agent · cold email · automation · open source · memory