# How Harmonya turned a monthly newsletter into a lifecycle program

*Published: 2026-08-24*

Cory Nelson is founding director of marketing at [Harmonya](https://www.harmonya.com). He's the whole function. Harmonya is a product-intelligence company for CPG brands and retailers, founded in 2021, based in New York and Tel Aviv.

He signed up for Brew one evening. The next morning Thomas and I were on a call with him. He'd already spent the night in the product. Harmonya emails were on the canvas, the agentic-commerce drafts and the product-intelligence ones. He booked the call because he wanted to go further, not because he needed a tour.

That's the part I can speak for. The operating detail below comes from [Noah Adelstein's piece for The GTM Engineer](https://thegtmengineer.substack.com/p/how-to-turn-email-marketing-into), published August 20, 2026. Brew sponsors that community. Noah says so in the essay. The numbers are his, attributed to Cory. We did not instrument this as a Brew case study.

## Key takeaways

- Cory spent about 5% of his time on email before and after. The change was precision, not hours, per [Noah Adelstein](https://thegtmengineer.substack.com/p/how-to-turn-email-marketing-into).
- HubSpot stayed the CRM. Brew sat on top for compose, segment, and send. Claude reached Brew over [MCP](/blog/brew-mcp).
- The first serious sequence used a white paper, a blog post, and a video, with wait logic and open-branching. A later fiber send split cereal, salty snacks, and canned goods.
- Cory read the first campaign against the assets he gave it. He told Noah it stayed self-contained. That read is the load-bearing step.

![Google Meet with Cory Nelson. The Brew canvas behind the call shows Harmonya emails on agentic commerce and product intelligence.](/blog/cory-nelson-call.png)

*The morning after signup. Cory on Meet, Harmonya drafts already on the canvas.*

## What was broken

Cory told Noah he was spending about **5% of his time** on email, and still not getting enough back. The old motion lived in HubSpot: open a template, select the whole list, send. A monthly newsletter, plus the odd product announcement. Same message, every name.

Noah's framing is that Harmonya sells into enterprise CPG brands, and he used PepsiCo and Colgate as the scale of those buyers. A blast that ignores category, role, and buying stage wastes a list like that. They had already tried to fix it inside HubSpot. More fields, more lists, more of Cory's week. The tool got heavier. The mail did not get more precise.

## What they changed

Cory kept HubSpot as the CRM. Brew sat on top of it for composition, segmentation, and send. He builds most of the email in the Brew UI, where he can see type and layout. He sends, stands up automations, and reads results in Claude through MCP.

The first serious sequence was not a newsletter. It used work Harmonya had already published: a **white paper on agentic commerce**, a blog post, and a video. Noah walked through the routing.

| Step | What it did |
| --- | --- |
| 1 | A short, zero-click email, a few stats, no download yet |
| 2 | A click through to the blog |
| 3 | The white paper, after they'd seen the argument |
| Logic | Wait between steps. Follow-ups only to people who opened the previous mail |

A later send on the **fiber** trend did not go to the whole list. Noah's example is the one I'd steal: cereal, salty snacks, and canned goods each got different copy about the same source.

![Diagram of Claude talking to Brew over MCP: compose, send, and read campaign results without leaving the chat.](/blog/brew-mcp-architecture.png)

*The loop Cory described to Noah. Claude on the outside, Brew in the middle, HubSpot underneath.*

## What Noah reported

Cory told Noah that **opens and clicks more than doubled** against the old all-list HubSpot baseline. Treat that as a directional comparison from one operator. The list, the offer, and the cadence all changed at once.

Two other details from that piece travel better than the multiple.

Cory read every line of the first campaign looking for invented numbers. He told Noah it was "self-contained within the assets that I gave it. It wasn't making up new stats and things like that." If you skip that pass, you will ship something that sounds finished and is not true.

He also said the setup only works because the CRM was already honest. Brew will not invent a buying-committee map you never stored. On our call we mapped accounts, roles, and who actually signs. That is the input. The agent is the throughput.

## What we heard that morning

Cory did not arrive as a prospect who needed a demo. He'd already used the product harder than the onboarding flow expected. He became a paying customer after that call. I wrote the morning down in [What we learned from hitting #1 on Product Hunt](/blog/what-we-learned-hitting-product-of-the-week), because it was the first time our ICP stopped being a slide.

The sentence he gave us was: *"You did to email what Claude did to design. It's the first email tool that fits how I already build with agents."* On LinkedIn, after Noah's piece ran, he wrote, *"Brew + Claude is a superpower!"*

We didn't spend that hour on onboarding slides. We spent it on the accounts he already sells, and on what a sequence looks like when the reader is a category manager rather than "the newsletter list."

## What I'd copy

Keep the CRM you already trust. Put an agent on top of it only if someone on the team will read the first send against the source material. Segment by the field that changes the sentence, not by a persona name from a workshop. And don't ask an agent for a lifecycle program if the list is still one field and a hope.

Read [Noah's essay](https://thegtmengineer.substack.com/p/how-to-turn-email-marketing-into). He sat with Cory longer than we did on any one call.

The brief shape we now tell other teams to use is in [how to brief an email agent](/blog/how-to-brief-an-email-agent). The inbox rules that still apply when Claude hits send are in [what still applies when an agent sends](/blog/agent-email-deliverability). To contact us about this article, write [Brew support](/support).

## How to use this page

**Harmonya** is a product-intelligence company for CPG brands and retailers.

**The GTM Engineer essay** is Noah Adelstein's write-up of Cory Nelson's email setup.

**A lifecycle program** is event-based mail, not a monthly blast to the whole list.

For example, a fiber trend can become three sends: cereal, salty snacks, and canned goods.

| Move | Why it matters |
| --- | --- |
| Keep the CRM honest | The agent cannot invent a buying-committee map |
| Read the first campaign | Cory's load-bearing step was checking invented stats |

US commercial mail still follows the [FTC CAN-SPAM guide](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) and [16 CFR 316.3](https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-316/section-316.3). Bulk sending still has to meet [Gmail's sender requirements](https://support.google.com/a/answer/81126). To contact us about this article, use the support link above.

## Frequently asked questions

### Who is Harmonya?

[Harmonya](https://www.harmonya.com) is a product-intelligence company for CPG brands and retailers, founded in 2021, with offices in New York and Tel Aviv. Cory Nelson is founding director of marketing.

### Did Brew pay for the Harmonya interview?

No. Brew sponsors The GTM Engineer community. [Noah Adelstein](https://thegtmengineer.substack.com/p/how-to-turn-email-marketing-into) says so in the essay. The operating numbers are Noah's, attributed to Cory. We did not run this as a Brew experiment.

### What changed in Harmonya's email program?

Cory kept HubSpot as the CRM and put Brew on top. The first sequence routed a zero-click note to a blog post to a white paper, with waits and open-branching. A later fiber send used snack sub-industry instead of the whole list.

### Did Harmonya become a paying customer before the call?

No. Thomas and I were on the call the morning after signup. He became a paying customer after that call. I wrote that morning down in [What we learned from hitting #1 on Product Hunt](/blog/what-we-learned-hitting-product-of-the-week).