How long does it take to launch one app?

Roughly ten minutes to finish the package from a scraped draft, then two to three minutes per directory with autofill.

Which AI agents work with WebMCP?

Any agent that runs in a browser supporting the WebMCP proposal (document.modelContext): Chrome and Edge through the origin trial today. The WebMCP documentation has the current browser table.

Yes. The free plan covers one package and the Chrome extension.

Launch to Win for vibe coders

Launch your vibe-coded app on every startup directory.

Built it in a weekend. Launch it by Monday. AI coding tools made building cheap. Distribution is still manual. Turn each new app into a launch package and get it onto every startup directory without the form-filling grind.

Free for your first package. See pricing.

one package → 45 directories

Paste the URL, get a draft package
Let the agent finish the launch
Or click once in Chrome

The problem

Why vibe coders stop at the first few directories

You ship faster than you launch

Three apps built this month, zero listed anywhere, because the submission forms are the least fun part of the whole thing.

Your agent writes the code but not the listing

Cursor or Claude Code can build the app. They cannot log into BetaList and paste your screenshots. Until now.

Directories are where small apps get found

Nobody is searching for your app by name yet. They are searching AlternativeTo, SaaSHub and AI tool directories for what it does.

How Launch to Win fits

One package per product. Every directory.

Paste the URL, get a draft package

We scrape the site, write description variants at every length and pull in the logo and screenshots. You edit, you do not start from blank.

Let the agent finish the launch

WebMCP exposes your package as tools an in-browser AI agent can call: list packages, read one, create one. Point your agent at a directory and it fills the form from your data.

Or click once in Chrome

The extension fills any directory form, uploads included. AI maps forms it has never seen.

Repeat for the next app

Same flow, new package. Launch every experiment, keep the ones that get traction.

How it works

Three steps, repeated per product

01
Paste the URL

We scrape your site and draft the package: name, tagline, descriptions at every length, logo, screenshots, links.
02
Finish the package

Fix what the scraper missed. Add pricing, categories, keywords and alternatives. The completeness score tells you when it is ready.
03
Submit everywhere

Pick directories. Autofill each form with the Chrome extension, copy fields one by one, or hand it to your AI agent through WebMCP.

FAQ

Frequently asked questions

How long does it take to launch one app?: Roughly ten minutes to finish the package from a scraped draft, then two to three minutes per directory with autofill.
Which AI agents work with WebMCP?: Any agent that runs in a browser supporting the WebMCP proposal (document.modelContext): Chrome and Edge through the origin trial today. The WebMCP documentation has the current browser table.
Is it free to try?: Yes. The free plan covers one package and the Chrome extension.

Automated directory submission with an AI agent (WebMCP)

How automated directory submission works with WebMCP: expose your launch package to an in-browser AI agent so it can read your product details and fill directory submission forms while you review.

Read the guide

8 min read

How to launch multiple products without redoing the work every time

The playbook for makers, studios and agencies shipping several products a year: one launch package per product, one submission process, every directory.

Read the guide

Also for: indie hackers · agencies and studios · AI tool makers · micro-SaaS founders

Launch the next one in an afternoon.

Build a launch package from your product URL and submit it to 45+ directories.

Build my launch package Browse the directories

Free plan available. No credit card required.