LaunchRepoA SaaS launch is not one day; it is a list of 346 places a buyer might look, each with its own form. Founders know this and still skip most of it, because the work is repetitive and nobody on the team owns it. LaunchRepo makes it a task an AI agent can own: the playbooks say what each platform expects, product.json holds the facts and copy, and submissions.csv shows what is submitted, pending, scheduled or live.
The specific pain: nobody owns the list
Every SaaS team has a spreadsheet of directories somewhere. It is usually half filled, out of date and nobody knows which rows led to a real listing:
- Forms with different field limits
- Tagline, short description, long description, category, pricing model, screenshots in three sizes — each platform slightly different, each one hand-edited from the last.
- Review sites with their own rules
- B2B review platforms want a company profile, a verified domain and sometimes a support contact before a listing goes live. Missing one field stalls the whole entry.
- Status nobody trusts
- “Submitted” in the spreadsheet can mean anything from live to bounced. Without evidence, the list is not a source of truth.
How the workflow fits a SaaS team
Product context the whole team can edit
product.json and identity.json hold audience, problem, differentiator, real features, pricing and the public contact. The local dashboard edits the same files your agent reads, so marketing can update copy without touching the terminal.
Standing permissions, once per product
authorizations.json records what the agent may do — free registrations, final submissions, verification emails, badges on your site. Granted once, respected on every resume; spending stays at zero.
Batches that respect your launch date
Set the earliest launch date once. Platforms that schedule launches are never booked before it, and free-tier queues are recorded as scheduled or queued rather than live.
A tracker you can hand to a colleague
Eleven states, each tied to a minimum observation, in a CSV and a local dashboard. “Live” requires a public URL and a human confirmation, so the number in the weekly update is real.
Which directory categories matter
The catalog tags every one of the 346 platforms with one category. The counts below are computed from the catalog at build time; how many platforms actually fit your product is something your agent checks per directory before it submits anything.
Product launch platforms
104 playbooksLaunch-day platforms and new-product feeds. For a SaaS these bring the first wave of attention and are usually free; the playbooks cover scheduling and maker profiles.
Software and tool directories
85 playbooksTool directories and alternatives sites where buyers compare options. Listing here is about category fit and complete profiles rather than a launch date.
B2B software review sites
32 playbooksReview platforms and B2B marketplaces. Slower, stricter and often with paid upsells your agent will decline; the playbooks name which fields block a free profile.
Example platforms from the catalog
Platforms from the catalog that a SaaS is usually expected to appear on. Six have a public field guide on this site; the rest are covered by the playbooks in the repository.
- Product HuntThe launch everyone asks about; the playbook covers the scheduling flow and the maker checklist.Field guide →
- SaaSHubAn alternatives directory where the profile lives on comparisons; category fit matters more than launch timing.Field guide →
- SaaSworthyA SaaS comparison site where an inquiry leads to a vendor portal and a profile that sits in review before it shows.
- GoodFirmsA B2B review platform with a multi-step vendor profile behind an email code; the basic listing is separate from the paid tiers.
- FazierA launch platform whose free checklist can include a domain-rating threshold and a badge; the playbook says when to record blocked instead.Field guide →
What LaunchRepo does not do
- It is not a submission service and does not create accounts for you. Your team’s agent works in your own browser, signed in as you.
- It does not guarantee listings, backlinks, domain metrics or traffic — no directory is under our control.
- It does not buy featured spots. Paid routes are recorded as deferred_paid; whether one is worth it stays your decision.
- It does not launch client products under one licence. Unlimited own products, yes; agencies need a separate licence.
Licence, in one sentence: pay once, then use it for an unlimited number of software products that you or your company own and operate, with as many agents as you like. Launching products for clients needs a separate licence.
Questions
Can several people on the team use it?
Yes. The licence covers unlimited agents and team members working on products you own; repository access is bound to one GitHub account, which clones the repo for the team.
Which directories should a SaaS start with?
The catalog ships with a priority guide: check category fit, the current free route and public evidence before queueing anything. Your agent picks a small batch per session instead of submitting the whole list.
Does it handle B2B review sites like G2 or Capterra?
The catalog has 32 playbooks in the B2B software category. They describe the free profile route and the verification steps; paid placements are declined and recorded.
How is this different from a done-for-you service?
A service submits once, for one product, and hands you a report. LaunchRepo is a process you keep: your accounts, your agent, every future product. The comparison pages put both side by side with checked prices.
What if we launch a second product next year?
Add a second product.json in the same workspace. The setup, the connected browser, the permissions and the playbooks are already there; the licence does not count products.
Ready when your next launch is
The launch price is €99.98, once. It rises 20 % after every 20 sales; the pricing page shows the live price, what is in the repository and the licence in short.
See pricing