Build › Launch and Tell the N who asked

Tell the people who asked, launch again and again

Updated 1 Nov 2026 · 6 min read

On this page
  1. Tell the N who asked
  2. Build › Launch
  3. Before you publish, from the Launch page
  4. Replies
  5. Draft the map (an idea, not built yet)
  6. Costs
  7. Who sees what
  8. FAQ

When something ships, two things are worth doing: tell the people who asked for it, and tell everyone else. MindBacklog drafts both. It never sends an email or posts anything. You send and post from your own accounts.

Tell the N who asked

A shipped feature's page has a Tell the N who asked card. Open it to see:

  • People to tell: everyone who asked for the feature, or for a problem it solves, or said so in a conversation, with an email address. Each person shows their own words (at most 140 characters), where they said it and when.
  • Who can't be told, and why: said in public (Reddit, an app-store review, a public page: there's no one to email), your own team, no email, opted out (or erased, or on your suppression list), or already told about this feature. Why these people? lists the rules.
  • One message: Mind drafts it from the done stories (and the help article, once it's final), with an invitation to say what still gets in the way. It never mentions anything an open story or the spec's out-of-scope list names. You can edit it before you make any drafts.
  • Create N drafts: personal drafts for up to 25 people, most recent first, as one plan you review and apply. Each draft starts with their name, when they asked and their own words. Open each one in Gmail or your email app, or copy it, send it from your own email, then press Yes, I sent it. Only then does that person count as told.
  • Export the rest for your email tool: a CSV (name, email, what they asked, the date and the source) for everyone else. Nothing is stored and nobody counts as told.
  • Copy one message: the message without the personal lines, to paste anywhere.

A feature that isn't live for users yet says so and offers nothing to send.

Build › Launch

Build › Launch is where one launch comes together. A launch (L-1, L-2, …) holds one or more shipped features, a day, the channels you'll post to and, if you want, the initiative it serves. New launch starts one; telling the people who asked starts one for you.

Before you launch

A readiness check that never blocks you. The first three lines are read from your data:

  • No open secret-scanning alert on the repository (from GitHub; unknown when no alert has ever arrived).
  • A feedback channel received something in the last 14 days.
  • The publish check was marked.

The other three are yours to confirm: sign-in works for someone new, a user sees only their own data, and you can tell whether it was used. Skip any line, or the whole check, with a reason: the reason is logged. When you mark the launch It's launched, it keeps the data lines as they stood.

The kit

Draft the kit (Draft again to redo it) writes four posts (Product Hunt, Hacker News, X and LinkedIn) from what your product says about itself on Positioning, the done stories and results you have a source for. Each post: Accept, Edit, Why? (what it was drafted from) or Not now, and I posted it once you have. A line that mentions something not built yet is flagged under Check before you accept. A post with a number or a quote that isn't in your data is dropped.

The help article and the release notes are your features' own documents: the kit shows where each one stands and links to its Docs tab.

Plan launch day

Plan launch day puts the whole day into one plan. You can untick any line:

  • the launch, on its day;
  • the personal drafts for the people who asked;
  • a reminder in your bell to post each accepted post, at the time you pick, in your own time zone;
  • 30 days of watching Feedback for the features' names (you can edit the words); the digest says "N new mentions since launch";
  • the outcome review, when the initiative has a prediction and no review yet.

Nothing is sent or posted. You can undo the plan for 24 hours.

What it taught

At the launch's outcome review, or 14 days after it launched, Mind can draft up to three lessons from what's counted: drafts made and sent, posts accepted and posted, mentions since launch, checks skipped and the review's verdict. Each lesson names the facts it rests on. Keep or Drop each one. Previous launches lists every launch with its result and the lessons you kept. Replies to your emails aren't counted.

Before you publish, from the Launch page

The readiness card's Before you publish line says when the publish check was last marked. Check it here opens the publish check itself under it: what changed since you last published, what the features make public, the checks, and Mark as published. It's the same check as Build › Publish check, not a copy.

You can tell whether it was used is yours to confirm, unless PostHog is connected (Settings › Connections). Then it is checked by data: it passes once your events are mapped and PostHog was read in the last 3 days. You can still skip it with a reason. A launched launch keeps the line as it stood on launch day.

Replies

When reply tracking is on (Settings › Outreach), a reply matched to one of your drafts shows on Tell the N who asked ("Replied 3 Nov", and "N replied" in the counts), and a launch's lessons count replies among their facts. The page's How this works says what it does with the switches you have on: sending from your own Gmail after you review it, and a BCC copy that counts someone as told when it arrives. Without them, someone counts as told when you say you sent it.

Draft the map (an idea, not built yet)

On Build › Map, editors see Draft the map. Before you build, Draft from your thesis: Mind proposes up to 12 things it should do, each labelled Must-have, Differentiator or Later, with one sentence of why from your positioning or from what a competitor's own docs say (with the date it was read). Every row is a guess. They come as one plan with every row unticked: tick the ones you want, and each becomes an Idea feature in its area. Mind never claims a competitor lacks something. Once you're live, From your site proposes the map from what your own site says (no AI).

Costs

The message to the people who asked: 1 AI credit. The four posts: 4 AI credits. The lessons: 1 AI credit. Draft the map: 3 AI credits. A draft that fails or comes back unusable gives the credits back. The readiness check, the drafts for each person, the export, reminders and watching Feedback are free.

Who sees what

Viewers see the pages but no button, and never a customer's email address. Only editors make drafts, export, plan and mark a launch.

FAQ

Did MindBacklog send my email or post my 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 (or, with reply tracking and a BCC copy on, when the copy arrives).

Why can't I tell some of the people who asked? They are listed under who can't be told, with the reason: they posted in public (Reddit, an app-store review: there is no one to email), they are your own team, there is no email, they opted out, or they were already told. Why these people? lists the rules.

Why is a post flagged "Check before you accept"? The line mentions something not built yet. A post with a number or a quote that is not in your data is dropped.

Why do I see no names or emails? Viewers see the pages but never a customer's email address, and have no buttons.