Tell the people who asked. Then check whether it worked.
When it ships, Mind drafts a note to each person who asked, in their words. You send it. Then check the prediction.
14 days free. No card needed.
Close the loop in their own words.
A shipped feature lists everyone who asked and left an email, each with their own words, where and when.
Who can be told, and who can't
Said in public, your own team, no email, opted out, or already told: each listed with the reason.
One message, N drafts
Mind drafts one message from the done stories, never naming what an open story holds. Then a personal draft for up to 25 people, each in their own words.
Caps you set
By default, at most two emails to one person in 30 days and ten new people a week. Over a cap there is no draft, and anyone who opted out is never drafted.
What changed, and what it makes public.
Before you publish: what changed since last time, from your GitHub commit titles. MindBacklog never reads your code.
- What it makes public comes from each feature's spec, never from your code.
- When GitHub reported nothing, the result is Unknown, never a pass.
- Mind can't tell whether code works or is safe. You confirm the rest.
The page for founders who can't see what a release makes public
Four posts Mind drafts. You post.
Draft the kit writes four posts: Product Hunt, Hacker News, X and LinkedIn. Each comes from your Positioning, the done stories, and results you have a source for.
- Each post has Accept, Edit, Why? and Not now.
- A post with a number or quote not in your data is dropped.
- Plan launch day puts the day in one plan; nothing is sent or posted.
Your prediction against what happened.
On the check date, the outcome review opens with the prediction in the owner's words. The result comes from the source chosen when it was written, with its n.
- Fewer rows than it needs says Not enough data yet.
- Mind never says whether it worked: Worked, Didn't, Mixed or Too early is yours.
- Your calls counts predictions whose value crossed their line, never how you marked them.
Counted, never guessed.
A weekly review Mind drafts and you send. Every Friday: what moved, your calls checked, and the week's number against its target.
Users talked to and the key metric are counted. The rest is drafted only from those facts and never names the people you talked to. Edit any part and your words are kept. Nothing is sent from MindBacklog.
Does MindBacklog send the emails or post the launch?
No. Drafts and posts wait for you to send and post from your own accounts. Someone counts as told only when you press "Yes, I sent it".
Why can't some of the people who asked be told?
Some posted in public, such as a public thread or an app-store review, with no one to email. Others are your own team, have no email, opted out, or were already told. The page lists each one with the reason.
Does Mind say whether it worked?
Never. Mind's read describes the numbers in the review and uses only them. You mark Worked, Didn't, Mixed or Too early, with a line about what you learned.
Does the publish check read my code?
No. It reads your GitHub commit titles, what each changed feature makes public from its spec, and what GitHub reports. MindBacklog gets no token and no access to your code. It can't tell whether code works or is safe, and says so.
Does it read my inbox to count replies?
No. Reply tracking counts replies without MindBacklog reading any mailbox: a BCC copy on the drafts you send, and replies you forward or mark. It never reads Gmail or any mailbox, and never sends an email for you.
Ship it. Tell them. Check whether it worked.
Mind drafts the notes and the posts, and puts your prediction against what happened. You send, you post, you decide.
- 14 days free
- No card needed
- Viewers are free
