Build it with AI
Create an email workflow around your audience, triggers, and conversion path.
Build the operating interface for segments, campaigns, sequence status, replies, and downstream actions.
Introduction
What an email marketing system has to hold.
Most teams end up with an email marketing system the same way: a sending tool that reports opens, and no view of what happened after the click. A monthly newsletter to one list is manageable anywhere. It stops working when segments multiply and a person can plausibly be in four of them, because nothing in the stack knows what else that person received this week.
The tool can say a campaign was delivered and opened, and nothing about whether it produced a conversation. There is no record of total contact frequency per person across campaigns, no link from a reply back to the campaign that produced it, and no suppression state that outlives a single tool.
What follows covers building an email marketing system: the records it holds (segments, campaigns, send state, replies, and the downstream action each reply should trigger), the systems it reads (Gmail and HubSpot), and what it does not fix.
The problem
Sends in one tool, replies in another, outcomes in neither.
Email platforms model the campaign and treat the recipient as a row in a list, which is why frequency capping across campaigns is either absent or an afterthought. CRMs model the person and cannot send at volume.
The records are segments, campaigns, send state, replies, and the downstream action each reply should trigger, and the authoritative copy of most of them already lives in Gmail or HubSpot. The suppression list in the sending tool, the opt-out flag in the CRM, and the person who replied asking to stop are three different states, and the third one is the one that matters legally.
The cost is not the inconvenience: send volume grows while the reply that mattered sits unread in a shared inbox.
You're likely here because
- Nobody can say how many emails one person received from the company last month
- The tool can say a campaign was delivered and opened, and nothing about whether it produced a conversation.
- When it is wrong, send volume grows while the reply that mattered sits unread in a shared inbox
What gets built
Launch builds it, Grow operates it.
Built in Launch
- • Campaign workspace
- • Segment views
- • Performance dashboard
Operated through Grow
- • Sequences
- • Reply handling
- • Pipeline actions
Systems it reads
- • Gmail
- • HubSpot
- • Resend
The record model
What the sending layer has to know.
- Per-person contact frequency
- Across every campaign, not within one. Frequency capping inside a campaign is the default and it is the wrong boundary, because the recipient experiences the total.
- Suppression state, single source
- One state read by every sending path. An opt-out honoured in the sending tool and not in the CRM is the compliance failure that arrives with a complaint attached.
- Consent basis and its source
- How this address became contactable. The answer is needed at the moment somebody asks and cannot be reconstructed from a list export.
- Segment as a rule, not a list
- Evaluated at send time against live CRM state, so a person who became a customer last week is not in this week’s prospecting send.
- Reply and its classified intent
- Because a reply saying stop is legally distinct from a reply asking a question, and a shared inbox treats them identically.
- Bounce and complaint history
- Per address, because deliverability is a reputation problem and sending to a repeatedly bouncing address damages every other send.
- Send record with campaign and version
- What was actually sent to whom. Reconstructing a send from a template is not the same as knowing what a given person received.
How it runs
From campaign sends to a connected conversation.
Step 01
Describe what an email marketing system has to do
Define the segments as rules over business state rather than as static lists, and decide the frequency cap per person before writing a single campaign.
Step 02
Connect the systems of record
The CRM supplies lifecycle state and ownership, the mailbox supplies replies and bounces, and the sending platform supplies delivery. Reading all three is how a reply becomes an event rather than an unread message.
Step 03
Build the operating surface
A campaign workspace with rule-based segments, per-person frequency visibility, reply handling routed to an owner, and suppression held once rather than per tool.
Step 04
Start narrow
Per-person contact frequency across every campaign, visible on the contact record. Ship nothing else in version one; most teams change their sending behaviour on seeing it.
Step 05
Route the exceptions
A reply that indicates intent — a question, an objection, a request to stop — routes to a named owner with the campaign context attached rather than sitting in a monitored-by-nobody inbox.
Step 06
Measure replies that became a booked conversation, per campaign
Track replies and downstream pipeline per thousand sends rather than open rate. Open rate has been unreliable since mail privacy protection and continues to be quoted as though it were not.
Implementation path
Building email operations that survive a list audit.
- 01
Audit the current suppression state across every tool before sending anything new. The gap between the sending tool and the CRM is where the compliance risk lives.
- 02
Baseline replies and pipeline per thousand sends, and per-person contact frequency for last month. The frequency number is usually higher than the team believes.
- 03
Define segments as rules over CRM state rather than as exported lists, so a person who becomes a customer leaves the prospect segment automatically rather than on the next export.
- 04
Run one campaign through the new path end to end, including a real reply, before migrating the rest. Reply routing is the part that is always assumed to work and frequently does not.
- 05
Build the narrowest useful version first: a reply queue that routes responses to an owner with the campaign context attached.
- 06
Auditing suppression state across every tool is the first day and is where the compliance risk shows up. Making per-person frequency visible on the contact record is a week and changes sending behaviour immediately. Running one campaign end to end including a real reply, before migrating the rest, is the step that catches reply routing — which is always assumed to work.
- 07
After frequency visibility and single-source suppression, add reply intent routing so a question reaches an owner rather than a monitored-by-nobody inbox. Send-time optimisation is far down the list and worth much less than either.
Controls
Controls that matter.
Control 01
One suppression state read by every sending path, so an opt-out recorded anywhere is honoured everywhere
Control 02
A per-person frequency cap enforced across campaigns rather than within them
Control 03
Consent basis and its source recorded per contact, since the answer to how someone joined the list is needed at the moment someone asks and not a week later
Examples
Three things that stop falling between tools.
The customer who got the prospect sequence
Segments defined as rules over live CRM state rather than as an exported list means a person who signed last week is not in this week’s prospecting send, without anyone having to remember to remove them.
The reply that said stop
Routing replies through a handler that reads intent, with a human confirming, means a request to stop becomes a suppression event rather than an unread message in a shared inbox.
The week four campaigns overlapped
Frequency visible per person across all campaigns makes the overlap a decision somebody makes rather than an outcome nobody sees until the unsubscribe rate spikes.
How it goes wrong
Three ways email operations break.
Optimisation is driven by open rate, and the numbers have been decoupled from actual opens since mail privacy protection.
Measure replies and downstream pipeline per thousand sends, with unsubscribes per thousand as the cost side. Both are observable and neither is inflated by a privacy proxy that pre-fetches images.
Segments are exported lists, and a customer who signed last week receives the prospect sequence.
Define segments as rules over live CRM state. An exported list is correct on the day it is made and wrong in exactly the way that reaches the people you most want not to annoy.
The list is migrated to better tooling and deliverability gets worse.
Reputation follows the sending domain and the list hygiene, not the tool. Warm the sending path, clean the list, and expect a better system sending to a stale list to produce better-organised complaints.
Limitations and considerations
What better email tooling will not fix.
- Open rate has been inflated and decoupled from actual opens since mail privacy protection shipped. Any optimisation built on it is optimising a proxy that no longer tracks the thing.
- Deliverability depends on sending reputation, authentication, and list hygiene far more than on tooling. A better system sending to a stale list produces better-organised spam complaints.
- Consent rules differ by jurisdiction and by how the address was obtained, and the differences are material. Recording the basis is engineering; deciding what it permits is not.
- With one list and a monthly newsletter, the platform alone is right. If deliverability rather than coordination is the complaint, this build addresses the wrong constraint — start with authentication, list hygiene, and sending reputation.
- Connector coverage varies: Gmail, HubSpot, Resend are representative rather than guaranteed, and the fields exposed depend on your workspace permissions.
FAQ
Build an email marketing system with AI: common questions.
Does this replace our email platform?
Usually not. The platform keeps sending; what moves is segment definition, frequency capping across campaigns, reply routing, and one suppression state. Those are exactly the four things platforms handle within a campaign and not across them.
Should AI write the campaigns?
It can draft against segment context and prior performance, with a human approving before send. What it should not do is send unreviewed to a segment defined by a rule that has not been checked against live data, which is how a list of customers receives a prospecting email.
What should we measure instead of open rate?
Replies and downstream pipeline per thousand sends, plus unsubscribes per thousand as the cost side. Both are observable, neither is inflated by privacy proxies, and together they capture the actual trade you are making.
How do we handle replies at volume?
Classify intent and route to a named owner rather than triaging one shared inbox. The failure mode at volume is not slow replies — it is the reply that says stop being processed as a general enquiry.
What should the first version contain?
A reply queue that routes responses to an owner with the campaign context attached. Everything else waits until that one is genuinely used.
How will we know whether it worked?
Measure replies that became a booked conversation, per campaign against the baseline taken before anything changed.
Start with ARIA
Ask ARIA to build it.
Describe the website, application, workflow, or operating surface you need. ARIA plans, connects, builds, tests, and keeps refining it — inside the permissions you set.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Build an email marketing system around the process you actually run.
Start by making per-person contact frequency visible, hold one suppression state, and measure replies rather than opens.