Sample Launch Pack report
This is a sample with example data. ExampleApp is a fictional product, these listings do not exist, and most directory names are placeholders (a real report names every directory). The numbers below are illustrative, not an average or a forecast; results vary by product and category.
Product: https://exampleapp.example · Category: General SaaS / B2B · Delivered Oct 9, 2026
Launch pack (founder pack) (showing 8 of 107)
Ranked best first. In the real report each name links to the directory's submit page, has its requirements one click away, and has an "I submitted this" button so it's included in the re-checks. Ready-to-paste copy and the Product Hunt and Show HN drafts sit above the list.
| # | Directory | Cost | Typical review | Why it's yours | Status |
|---|---|---|---|---|---|
| 1 | Product Hunt | Free | You pick the launch day | Expects the maker to post. Draft in your kit. | Submitted, waiting on the directory |
| 2 | Hacker News (Show HN) | Free | Instant | Expects the maker to post. Draft in your kit. | Yours to submit |
| 3 | Launch community I | Free (paid upgrades) | Weeks or longer | Has a captcha. We don't use captcha-solving services. | Live |
| 4 | Startup directory J | Free (paid upgrades) | Days | Its terms forbid submitting on someone else's behalf. | Submitted, waiting on the directory |
| 5 | Launch site K | Free (paid upgrades) | Weeks or longer | The free listing needs a badge or link on your site. | Yours to submit |
| 6 | Review site L | Free | Not stated | Sign-in needs your own Google, GitHub, or X account. | Yours to submit |
| 7 | Launch site M | Free | Not stated | A captcha appeared when we tried; moved to your pack. | Yours to submit |
| 8 | SaaS directory N | Paid (from $39) | Days | No free listing. We never buy listings for you. | Yours to submit |
Done for you (showing 3 of 3)
Directories that fit the product, have a free listing, and allow submissions made on the founder's behalf; the count matches today's measured number for a general SaaS. Pending, declined, and failed submissions are shown with the reason.
| Directory | Status | Listing URL | Submitted | 7-day check | 30-day check | Notes |
|---|---|---|---|---|---|---|
| Alternatives site A | Live | https://alternatives-a.example/exampleapp | Oct 6 | live | live | |
| Similar-sites engine B | Live | https://similar-b.example/site/exampleapp.example | Oct 6 | live | live | Approved instantly. |
| Launch site C | Live | https://launch-c.example/products/exampleapp | Oct 6 | not yet | live | Free queue cleared on Oct 28. |
AI-search-ready product page
Four files built only from the intake answers, by the same code that builds real orders. Nothing is invented, and an answer left blank is left out. They state the product's facts in formats search engines and AI assistants read; they don't guarantee rankings, citations, or traffic.
- facts.html: a standalone facts page for https://exampleapp.example/facts, with 8 questions answered from the intake.
- facts.md: the same page in Markdown.
- homepage-jsonld.html: schema.org structured data (SoftwareApplication and Organization) to paste into the homepage's <head>.
- llms.txt: a plain summary with links, for the site root.
The report explains where each file goes. The sample's homepage JSON-LD:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "SoftwareApplication",
"name": "ExampleApp",
"url": "https://exampleapp.example",
"description": "ExampleApp watches your API endpoints and pages the engineer on call with the failing request.",
"slogan": "Uptime checks that page the right engineer",
"applicationCategory": "BusinessApplication",
"operatingSystem": "Web",
"isAccessibleForFree": true,
"keywords": "api monitoring, uptime, alerts",
"datePublished": "2026-09-01",
"softwareHelp": {
"@type": "CreativeWork",
"url": "https://docs.exampleapp.example"
},
"publisher": {
"@id": "https://exampleapp.example#organization"
}
},
{
"@type": "Organization",
"@id": "https://exampleapp.example#organization",
"name": "ExampleApp",
"url": "https://exampleapp.example",
"founder": {
"@type": "Person",
"name": "Ada Founder"
},
"email": "[email protected]",
"sameAs": [
"https://x.com/exampleapp"
]
}
]
}
</script>
The sample's llms.txt
# ExampleApp > Uptime checks that page the right engineer ExampleApp watches your API endpoints and pages the engineer on call with the failing request. ExampleApp watches public and private API endpoints and alerts the engineer on call with the failing request, the response, and a diff against the last good run, so small teams fix outages faster. - Category: API monitoring - Who it's for: Small teams running public APIs - Pricing: Freemium (free plan + paid plans) - Platforms: Web - Open source: No - Launch date: September 1, 2026 - Founder: Ada Founder - Contact: [email protected] ## Links - [Facts page](https://exampleapp.example/facts): a plain summary of ExampleApp - [Facts page in Markdown](https://exampleapp.example/facts.md) - [Website](https://exampleapp.example) - [Documentation](https://docs.exampleapp.example) - [X (@exampleapp)](https://x.com/exampleapp)
Launch-day checklist
The report also opens with a short checklist built from the order: publish the product page files, post the Show HN draft, schedule the Product Hunt launch, then work through the top free directories in your pack, ticking each one so it's included in the re-checks.
What each status means
- Live The listing page loads and shows the product.
- Submitted, waiting on the directory Sent by us, or ticked by the founder. Many directories moderate by hand; the re-checks pick it up when it goes live.
- Yours to submit In the founder pack, with the link and copy.
- Manual step in progress An email or application we've sent and are following up.
- Declined by the directory The directory said no, with its reason when it gives one.
- Could not submit We couldn't submit after retries; the reason is in the notes.
Your real report lives at a private link we email you, and it fills in as the work happens.