Free Launch Brief

The brief asks for a public product URL, the product name, who it is for, and a handful of facts that would still be true if the marketing site went down: what it does, what changed recently, and one constraint you will not hide (price, audience, or what it is not). You can add a competitor only as contrast, not as a claim about their ranking.

Nothing in the form is stored. The URL is read in this session so the draft can mention the real product. Localhost and private addresses are not fetched. If you do not have a live URL yet, describe the product in the fact boxes and leave the address for later.

You get a canonical paragraph first: one block of copy that names the product, the audience, and the outcome without stuffing a keyword. Then you get listing copy aimed at the ten editorial sites in the monthly mix — Aura++, IndieHunt, EarlyHunt, Uno Directory, MakerHunt, SideHunt, LedePress, HedPress, ListedPress, and PiecePress. Each block is a short pitch in the shape that site’s listing or article usually needs, not a promise that the site will run it.

Optional extra-channel drafts (for outlets such as Peerlist, Dev Community, Indie Hackers, Quora, Medium, Hashnode, X, and LinkedIn) appear only when the facts you entered look like a genuine fit for that audience. They are not a quota and they are not appended to every brief. If the product is a local services firm with no builder audience, those extras stay off.

The brief does not log in anywhere. It does not create a listing. It does not publish an article. It is a drafting room for the same kind of copy a writer would start from before editing against the live product.

Before: “AI-powered platform that leverages synergy to 10x productivity for teams.” After: “Posting Dude writes and publishes one editorial article a month on each of ten sites in a publishing network. You send a URL and three facts. You get live links in the dashboard. Launch is month to month for one project.” The second version names the work, the input, and the output. It does not claim traffic.

Before: “The #1 directory for indie hackers to get backlinks fast.” After: “A public product page for a time-tracking app aimed at solo lawyers. The listing copy says what the timer does, who it is for, and that it exports to CSV. It does not say the listing will rank, get cited, or replace a launch post.” Specific beats superlative. The brief is built to prefer the second shape.

Paste the live product, not a coming-soon page, unless you are honest that it is not shipping yet. Editors open the URL. If the facts in the brief disagree with the homepage, the homepage wins and the draft looks careless. Keep one number you can defend (price, seats, or time saved on a real workflow) and drop the rest.

Read the canonical paragraph aloud. If you cannot say it in one breath, cut the clause that names a ranking, a citation, or a competitor’s failure. Then skim each site’s block: directory listings usually want category and a one-line outcome; editorial sites want a reason to write this week. The UTM builder is the next click if those listings will carry campaign links.

When the extra-channel drafts appear, treat them as optional. They are a fit check, not a to-do list. A product that belongs on a builder directory does not automatically belong in a Q&A thread. Leave those blocks unused rather than posting them as filler.

It does not publish anything. It does not submit the copy to Aura++, IndieHunt, or any other site. It does not guarantee pickup, a follow link, an AI citation, or a ranking. A clean paragraph can still be rewritten by an editor, or declined because the product is a poor fit that week.

It is not an SEO audit. Pair it with the UTM builder when you need tagged links in a listing, and with the llms.txt checker when you care what assistants are allowed to read on your domain. The free tools index lists the rest.

The UTM builder tags campaign links. The llms.txt checker reads the crawler file on your domain. The free tools index lists the rest.