Submitting to directories suck and it's a full-time effort 🥲

I recently built a bunch of mini products and from experience I know that submitting to directories improve backlinks, visibility etc. Though some of them are paid, it's so painful to create accounts in each and every one of them for each one of my products (mostly vibe coded).

But, with that said, I also understand the importance of it. Every good product I have worked with (I have 12 years of experience working with various startups), keep launching and keep adding to all the directories. One or some of them click and it works well.

Today, with all the AI, automations around, I just started using claude code + my browser to let it do these by itself. Not sure how efficient this will be. But I'm open to ideas from others in the subreddit on this. Especially launching consistently, submitting to directories etc.

reddit.com
u/thehungryindian — 19 hours ago

Building products has never been easier. Launching them again and again still is.

Launching a product has never been easier to attempt and harder to actually pull off. There are more places to launch than ever, more noise to cut through, and more products competing for the same five minutes of attention.

The builders who actually play this game right don't care about landing #1 on launch day. They care about launching again. And again. And again.

I've watched the opposite happen to myself the last six months. Coding got so easy that I started building constantly, and somewhere in there I stopped launching almost anything. Launching is step one. Not just on Product Hunt, everywhere. It's however you get a product in front of people, get feedback, and find out if it sticks.

The only test that matters is whether it gets any traction, any revenue at all. That's what separates a real vibe-coded app from a folder full of finished ones nobody ever saw, mine included.

On that note, i'm going to keep launching more often in multiple places to get more out of the product, solutions I build.

reddit.com
u/thehungryindian — 2 days ago

Made a tool that roasts how few places you've actually launched your app. Looking for testers to break it.

I keep seeing the same pattern with vibecoded apps, mine included. You ship it, post once on Product Hunt or Show HN, and call it launched. There are 60 to 80 other places. Most builders don't know they exist. And even if they do (which we all come across in X threads and LinkedIn posts) don't have the submission requirements on hand or the time to do it.

So I built VibeLaunched. Paste your app's URL and it scans for all the places you launched so far and gives you the places where you still haven't. A kit of each destination that is cureated for that direcotry or platform.

A kit = curated prompt with exact requirements from the platform so you can literally just paste it in your existing vibecoding agent.

Next up, I'm wiring up browser use so that if not all of the listings (which might be too much), some of the destinations can be run in the bg with review cycles and iterations. It will keep launching for you so you can keep building what you love ❤️

Help me test this. Specifically:

  • Run it against your own app. Tell me where a venue requirement is wrong or out of date. That's the part I care most about getting right.
  • Tell me if a launch pack actually got you through a real submission, or just spat out generic copy.
  • Tell me what's missing for your category. Indie game, MCP server, Chrome extension, whatever doesn't fit the mold.

First 3 kits are free for anyone who tries it. Find a broken requirement and I'll fix it the same day and credit you in the commit 🙏

reddit.com
u/thehungryindian — 3 days ago

The average vibe-coded app launches in 3.6 of the 80 places you could post it. I built a tracker to find out why.

I build small apps constantly. Ship one, forget about it, start the next one. A few months ago I noticed the pattern in my own habits: deploy something, post it in exactly one place, never touch distribution again.

So I built a tracker. It checks a product's footprint across the places builders actually launch: Product Hunt, Hacker News, Indie Hackers, directory sites, the usual list. There are 80 of them worth checking.

The number that got me: across every app on the tracker, the average has launched in 3.6 of those 80.

Most of that gap is about format. Every one of those 80 places wants something slightly different: a tagline capped at 60 characters here, a 1270x760 image there, a form with a founder-story field nobody warns you about until you hit it. Multiply that by 80 and the real bottleneck shows up. Most of the work in launching somewhere new is producing the right-shaped asset for that one venue, not finding the will to post again.

I ended up building the tool I wished existed while doing this for my own apps. Paste a URL, it checks the live page against the real requirements for each venue, and writes the prompts you feed into whatever coding agent you already use, Claude Code, Cursor, whatever's on your machine. It rechecks your footprint after you launch somewhere new, so the number actually moves.

Genuinely curious whether other people here see the same drop-off after the first post, or if I've just been unusually bad at this part.

vibelaunched.com, if anyone wants to poke at the tracker itself.

u/thehungryindian — 3 days ago
▲ 0 r/mcp

Your agent shouldn't burn tokens to learn someone signed up

Hot take: if your agent polls for product events on a heartbeat, you're doing it wrong.

I open-sourced Cairo. MCP-native event tracking where the agent is the consumer, not a dashboard.

You say "notify me on signup." It calls setup_product, returns a write key, and after that alerts fire through a thin webhook relay. Zero LLM turns on the hot path. Cairo never talks to Slack/Discord. Your gateway does.

Self-host. Node + Postgres.

https://github.com/Ani-HQ/cairo

npx -y u/ani-hq/cairo-mcp

Be honest: are you still waking an LLM to check if anything happened?

u/thehungryindian — 16 days ago

I built a map of India where you can tap your seat and see your MP’s numbers + late central projects (sourced from MoSPI / PRS)

I got tired of digging through government portals for basic facts. MPLADS utilisation, attendance, questions, and which big projects near me are years late.

So I built Beacon: https://trybeacon.in

What it does:

• Type a PIN / use location / tap the map - your Lok Sabha constituency

• MP report card with national ranks (MPLADS + PRS)

• Project board of central infra projects (₹150cr+) shown like open tickets: how late, how much over budget

• A state heatmap for late / open projects and ₹ at stake

Rules I forced on myself:

• Every number links back to the source

• Missing data stays “Not published” - no guessing

• No verdicts, no party framing - just the records

Would love feedback from other builders:

  1. Is the map the right hero, or should the board come first?

  2. What would make you actually share this with friends/family?

Happy to answer anything about the stack / data pipeline.

u/thehungryindian — 19 days ago