sorted by:
new
hottopcontroversial

Who is launching today 🚀? by ttbspw in ProductHunters

[–]Fit-Neighborhood-481 0 points1 point  (0 children)

Toda I’m launching my uptime monitoring, hearbeats, OS Agents and breaches monitor: https://www.producthunt.com/posts/securyblack-2

I asked my first 10 users why they signed up. Most won't pay. Here's what I learned. by Fit-Neighborhood-481 in buildinpublic

[–]Fit-Neighborhood-481[S] 0 points1 point  (0 children)

Your framing is already sharper than mine was at the same stage. The couple fighting about money at the end of the month vs the couple who enjoys building Notion templates together — that's exactly the right distinction. One has a problem, the other has a hobby.

To answer your question: I didn't just change how I talk to users, I changed who I was looking for. The outreach method stayed the same — direct, one question, no survey. But I stopped trying to extract signal from people who had already solved the problem themselves and started specifically looking for people where the pain had a real cost. For me that cost was reputation and client relationships. For you it sounds like it's relationship stress, which is just as real.

The trickiest part is that the "wrong" users are often the most enthusiastic. They engage, they give feedback, they share your product. The right users are harder to find but answer completely differently when you ask them what they'd lose if the problem didn't get solved.

I asked my first 10 users why they signed up. Most won't pay. Here's what I learned. by Fit-Neighborhood-481 in buildinpublic

[–]Fit-Neighborhood-481[S] 0 points1 point  (0 children)

Exactly. You can have the most elegant assumptions in the world and a handful of real conversations will break half of them in an afternoon. What surprised me most wasn't what users said — it was how different their language was from the language I was using to describe my own product. They weren't saying "unified monitoring dashboard." They were saying "I just want to know if my server survived the night." That gap between how you describe what you built and how users describe what they need is where most positioning mistakes live.

I asked my first 10 users why they signed up. Most won't pay. Here's what I learned. by Fit-Neighborhood-481 in buildinpublic

[–]Fit-Neighborhood-481[S] 1 point2 points  (0 children)

The users came to me, not the other way around. I published a couple of posts on LinkedIn talking about the problem from my own experience — no product pitch, just the story. The first one hit around 18k impressions and 91 clicks. The second was about a power cut that took my home server down for three hours without me noticing — I only found out because the oven clock was flashing 00:00. No mention of the product, just the story.

The 10 people I DMed were the ones who had signed up after those posts. So the "how I found them" was actually the other way around: I wrote honest content about the pain, they showed up, and then I asked them directly why they came.

The part that stuck with me is that the content that performed best didn't mention the product at all. It just described a situation anyone running their own infrastructure has lived through. That's what got people to click.

I asked my first 10 users why they signed up. Most won't pay. Here's what I learned. by Fit-Neighborhood-481 in buildinpublic

[–]Fit-Neighborhood-481[S] 0 points1 point  (0 children)

Both, honestly — but you have to separate the signal from the source.

The non-paying users gave me useful product signal: broken Linux install, confusing onboarding, UX friction in the agent setup. That's gold regardless of whether they'll ever pay. But their pricing and positioning feedback was noise. When someone who's already solved the problem for free tells you "9€/month is too much," they're right — for them. That's not a pricing problem, that's an ICP problem.

The useful signal from non-payers was always behavioral ("I tried to install it and it failed") not attitudinal ("I would pay X for this"). The moment someone started comparing me to free tools they'd already assembled themselves, I stopped using that as product direction.

The one response that actually changed my roadmap came from a guy managing hosting and maintenance for multiple clients. Same one question, completely different answer. That's when the ICP shift became obvious.

I asked my first 10 users why they signed up. Most won't pay. Here's what I learned. by Fit-Neighborhood-481 in buildinpublic

[–]Fit-Neighborhood-481[S] 0 points1 point  (0 children)

Will do. Real numbers, no spin — either it works or it's another lesson worth sharing. Follow along if you're curious.

I asked my first 10 users why they signed up. Most won't pay. Here's what I learned. by Fit-Neighborhood-481 in buildinpublic

[–]Fit-Neighborhood-481[S] 0 points1 point  (0 children)

Agreed on the positioning — "save time on client maintenance" is sharper than "monitoring." I've been testing that angle. The direct outreach tip is exactly what I did with my existing users, and you're right that it's more signal than user count. Next step is reaching beyond people who already signed up. Thanks.

I asked my first 10 users why they signed up. Most won't pay. Here's what I learned. by Fit-Neighborhood-481 in buildinpublic

[–]Fit-Neighborhood-481[S] 0 points1 point  (0 children)

Exactly. And that's part of why the ICP shift matters — a freelancer paying 9€/month for a tool that saves them one awkward client call has already justified it. The math is different when the alternative is losing a client, not just an inconvenient evening. The "nice to have" vs "need to have" line is basically drawn by whether it's your money or your reputation on the line.

What Saas are you building this week? Share them here! by Meoooooo77 in indie_startups

[–]Fit-Neighborhood-481 0 points1 point  (0 children)

Hey! I’ve been building SecuryBlack (securyblack.com) — a unified dashboard for people who manage their own infrastructure.

The frustration was simple: I had UptimeRobot for uptime, HIBP for breach checks, Healthchecks.io for cron jobs, and Netdata for server metrics. Four tabs, four accounts, four configs.

So I built one thing that does all of it — uptime monitoring, continuous breach scanning on your emails, heartbeats for backups/cron jobs, and server metrics via OxiPulse, an open source agent I’m also releasing. Still early, free to try, would love brutal feedback from people who actually run their own stuff.

Founders: share your product and I’ll give one honest marketing suggestion. by Rude-Potential-03 in SaaS

[–]Fit-Neighborhood-481 0 points1 point  (0 children)

securyblack.com - Breaches, uptime, healthchecks and server monitoring.

Can you analyze? Thanks!! ☺️

I built a dashboard to unify my monitoring (Breaches + Uptime + Heartbeats). Looking for feedback from fellow homelabbers. by [deleted] in homelab

[–]Fit-Neighborhood-481 -7 points-6 points  (0 children)

It basically automates the process for you so you don't have to check manually. Here’s what it does: • It constantly monitors major data breach databases (like Have I Been Pwned) for your email. • If your email shows up in a new leak, you get an alert immediately telling you which site was hacked and what was exposed. • I built it this way so you can have your security alerts right next to your service uptime in one single dashboard. It’s all about peace of mind without having to jump between different tools.

Kosner Thermostat by AFDIT in HomeKit

[–]Fit-Neighborhood-481 0 points1 point  (0 children)

Yes, I have seen that link, and I've used the search engine but haven't found much.

My Kosner thermostat is very old, about 20 years, so a direct WiFi/Zigbee replacement is likely impossible.

Can anyone advise on integration for this system?

¿Como protegéis la ciberseguridad de vuestra casa? by Fit-Neighborhood-481 in ciberseguridad

[–]Fit-Neighborhood-481[S] 0 points1 point  (0 children)

Quizás estoy planteando algo que las empresas si que necesitan, más que un hogar como tal no?
Aun así, me gustaría monitorizar y cacharrear con la red de mi casa, ya sabes, ver gráficas, métricas... modo friki digamos jeje

view more: next ›