I spent months chasing clients who already had a webmaster. So I built something that only finds the ones who don't.

The first 10 users get 30 days of PRO VERSION!
https://signalshunt.com/login?promo=ih1

Love this idea

smart pivot — building your whole funnel on someone else's API (Reddit) is exactly the trap, good instinct killing it fast. one signal worth adding: businesses actively running Google/Meta ads to a weak site. "no website" can mean they don't want one, but "spending money to send traffic to a slow/broken site" means they already believe in growth AND have an obvious gap — much higher intent than an outdated footer year. that's the buyer who actually replies.

This is a good example of narrowing the market by negative signal.

A lot of prospecting starts with “who might need this?” which creates huge lists and weak outreach. Your angle starts with “who is missing the thing that creates obvious pain?” That is a much better wedge.

The same pattern works in other markets too: find the missing setup, the broken workaround, the repeated complaint, or the public request for alternatives. Then the conversation starts from evidence, not a guess.

The risk is false positives, so I’d track which signal actually converts: no webmaster, old site, slow page, bad mobile UX, missing forms, etc. The winning signal becomes the positioning.

I do a similar signal-based motion for my own outreach and one thing I'd flag: an outdated site isn't the same as an owner who cares. That 2019 footer has been there six years, they've made peace with it. I'd trust fresh signals way more, new hire, half-shipped redesign, anything that shows they're spending on the problem right now.

This is a really useful pivot. The part that stood out to me is the shift from “who is complaining online?” to “who actually needs help right now?”
I’m learning something similar while building my own product. Broad pain signals can be noisy, but visible need signals are much stronger.
I also like that you’re not just finding leads — you’re giving the first message a real reason to exist. Cold outreach feels much less cold when it references something specific and true about the business.
Curious how you handle false positives though — for example, when a site looks outdated but the owner doesn’t actually care or already has someone working on it?

This is the lead qualification problem every B2B founder faces. I've been through the exact same cycle — spent weeks DMing agency owners on LinkedIn, only to find half were solo freelancers, some were competitors who build software themselves, and a few had already solved the problem with existing tools. The 'research before DMing' lesson cost me real time and a few awkward rejections. Your approach of filtering before outreach is the right one. I've started doing it manually — checking company size, team count, and whether they already use a competing tool — before every connection request. Cuts my outreach time in half but doubles my reply rate. Would love to see this concept applied to B2B SaaS prospecting, not just web services.

The visible, verifiable problem approach works because it flips the pitch from selling capacity to pointing at a specific broken thing. That's how I landed my first Henson Group clients in 2002: I offered free migrations to businesses that were clearly hurting, and they hired me to run everything afterward. One caution as this scales: once every freelancer's tool flags the same 2019 copyright footer, that signal becomes the new spam, so your durable edge will be the signals competitors' scrapers can't see.

Honestly, what stood out to me is that this doesn't just pull in leads,
it actually helps you filter them before you even hop on a call.
I build websites for a living and if there's one thing I've figured out, it's that landing the right client matters way more than having some slick pitch.
I'd genuinely rather have one solid conversation with someone who needs my help than blast out 50 emails and hear nothing back. Interested to see how this holds up in the long run.

The Reddit API story hit close to home. Watched a few people get completely wiped out when that happened overnight. Building on signals you actually control is the right move. Genuinely curious though, does the outdated copyright year actually convert into paying clients? Would love to know if that signal holds up in real outreach.

"This is such a sharp reframe. Most SaaS chases the market that exists and fights for share. You're doing the inverse: targeting the unmet demand (SMBs without a tech person) instead of competing for the attended market.
That's distribution leverage hiding inside product design. You've essentially pre-filtered your TAM to 'people who desperately need this solution.' The sales process gets easier because you're not convincing someone with an existing solution — you're solving a void. And the churn risk is lower because switching costs include finding another person to hire, not just swapping tools. Smart move turning a sales problem into a product feature."

Smart pivot. The Reddit API lockdown killed a lot of monitoring-based tools last year — glad you caught it early instead of doubling down.

The "visit each website and check for problems" angle is interesting. I've been doing something similar but from the other side — monitoring my own sites for outdated pages, broken links, expired certificates. Same concept, different use case.

One question: how do you handle false positives? Like a copyright year showing 2023 doesn't always mean the site is neglected — some businesses just don't update the footer. Do you weigh multiple signals together or is one red flag enough to surface a lead?

I relate to the pain you described. I've spent hours researching agencies only to realize they already had everything covered. The biggest challenge isn't sending outreach—it's knowing who's actually worth reaching out to. Curious to see how accurate your website analysis is in practice. If it delivers on that, it could save a ton of wasted time.

The pivot after watching a competitor die from a rented API is the sharpest decision in this post: never build your core on data someone else can turn off. On the outreach itself, the outdated-footer detail is the product, because proof you did homework earns the reply, not the pitch. My first company grew by doing free IT migrations for businesses that were visibly struggling, and "I can see the problem from here" beat every cold script we ever wrote.

The "checks the actual website, not just the listing data" step is the part I'd lean into hardest. I built something with a similar shape recently — a Shopify app that scans a store's live theme for leftover code from apps that were installed and later uninstalled — and the whole value is in verifying ground truth instead of trusting a directory/API. A listing can say a business "has a webmaster," an app store can say an app is "installed," but neither tells you what's actually still running. Once you're willing to go fetch the real page and check it yourself, you catch the stale entries everyone else's leads-lists are full of.

Curious how you're handling false positives — sites that look outdated (old copyright year, no booking widget) but are intentionally simple by choice rather than neglect. That distinction seems like it'd matter a lot for how warm the lead actually is.

the underrated lesson in your own story isn't the targeting — it's that you moved off a rented API onto signals you crawl yourself. that 140k competitor didn't die from a bad idea, they died because their whole business sat on Reddit's terms, and Reddit changed them overnight. that's the real thing you built here: the day someone can flip a switch and kill your data source, you don't have a company, you have a feature on their platform. owning the pipeline end to end beats any single signal running through it.

This tool is very, very interesting. I'm wondering if it only works for B2B or if it also works for B2C, even if not now, in the near future. Could you clarify this for me? Thank you and good luck on your journey ahead.

the "qualify before you pitch" shift is the whole game, nice work. one thing i'd watch: "no website" on its own is a weak signal. a plumber with a full book from word of mouth doesn't want a site, and pitching them is the same dead end as pitching someone who already has one.

the strong signal is "no website AND visibly trying to get customers": running ads, a barely-updated facebook page they clearly care about, a gmb listing they're actively managing, posts like "we're taking new clients." absence of a site plus evidence of demand-chasing is the actual buyer. if SignalsHunt can layer even one intent signal on top of the filter, your reply rate probably jumps, because you stop pitching people who are deliberately offline.

This resonates — the "just another person in their
inbox" feeling is exactly why generic outreach
fails. Love that you rebuilt around "who needs help
right now" instead of "who's complaining." The
detail about checking outdated copyright years and
missing booking options is smart — that's the kind
of specific signal that makes a first message
actually land.

The pivot story hits home too. I'm building in a
different space (checkout/fintech) and had the same
experience — my first version was something I ended
up scrapping almost entirely once real users told me
what was actually broken. Watching that competitor
get killed by the Reddit API change is a brutal
lesson in platform risk.

Curious — when the AI writes the personalized first
message, how often do you find people still tweak it
before sending vs. sending as-is? Wondering how close
to "ready to send" it actually gets.

This resonates hard. I'm a solo dev who built a macOS app (Emdee) and now
trying to find my first paying client projects.

My ideal clients: indie SaaS founders who need a desktop layer, export
system, or AI workflow — not local businesses who need websites.

The "filter out people who already have help" insight is underrated.
I wasted time on communities before realizing I should look for founders
who posted "need a dev" in the last 48 hours, not everyone building something.

Would love to try it — trying to land clients in the dev/services space,
not web design. Curious if that works with your tool.

I really like the idea. However, when I pasted my website and recieved 20 leads, most of them were pin pointing on technical issues and not so much issues that I would try to solve with my app.

The insight of "only pitch the ones who don't already have it" is one of those things that sounds obvious in retrospect but almost nobody executes on. Most cold outreach tools optimize for volume; yours optimizes for relevance. Curious — what's the false-positive rate looking like? i.e., how often does the AI flag a site as "needs help" when actually the business already has someone in-house who just hasn't updated the footer?

i think the "who not to contact" filter is one of the biggest levers in outbound. Most campaigns fail because they're optimized for volume instead of relevance. The better your exclusion criteria, the higher the quality of every conversation.

Smart — most outreach dies on targeting, not the pitch. Filtering out the ones who already have the solution is exactly the trigger-signal that turns a cold list warm; the "who NOT to contact" filter is underrated. Curious how you detect the absence at scale — tech-stack detection, or manual checks?

How are you handling false positives on the "needs help" detection?
An outdated footer year or slow load doesnt always mean they're unhappy with their current setup, plenty of businesses know their site is old and just dont care. Curious if you found a signal that actually correlates with them being ready to switch vs just having a rough site

Good

The pivot after watching that 140k user competitor get wiped by an API change is such a good instinct honestly, most people would've kept building on the same shaky ground.

The "outdated copyright year, no booking option" detail in the personalized message is a smart way to actually earn that first reply.

Painful pattern — hunting people who are actually in-market vs everyone who could theoretically buy. Curious which channel surfaced the "already have a webmaster" vs open prospects — cold outbound, communities, or something else?

The shift from “pain signals” to “clear underserved intent” is the real unlock here. That’s also where most tools either get too noisy or too confident.

Curious how you’re validating that a site is actually worth pitching vs just looking outdated.

Strong idea — this solves a real pain: wasted cold outreach. Curious to see how accurate the “needs detection” is in real client scenarios. 👍

The strongest part here isn't the prospecting logic—it’s the shift from “finding people who have a problem” to “finding people who are demonstrably underserved right now.” That second framing is closer to intent than interest, and I think that's what actually makes outreach feel relevant instead of intrusive.