Indiehunt

Launch your product on Indiehunt to get discovered by indies

Visit Website
October 2, 2026 I write launch tags from the buyer job, not from my feature list

I used to tag weekly listings like a product sheet. "AI," "automation," "analytics," "API," whatever feature sounded impressive that Tuesday. The tags matched my roadmap. They did not match how a stranger searches when they have a problem at 11pm.

Hunters scanning a weekly board do not think in my feature language. They think in jobs. "Need a cleaner way to chase unpaid invoices." "Want a weekly digest of competitor pricing." "Tired of pasting the same reply into every launch comment." If my tags say "AI + productivity" and their brain says "invoice follow-ups," we never meet — even if the tool does exactly that job under the hood.

So before I lock categories on IndieHunt, I write the job in plain words first. One sentence. No model names. No "platform." Then I pick the two tags that a buyer would actually filter for if they already knew the job. Features become proof in the body copy. Tags become the aisle they walk down.

Example from a billing-helper launch. Old tags: AI, SaaS, automation. New tags: finance tools, B2B, productivity — with a title that named the invoice job. Same product. Different people opened the page. The comment questions shifted from "which model?" to "does it sync with Stripe?" That is the signal I wanted.

I still skim Product Hunt Alternatives when I am deciding which weekly room fits the job aisle. Some boards are feature-tag theaters. Others are quieter and closer to how buyers already shop. Pick the room whose tags match the job language, then write yours the same way.

If your tags describe what you built instead of what someone is trying to finish today, rewrite them before you submit.

What job sentence would a stranger type — and do your tags answer that, or only your feature pride?

Comment

October 2, 2026 My weekly launch page gets one primary CTA — I demote the other two to the footer

Worst weekly launch page I shipped had three buttons fighting above the fold. Start free. Book a demo. Join Discord. Looked "complete." Conversion was mush. People did not know what winning looked like that week.

Some clicked Discord and vanished into a quiet channel. Some booked a demo for a product that was not ready for a sales call. Signups arrived cold with an empty dashboard and no idea what to click next. Three CTAs felt generous. They were just me refusing to choose.

I force one primary CTA for the cohort week now. If the product needs a guided first run, the button is Book a 15-min setup. If self-serve activation is solid, it is Start free with one clear first action named under it. Discord lives in the footer as optional — never competing with the main ask.

Same discipline on the IndieHunt listing copy. Mid-week hunters scan. Three asks read like you do not trust your own funnel. One ask reads like you know the next step. I write the listing CTA to match the landing page CTA. If those disagree, the visitor feels the wobble even if they cannot name it.

Where founders get stuck is ego. Demo feels enterprise. Discord feels community. Signup feels product-led. So they ship all three and hope. Hope is not a CTA. Pick the outcome you can support for seven days — then demote the other two without apology.

When I am sequencing boards I still glance at Best Launch Platforms, but the page that greets traffic from any of them needs one job. Pick the job before you pick the board. Fix the button before you rewrite the hero again.

What is your one primary CTA this week — and which two buttons did you quietly bury in the footer?

Comment

September 30, 2026 I stopped writing SaaS comparison pages like brochures — one competitor, honest rows, one CTA

Most "vs" pages I used to ship were homepage copy with a table glued on. Every row green for me. Competitor looking thin on purpose. Buyers bounced. Google did not care either.

What changed it for me was forcing one rule before any HTML: pick ONE competitor people already name in calls or Reddit threads. Not the biggest brand. The one with real overlap on buyer job and price band. Everything else waits.

Then I fill a one-page brief — who each product is for in one sentence, 6–10 decision criteria as outcomes not feature checkboxes, one honest win for them, one weakness I will own, pricing snapshot with a date, switching notes. If I cannot fill the brief I am not ready to publish. I am ready to talk to five more buyers.

The page itself stays boring on purpose. TL;DR who should pick whom. Choose-X / Choose-Y bullets. Decision matrix that leaves two or three rows to the other side. Dated pricing. Migration notes. FAQ with the awkward sales questions. Single CTA. Not trial plus demo plus Discord fighting each other.

I learned this the same way I learned launch pages on IndieHunt — weekly cohorts punish fuzzy CTAs and punish brochure tone. A comparison page is mid-funnel. People are already shopping. They want contrast, not another pitch.

Trust rules that actually matter: date the competitor facts, never win every row, no trash-talk ("their UI is dated" is useless; "they optimize for agencies, we optimize for freelancers who hate bookkeeping" is useful), update after price changes.

I wrote the longer breakdown on Aura++ Studio with the 7–14 day solo-founder checklist and a fictional bookkeeping example if you want the full skeleton.

If you already have a vs page live, does it leave any rows to the other side on purpose — or does it still read like a brochure with a table?

Comment

September 28, 2026 I stopped hunting for AI tags and pick the board whose hunters already buy tools like mine

For a while my launch filter was dumb. Search "AI." Sort by traffic. Submit. Hope the tag did the selling.

It did not. AI tags are crowded, loud, and full of people browsing demos they will never pay for. I wasted a few Mondays ranking fine next to chat wrappers while the buyers I actually wanted were somewhere quieter, looking for the category my tool sits in — reporting, billing, ops, whatever the job is when you strip the model name off.

Now I pick boards by hunter behavior, not by the word in the category chip.

Before I put something on IndieHunt, I scroll last month's winners. Not the titles. The commenters. Are they asking about pricing and workflows, or are they arguing about which model is cooler? Are the upvoters other founders with products in adjacent categories, or drive-by badge collectors? If the thread energy is "show me the invoice," I belong there. If it is "which LLM," I probably do not — even if my product uses one under the hood.

Same screen when I browse Product Hunt Alternatives. I am not hunting the biggest AI room. I am hunting the room where people already buy tools that look like mine. A smaller weekly board with paying operators beats a huge AI shelf where everyone is demo-curious and wallet-closed.

I still mention the model if someone asks. I just refuse to let the tag choose the audience for me. The product is the job. The model is an implementation detail. Launch rooms that forget that will train you to market the wrong thing.

Last time you picked a board, did you follow the AI tag — or did you follow where people like your buyers already hang out?

Comment

September 28, 2026 I keep a one-page reply kit for the weekly cohort instead of improvising every comment

By Wednesday of a weekly launch I used to sound different in every thread. Tired. Sloppy. Sometimes contradictory on pricing because I was typing from memory at 11pm. Strangers can feel that. So can you, when you re-read your own replies on Friday and wince.

I fixed it with something boring: a one-page reply kit I open before I open the comment box.

It is not a script. Scripts sound like support bots. It is four blocks I refresh the Sunday before a Monday cohort on IndieHunt. One sentence on who it is for. One sentence on who it is not for. The honest pricing line, including what is free. Three short answers to the questions I already know are coming — integrations, data, refunds, whatever broke last launch. Plus one link I am allowed to send if someone asks for proof, not before.

When a comment lands, I still write like a person. I just stop inventing the product from scratch every time. If three people ask the same thing, I update the kit that night instead of "remembering" to fix the landing page later and forgetting.

I started doing this after a cohort where I told two different founders two different free-tier limits in the same afternoon. Both were polite. Both bounced. That was on me, not the board.

When I compare weekly rooms for Best Launch Platforms, presence is the whole product. Seven days of improvisation burns trust. Seven days with a living one-pager keeps your voice consistent without turning you into a FAQ page.

The kit lives in a plain note. No Notion temple. If I cannot find it in five seconds, it is useless.

Do you already keep canned answers for launch week, or are you still winging every reply from a cold brain?

5 Comments

  1. 1
    This is such a boring-but-correct fix. The “two different free-tier limits in one afternoon” story is painfully familiar. We hit the same pattern on paid course/cohort Discords: week one, the same five questions land in #general (where’s the recording, how do roles work, refund window, which channel for X). If staff improvises from memory at 11pm, trust erodes fast — same as your launch-week replies. What helped on our side: - a living FAQ surface members can hit themselves (slash /faq, not a buried pin) - refresh it whenever the same question shows up 3× (your “update the kit that night” rule) - /ask → private staff thread for the ones that actually need a human, so #general doesn’t become the FAQ page I wrapped that as ServerDesk for paid course servers ($19/mo) — https://serverdesk-landing.onrender.com — but the one-pager habit is the real win either way. Do you keep the kit Discord-side too, or only for public launch comments? — Carol
    1. 1
      Yeah, I’d keep a Discord version too, but split it a little from the public kit. The repeated questions are mostly the same, but the answers can point to the exact channel or command instead of a launch CTA. I like your 3× rule — I’d probably add a tiny “last updated” line too, so I know I’m not trusting an old answer. The /ask → private thread part is smart; otherwise the FAQ just becomes another room people ignore.
      1. 1
        Nice call on the last-updated line — that’s the piece that keeps the kit trustworthy when the cohort rules change mid-week. Discord vs public split is exactly how I’d run it too: same questions, channel/command answers inside, CTA only outside.
        1. 1
          Yep, that split keeps the public thread from turning into support. I’d add one rule: if the same Discord question shows up twice in a launch thread, it goes back into the public kit too. Otherwise the useful answer gets trapped in one room.
          1. 1
            Love that promotion rule — twice in Discord and it graduates to the public kit. Keeps the useful answer from dying in one room and stops the next launch from rediscovering the same FAQ.
September 27, 2026 For B2B tools I pick a niche weekly board over another general daily slot

I used to shove every B2B tool onto the loudest general daily board I could find. Felt like "real distribution." Felt serious. Then I watched buyers bounce because the room was full of consumer apps, AI toys, and meme launches. Wrong crowd. Wrong questions. Wrong clock.

B2B buyers do not always decide in a 24-hour upvote fight. They need a week to poke the demo, forward it to a teammate, come back with a pricing question. A niche weekly board matches that pace better than another general daily sprint.

That is why I put serious B2B launches on IndieHunt instead of stacking them next to twelve consumer cards. Indie hackers and operators browse with more patience. The homepage lasts Monday to Monday. You get time to answer "does this integrate with X" without the whole story dying at dinner.

I still use general daily boards. Aura++ is great when the product is simple and the ask is try-it-today. Different job. Daily for a clear consumer loop. Weekly niche when the sale needs a conversation.

What went wrong before was treating every board as interchangeable traffic. They are not. A general daily can give you noise that looks like traction. A niche weekly can give you three boring comments that turn into a call. I will take the call.

If your tool needs a teammate to say yes, ask yourself before you submit: is this room built for impulse votes, or for people who actually buy software for work?

Where do you put B2B launches first — weekly niche, or another general daily because it feels bigger?

Comment

September 27, 2026 On a Monday cohort, day 2–4 replies matter more than the day-1 spike

Monday feels like the whole launch. Graph goes up. Inbox pings. You screenshot it. Then Tuesday comes and you half-disappear because the "event" already happened.

That habit makes sense on a 24-hour board. On a Monday-to-Monday weekly board it is how you waste the good part of the week.

I run IndieHunt. Products sit on the homepage for seven days. Day 1 is mostly friends, Discord pings, and people who already knew you were shipping. Fine. Useful even. But the strangers show up later. Day 2, day 3, day 4. They found you while browsing, not because you DMed them. Their questions are colder. Pricing. Who it is for. What breaks. That is the cohort that tells you if the page works without a hype machine behind it.

So my pacing rule is simple. Protect day 1 for fast replies. Protect days 2–4 even harder. That is when I am still at the keyboard after dinner. That is when I fix a fuzzy screenshot if three people misread it. I do not treat Wednesday like cooldown. I treat it like the real interview.

I see the same split when I compare board types for Best Launch Platforms.

Daily rooms reward a sprint morning. Weekly rooms reward a week of presence. If you only show up for the spike, you paid for seven days and used one.

What I stopped doing: vanishing after the Monday screenshot, then blaming the board on Friday when nobody "engaged."

If your product is on a Monday cohort right now, are you still answering on day 3 — or did the spike already steal your attention?

2 Comments

  1. 1
    Still me for the day-3 questions, at least for now. The kit handles repeats, but I want to see the first few cold questions myself — that’s usually where the listing or docs are lying. Once I see the same blocker twice, I fix the page before handing it off.
  2. 1
    This maps weirdly well to paid course Discords too. Day 1 is welcomes and “just joined” energy. Days 2–4 are when the colder questions show up — where’s module 2, how do refunds work, why can’t I see the channel — and that’s exactly when founders half-disappear after the launch screenshot. Protecting mid-week presence helped us more than fancy bots. Lightweight ops that held up: - clear welcome so day-1 noise doesn’t bury the real asks - a pullable FAQ for the repeats - a private staff path (/ask → thread) so day-3 blockers don’t sit unread in #general while someone waits on a refund decision Built that combo as ServerDesk for course/cohort servers ($19/mo): https://serverdesk-landing.onrender.com — but the pacing rule is the bigger lesson: Wednesday is still the interview. Are you still answering IndieHunt day-3 questions yourself, or do you hand any of that to a kit/mod? — Carol
September 24, 2026 I stopped writing “hunters will love this” and just named the job the product does

My old taglines were written for imaginary applause. Stuff like “the smarter way founders launch” or “hunters will love this workflow.” It sounded launch-y. It explained almost nothing. People scrolled past because there was no job in the sentence — no who, no task, no outcome.

I rewrote one listing to the dull version: who it’s for and what job it finishes. Something closer to “weekly launch board for indie products that need a full week, not one frantic day.” Ugly. Clear. Comments shifted from polite emoji to “oh, so it’s not another daily PH clone.” That was the win.

PH-style taglines are short — often capped around 60 characters on the big daily boards — so every word has to earn its spot. Weekly boards give a little more room in the body, but the card people see first still has to parse in a couple of seconds. Padding for hunters (“community-loved,” “made for makers,” “AI-powered discovery”) burns those seconds. Naming the job keeps them.

I catch myself slipping. When I’m tired I still draft a line that flatters the audience instead of helping them. Then I do the stranger test: say the tagline out loud without the product name. If a friend can’t repeat the job, it isn’t ready. On IndieHunt I’ve started nudging founders toward that same edit before they obsess over gallery polish. Pretty screenshots on a mushy one-liner still bounce.

Rewrite pattern that works for me is boring on purpose. Actor + job + constraint. “Solo founders scheduling one weekly launch without stacking five boards.” No “love,” no “delight.”

If you want a wider map of where that line will appear, Best Launch Platforms is where I keep cadence notes so I know whether the tagline has one day or seven days to be misunderstood.

What’s the dullest accurate tagline you’ve written for your product — the one that finally made strangers stop asking what it is?

Comment

September 24, 2026 Soft launching Thursday taught me when the weekly board actually reads you

I used to treat every launch day like it needed a long writeup ready at dawn. Essay in the maker comment, polished gallery, thread drafted. Then I’d wonder why a Thursday soft drop on a weekly board felt quieter than the Monday I spent writing about it.

The board wasn’t broken. My timing of effort was.

On a weekly board the listing sits for the whole ISO week. Votes and comments trickle across days and timezones instead of dying at midnight Pacific like a classic daily race. That changes when people actually read you. Early week a lot of hunters are still browsing. Mid-week they’re more likely to open the page, try the product, and leave a note that isn’t just “congrats.” A soft Thursday drop with a clean one-liner and a working free path can collect useful confusion while you’re still awake to fix it. Monday is when I write the longer post — after I’ve heard what they misunderstood.

I run IndieHunt as that weekly room for indie products, so I’ve watched this from both sides. Soft first: ship the listing, reply fast, rewrite the blurb when two people ask the same wrong question. Loud second: once the sentence survives, publish the founder writeup and point warm eyes back at the same page. Doing the essay first meant I was explaining a version the board was about to invalidate.

Soft launch week, done right, is copy QA with strangers. One weekly home is enough for that week. You don’t need five directories open in tabs.

I still like a strong Monday post for distribution. I just stopped using Monday as day zero for the board itself. Thursday soft → weekend fixes → Monday story has been less stressful and more honest.

On Best Launch Platforms I keep a note: weekly = soft mid-week, write after signal.

If you use weekly boards, do you soft drop mid-week and write later, or do you still try to make day one carry the essay and the listing at once?

Comment

September 23, 2026 I used to treat the weekly board like Product Hunt Lite — wrong crowd, wrong ask

Honest confession: for a while I treated every launch board as a smaller Product Hunt. Same assets. Same “hunt us at midnight” energy. Same ask for upvotes in the first hour. On a weekly indie board that framing just… misfires.

Product Hunt is a day zero spike culture. Velocity in the first hours matters a lot. A weekly room like IndieHunt runs Monday to Monday. You’ve got days, not a panic window. The people browsing are often other builders and early adopters who will try a tool if the problem is clear — not a mass consumer feed hunting for the shiny badge.

When I showed up with PH muscle memory I asked for the wrong thing. I pushed friends to vote early and then went quiet. The listing looked artificially hot then dead. Worse, my maker comments sounded like I was chasing rank instead of talking to the few people who actually left questions.

What changed: I treat the week like a soft office hours. Answer slowly and specifically. Share one update mid week if something shipped. Don’t spam the same screenshot on day one across every Product Hunt Alternatives style board as if they’re clones. IndieHunt’s job for me is seven days of homepage presence plus a chance at lasting link value — not a miniature Product of the Day cosplay.

I still launch on PH when the product is ready for that crowd. I just stopped pretending the weekly indie board wants the same script. Different room, different ask, different patience.

Have you caught yourself copying a Product Hunt playbook onto a weekly board, and what broke when you did?

Comment

About

We built IndieHunt because launching as an indie maker is still too noisy and unfair. Most platforms favor already-established products with large audiences, making it hard for early-stage builders to get visibility.