SYNTHESIS GUIDE

Email That Builds a Business: Frequency, Relevance, Automation and Deliverability

Email advice often collapses into a fight about cadence.

Send every day. Send once a week. Automate everything. Write fresh broadcasts. Clean the list. Grow the list. Sell more. Sell less.

The Genius Talk archive suggests a better way to frame the problem. Frequency matters, but frequency sits inside a larger operating system. The sender has to earn attention, set expectations, keep the list healthy, decide what deserves automation, stay close enough to the market to write timely messages, and maintain the technical conditions that let those messages reach the inbox.

That wider view explains why experienced practitioners can disagree sharply about how often to send and still agree on much of what makes email valuable.

Ben Settle argues for unusually frequent communication and prefers fresh email because the market changes. Ken McCarthy also stresses timeliness, but puts a strong test in front of every message: is this email worth interrupting the subscriber for? Cole VanDeWoestyne treats the list as a relationship that needs deposits before withdrawals, then adjusts the conversation according to engagement. Lars Helgeson brings in the technical side, where authentication, sender reputation and list quality can undermine strong copy before the reader sees it. Anton Volney widens the lens again by treating the email list as an owned business asset that reduces dependence on clients and platforms.

Taken together, those positions lead to an email strategy built around five questions:

  1. Why did this person join?
  2. What kind of relationship have you trained them to expect?
  3. Does this message deserve their attention now?
  4. Should this communication be automated or written fresh?
  5. Can your sending infrastructure support the volume and behavior you are asking of it?

Those questions are more useful than searching for one universal sending schedule.

Email remains strategic because the relationship can continue

An email list is valuable for a simple reason: it gives a business a repeatable way to reach people who have chosen to hear from it.

That choice creates a different relationship from a passing social impression or a search visit. A subscriber may still ignore the next email, unsubscribe, filter the sender or change addresses. Email is not guaranteed access. Yet the business has a direct channel it can keep developing instead of starting every interaction from zero.

Ken McCarthy's view of an email-led information business begins with the market itself. He looks for areas where people keep needing new information, help or decisions over time. In that kind of market, one useful answer can lead naturally to another question. The commercial opportunity comes from a continuing relationship rather than a single transaction.

Anton Volney reaches a similar destination from the perspective of a freelance copywriter. His argument is that client work can be a strong way to build skill and income, while an owned audience creates another kind of leverage. A list gives the operator a relationship that is less dependent on whether one client renews a contract or whether one platform continues to distribute the work.

This is why list growth should not be separated from list quality. A large collection of addresses with weak permission, unclear expectations or little interest is a poor substitute for a smaller group of people who know why they subscribed and still want the conversation.

Permission includes the expectation you set

Consent is the starting point. Expectation is what makes that consent workable over time.

Settle is associated with frequent email, but the nuance matters. His position is not that every business should suddenly increase to a daily cadence regardless of what subscribers were promised. He argues that frequency should fit the expectations established when people joined.

That distinction matters because subscribers experience cadence as part of the offer.

A weekly briefing that suddenly turns into several promotional emails a day creates a mismatch even when every message contains an unsubscribe link. A daily newsletter that sends daily is doing what the reader signed up for. The raw number of sends tells only part of the story.

A strong welcome process therefore has two jobs. It should deliver whatever caused the signup, and it should explain what comes next. That can include the themes the sender covers, the likely cadence, the kind of offers subscribers may receive, and how to change preferences or leave.

Clear expectations give the business more room to communicate. They also give the subscriber more control.

This turns frequency from a private marketing decision into part of the value exchange.

There is no universal answer to "How often should I email?"

The interviews contain a real disagreement here, and smoothing it away would remove the most useful part.

Settle favors frequent fresh broadcasts. His reasoning is rooted in relevance. Evergreen material can keep working, but it cannot react to what customers are thinking about today, what just changed in the market, what the sender learned this morning or what has become newly urgent.

McCarthy shares the emphasis on timeliness but places more weight on interruption value. Email feels cheap to send, which can make it easy for marketers to treat attention as free. His test forces a higher standard. The sender should have a reason to disturb the reader.

VanDeWoestyne adds relationship depth and segmentation. His "deposits before withdrawals" metaphor reframes frequent selling as something that has to be earned. Useful material, questions, relevant stories and evidence can build enough value that a direct offer feels like part of the relationship rather than an extraction from it.

These positions can support different cadences because they are optimizing for different things.

A sender with a strong daily-news habit, a clear promise and an audience that expects commentary may have room to write every day. A specialist who only has something substantial to say twice a month may damage the relationship by forcing volume. A retailer with a known promotional calendar has a different job again.

The better operating question is: what cadence can this business sustain while keeping the messages relevant, expected and commercially useful?

Then watch behavior.

Look at replies, clicks, purchases, unsubscribes, complaints, re-engagement and the performance of different segments. Avoid treating a single metric as a complete picture. The point is to learn how the relationship changes as cadence changes.

Earn the right to send more to the people who want more

Segmentation is where the frequency debate becomes practical.

VanDeWoestyne describes separating more engaged subscribers from people who have gone colder. The warmer group can receive a deeper or more frequent conversation because their recent behavior shows interest. The colder group may need a different message, a re-engagement sequence or a lower cadence.

This is a better use of data than treating the entire database as one audience.

The relevant signals depend on the business. They may include recent clicks, replies, purchases, event attendance, content interests, recency of signup, product category or another behavior the subscriber has knowingly created. A useful segment should change what the business says or how it says it. Otherwise it is just a label in the CRM.

Segmentation also protects relevance.

A buyer who just purchased does not need the same sequence as a prospect who has never bought. A reader who regularly clicks content on one topic has given the sender information that can make the next email more useful. A long-inactive subscriber should not automatically receive the same escalation in promotional pressure as the most engaged customer.

This does not require a maze of tiny segments. The goal is enough distinction to make the communication more appropriate.

A simple starting model can be:

  • new subscribers who need orientation;
  • engaged non-buyers who need useful follow-up and the right offer;
  • customers who need delivery, education, retention and relevant next steps;
  • inactive subscribers who need re-engagement or removal.

The exact labels matter less than the decisions they improve.

Automation is strongest when the context is stable

Automation solves a real problem. Businesses repeatedly need to welcome subscribers, deliver resources, confirm purchases, remind customers, teach onboarding steps, recover abandoned actions and route people based on behavior.

Those jobs are predictable enough to systematize.

Settle's criticism is aimed at a different mistake: assuming that because something can be automated, it should replace fresh communication.

An evergreen sequence can be excellent at explaining a stable idea. It is weaker at responding to a market event that did not exist when the sequence was written. It cannot naturally react to a customer question that appeared this week unless someone updates it. It may keep saying the same thing long after the context that made it persuasive has changed.

The practical answer is a layered system.

Use automation where the trigger and required response are stable. Use fresh broadcasts where timing, interpretation and current relevance create the value.

That gives automation a clear job instead of asking it to become the whole relationship.

A welcome sequence can explain the core worldview and set expectations. A post-purchase sequence can help a customer use what they bought. A re-engagement sequence can ask whether the reader still wants the emails. Fresh broadcasts can respond to current concerns, new evidence, seasonal moments, recent customer questions and new offers.

The distinction also improves maintenance. Evergreen sequences deserve scheduled review because "evergreen" does not mean permanent. Prices change. products change. links break. claims age. reader expectations shift.

Automation should remove repetitive work without freezing the business in an old version of the market.

Relevance comes before cleverness

McCarthy's interruption test is useful because it forces the sender to think from the inbox outward.

The recipient does not experience an email as a line in a campaign calendar. They experience one subject line among many messages competing with work, family, notifications and other demands.

The email has to justify the click, then justify the reading time.

That does not require every message to be profound. A short note can be useful. A direct promotion can be welcome when the offer fits. A reminder can be exactly what the reader needs. The standard is relevance to the subscriber's situation.

VanDeWoestyne's relationship model adds a second check: what has the sender contributed before asking for attention or money again?

This is where many lists become brittle. They receive a long silence, then a concentrated burst of sales messages, then another silence. The subscriber learns that the sender appears mainly when a launch needs traffic.

A healthier list has continuity. The sender keeps listening and contributing between promotions. That can mean teaching one useful distinction, answering a common question, showing a relevant example, surfacing a mistake, sharing a decision process or asking for a reply.

A useful email does not always need to sell immediately. It should help the relationship stay worth having.

Deliverability starts before the send button

Copy cannot perform in an inbox it never reaches.

Helgeson's interview makes this visible by connecting deliverability to sender reputation, list source and shared infrastructure. He argues against purchased or rented lists and describes vetting senders because abusive behavior can damage reputation, particularly where infrastructure is shared.

He also discusses SPF, DKIM and DMARC, which have become even more important as mailbox providers tightened requirements for higher-volume senders.

As of September 2026, Gmail requires SPF or DKIM for all senders to personal Gmail accounts and requires SPF, DKIM and DMARC for bulk senders. Google defines bulk senders around a threshold of roughly 5,000 messages to personal Gmail accounts in a day and also requires practices such as easy unsubscribe for relevant bulk traffic. Yahoo similarly requires stronger authentication, DMARC and easy unsubscribe for bulk senders. Microsoft applies SPF, DKIM and DMARC requirements to domains sending 5,000 or more messages a day to its consumer email services.

The thresholds and enforcement details belong in technical documentation, not in a permanent marketing philosophy. They can change. The durable lesson is simpler: authentication, list hygiene, permission and complaint behavior are operating requirements.

A business that treats deliverability as a late technical cleanup is taking a preventable risk.

The marketing team should know who owns DNS records, which platforms send on behalf of the domain, whether SPF and DKIM are configured correctly, whether DMARC reporting is monitored, how unsubscribes are handled, how bounces are suppressed, and how new list sources are approved.

Those are marketing questions because they affect whether the marketing reaches anyone.

Preference management is part of the relationship

A subscriber does not have to be either fully subscribed or fully gone.

For some businesses, preference management can preserve a useful relationship when interests change. A customer may want product education but not event promotion. A reader may want a weekly digest rather than every broadcast. A buyer may want messages about one category but have no interest in another.

That does not mean every small list needs a complex preference center. It means the sender should recognize that attention is not one binary state.

This fits VanDeWoestyne's segmentation principle. The more a business learns about what a subscriber actually wants, the less it needs to rely on one cadence for everyone.

It also supports McCarthy's interruption standard. Giving people a sensible way to reduce irrelevant messages can protect future attention better than forcing them to choose between receiving everything and leaving entirely.

Operationally, preference management requires discipline. The CRM and sending platform need to preserve the subscriber's choices. A campaign should not re-add someone to a category they already declined. Unsubscribe and suppression rules should be treated as part of the data model rather than cleanup performed after a send.

The larger principle is respect for the relationship the person chose.

Promotions need a rhythm around the value rhythm

A list can be useful and still fail commercially if the business never makes an offer.

VanDeWoestyne's promotion sequence moves from useful priming into offer awareness, emotional relevance, proof and a real deadline. McCarthy also emphasizes offers and the commercial side of direct response. Their approaches make it possible to separate constant promotion from the legitimate need to sell.

A promotion window should feel like an event in an ongoing relationship.

Before the offer, the sender can surface the problem, teach a useful distinction, share a relevant story or answer an objection. During the promotion, the message can become more direct because the subscriber understands what is being offered and why it matters. After the window closes, the relationship continues.

This matters for frequency because promotions often require a temporary increase in sends.

A subscriber who normally receives one or two useful messages a week may reasonably receive more during a deadline-driven launch if that pattern fits the expectations the sender has established. The same increase can feel intrusive when the list has heard nothing useful for months.

The question is not whether promotional email is allowed to be frequent. It is whether the increase makes sense inside the relationship.

A calendar can help teams see this before they over-send. Mark the main promotional periods, the educational or nurture periods, customer communications and major seasonal moments. Then ask whether the list receives enough useful continuity between revenue events.

The calendar should protect relevance rather than force content into empty dates.

Deliverability data should inform editorial decisions

Deliverability is often owned by operations while content is owned by marketing. The separation can hide useful signals.

Complaint rates, bounce patterns, unsubscribe spikes and sharp engagement changes can indicate more than a technical problem. They can reveal a mismatch between acquisition source, expectation, cadence and message.

A sudden increase in complaints after a new lead source may mean the consent experience was unclear.

A wave of unsubscribes after a cadence increase may mean the list was not prepared for the new rhythm.

A cold segment that never re-engages may be telling the business that continued sending has little value.

These signals should not be interpreted in isolation. Mailbox-provider reporting is imperfect and privacy features can make some engagement metrics less reliable than they once were. The useful approach is to combine technical signals with customer behavior and commercial results.

The list is both a communications channel and a feedback system.

List growth should preserve the reason the list is valuable

Volney describes experimenting with multiple ways to grow his own audience, including author-promotion communities, website opt-ins, giveaways and newsletter platforms. VanDeWoestyne discusses co-sponsored events with explicit opt-in disclosure.

The common principle is that growth should preserve a clear subscriber relationship.

A list grows in value when new people know what they asked for, the sender can continue serving that interest, and the acquisition source produces people who fit the business.

This argues against chasing subscribers as a vanity number.

A lead magnet that attracts people who will never care about the core offer can make the list bigger while making the business harder to read. A partner promotion can work well when the audience fit is strong and the signup is transparent. A relevant resource attached to a useful article may grow more slowly than a broad giveaway but create a better next conversation.

The acquisition source should be judged by what happens after the opt-in.

Do those subscribers engage with the themes the business needs to own? Do they become customers? Do they reply? Do they remain subscribed? Do they create useful market feedback? Do they continue into other owned assets?

Growth and nurture are one system.

Ownership creates strategic options

Volney's shift toward publishing highlights a broader advantage of email: an audience can become an asset around which several business models are possible.

A service provider can use a list to create demand between client projects. An author can launch a book to readers who already know the work. A consultant can turn recurring questions into products, events or research. A retailer can retain customers instead of paying to reacquire every relationship from scratch.

Ownership here should be understood practically rather than absolutely. Email still depends on infrastructure, law, mailbox providers and the subscriber's continuing permission. The business does not own a person or a guaranteed slot in their inbox.

What it controls is more of the relationship architecture: the domain, the signup path, the content, the offer, the customer data it is entitled to use, and the process for communicating again.

That control becomes more valuable when paired with useful content and a reason for the subscriber to stay.

A practical operating model for email

The interviews point toward an email system that can be run as a set of recurring decisions.

1. Define the relationship

Write down why people subscribe, what they are promised, what themes they will receive, the likely cadence and what commercial messages belong in the relationship.

If the team cannot explain this in a few sentences, the subscriber is unlikely to understand it either.

2. Build the minimum automations

Create the stable sequences that remove avoidable manual work: welcome, delivery, onboarding, customer education, re-engagement and other repeatable triggers that matter to the business.

Then assign an owner to review them.

3. Keep a fresh broadcast rhythm

Choose a cadence the business can sustain with relevant material. Do not manufacture daily email because a guru prefers it. Do not hide behind a monthly newsletter because writing more often feels uncomfortable.

Use subscriber expectation and market response to decide.

4. Segment where the decision changes

Separate groups when they need materially different communication. New subscribers, engaged prospects, customers and inactive contacts are a useful starting point.

Add complexity only when it creates a better message, offer or timing decision.

5. Protect deliverability

Maintain authentication, monitor sending reputation, suppress invalid addresses, honor unsubscribes and avoid list sources that create unclear permission.

Treat mailbox-provider rules as current operational documentation that should be reviewed, not as facts that can be set once and forgotten.

6. Listen to the list

Use replies, customer conversations, sales questions and behavior to learn what the audience is thinking now. Feed that information back into broadcasts, offers and automations.

The list should make the marketing smarter over time.

7. Measure commercial response without reducing the relationship to one metric

Track what matters to the business: qualified replies, purchases, booked calls, repeat orders, subscriber retention, complaints, unsubscribes and other meaningful actions.

A high click rate on irrelevant content can still be poor marketing. A direct email that produces few clicks but several high-value conversations may be doing exactly the right job.

The frequency question becomes easier once the system is healthy

The most useful conclusion from these interviews is not a send number.

Settle shows why freshness and frequent contact can create commercial advantage. McCarthy shows why every interruption needs to earn its place. VanDeWoestyne shows how value, engagement and segmentation change the conversation. Helgeson shows that technical discipline can determine whether the message gets a chance to work. Volney shows why the list itself can become a strategic asset.

Once those pieces are in place, cadence stops being a superstition.

It becomes a decision you can make from subscriber expectation, relevance, capacity, behavior and business economics.

That is a much stronger foundation for email than a calendar copied from someone else's list.