Vol 1 · Issue 100 · Sunday, August 30, 2026

This is the hundredth one of these.

I'm not going to pretend that's a monument. Plenty of people have written more, and better. But a hundred is enough repetitions that the lessons stop being theories and start being things I'd bet money on, so it seems like a reasonable place to stop and tell you what I actually learned. Not about newsletters. About running anything.

Because here's the uncomfortable thing about doing something a hundred times in a row. The results have almost nothing to do with how good any individual attempt was.

I'll start with the part that stung.

There are maybe six issues in this run that I genuinely sweated over. Rewrote them three times. Sat with the opening for an hour. Sent them thinking, that's the one.

Most of them landed like a wet towel. Perfectly fine numbers. Nothing special.

Meanwhile, the pieces that consistently blew up were the ones I wrote fast because I was annoyed about something. A client had said something dumb, or I'd watched a good operator make an avoidable mistake for the fourth time that month, and I sat down and typed for forty minutes and hit send with a shrug.

Those are the ones people forward. Those are the ones that get replies six months later.

I've stopped trying to explain it and started planning around it, which is a different thing. I can't tell in advance which one is going to work. Neither can you. Anybody who says they can is selling a course.

So the only move that makes sense is more attempts. Not better attempts. More of them, at a quality floor you can actually sustain.

This is true of everything. You don't know which sales call converts. You don't know which piece of content brings the client. You don't know which follow-up email is the one that lands the week they finally have budget. You're not smart enough to pick, and neither am I. What you can control is how many swings you take and whether every swing clears a minimum bar.

Now, before somebody takes that and runs off to publish garbage five times a day, there's a second half to it.

Volume only compounds if the floor is high enough that nobody regrets opening it. The moment your worst piece is bad enough to make someone unsubscribe, volume works against you. You're not compounding anymore. You're churning through your own audience faster than you're building it.

So the actual system is a floor plus a cadence, not a ceiling plus inspiration.

For me the floor is simple. Every issue has to contain one specific thing somebody could go do on Monday. Not a concept. Not a mindset. A thing. If a draft doesn't have that, it doesn't go out, no matter how nicely it reads.

That single rule has killed more drafts than anything else I've written down, and it's the reason the bad issues are merely forgettable rather than harmful.

Go define yours. What's the one non-negotiable that has to be true before a piece of your work goes out the door? Write it down. Then stop negotiating with yourself about it at eleven at night, because you will lose that negotiation and you'll lose it politely.

People assume consistency is a discipline problem. It's almost never a discipline problem. It's a logistics problem wearing a discipline costume.

I have never once sat down on a Sunday night and written Sunday's issue. Not once in a hundred. If I had, there'd be maybe thirty of these instead of a hundred, because life happens and the week I got the flu would have been the week the streak died and the streak dying is usually the end of the whole thing.

Everything gets written in batches, a week or more at a time, and the whole week gets scheduled at once. When Sunday shows up, my only job is to have already done the work. That's it. The system carries it from there.

The same principle applies to literally every recurring thing in your business. Client reporting. Invoicing. Follow-up. Payroll. If any of those depend on you feeling like doing them on the correct day, you don't have a process, you have a hope.

Batch the work. Schedule the output. Separate the making from the shipping so a bad Tuesday can't take out a good month.

A note on tools, since people always ask. I use Claude as a thinking partner constantly, mostly for the parts that are genuinely mechanical. Pulling the archive so I don't repeat myself, arguing with an outline until it stops being boring, catching the three sentences in every draft where I said the same thing twice. It doesn't write these. It removes the friction that used to make me skip a week, which turns out to be most of the actual battle.

I also track where my hours actually go with Rize, which was humbling in the way that data usually is. I'd have sworn writing was eating my week. It wasn't. Context switching was, and I'd never have believed that without the receipts.

Here's the part I wish somebody had told me plainly, so I'm going to tell you plainly.

For the first thirty issues, essentially nothing happened.

Small list. Handful of opens. A couple of replies, mostly from people I already knew, which honestly makes it worse because you can't tell whether they liked it or were being kind.

That stretch is where almost everybody quits, and they quit for a reason that sounds smart. It isn't working. Let me try a different approach. And the different approach also doesn't work for thirty attempts, so they try a third, and now they've got three abandoned foundations and nothing built on top of any of them.

The compounding is real, but it is genuinely back-loaded, and I don't think there's a way to shortcut that. Somewhere around issue forty things started shifting. Replies from strangers. People referencing an issue from two months earlier. A guy who'd been reading for a while emailing to ask about working together, having never once clicked a link or replied to anything, which taught me something about how quiet most of the value is.

That's a lagging indicator by definition. Which means for the entire period where you most need proof that it's working, no proof is available. You just have to decide, up front, how long you're willing to do it before you're allowed to reassess. And then you have to not reassess before then, even on the bad weeks. Especially on the bad weeks.

Pick a number. A hundred is a good one. Not a hundred days, a hundred repetitions, whatever the unit of your thing happens to be. Then run it and refuse to have opinions about whether it's working until you're done.

Since I'm being honest about the whole run, here's what I got wrong.

I waited far too long to ask for replies. For the first couple of months I wrote at people instead of to them. The second I started ending with an actual question and a reason to hit reply, the whole thing changed character. It stopped being publishing and started being a conversation, and the conversation is where the business is. If you're doing anything like this, build the reply mechanism in on day one, not on day forty.

I over-edited early and under-edited later. The first thirty took me hours each because I was trying to sound like a business writer. They read like it. Somewhere in the forties I relaxed and started writing the way I talk, and those are better. Then I got a little too comfortable and shipped a few that needed one more pass. The sweet spot is one honest read-through where you cut anything that sounds like it came off a conference stage.

And I tracked the wrong number for way too long. I watched the subscriber count, because it goes up and it feels good. Subscriber count told me almost nothing. Replies told me everything. Replies are the leading indicator of every piece of business this thing has ever produced, and I ignored them for months in favor of a vanity metric that just happened to be on the dashboard by default.

Everybody frames this as an audience-building exercise. That's the smallest part of what it does.

Writing a hundred of these forced me to have an actual position on about a hundred business questions. Not a vibe. A position I had to defend in public with my name on it. That has made me measurably better at the consulting work, because when a client describes a problem, I've usually already argued myself into a view about it in writing, which is a very different level of readiness than having thought about it in the shower.

It also creates trust in a way that is almost impossible to fake. Showing up four times a week for six months is a signal you can't buy. Anybody can produce one great thing. Almost nobody will produce a hundred adequate ones on schedule, and the market knows it, even if it can't articulate why it trusts you.

And the last thing, which surprised me most. It kills the anxiety around any single attempt. When the next one goes out in two days, no individual piece carries much weight. The stakes on any given issue are almost zero, and that freedom is precisely what makes the good ones possible. The pressure to write something great is the single biggest reason people write nothing at all.

You've got something you've been meaning to do consistently. Content, outreach, follow-up, the weekly team meeting you keep cancelling, the client check-in you know matters. Something.

Pick one. Just one. Define the floor, the thing that has to be true every time. Pick a cadence you'd still hit during your worst week of the year, not your best. Then batch the work so it doesn't depend on your mood, schedule the output so it happens without you, and commit to a hundred reps before you're allowed to judge it.

Most of them will be unremarkable. A few will do more than you expected. You will not be able to tell which is which in advance, and that's fine, because it's not the point.

The point is that at rep one hundred you'll be a different operator than you were at rep one, and the compounding will have quietly done its work in the background while you were busy showing up.

Thanks for reading these. Genuinely. The replies are the best part of my week and I read every one of them, including the ones telling me I'm wrong, which are frequently the most useful.

See you Monday for a hundred and one.

Talk Soon,

Dan

Dan Kaufman
Founder, Dead Simple Growth and Pinnacle Masters

P.S. The batching and scheduling setup behind all of this is the same thing I use to keep the rest of the week from eating me alive. If you want it, reply with the word AUTOMATE and I'll send it over.