This is a full example content pack for a demo idea, so you can see exactly what you get. Yours is built from your own idea.
Content Pack
What arrives, and where it arrives
Not a document. The words below are the pieces themselves, and each one is delivered as something you can post: copy you can edit, slides rendered as images, and a picture made for it.
- The copy for every piece, editable before anything goes out
- Each carousel as finished slide images, plus a PDF you can upload to LinkedIn yourself as a document post
- A picture per piece, carrying your own logo, saved to your project library
- A day and an hour for each piece, chosen in your audience's timezone
- Connect an account and we post them on that schedule; leave it unconnected and you download everything and post by hand
The idea: FreshNest, a weekly meal-kit subscription for busy parents who want healthy family dinners without the planning. Pre-portioned ingredients, child-tested recipes ready in 30 minutes, portions that scale to the household, and a menu you can swap in one tap.
Preview
01The week at a glance
One story, told ten ways, across five days. The story this week is the finding that changed the product: parents did not want more recipes, they wanted the deciding to stop. Every piece below comes at that from a different angle, so somebody who sees three of them gets a fuller picture rather than the same post three times.
Monday 8:10am, LinkedIn post. Tuesday 7:45am, carousel. Wednesday 8:10am, LinkedIn post. Wednesday 12:30pm, X thread. Thursday 7:45am, carousel. Thursday 5:30pm, LinkedIn post. Friday 7:45am, carousel. Friday 9:00am, newsletter. Plus two LinkedIn posts held for the following Monday and Tuesday so the week does not end on a cliff.
Every hour above is in the audience's timezone, not the founder's. FreshNest sells to parents in the United States, so the pieces land before the school run rather than at nine in the morning in another country.
02Monday, LinkedIn post: the finding
We interviewed 31 parents about dinner. Not one of them asked for more recipes.
What they said, almost word for word, was that the cooking is fine. It is the deciding that breaks them. By six o'clock they have made a few hundred small decisions and the question of what to feed four people is the one that finally lands badly.
So we stopped building a recipe app. The product now makes one decision a week and then gets out of the way: a menu arrives, you swap what you do not want in one tap, and that is the whole interaction.
If you are building for tired people, the feature is not more choice. It is fewer decisions.
03Tuesday, carousel: what 31 parents actually said
Slide 1. We asked 31 parents what makes dinner hard. The answer was not cooking.
Slide 2. 27 of 31 said the hardest part is deciding. A bar chart of the four answers, drawn from the interview counts, with deciding well clear of the rest.
Slide 3. What we expected to hear: not enough time. What we heard instead: not enough decisions left.
Slide 4. One parent: I can cook. I just cannot face working out what.
Slide 5. The average household makes this decision 260 times a year, and treats it as new every time.
Slide 6. So the product makes it once a week. A menu arrives. You swap what you do not want.
Slide 7. Fewer decisions, not more options. That is the whole idea.
Slide 8. Building something for tired people? Ask them what they decide, not what they want.
04Wednesday, LinkedIn post: the thing we got wrong
Our first version had a browse tab with 200 recipes. It tested badly and it took us a while to admit why.
A browse tab is a shop. It asks the person to choose, which is the exact work they came to us to avoid. We had built the problem back into the solution and called it a feature.
We replaced it with a single weekly menu and a swap button. Same recipes underneath. The difference is who does the deciding.
The uncomfortable part is that the browse tab was the thing we were proudest of.
05Wednesday, X thread: the 260 decisions
1. A household decides what is for dinner about 260 times a year. Almost every one is treated as a fresh problem.
2. We asked 31 parents about it. 27 said the deciding is harder than the cooking.
3. The market answers this with more recipes. More recipes is more deciding.
4. So we built the opposite. One menu a week, arriving without being asked for. Swap anything in one tap.
5. Early result: the swap button gets used about twice a week. People are not rejecting the menu, they are editing it.
6. That is the number we are watching. If swaps climb past four, the menu is wrong and we are back to a shop.
06Thursday, carousel: how the menu is built
Slide 1. How a week of dinners gets decided in about four seconds.
Slide 2. It starts from what your household already ate, not from a catalog.
Slide 3. A donut chart of a real week: 3 repeat favorites, 2 close variations, 2 new things.
Slide 4. The repeats are there on purpose. Novelty every night is another decision.
Slide 5. Portions scale to the household, so a family of five is not doing arithmetic at the register.
Slide 6. Everything is 30 minutes or less, tested with children who say so when it is bad.
Slide 7. And if a night is wrong, one tap swaps it. No browsing, no cart.
Slide 8. One decision a week, made for you and easy to overrule.
07Thursday, LinkedIn post: what the competition is doing
Three of the big meal-kit services changed their pricing page this quarter. All three moved in the same direction: more plans, more customization, more choice at the point of sale.
I think that is the wrong read of the market, and I think it comes from listening to the people who churn rather than the people who stay.
People who churn say they wanted more options. People who stay say the box just arrives and they stopped thinking about it. Those are not the same customer and they do not want the same product.
We are going the other way on purpose.
08Friday, carousel: the first ninety days
Slide 1. What we learned in ninety days of building a meal kit nobody asked us to build.
Slide 2. A line chart of weekly retained households across twelve weeks, from the real signup data.
Slide 3. Week 1: 41 signups from one post. We thought we had it.
Slide 4. Week 4: 12 still ordering. We did not have it.
Slide 5. The 29 who left all said a version of the same thing: it became another thing to manage.
Slide 6. So we removed the managing. No browse, no cart, no weekly planning session.
Slide 7. Week 12: 34 of 47 still ordering, and the swap button is doing the work the browse tab used to.
Slide 8. The feature that saved it was the one we deleted.
09Friday, newsletter: the week in one place
Subject: We deleted our best feature
This week we took the browse tab out of FreshNest. It had 200 recipes in it and it was the part of the product I liked most, and it was making the thing worse.
Here is the reasoning, in short. We interviewed 31 parents. 27 of them told us the hard part of dinner is not the cooking, it is the deciding. A browse tab is a shop, and a shop asks you to decide. We had spent three months building a beautiful version of the exact problem people came to us with.
What replaced it: one menu a week, arriving without being asked for, with a swap button for anything you do not want. Same recipes underneath. The difference is who carries the decision.
The early read is that this was right. Twelve weeks in, 34 of 47 households are still ordering, and swaps are running at about twice a week, which is people editing a menu rather than rejecting it.
What I am watching next: if swaps climb past four a week, the menu is wrong and we have quietly rebuilt the shop.
If you are building for people who are tired, it is worth asking what they decide rather than what they want.
10What you also get, and what this never does
Each carousel arrives as finished slide images in the brand colors, plus a PDF you can upload to LinkedIn yourself as a document post. Each piece has its own picture, art directed for that beat and carrying the real logo file in the corner. The charts named above are drawn from the numbers in the research, and any figure that cannot be traced back is dropped rather than illustrated.
Connect an account and each piece goes out at the time above, once. Leave the accounts unconnected and everything is still yours to download and post by hand.
It writes, designs and posts. It does not reply to comments, send messages, or manage a community, and nothing goes out that has not been approved first.