Run The Week After Publish

Hitting publish is the start of the campaign, not the end of the work.

Most teams spend days on the post and twenty minutes on the paste. They drop a link on LinkedIn, maybe on X, and call it distribution. The teams that get the piece seen run a written week: native posts, community replies, a reprint, and a reshare after the first audience has scrolled past. None of that requires a new idea. It requires a calendar you refuse to skip.

What to do: Before the post goes live, write the week. Day one is owned channels and one community. Day two is two more surfaces. Day three is a long-form reprint. Later in the week, reshape, do not just relink. Six months later, refresh the URL. That last step is Refresh, Don't Reprint. This chapter is the seven days after the first publish.

Why it works: Most of your audience missed it the first time, and the platforms reward native posts more than link dumps.

Example: On August 4, 2020, Ross Simmonds published the distribution log for a Canva case study his firm had just shipped. The post is still on rosssimmonds.com. Next to the analytics screenshot he prints the number: 26,282 pageviews in the first 7 days. On July 26, 2021, in a Superpath AMA with Jimmy Daly, he wrote the week Foundation actually runs. Day 1 is two tweets, one LinkedIn post, a subreddit, the email, and a Slack group. Day 2 is GrowthHackers, an Instagram story, Hacker News, and three Quora answers. Day 3 is a Twitter thread and a Medium reprint. Then they keep going.

Walk it through

I opened his own post, then the AMA, so the number and the calendar come from him.

1. Read the result next to the chart he embedded.

Ross Simmonds, August 4, 2020: 26,282 pageviews in the first 7 days, with the analytics row on the page

The row under the chart is the receipt. 26,282 pageviews. 23,678 unique pageviews. Seven minutes and 38 seconds on the page. One asset, one week, his domain. Above the chart he names the three moves: talk about the piece before it exists, treat launch day as an event, then reply to the reactions instead of posting once and leaving.

2. Copy the calendar, not the agency headcount.

Ross Simmonds, Superpath AMA, July 26, 2021: Day 1 through Day 3 of the distribution cadence, then "we never stop"

Day 4 on that page is "so on and so forth" and "we never stop promoting it." That is the line a one-person team will skip. It is also the line that compounds.

Cut the agency week down to rooms where you already have permission:

Day 0, before publish: pick the one community and the one newsletter the piece is for
Day 1: email the list, one LinkedIn post that teaches a point from the piece, one X thread, one Slack or Discord if you are a member
Day 2: answer one related Quora or Reddit question, and submit to HN only if the piece is actually for that room
Day 3: Medium or a LinkedIn article import, canonical back to you
Day 5: reshare a different excerpt, not the same sentence
Day 7: one DM to three people who would genuinely care, no blast

3. Do not confuse this with 1-3-5.

The 1-3-5 Repurposing Method is how one pillar becomes sixteen formats. This chapter is the sequence those formats travel through after the pillar is live. You can run a week with a single post and no carousel. You cannot run 1-3-5 without a pillar worth cutting.

The read

Publish is minute zero. The chart starts the day the piece goes up, not the day you remember to share it.
Link dumps are how platforms ignore you. Native first, URL second.
A written week beats a remembered week. If it is not on a calendar, it will lose to the next draft.

Steal it

Hand the assistant the post and the rooms you actually belong to: the subreddit, the newsletter, the Slack. Have it write the week as native posts, each one teaching a different sentence from the piece, with the URL last. You send them. Do this before the intro is finished, not the afternoon after you hit publish.

Skip Product Hunt, Hacker News, and Medium if the piece is not for those rooms. The launch-surface version of this, when the asset is a product rather than a post, is Seed The Launch Surfaces.

Gotchas

26,282 is one Canva case study in 2020. It is his analytics, on his post. It is not your forecast, and it is not a 2026 benchmark.
The AMA week is an agency week. GrowthHackers plus three Quora answers plus HN is a team. If you are one person, run Day 1 properly before you collect surfaces.
HN and Reddit will punish a marketing title. If you are going to those rooms, go with a sentence they would upvote without knowing you.
Resharing the identical URL every day trains your list to ignore you. Change the excerpt or wait.