Launch a SaaS
Consistent public facts and relevant free listings across several discovery categories.
Product-type launch guidance
One Launch Master. Different Evidence for Every Product Type.
Vibe Launch Master uses one canonical workflow, but a SaaS, AI tool, desktop app, mobile app, developer tool, and open-source product require different sources, assets, directory matches, risks, and success checks.
Built for finished products
The same launch workflow adapts to six different evidence profiles.
A SaaS, AI tool, desktop app, mobile app, developer tool, and open-source product should not be submitted with interchangeable facts or assets.
Launch an AI tool
A precise explanation of the user task, model boundary, and current capability instead of generic AI wording.
Launch a desktop app
Every listing matches the verified release state and links to an official signed artifact or honest Coming soon status.
Launch a mobile app
Store and directory listings describe the same current app, platform support, pricing, and privacy boundary.
Launch a developer tool
A developer can verify what the tool does, how to install it, where it runs, and which version the listing describes.
Launch an open-source product
Listings point to the canonical project and accurately describe the current license, release, maintenance, and support state.
Evidence map
Each product type starts from a different authoritative source and material set.
The Launch Master remains one canonical structure, but the sources and evidence required to support it change by product type.
Primary source
The official source that should define the product.
Required materials
The materials needed for accurate directory adaptations.
Field Primary source Required materials
a SaaS Official website, pricing, documentation, integrations, privacy, terms, and support. Pricing summary, feature groups, integrations, browser screenshots, onboarding, and support facts.
an AI tool Official product page, documentation, model or provider facts, pricing, privacy, and examples. Input, output, use cases, model boundary, data handling, screenshots, prompt examples, and limitations.
a desktop app Official website, release manifest, download page, changelog, security page, and support documentation. Platform-specific screenshots, architecture, version, signed state, checksum, system requirements, and install steps.
a mobile app Official App Store or Google Play page, product website, privacy policy, support page, and release notes. Store URLs, mobile screenshots, supported devices, pricing, permissions, category, and privacy facts.
a developer tool Official repository, documentation, package or binary release, license, examples, and support route. Installation, supported environments, API or CLI examples, license, screenshots, architecture, and limitations.
an open-source product Canonical repository, license file, README, documentation, release notes, contribution guide, and official website. Project purpose, install path, license, maintainers, contribution process, releases, screenshots, and support model.
Product type
Launch a SaaS
The destination mix is only useful when the underlying product facts and public release state are accurate.
Primary source
Official website, pricing, documentation, integrations, privacy, terms, and support.
Consistent public facts and relevant free listings across several discovery categories.
Materials Pricing summary, feature groups, integrations, browser screenshots, onboarding, and support facts.
Directory mix Product, SaaS, startup, software-alternative, industry, and developer directories when relevant.
Main risks Outdated pricing, unclear free trial, missing privacy details, and claims that confuse roadmap with shipped features.
Success condition Consistent public facts and relevant free listings across several discovery categories.
Product type
Launch an AI tool
The destination mix is only useful when the underlying product facts and public release state are accurate.
Primary source
Official product page, documentation, model or provider facts, pricing, privacy, and examples.
A precise explanation of the user task, model boundary, and current capability instead of generic AI wording.
Materials Input, output, use cases, model boundary, data handling, screenshots, prompt examples, and limitations.
Directory mix AI tool, product, SaaS, startup, software-alternative, and developer-tool directories when applicable.
Main risks Unsupported model claims, unclear data retention, fabricated benchmark language, and category overreach.
Success condition A precise explanation of the user task, model boundary, and current capability instead of generic AI wording.
Product type
Launch a desktop app
The destination mix is only useful when the underlying product facts and public release state are accurate.
Primary source
Official website, release manifest, download page, changelog, security page, and support documentation.
Every listing matches the verified release state and links to an official signed artifact or honest Coming soon status.
Materials Platform-specific screenshots, architecture, version, signed state, checksum, system requirements, and install steps.
Directory mix Product, app, desktop-software, software-alternative, startup, and developer-tool directories.
Main risks Showing unreleased platforms as available, missing signatures, stale checksums, or screenshots from concept builds.
Success condition Every listing matches the verified release state and links to an official signed artifact or honest Coming soon status.
Product type
Launch a mobile app
The destination mix is only useful when the underlying product facts and public release state are accurate.
Primary source
Official App Store or Google Play page, product website, privacy policy, support page, and release notes.
Store and directory listings describe the same current app, platform support, pricing, and privacy boundary.
Materials Store URLs, mobile screenshots, supported devices, pricing, permissions, category, and privacy facts.
Directory mix App, product, startup, industry, software-alternative, and mobile-discovery directories.
Main risks Wrong store region, unsupported device claims, stale pricing, unavailable builds, and inconsistent permission descriptions.
Success condition Store and directory listings describe the same current app, platform support, pricing, and privacy boundary.
Product type
Launch a developer tool
The destination mix is only useful when the underlying product facts and public release state are accurate.
Primary source
Official repository, documentation, package or binary release, license, examples, and support route.
A developer can verify what the tool does, how to install it, where it runs, and which version the listing describes.
Materials Installation, supported environments, API or CLI examples, license, screenshots, architecture, and limitations.
Directory mix Developer-tool, open-source, product, SaaS, startup, and software-alternative directories.
Main risks Broken install commands, unclear license, stale API examples, unsupported platform claims, and missing security boundary.
Success condition A developer can verify what the tool does, how to install it, where it runs, and which version the listing describes.
Product type
Launch an open-source product
The destination mix is only useful when the underlying product facts and public release state are accurate.
Primary source
Canonical repository, license file, README, documentation, release notes, contribution guide, and official website.
Listings point to the canonical project and accurately describe the current license, release, maintenance, and support state.
Materials Project purpose, install path, license, maintainers, contribution process, releases, screenshots, and support model.
Directory mix Open-source, developer-tool, product, startup, software-alternative, and ecosystem-specific directories.
Main risks Unclear maintenance state, missing license, unofficial forks, stale installation steps, and false support commitments.
Success condition Listings point to the canonical project and accurately describe the current license, release, maintenance, and support state.
Next step
Prepare one verified product source before choosing targets.
The automatic workflow starts with official facts, then matches directories. It does not begin from a copied target list and force every product into it.
Choose the product type first
Prepare one verified source before matching any directory.
The product type changes the required facts, assets, risk checks, and eligible destination mix.