Free Claude Project
A Claude Project you fill in from your own spreadsheet and sent folder. It tells you the month people stopped posting, why they stopped, and who's worth asking again.
Free. The Project instructions, the roster template, 6 prompts and a worked example.
The Project works from your own records. Every answer it gives points to the line in your roster it came from, so when leadership asks what happened, you have something to show them.
See how Supergrow catches it earlyI'm Deven, founder of supergrow.ai, the LinkedIn content platform for B2B teams. A programme dies from people not posting, not from posts doing badly. Nearly every marketing person I talk to has a dead one behind them and can't say why. This is what I'd run before asking anyone to try again.
Bootstrapped since 2023 · profitable, no investors · #1 Product of the Day and Week, Product Hunt, 19 February 2024
Quick start
Create a Claude Project called Post-Mortem. Paste instructions.md into the instructions box.
One block per person who signed up. Rough dates are fine. Gaps are fine. Or build it further down this page and copy it out. Then add ROSTER.md to the Project's knowledge.
Prompt 1 tells you when it stopped. Prompts 2 to 5 look at why. Prompt 6 gives you the verdict and writes the messages to the people worth asking again.
Gaps are fine. If a field is empty the Project says so and moves on. It doesn't make things up to fill the space.
Before you start
Four things. Most of it is already in a spreadsheet and your sent folder.
One thing before you paste. The roster will have names, rejected drafts and things people said in private. Use a work account your company has approved, leave out anything you wouldn't show the person it's about, and keep customer names and deal details out of it.
Why this happens
This is how it usually goes. Someone announces the programme in an all-hands. 12 people sign up. 7 post in month 2. By month 4 it's down to 2, and one of them is you. A quarter later someone asks what happened, and nobody has a clear answer.
The answer is usually in records you already have. Who was interviewed and who was just sent a topic. Which drafts came back, and what the person said about them. How many drafts were sitting unread when someone stopped replying. The 6 prompts go through those records and give you the month posting stopped, the most common reason, and the 3 people worth contacting again.
Who this is for
For
Not for
What it takes
Try it here
Add the people who signed up and answer 7 questions about each one. It shows who posted each month, when posting stopped, a likely reason for each person, and the first thing to change. Nothing is saved or sent anywhere. This is the rough version. The Project reads the full roster and quotes the line behind every answer.
| Name, role | Interviewed | Drafts sitting unread | Published | First post | Last post | Rejected a draft | Replied to reminders | Their subject | Reason |
|---|
Who posted, by month
Copy the roster out, add the dates and quotes the table doesn't have room for, and run prompt 1 in the Project.
The 5 reasons
Everyone who stopped fits one of these. The reason is always about what they were given, never about who they are.
They were never interviewed, or they were told to "share something" and had nothing to share. There was nothing to approve.
It came back with "this isn't me" and nothing happened after that. They were reading, which is better than silence. The problem is the draft was written from a topic, not from them.
3 drafts sent on the same day, sitting for 5 weeks, 2 reminders sent. They stopped opening the emails because every email was 3 decisions.
The thing they'd post about belonged to someone more senior, or 2 people kept writing the same post. A CEO whose subject is "the company" doesn't have one.
No draft opened, no reminder answered, nothing said. A third message hurts your standing with the people who are still reading.
The Project
Open any file to read it or copy it. Run the prompts in order. Prompt 6 wants the answers from 1 to 5 pasted in, and that's where the verdict comes from.
Worked example
The company, the people and the dates are made up, so you can see what comes back before you run your own. 12 people signed up in March. 5 were interviewed that month, Karl in April, and 4 were sent topics. 7 posted in April. By July only Dev was still posting.
The reason
Nobody asked them anything
3 of the 10 who stopped, and it's underneath a 4th. 4 people were never interviewed. All 4 never started.
When it stopped
May
7 people posted in April and 3 in May. It never recovered. 4 people's last post was in April.
What it wasn't
"People got busy"
Hana replied to both reminders. Omar replied. Karl posted twice in 3 weeks and then had nothing new to say, because nobody had asked him anything since 2 April.
The one change
Interview first, every month
15 minutes with each person before anyone writes a draft, and again every month.
Everyone, and the line that decided it
Who to contact first, and what to send
1 · Hana, VP Sales
"Hana, one thing, not three. The oldest of the 3 drafts, as it is or binned, your call. If it's a no, that's fine and I'll stop sending them."Posted 4 times, replied to both reminders, 3 drafts still sitting.2 · Ruth, Product lead
"Ruth, you were right about the third one. I'll rebuild the next one from your own emails. One look, yes or no, and no more polished ones."Posted twice and told you exactly why she rejected the third.3 · Lena, Head of Customer Success
"Lena, churn is yours from here. Dev's off it. 15 minutes next week, just on churn?"Posted 3 times and stopped for a reason you can fix in a sentence.Let go: Sam. One draft, 2 reminders, nothing. A third message hurts your standing with the 3 above.
The full roster and the complete answers to prompts 1 and 6 are in example.md in the download.
Get it
instructions.mdthe Project rules, pasted in onceROSTER.mdthe roster template, filled in per programmeprompts/01 to 06the 6 prompts, run in orderexample.mdthe worked example, roster and verdictREADME.mdthe setup steps, 20 minutesSet it up in 20 minutes. Fill in the roster from what you have. Run prompt 1 today.
Or copy any file from the list above.
Where Supergrow comes in
Everyone signs up. Nobody records who was interviewed and who was sent a topic.
Half the people have stopped. Nobody notices, because nobody is counting who published.
Someone asks what happened. You run this.
PostCast interviews each person, so everyone has something to post from. Content DNA learns how each person writes, so drafts sound more like them. Drafts go to each person one at a time for a one-tap yes. And the dashboard shows who published from week 1, so a drop in month 3 is visible in month 3.
When it goes wrong
You're missing dates. Check the sent folder and their LinkedIn profiles, fill in the last post for everyone, and run prompt 1 again.
That one needs no draft opened, no reminder answered and nothing said. If someone replied to a reminder, they don't belong there. Check what you put under reminders and what they said.
Once, in month 1. The roster will show one interview date and nothing after it. One interview gets you a month of posts, not a programme.
Give them the 3 sentences from prompt 6. 7 of 12 at the peak, 1 of 12 at the end, the reason, the change. Reach didn't stop the programme and won't restart it.
They usually aren't. The order is: posted, then rejected a draft, then replied to a reminder. Seniority comes last. Trust the order.
That means updating a roster by hand once a week for 12 people. The 10-Person Pilot runs into the same thing, because it tracks who posted in a spreadsheet too. Counting who posted should be the tool's job, not yours.
Supergrow does the interview, the voice, the drafting, the approval and the publishing for every person, and counts who published from week 1. If someone stops, you see it that week.
Deven Bhooshan, co-founder of Supergrow