I launched a cron monitor on Product Hunt and got zero trials. Here's what I built and what I'm changing.

Zero signups from Product Hunt on an infra CLI is closer to normal than it feels. PH converts for things people can evaluate from a screenshot. Nobody can evaluate a cron monitor from a screenshot, and the people who need one aren't browsing launch pages. They come looking for you at 3am on the day a job silently stopped running.

But I think the bigger thing is sitting in your own description.

The feature you led with is "reads your crontab, creates a monitor per job and wraps each line." That is genuinely clever, and it is also asking a stranger to let an unknown binary rewrite their production crontab on first contact. "Shows the plan and backs up first" is doing an enormous amount of work in that sentence, and it's buried at the end of it.

I'd invert the whole thing:

1. Make the headline the safety, not the magic. Dry run by default, prints a diff, writes nothing without --apply. Lead with that and the clever part reads as appealing instead of alarming. Right now the order of those two clauses is costing you more than the pricing is.

2. Add a zero-blast-radius way in. One URL someone curls at the end of a single cron line. No install, no account, no rewrite. That's a ten-second decision with nothing at stake. sync is the second thing they do, after you've earned it, not the first.

3. The account wall costs more than the price does. Free for 10 monitors is generous, but the thing being asked for isn't money, it's signing up before knowing whether the tool works.

On distribution: the highest-intent traffic in this category is people typing "healthchecks.io alternative" or "cronitor alternative" into Google, and people in ops threads describing the exact failure your tool catches, which is a job that quietly stopped running and nobody noticed for a week. Write that failure up as an incident story rather than a product post, with the timeline and what you checked. The tool sells itself as a footnote and the post outlives the launch by years.

I've shipped a launch that landed the same way. The fix was never the launch. It was the first ten seconds after someone clicks.

Helpful post. How did you get your first bit of traction?

Helpful post. How did you get your first bit of traction?

Really relatable. How much time do you put into this each week?

How did you decide this was worth building in the first place?

Nice work shipping it. What has been the biggest challenge since launch?

Really relatable. How much time do you put into this each week?

Clear and practical, thanks. Did anything surprise you along the way?

Makes sense. Are you planning to charge for it, or keep it free for now?

Really relatable. How much time do you put into this each week?

Nice work shipping it. What has been the biggest challenge since launch?

How did you decide this was worth building in the first place?

Really relatable. How much time do you put into this each week?

Clear and practical, thanks. Did anything surprise you along the way?

Makes sense. Are you planning to charge for it, or keep it free for now?

Helpful post. How did you get your first bit of traction?

Zero after launch is a rough feeling. Same here with my first few days. Something that helped me separate "wrong channel" from "wrong pitch": track the steps, not just signups. I log visit → picked something → opened checkout → tapped pay. My first real visitor made it to checkout and stopped, which tells me something very different than "nobody came".

Do you know how many PH visitors got past the landing page? If they bounced there, it's the pitch; if they got to pricing and left, it's the offer.

PH mostly sends you other makers, not people who got burned by a silent cron. id put the rippler sync demo in front of people who already complain about that, sysadmin and selfhosted threads. the auto wrap of every line is the part that sells it

Nice, this makes a lot of sense. What's been the most surprising part of it so far?

Really relatable. How much time do you put into this each week?

How did you decide this was worth building in the first place?

Really relatable. How much time do you put into this each week?

Nice work shipping it. What has been the biggest challenge since launch?

Clear and practical, thanks. Did anything surprise you along the way?

Makes sense. Are you planning to charge for it, or keep it free for now?

Clear and practical, thanks. Did anything surprise you along the way?

Makes sense. Are you planning to charge for it, or keep it free for now?

The zero-trials result doesn’t necessarily mean PH was wrong for this. We’re preparing our own PH launch and the pattern we keep seeing is: the launch page gets traffic, people look, nobody converts — because the landing page answers “what is this” instead of “why switch from what I already do.”

For cron monitoring, most devs discover a cron failed when something downstream breaks. The rippler sync — reads your crontab, wraps each line, shows the plan first — is the answer, but it needs to be the hero of the landing page, not a feature in a list.

We run translation crons that auto-translate seven languages through Groq. Our monitoring is literally checking the Strapi content the next morning. That’s the gap your tool fills, and I’d bet most potential users are in the same “monitoring by accident” state.

How many PH visitors actually reached your pricing page?

With zero signups from Product Hunt, what evidence would separate a distribution problem from developers simply not seeing enough value to replace how they monitor crons today?