Playbook replay
Repurpose hero content
Six posts rewritten natively per platform, with one idea named as unrepurposable and one as worth cutting.
Run for Lumira, a demo brand we invented for this page. No customer data. Nothing here runs against a live account.
Every session here was run once and saved, against a demo brand or public data. On your own account Naise works from your brand voice, your campaigns and your connected channels, so it reasons about your data instead of a stand-in.
The default failure is slicing: the same argument cut into six pieces, each of which needs the other five. A repurposed post has to make sense to someone who never saw the original.
Reading the piece for ideas that stand alone rather than for passages that fit a character count. Those are different jobs and only the first one produces posts anyone reads.
Six standalone ideas found. Here is where each one goes and why.
1. LinkedIn, text post. The crossover point.
Refill schemes lose money until roughly 60,000 units. Below that, reverse logistics costs more per unit than the packaging saves.
Almost every scheme that has quietly disappeared was cancelled before reaching it. Not because customers would not return packaging. Because the finance review came first.
Native because it is an argument with a number, which is what performs here. Would die on TikTok.
2. TikTok, 25-second script. The city split.
"Same product. Same price. Same launch day. Two cities. Seventy-one percent returned in one, thirty-four in the other." (beat) "The difference was how far people had to walk."
Native because it is a reveal with a delay in it. Would be a boring paragraph on LinkedIn.
3. Instagram, carousel, 5 slides. Why yours will fail, as a checklist.
4. LinkedIn, text post. The wrong metric: refills judged on first purchase, paid back in month five.
5. TikTok, 15-second script. "We built the collection network before we launched the product. Everyone said that was backwards."
6. Instagram, carousel, 4 slides. What happens to a pouch after it comes back, told as a journey.
Each one is rewritten for its platform, not trimmed to fit it. Post 1 and post 4 are both LinkedIn text posts making related arguments, so space them at least a week apart.
The idea strong enough to carry a post by itself: the 71 against 34 city split, post 2. It is a finding, it needs no context, and it is the only thing in the source piece that a stranger would repeat to someone else.
The idea that needs the full piece: the argument about shared collection infrastructure. It only lands after the reader accepts the volume threshold, and any short version reads as special pleading. Leave it in the blog.
The idea to cut rather than repurpose: the section comparing your programme to two named competitors. It is the weakest part of the source and it is worse in short form, where there is no room for the qualification that makes it fair. Repurposing it would produce your first genuinely unfair post.
Where this stops today. Six posts, ready to paste. Scheduling them is a later ship, so the sequencing note above about spacing posts 1 and 4 is something you will need to enforce by hand.
Naise created an artifact
Six standalone ideas rewritten per platform, with one left in the blog and one cut.
Where each idea goes
| # | Platform | Idea |
|---|---|---|
| 1 | The 60,000-unit crossover | |
| 2 | 71% vs 34%, the city split | |
| 3 | Why yours will fail, checklist | |
| 4 | Judged on the wrong metric | |
| 5 | Network before product | |
| 6 | What happens to a returned pouch |
Carries a post alone: the city split. A stranger would repeat it.
Leave in the blog: shared infrastructure. Reads as special pleading when short.
Cut: the named-competitor comparison. No room for the qualification that makes it fair.
That was a sample. Run it on your own brand.
Naise reads your brand, your channels, and your market, then does this against your real data.
Run this playbook free