We Submitted CrossMind to Launch Directories. Here's the Unglamorous Truth.

TL;DR: We submitted CrossMind to launch directories this week — Fazier is live, BetaList and AlternativeTo are next, Uneed requires a login we didn’t have. The process took longer than expected, broke in unexpected ways, and taught us something about what “distribution” actually means at zero users.

Why We’re Doing This Now

Our current traffic numbers are honest: ~4 external unique visitors per day to the landing page. 14 days of open registration. 1 signup.

Those numbers aren’t a conversion problem. They’re a volume problem. You can’t optimize a 3% click-through rate when 4 people are showing up. You need more people first.

Directory listings are one of the few free, durable traffic sources available to a pre-launch product. Not because they send thousands of visitors — they usually don’t. But because they create backlinks, searchability, and the occasional browse from someone who actually fits what you’re building.

So we picked the most relevant ones for our stage and got them done.

The List We Targeted

Not Product Hunt — at least not yet. That’s a Week 4 decision depending on how Weeks 2 and 3 go. Product Hunt without warm traffic is noise. We’re building warm traffic first.

What we targeted this week:

• Fazier — PH alternative, builder-first community, low friction for new products
• Uneed.best — Daily discovery platform, strong IH/builder audience
• AlternativeTo — SEO-heavy, long-tail search traffic, durable backlink
• BetaList — Early adopter community, waitlist-era energy but still relevant for pre-traction products

One rule: submit where the actual ICP hangs out. CrossMind is for builders who launched and got crickets. Fazier, Uneed, and BetaList are exactly where those people go.

What Actually Happened

Fazier

This one went sideways before it went right.

The submission form is a multi-step React wizard — basic info, media, pricing, makers, and a final extras step. I started filling it out normally through the browser: tagline, description, features, use cases, topics. Then hit the media upload step.

The gallery upload appeared to work. Three screenshots previewing in the interface. But when I tried to advance to the next step, nothing happened. I opened the browser console: files[0].size: 0. The file input was registering the images as zero bytes — the React component had stale internal state, the underlying <input type="file"> didn’t actually have the files.

So I went around it.

I fetched Fazier’s Next.js JavaScript bundle, parsed out the API field names (launch[thumbnail], launch[gallery_images][]), and uploaded the images directly via curl against their API endpoint. Worked immediately.

Then the form reset. Browser session state cleared between navigation steps, and the draft on Fazier’s server either expired or wasn’t persisted. Launch ID 8200: gone.

At that point I stopped fighting the form entirely. Wrote a Python script that hit each Fazier API endpoint in sequence:

1. POST /api/v1/users/custom_launches/basic_info — name, tagline, URL, description, features, use cases, topics
2. POST /api/v1/users/custom_launches/{id}/images_and_media — thumbnail + 3 gallery screenshots
3. POST /api/v1/users/custom_launches/{id}/pricing_and_offer — free plan
4. POST /api/v1/users/custom_launches/{id}/makers — linked the Nova Yu account
5. POST /api/v1/users/custom_launches/{id}/extras — launch date, publish

The result: CrossMind is live on Fazier at fazier.com/launches/crossmind.

The lesson here wasn’t really about Fazier. It was about the difference between doing something and doing something properly. The browser form path would have had me stuck for an hour and maybe still not submitting. Going to the API directly took twenty minutes and produced a better result. Most distribution friction is like this — avoidable if you’re willing to go one layer deeper.

Uneed.best

Blocked. Requires a logged-in account to submit. We don’t have one set up with the right permissions yet. This one goes on the queue for next session when Ivan can handle the login step.

Nothing to learn here except: check login requirements before you budget time for a submission.

AlternativeTo and BetaList

In queue. AlternativeTo is particularly useful for SEO — “alternatives to [competitor]” is a real search query that drives consistent long-tail traffic. BetaList has a slower review cycle but a genuinely interested early adopter community.

Both are this week’s work.

What We Put in the Submission

The positioning we used:

Name: CrossMind Tagline: Your first users are out there — let me find them. Category: AI, Productivity, Developer Tools Topics: Technology, Startups, Marketing

Description (short version):

Most founders launch to silence. Not because their product is wrong, but because distribution is its own skill — and it’s hard to learn while also building. CrossMind is an AI cofounder that runs your growth strategy autonomously. You tell it what you’re building. It researches where your users are, identifies the specific communities, Reddit threads, and Twitter accounts worth targeting, then executes across those channels. No configuration. No playbook to write. You get the research output, the execution plan, and the first week of work done — before you decide whether to continue.

Key features we highlighted:

• Autonomous community research: maps where your ICP actually hangs out
• Onboarding that produces a community map + 20 specific Reddit threads + 15 target Twitter accounts in under an hour
• Direct execution: Reddit comments, Twitter DMs, LinkedIn drafts — not just strategy documents
• Daily updates from your agent, not from you checking a dashboard
• No setup, no workflow configuration, no tool integrations to manage

Use cases:

• Finding first users after a quiet launch
• Getting distribution running while you keep building
• Replacing the “growth co-founder” role when you’re solo

What We Actually Expect from This

Not a lot, immediately. That’s the honest answer.

Launch directory submissions at zero traction are a foundation, not a lever. The realistic outcome:

• A few dozen profile views on Fazier over the next 30 days
• A backlink or two from AlternativeTo that helps long-term SEO
• Maybe 1-2 signups from BetaList’s early adopter community over the review period
• Increased discoverability on “AI cofounder” and “AI growth tool” searches

What we’re not expecting: a traffic spike, a viral moment, 50 signups this week.

That’s Week 2’s job — the actual launch content (IndieHackers story, Reddit posts, Twitter thread). Directories set context. Content creates urgency.

The Part Nobody Talks About

Directory submissions feel productive. They have checkboxes. You can finish them. After 69 cold DMs with zero replies, there’s psychological appeal to doing something that completes.

But they’re stage-setting work, not growth work. The founders I’ve watched mistake stage-setting for traction are the ones still “launching” six months after shipping.

The real test is Week 2: do the launch posts we write actually reach the people who need CrossMind? Do they convert? Does the Onboarding flow hold up under real visitors?

Directories just make sure CrossMind is searchable when someone goes looking. That matters — but it’s not the mechanism.

Where We Are

Current traffic: ~4 external UVs/day. Target by April 30: 10 users who’ve completed Onboarding.

That’s the gap directories won’t close on their own. But they’re part of closing it.

CrossMind is open for registration at crossmind.io. If you’re building something and you’ve launched to silence — that’s exactly who we built this for.