YMLP Tech All articles
Creator Economics

What a Weekly Email Really Costs: Four Creators Log Every Minute for a Month

YMLP Tech
What a Weekly Email Really Costs: Four Creators Log Every Minute for a Month

Photo by Photo by laura adai on Unsplash on Unsplash

Ask a newsletter creator how long their weekly issue takes, and you will usually get a confident answer: "About three hours, tops." Ask them to actually log the time — every draft, every edit, every link check, every promotional tweet — and that estimate tends to triple.

To find out where the hours genuinely go, we followed four US-based creators through a full month of production. Each kept a running time log across drafting, editing, design, list management, and promotion. Their publications ranged from a 900-subscriber side project to a 28,000-reader operation run by a two-person team. What emerged is a picture of newsletter labor that looks very little like the one most newcomers carry into their first send.

The Assumption Versus the Ledger

New senders typically budget for writing. They imagine the process as: think of an idea, write it, hit send. The time logs told a different story.

Across all four creators, writing the core draft accounted for an average of just 38% of total production time. The rest went to everything surrounding the words: sourcing and verifying links, formatting for both desktop and mobile, writing subject line variants, scheduling, managing the list, and — the single most underestimated category — promotion.

One creator, a product designer in Austin who publishes a weekly curation letter to about 3,500 subscribers, spent 6.2 hours per issue on average. Of that, only 2.1 hours involved drafting the actual commentary. Another 2.8 hours went to reading source material and collecting links — work that happens before a single sentence is written and that almost never appears in anyone's mental estimate.

Where the Hours Pile Up

Three categories dominated the unaccounted-for time:

Research and input consumption. Curation and analysis newsletters demand a reading pipeline. The Austin creator's 2.8 hours of source reading was not unusual; a finance-focused writer in Chicago logged 3.5 hours weekly just staying current enough to have something worth saying.

Promotion and distribution. Cross-posting to LinkedIn, replying to comments, pitching guest spots on podcasts, and managing referral incentives consumed between 45 minutes and 2 hours per week for every creator tracked. This was the category nobody had budgeted for when they started.

The mechanical tail. Fixing a broken link after send, adjusting a template that renders oddly in Outlook, pruning bounced addresses, answering subscriber replies — individually trivial, collectively a reliable 40-to-70-minute weekly tax.

The Frequency Multiplier

Perhaps the clearest finding: cadence matters more than length. The creator publishing every other week spent 5 hours per issue. The creator publishing weekly spent 6.2. But the weekly publisher produced 2.2 issues for every one of the biweekly publisher's — meaning her monthly commitment was roughly 25 hours versus 10.

Frequency compounds. A weekly commitment is not twice a biweekly one; it is a different lifestyle, because the recovery time between issues shrinks to nearly nothing. Several creators noted that the weekly schedule left no room for the “missed week” that a biweekly publisher can absorb without consequence.

Templates for the Employed Publisher

Most side-project newsletter operators in the US are fitting publication around a full-time job. The logs suggest three workable models:

The batch weekend model. Draft on Saturday morning, edit and format Sunday evening, schedule for Tuesday morning. Total weekly commitment: 4 to 5 hours in two blocks. This suits commentary-driven letters where the material lives in the writer's head.

The daily-capture model. Fifteen minutes each weekday spent collecting links and jotting notes, then a single 3-hour Sunday session to assemble. This works well for curation formats and reduces the Sunday burden substantially, since the raw material is already gathered.

The seasonal sprint. Publish in 6-to-8 week runs with planned breaks between. Creators using this model reported the highest consistency — paradoxically, because the breaks were scheduled rather than failed.

The model that failed for every creator who tried it: writing the issue the night before sending. Every instance of night-before drafting in the logs correlated with longer total production time, more errors, and — per the creators' own reports — issues they were less proud of.

Pricing Your Own Hours

There is a practical reason to know these numbers. If a weekly letter costs you 6 hours and your professional rate is $75 per hour, you are investing $450 of labor per issue — $23,400 annually — before earning a dollar. That figure does not argue against starting a newsletter. It argues for starting one with clear eyes about the exchange rate between your evenings and your audience.

The creators we followed were unanimous on one point: the hours never got smaller as they grew more experienced. The work simply shifted. Drafting got faster; promotion, list hygiene, and community management got bigger. Anyone budgeting time for a newsletter side project should budget for the whole machine, not just the writing.

The inbox rewards consistency, and consistency is fundamentally a scheduling decision. The senders who last are not the ones who write fastest. They are the ones who know exactly what their Tuesday evening costs — and decided, in advance, that it was worth it.

All Articles

Related Articles

When the Inbox Becomes the Product: How Solo Publishers Are Selling the Conversation

When the Inbox Becomes the Product: How Solo Publishers Are Selling the Conversation

Rehearse Before the Curtain Rises: Building a Seed List That Catches Problems Before Subscribers Do

Rehearse Before the Curtain Rises: Building a Seed List That Catches Problems Before Subscribers Do

Nobody Scrolls Past Issue #12: Rethinking What a Newsletter Archive Is Actually For

Nobody Scrolls Past Issue #12: Rethinking What a Newsletter Archive Is Actually For