There is a moment on a voice sync, usually somewhere around month fourteen, where the answer changes shape.
For a year the founder has been answering questions like this: "I pulled ninety days of return comments on the hero SKU and twenty-six of sixty-one mentioned size." Specific. Dated. First-hand. The kind of sentence nobody else in the category can produce.
Then one week the answer is: "I think our ops lead mentioned something about that. Let me check."
Nothing has gone wrong. The founder hasn't got lazy, hasn't lost interest, hasn't drifted into leadership content. They got the thing they were working toward. They hired someone. The reports have an owner now. The inbox has a filter. They are not in the return comments any more because being in the return comments was never the job — it was what the job looked like when there were four people.
And the founder brand they spent a year building runs entirely on being in the return comments.
This is not altitude drift, and treating it like altitude drift makes it worse
We write a lot about founders drifting upward — trading the specific mechanism for the general principle because the general principle is easier to write on a Tuesday night. That's a writing problem. The material is still there. The fix is to go back down and use it.
This is different. This is a supply problem. The founder hasn't stopped reaching for the working detail. The working detail stopped arriving at their desk.
The difference matters because the fixes are opposites. "Be more specific" is useless advice to someone who genuinely no longer has the specifics. It produces one of two outcomes, both bad: the founder writes in the present tense about work they don't do any more, which the one operator in their audience who does that work can spot in a sentence. Or the founder quietly gives up on specificity and starts publishing the version of their expertise that survives without evidence — which is opinion.
Opinion is the most copyable layer of anything you publish. A competitor can adopt your position in a week. They cannot adopt your access, because your access refreshes on its own and their restatement doesn't.
So the founder who scaled out of their material doesn't stop sounding smart. They stop sounding sourced. And that happens months before anything shows up in the analytics.
Three things get taken away, in this order
Founders lose access in a predictable sequence, and the sequence is worth knowing because the third one is the expensive one.
First, the reports. Somebody else pulls them now. This is the least damaging loss and the easiest to fix, because a report is a file and files can be forwarded. Most founders who feel this are actually one standing request away from having it back.
Second, the inbound. The customer service inbox, the supplier calls, the 3PL escalation, the agency's Tuesday check-in. These get filtered because filtering them is the entire point of the hire. This one is worse, because the raw material here isn't data — it's language. The exact sentence a buyer typed. The way the supplier phrased the rate increase. You cannot get that from a summary, and the person summarising for you is correctly summarising, which means correctly removing the part you needed.
Third, and this is the one nobody sees coming: the decision. Early on the founder made every call themselves, which meant every call came with a reason they could describe. Now the call gets made by someone else against a rule the founder set. The rule is a better business outcome. It is also the moment the founder's content stops having a "here's what I decided and why" at the centre of it.
Founders notice the first loss, tolerate the second, and never register the third — because being removed from a decision you delegated well doesn't feel like a loss at all.
The tell shows up in your hedges before it shows up in your reach
If you want to catch this early, don't watch impressions. Watch your own qualifiers.
Open your last twenty posts and count how many times you wrote some version of: I think, generally, we've seen, in most cases, typically, from what I understand, a lot of brands. Then do the same for twenty posts from a year ago.
A rising hedge count is the earliest signal that a founder has been promoted away from their own evidence. It arrives three to six months before the distribution consequence, because a hedged post still reads competently — it just reads like it was written by someone who read about the thing rather than someone who did it. The platform doesn't punish it. Human readers don't comment on it. They just quietly stop treating you as the source.
The second tell is what happens in the DMs. Founders in full possession of their material get asked how. Founders who've scaled out of it get asked what do you think about. The first is somebody trying to do the thing. The second is somebody making conversation.
Four supply lines that actually work
You're not going back into the return comments. Let's not pretend otherwise. The fix is to build a route from the work to your desk that survives your seniority.
1. Second-hand access, with the seat named. The instinct is to launder somebody else's finding into first person because first person sounds stronger. It doesn't — it sounds fine until it doesn't, and the downside is severe. What actually reads stronger is the truth: "our ops lead pulled the return codes on the hero SKU last month and came back with something I'd have got wrong." That sentence does three jobs at once. It's specific. It's honest about the org. And it tells a reader you run a business where somebody's job is to go and look, which is a better signal about you than doing it yourself would have been at this size.
Make it a standing ask, not a favour. One question, one person, once a week: what did you find this week that surprised you.
2. Keep one live surface on purpose. Pick one thing you still touch personally and defend it. One SKU. One channel. One account. One weekly report you pull yourself even though someone else could. This is operationally slightly irrational and it is the single highest-return content decision a scaling founder makes, because it keeps one genuine first-person tap open. Founders resist it because it looks like failing to delegate. Frame it correctly and it's a research line item.
3. Publish the delegation itself. This is the one almost nobody uses, and it's the best material available to a founder at this stage.
When you hand a decision to someone else, you have to write the rule down. You have to convert a judgment you were making by feel into something another person can execute without you. That conversion is extremely hard, it is the actual work of scaling, and nearly nobody publishes it.
"Here's the call I used to make by instinct. Here's what I found when I tried to write it down so somebody else could make it. Here's the part of my own reasoning that turned out to be wrong once I had to say it out loud." That post requires access nobody outside your business has, cannot be restated by someone who hasn't done it, and speaks directly to every operator in your audience heading toward the same problem.
4. Move to pattern, and attach a count and a date. You can no longer say what happened on Tuesday. You can now say what happened across nine accounts over two quarters, which is something you couldn't say two years ago. That's a real trade, not a downgrade — but only if you attach the numbers. "Across the eleven brands we've onboarded since January" is pattern material with a receipt on it. "In our experience" is the same sentence with the receipt removed, and readers grade those two very differently.
The one thing to stop doing immediately
Stop writing in the present tense about work you've stopped doing.
Not because it's dishonest in any serious way — the founder usually isn't thinking about it at all — but because the reader most likely to catch it is precisely the senior operator you're writing for. They know what the day-to-day of that job looks like this year. Their conclusion isn't "he's exaggerating." It's "he's not current," which is a much harder thing to come back from than "he's busy."
Date it and the whole problem disappears. "When I was still running this day to day" costs you nothing and buys you the thing an undated claim actively spends: the reader's assumption that you keep records.
What good looks like at ninety days
Two markers, neither of which is reach.
The specifics come back at a different altitude. You're not producing Tuesday's number any more. You're producing quarter-level findings with counts attached, plus first-hand material from the one surface you kept, plus attributed findings from your team. Together, that's a denser evidence base than you had when you were doing everything yourself — you just had to build a route to it instead of tripping over it.
Somebody on your team disagrees with a post. When you're publishing findings that came from inside the business, the people inside the business start reading with an opinion. That's the sound of the supply line working. A founder whose team has nothing to say about their content is a founder writing about something other than their company.
FAQ
Isn't the honest answer just to write less? Publishing less is almost always more expensive than publishing thinner, because a gap in the archive is dated and permanent while a soft month is invisible. Hold cadence, fix supply. If you have to choose, one properly sourced post a week beats four hedged ones.
What if my team's findings aren't as interesting as mine were? They usually aren't, at first — because you're asking the wrong question. "Anything interesting this week?" gets you nothing. "What did you have to go and understand that you'd never had to understand before?" gets you the material. The person doing the work always has it; they just don't know it's interesting, for the same reason you didn't when you were the one doing it.
Should I say publicly that I've stepped back from the day-to-day? Once, plainly, inside a normal post. Not as an announcement. The founders who get hurt here are the ones who let a reader work it out; the ones who state it and keep publishing get read as someone who grew a business, which is the thing they actually did.
How long before this becomes a real problem? Longer than founders fear and shorter than they'd like. The archive keeps working for a while — a reader doing a read-through in November is experiencing eighteen months of your best material, not last month's. But it's a wasting asset. Six months of hedged, unsourced content in front of the same audience will change how you get described, and getting re-described is slow work.
If you're a founder whose content was built on access you no longer have day-to-day, that's a supply problem with a fix, not a signal to publish less. Get in touch and we'll look at where your material is actually coming from now.