Definition
A directory submission is the complete act of entering a product into a single directory: creating or signing in to the account, filling the form with tagline, description, category, pricing and screenshots, satisfying extra requirements such as a badge or a verification email, and pressing submit. The submission ends with an observed outcome — a thank-you screen, a dashboard label, a confirmed date or a public page.
A submission is not a listing. The listing exists when the directory publishes it; the submission is what you did to ask for one.
Why it matters for a directory launch
Every launch stalls at the same place: the twentieth form with slightly different field limits. Submissions are repetitive, but they are not identical, and the difference between “I clicked submit” and “the platform received it” is where inflated totals come from. Treating each submission as one row with its own state keeps the count honest and tells you what to do next.
How LaunchRepo handles it
LaunchRepo does not submit anything by itself. Your agent works one platform at a time from its playbook, reuses the product context file, stops at any payment or CAPTCHA and records the result with record.py — one current row per platform, replaced explicitly, never appended silently. The local dashboard groups the rows by needs-you, problems, in review, scheduled and live.
See the term in the repository
LaunchRepo is 346 directory playbooks, a product context file and a submission tracker your own agent runs. Pay €99.98 once; use it for every product you own.
See pricing