Slow Season, Strong Library: Why Slow Stretches Are Where Evergreen Content Actually Gets Made
The Edit #5
Let’s talk about evergreen content.
Ask five people what “evergreen content” means and you’ll get five versions of the same fuzzy answer. Something timeless. Something that doesn’t go stale. A how-to instead of a hot take.
That’s true enough. It’s just too thin to act on.
Evergreen isn’t a content type. It’s not a writing style either, no matter how many style guides talk about it like one. It’s a decision about durability, made once when something gets published and made again every time you choose whether to keep it standing.
A piece is evergreen because somebody keeps maintaining it, not because it was written in timeless sounding language.
Write the most timeless sentence in the world about a product that gets discontinued next spring, and you’ve written something that will be wrong in eight months, no matter how good the sentence was.
What you’re actually agreeing to, when someone says “let’s build something evergreen,” is a maintenance commitment. Most teams quietly drop that commitment the moment the piece goes live.
This issue of The Edit is brought to you by Shlomo Genchin:
CopyTemplates
My friend Shlomo just launched CopyTemplates ($97) – a library of 63 proven copywriting techniques, each comes with handpicked examples (500+ in total), plus 70+ copy-paste AI prompts and Claude skills.
It’s the best resource I’ve seen for writing headlines, with or without AI.
Building is the obvious move. Maintaining is the one people skip.
There are two different jobs hiding inside “let’s use this slow stretch for evergreen content,” and they deserve to be named separately, because most people only do one of them.
The first is building new. This is the deep guide you’ve been meaning to write since February. The resource page that would save your team the same explanation for the fortieth time. The framework piece that’s been a half finished doc for three months because nobody could carve out the four hours it actually needs. The slow season hands you those four hours. Use them.
The second is maintaining what’s already there, and this is the one that gets skipped almost every time.
Go pull up something you published a year or two ago. Look closely. The example you used is probably out of date. The screenshot shows a version of a product that’s been redesigned twice since. The tone might not even sound like you anymore, because you’ve changed and the page hasn’t.
That piece is still live and maybe it’s still ranking. It’s still the first thing a new reader finds when they search your name next to the topic. And yet it’s passively representing a version of your thinking you’d correct yourself on if anyone asked you directly.
Most content strategies treat evergreen as something you make once and check off. But the actual job is something you keep doing, and a slow season, summer for a lot of people, is exactly when you have the room to do it without it competing with everything else on your plate.
If you lead a team, this is worth saying out loud to them, because nobody puts “go fix a two year old blog post” on a list of impressive downtime projects. It feels small, but it isn’t. It’s the unglamorous half of the same investment as building something new.
Deadlines optimize for today. Downtime optimizes for the next two years.
This is the actual mechanism behind all of this, and it’s simpler than it sounds.
When you’re working under pressure, you optimize for whatever’s due. A launch needs copy by Thursday, so you write copy that’s good enough to ship by Thursday. That’s not a knock on the work. It’s just what pressure does. It narrows your view down to the thing in front of you, and the thing in front of you is rarely “will this still hold up in two years.”
When the pressure lifts, the aperture opens back up. You’re no longer asking “is this good enough for Thursday.” You’re free to ask “is this good enough to still be true next spring,” which is a completely different question with a completely different answer.
Same person.
Same skill.
Different question, because the only thing that changed is whether something was bearing down on you while you answered it.
This works exactly the same way whether you’re allocating a team’s hours or your own.
If you run a department, the version of this is choosing, on purpose, to point a few people at long horizon work instead of letting the calendar default to whatever’s loudest.
If you’re a freelancer or a solo operator, it’s the same decision made with your own time, which arguably takes more discipline, since there’s no one else’s calendar making the call for you.
Either way, the slow season isn’t a break from the real work. It’s the only window where the durable kind of work actually gets a fair shot.
Most of what you could build doesn’t deserve the investment.
None of this is permission to spend the summer building everything you’ve ever thought of. Not everything earns evergreen treatment, and pretending otherwise just produces a different kind of clutter.
Here’s the filtering question: would this still be true and useful in two years if nobody touched it again?
If the honest answer is yes, then great! You’ve found something worth either building from scratch or adding to the maintenance list. It’s durable enough to be worth the upkeep.
If the answer is no, well, that’s fine too. It just means the idea was never evergreen. It was a good piece for right now, and right now is a perfectly respectable thing for content to be. Honestly, not everything needs to last. Plenty of useful work has a shelf life of a season, does its job in that time, and that’s enough.
The mistake isn’t writing things that expire. The mistake is mislabeling them, calling something evergreen out of habit and then being surprised two years later when it’s wrong.
AI can spot what’s gone stale. It can’t decide if anyone still needs it.
This is one of the places AI is genuinely useful.
Point it at your existing library and ask it to flag what’s likely outdated: references to discontinued products, links that no longer resolve, examples leaning on numbers from two years ago.
Ask it to draft a first pass at an outdated section, or spin a long guide into a shorter version for a different platform, or tighten the SEO on something that’s been underperforming for reasons nobody’s diagnosed.
All of that is real time saved, and during a slow season it means the maintenance half of this work stops competing for hours with the building half.
What AI can’t do is tell you whether the piece still matters. It doesn’t know if your audience moved on, if your positioning shifted, or if the topic itself just isn’t the one you want to be known for anymore. AI can tell you what’s stale, but only you can tell whether it’s still worth keeping fresh. Treat it as the thing that hands you a shorter list to think about, not the thing that thinks about it for you.
The pressure is coming back. The question is what it’ll find.
The slow seasons won’t last. They never do. Your busy season will show up the way it always does, with a calendar that fills back in faster than anyone expects, and the version of you that exists then is going to be very busy optimizing for whatever’s due that week.
That version of you is going to need something to stand on. Whatever you build or fix now is what they’ll be standing on later.
When the pressure comes back, what will you wish you’d built while it was slow?
👀 If you’ve been looking for the operating logic underneath the craft…
Most copywriting education teaches rules. What to do. What not to do. When to use this formula, when to try that one.
That’s fine as far as it goes, but rules conflict! And when they do, you need something that tells you which one wins.
That’s what I’ve been building.
The Conversion Copy Operating System is a premium reference manual for senior copywriters, content leads, and marketing managers who already know how to write but have never had a governing structure for the craft.
Five principles that sit above the rules.
A headline system.
The Five-Layer Edit.
A QA rubric for reviewing others’ work.
Decision logic for the frameworks you already use.
Not “tactics.” Not “templates.” The underlying thinking that makes everything else make sense.
It’s built for practitioners with 3-10+ years of experience who sense there’s a structure underneath what they’re doing but haven’t had it mapped out clearly.