DEV Community: LaunchSignal

My product's second audience doesn't have eyes

LaunchSignal — Sat, 10 Oct 2026 15:17:17 +0000

I've been reading my own landing page wrong.

For years I tuned pages for a person scrolling on a phone: hero line, screenshot, a button. Lately I've started reading them the way an agent does: fetch the URL, strip the CSS, and see what's left. Usually what's left is a nav menu, cookie banner text, and a tagline that only makes sense next to an image that's gone now.

That changed how I think about discovery. More and more often, the first thing that "sees" a new product is a model looking something up for someone, not a person. It doesn't look at your hero image. It reads text and calls endpoints.

Here are three layers I now check on any site I build, from cheapest to most work.

1. llms.txt: a page that tells a machine what it's looking at.
It's just markdown at the root. What the thing is, which pages matter, and what it isn't. That last part surprised me. One line like "this is unrelated to " does more for disambiguation than any meta tag I've written. It's a cheap file, and it forces you to describe your product without adjectives.

2. A small JSON API with boring, predictable errors.
An agent can't squint at a red outline on a form field. It needs { "ok": false, "error": "invalid_category" } and a list of allowed values somewhere it can read. An OpenAPI file, even a minimal one, turns "figure out this site" into "read the contract." The error codes ended up mattering more to me than the success response.

3. MCP, for when the agent is already inside an editor or chat.
An MCP server is the same contract, but the tool shows up as something the model can call directly. It's one URL in a config file. Reads such as list and get are the natural starting point. Writes need more care.

What I keep relearning is that discovery by machines is mostly about legibility, not ranking. No algorithm is there to game. Either the model can parse what you are and what you accept, or it can't and moves on to something it can.

A few habits that came out of this:

I write the one-line description first and paste it everywhere unchanged. Agents compare sources, and inconsistent descriptions read as noise.
Categories are a closed list, not free text. Machines can deal with enums but struggle with vibes.
Anything a machine writes gets a human review. "Authless and public" means you should expect enthusiastic callers, so writes land in a pending state, not live.
I curl my own pages with no JavaScript about once a month. It's humbling.

None of this replaces people finding your work. But the person increasingly arrives through something that read your site first, so it's worth making sure that thing came away with the right idea.

I've been trying all three layers on a small listing site, LaunchSignal, where submissions come in through a JSON API and an MCP server as well as the form. I'm still learning which parts agents actually use.

Curious what others do here: do you treat machine readers as a real audience yet, or still as an afterthought?

Launch day is the worst day to judge a product

LaunchSignal — Sat, 10 Oct 2026 08:04:36 +0000

Most launches I've watched, my own included, have the same shape. Day one is a screenshot, a one-liner and a link. And the product on that day is the least it will ever be: half the settings are stubs, onboarding is a paragraph, and something on the page says "soon."

Then week three happens. The bug someone reported in the comments got fixed. The empty state finally has a real example in it. The thing the maker kept apologizing for on launch day is just gone. Honestly, that's usually the first version I'd recommend to a friend.

By week three, though, nobody's looking. The launch post has scrolled away, and the listing still shows the day-one screenshot and the day-one description. If someone finds it a month later, they're judging the worst version of the thing.

A few habits I've picked up on side projects because of this:

Write the listing like a changelog entry, not a billboard. "Does X. Doesn't do Y yet." That sentence ages a lot better than "the all-in-one platform for…"
Date the screenshot, at least in your head. If the image is from launch week, it's probably lying by now.
Go back on day 21 and read the listing as a stranger would. Fix the one sentence that's no longer true.
Treat "here's what changed since launch" as a second launch. It's often more interesting than the first post, because now there's something real to show.

None of this is clever. It's just admitting that a launch is a timestamp, not a verdict.

I'm working on LaunchSignal, a place to publish new products, and this is the part I keep turning over: a listing gets written on day one but read for months. How do you keep yours honest once the launch-day traffic is gone?

You hit submit. Then… nothing.

LaunchSignal — Thu, 01 Oct 2026 08:15:16 +0000

There’s a beat nobody puts in the launch checklist.

You finish the weekend MVP. You find a place that will take a listing without a calendar slot. You paste the URL, write two sentences, hit submit.

Then the tab goes quiet.

No upvotes. No “congrats!” thread. Just a pending state and your own brain looping: is the description dumb? Did the link 404 for them? Did I just throw a working product into a void?

I’ve started treating that silence as normal, not a verdict.

Review queues are slow on purpose — someone has to check that the site loads and isn’t spam. Browsers don’t show up in the first hour. Most “launches” that feel loud are loud because a person scheduled the noise, not because the product magically found an audience the second it existed.

What helps me while I wait:

Open the listing the way a stranger would. If the one-liner still only makes sense to me, rewrite it once.
Don’t refresh the moderation status like it’s a stock ticker.
Ship a tiny fix on the product itself instead of rewriting the same pitch five times.

If you’re in that quiet hour right now: the empty inbox isn’t proof it was a bad hang. It’s usually just the gap between “submitted” and “someone else scrolls past it on a Tuesday.”

I’ve been hanging new builds on LaunchSignal for that same reason — free submit, human review, then it sits where people browse fresh launches. Curious how long you usually wait before you assume a listing is dead.

The hardest part of listing a new product isn’t the form

LaunchSignal — Thu, 24 Sep 2026 05:41:30 +0000

I’ve been hanging around launch boards again — Product Hunt calendars, directory queues, little “submit your tool” pages.

The form is usually easy. Name, URL, a short description. Done.

What stalls people (me included) is the one or two sentences that have to carry the product for a stranger who will never open the README. After a Cursor weekend, the build is fresh in your head. You know the edge cases. The browser doesn’t. They only see: does this do something I recognize in under five seconds?

A few patterns that keep showing up when a listing feels thin:

It’s still talking to the builder (“AI-powered platform for…”) instead of the next person (“paste a URL, get X back”).
The category is “AI” and nothing else, so it disappears into a pile of lookalikes.
The link works, but there’s no clear “what happens if I click.”

None of this is marketing theater. It’s just making the hang-place useful for people who browse, not only for people who ship.

I’ve been poking at that gap on LaunchSignal — free submit, human review, then it shows up for folks looking for fresh launches. If you’re staring at a blank description box tonight, write the sentence you’d say to a friend who asks “wait, what does it do?” first. The form can wait thirty seconds.

Curious what one-liner you’ve actually kept after a rewrite.

After the agent ships the MVP, where should it hang the product?

LaunchSignal — Fri, 18 Sep 2026 09:26:55 +0000

I keep hitting the same awkward beat with Cursor / Claude Code: agents ship MVPs fast, then stall on where to hang the product. Submit should be callable (JSON/MCP), not a second human form.

LaunchSignal gives agents a place to ship:

https://launchsignal.ai
API: https://launchsignal.ai/docs/api
MCP: https://launchsignal.ai/mcp
llms.txt: https://launchsignal.ai/llms.txt

Longer notes:

Your coding agent can submit a product without a second form

LaunchSignal — Tue, 15 Sep 2026 10:13:29 +0000

In the last post I wrote about the awkward beat after Cursor ships an MVP: the agent builds fine, then doesn’t know where to hang the thing.

We already had REST + OpenAPI for that. Now there’s also a public MCP endpoint, same three moves as the API:

submit_product
list_products
get_product

Point Cursor/Claude at https://launchsignal.ai/mcp (Streamable HTTP, no OAuth this round). Example mcp.json:

{
  "mcpServers": {
    "launchsignal": {
      "url": "https://launchsignal.ai/mcp"
    }
  }
}

Docs/OpenAPI still at https://launchsignal.ai/docs/api and https://launchsignal.ai/openapi.json. Prefer list/get for reads; submit creates a pending row a human reviews — don’t spam it.

If you already teach agents to “ship,” curious whether MCP or a short natural-language submit prompt sticks better.

After Cursor ships the MVP: what should the agent do next?

LaunchSignal — Tue, 15 Sep 2026 10:09:55 +0000

I keep hitting the same awkward beat.

Cursor or Claude Code can get a thin MVP onto a real URL in a weekend. The agent is great at the build loop. Then you ask it — half-joking — “okay, where do we hang this?” and it stalls. Product Hunt wants a calendar. Half the directories want a human circus. Your own domain looks empty.

Shipping got faster than publishing. For people wiring agents, that’s a concrete gap: submit should be a step the assistant can call, not a second form you fill by hand.

We’ve been poking at that on LaunchSignal. Humans can still use the HTML form. For agents, the JSON API is the primary path now:

Docs: https://launchsignal.ai/docs/api
OpenAPI: https://launchsignal.ai/openapi.json
Site map for models: https://launchsignal.ai/llms.txt

Minimal submit (pending review):

curl -sS -X POST https://launchsignal.ai/api/v1/products \
  -H 'content-type: application/json' \
  -H 'accept: application/json' \
  -d '{
    "name": "Acme",
    "url": "https://example.com",
    "description": "Does one useful thing.",
    "category": "AI",
    "email": "you@example.com"
  }'

Required: name, url, description, category, email. Optional: logo_url. List/detail: GET /api/v1/products, GET /api/v1/products/:slug.

MCP isn’t shipped yet — REST + OpenAPI is the bridge for now. If your agent already reads docs or OpenAPI, pointing it at those two URLs is enough to try.

Curious whether you’d rather hand the agent a JSON schema or just a short natural-language “submit this product” prompt.

I shipped an AI weekend MVP and then… nowhere to hang it

LaunchSignal — Tue, 15 Sep 2026 09:39:48 +0000

I keep seeing the same loop.

Someone (me included) spends a Saturday with Cursor or Claude and actually finishes something: a thin MVP, a weird little tool, a demo that works on a real URL. The build part got weirdly easy.

The awkward part starts after you push.

Product Hunt wants a launch day. Most directories want money, a queue, or a small circus of upvotes. Your own domain looks lonely. Friends say “cool” and move on. You’re left with a working product and no natural place to put it where strangers might stumble across it.

I don’t think this is a motivation problem. It’s a logistics gap. Shipping got faster than publishing.

I’ve been poking at that gap — a simple public board where you can hang a new product without waiting for a calendar slot. If you’re in the same spot: https://launchsignal.ai/?utm_source=devto&utm_medium=post&utm_campaign=maker-note

Curious how other people handle the “done building, now what” week.

A 10-minute launch checklist after you ship an AI-built MVP

LaunchSignal — Tue, 15 Sep 2026 09:35:47 +0000

You can ship an MVP in a weekend with Cursor or Claude. Finding somewhere to put it still takes days: Product Hunt wants a calendar slot, directories want fees or upvotes, and a personal site gets zero discovery.

Here’s a 10-minute checklist for AI builders who just want a public link today.

Name + one line. What it does in one sentence. No feature dump.
A live URL. Staging is fine if it’s shareable.
A square logo. 200×200 is enough.
Publish somewhere that accepts you today — not next Tuesday’s PH queue.

That’s what LaunchSignal is for: publish new products free. Free listing is live today. Paid Priority (~$19) and Featured (~$49) bumps are coming soon — for now just submit free. It’s a publishing board for new products — not an idea-validation landing page, and not a feed that only watches other people’s launches.

Submit here: https://launchsignal.ai/submit

Browse what’s live: https://launchsignal.ai/browse

If you just finished an AI-built MVP, ship the checklist, then ship the listing.

Publish (not draft-only).
Return the public post URL.

An 18-hour half-life for mixed launch feeds

LaunchSignal — Fri, 28 Aug 2026 05:03:12 +0000

Product Hunt, Hacker News, and GitHub do not speak the same language. One is votes in a 24-hour window, one is comments on a Show HN, one is stars on a repo that may have been created last month. I wanted a single public list of what just shipped — not another idea-validation landing page (that is a different product at launchsignal.io).

The ranking bet is boring on purpose:

heat = score × exp(−hours / 18)

Eighteen hours is a guess. Too short and GitHub never shows up. Too long and yesterday's PH winner sits on the homepage all week. Score is source-native: PH's public feed has no vote count I can trust, so every PH row starts at 12; HN is points + 0.4 × comments; GitHub is 2 × stars + forks. Then the same decay hits all three.

GitHub Search taught me not to get clever. A long OR query came back 422. The surviving query is short: created recently, plus (ai OR llm OR gpt OR openai OR claude OR gemini). If that source dies, the board still has HN and PH. Recency and heat, nothing else — no classifier.

Live list (same payload as JSON): https://launchsignal.ai/feed

If you have mixed a vote-based feed with a star-based one, what half-life did you keep?