A Real Week in the Life

Tuesday, six thirty in the morning

Start where the work actually starts, days before the send button: early on a random weekday, coffee, twenty browser tabs, and a slow read through everything that happened in the niche this week. Trade press. A regulatory update. Two earnings calls. A thread where practitioners are arguing about a new tool. This scanning session is the real job: it is where judgment gets fed. A paid newsletter is a digestion business before it is a writing business, and the publisher who skips the reading week ships opinions that readers can smell a mile off.

Notes go into a running capture file, one line each, tagged possible-issue or background. Not everything becomes an issue. Most becomes compost.

The two blocks that produce the issue

Wednesday holds the draft block: two or three hours, door shut, turning the strongest one or two ideas from the capture file into an ugly first draft. One idea per issue, not five. The draft is allowed to be bad; its only job is to exist. Experienced publishers separate drafting from editing as a matter of discipline, because polishing sentence one for forty minutes is how issues die unpublished.

Thursday is the edit block: cut the draft by a third, fix the opening three sentences, write five subject line options, set the paywall placement, decide what the free preview shows. This is craft work, deliberate and slower than it sounds from the outside. Then the issue schedules for Friday morning, and Friday is replies: reader email, corrections, the small conversations that later become the best issue ideas you will ever have.

Around the writing sits the invisible hour or two: the growth actions from later in this course, platform maintenance, updating the welcome email, and the admin that comes with any business, invoices, taxes, bookkeeping. Budget for it or it eats your weekend.

Launch weeks are not normal weeks

The week you open paid subscriptions, or run a founding-member push, is a different animal: extra emails, a launch issue, answering every single reply personally, watching the dashboard more than is healthy. Fine, and temporary. The trap is treating the adrenaline of launch week as the baseline and burning out by month three. The business runs on the boring Tuesday.

Realistic time budget for a weekly publication: eight to twelve hours a week once the machine is running, heavier in the first two months while templates and habits form. A monthly cadence proportionally less. If you are also working a job while you build, and many readers of this course are, that budget fits evenings-and-one-morning. Building alongside employment is its own discipline with its own guide, and the planning lesson later in this course builds the schedule around exactly that shape.

The texture nobody posts about

Here is the part that decides whether you last. The work is quiet. You send an issue you spent six hours on, and the immediate response from the universe is: almost nothing. A few opens ticking up. One kind reply. Then Saturday, and a stranger's five-dollar subscription, and one comment in a forum you have never visited. The feedback loop of this business is real but slow, and it rewards people who can find the signal in small numbers.

There is also a compounding feeling available here that most corporate work never offered: nothing in the issue is diluted by committee, and every week the asset, the list, the habit, the reputation, is measurably yours. Publishers who survive the first year describe the same thing: the shift from "did anyone notice me" to "I am building a body of work." That shift usually lands somewhere around issue twenty.

If the week you just read sounds like a fair trade, the next step is choosing who it is for, and that choice is the most consequential decision in the entire course.