Skip to content
Hugin
VerdictSock-puppet ring, self-promotion funnel

Likely scam.

The post is a suspiciously polished 'quit my job and built a SaaS' success story, but the same user (u/Big_Employment1624) appears in all three top comments promoting a different product (exposd.dev, a vulnerability scanner) while pretending to be a separate person asking questions. This is a classic sock-puppet reply ring where the OP manufactures engagement and subtly cross-promotes another tool. The exposd.dev domain is only 18 days old, consistent with a rapid-cycle grift funnel.

r/B2BSaaSPosted by u/Downtown_Pudding9728Original
Sources6/12checked
Flags11 high, 0 med
Work34 limits
People10 histories
Scan shape50% source coverage
High flags1
Medium flags0
Work signals3
Sources checked6
Decision path

Hugin marked this as likely scam because multiple structural signals stacked high enough that the post should not be treated as organic.

  1. The final verdict text came from the AI verdict engine using the stored structural signal block.
  2. The scan reviewed 3 comments and 1 unique commenter accounts.
  3. Signal count: 1 high, 0 medium, 0 low flag; 0 coordination-class signals.
Linked domain exposd.dev is only 18 days old

The registry's RDAP record shows exposd.dev was registered on 2026-06-10. A marketing push running on a domain this young is the classic launch-and-burn pattern — by the time complaints accumulate, the operator has rotated to a fresh domain.

JSON
Full evidence trailSources, public checklist, values lens, network map, account coverage, archive, and sharing tools.
Validation protocol

Review before sharing.

Hugin reports are evidence packets, not accusations. Use the rating as a prompt to inspect sources, limitations, and archived material before quoting a claim elsewhere.

The post
I quit my job to vibe code a LinkedIn Automation SaaS tool, with no Engineering background, and made ~$3.6k in the first 3 months
Post age
46.0h
Commenters scanned
1
<7d-old accounts
0 (0%)
Removed comments
0
Median age
unknown

Source checks

Checked
6
Limited
3
Needs key
2
Total sources
12
checked / thread
Reddit thread snapshotReddit JSON or RSS

5 public comments loaded for r/B2BSaaS.

checked / thread
Comment evidence archiveHugin snapshot

Public comment bodies were retained with the report snapshot.

limited / accounts
Author account metadataReddit account about + old Reddit profile + Arctic Shift/PullPush archives

2 author age values were unavailable after Reddit profile JSON, old Reddit profile HTML, and archive fallbacks.

limited / accounts
Recent author historyReddit user activity + old Reddit profile + Arctic Shift/PullPush archives

1 selected author history checked; 1 unavailable.

checked / coordination
Reply graphHugin graph pass

3 reply edges mapped.

limited / coordination
Writing-style comparisonAI stylometry pass

Stylometry did not run for this scan, usually because no key/budget or too few samples were available.

checked / coordination
Shared identifiersHugin extractor

2 unique external identifiers extracted.

checked / archive
Prior report matchesHugin report archive

0 prior archive matches returned.

Show your work

Deterministic explanation of the stored scan inputs behind the verdict. This is not hidden model reasoning; it is the evidence checklist Hugin can show publicly.

Verdict path · AI summary

Hugin marked this as likely scam because multiple structural signals stacked high enough that the post should not be treated as organic.

  1. The final verdict text came from the AI verdict engine using the stored structural signal block.
  2. The scan reviewed 3 comments and 1 unique commenter accounts.
  3. Signal count: 1 high, 0 medium, 0 low flag; 0 coordination-class signals.
  4. The scan crossed the high-risk threshold through stacked structural evidence.

What pushed risk up

riskHIGH flag: Linked domain exposd.dev is only 18 days old

The registry's RDAP record shows exposd.dev was registered on 2026-06-10. A marketing push running on a domain this young is the classic launch-and-burn pattern — by the time complaints accumulate, the operator has rotated to a fresh domain.

  • registered 2026-06-10

What limited confidence

uncertainAuthor metadata gap

2 scanned authors had unknown account age. Profile metadata remained unavailable for 2 hosted fetches after archive fallbacks. Absence of young-account signals is lower confidence.

What kept the rating lower

cleanNo reply ring detected

Hugin mapped 3 reply edges and did not find a mutual-reply clique.

Limitations
  • 2 author account ages were unavailable after profile metadata and archive fallbacks.
  • 1 selected author history was unavailable to the scan.
  • Stylometry did not run, usually because no API key/budget was available or too few useful samples existed.
  • Username shape alone is never treated as a finding; it is only context when stronger public signals also appear.
Rating thresholds
  • Likely scam: multiple high-severity signals, prior identifier reuse, or several coordination signals stacking together.
  • Suspicious: one high-severity signal, multiple medium signals, or one concrete coordination signal that deserves review.
  • Inconclusive: weak, conflicting, or partial signals where the scan cannot justify either trust or a stronger warning.
  • Looks legitimate: no structural red flags, available metadata, and clean coordination passes.

Values lens

Use standardEvidence, not pile-ons

Use scans to slow down, inspect public signals, and keep uncertainty visible. Never use them to harass, shame, or flatten people into a verdict.

EvidenceDignityRepairCommon good
source humilityhuman dignityno pile-onsrepair when possible
Fair-use checks
  • What was observed, and what is interpretation?
  • What data is missing, blocked, or confidence-limiting?
  • Would the wording feel fair if it were about someone you care about?
Stable reference

What the post is doing

  • Same account u/Big_Employment1624 posted all 3 top comments under different guises: first as a skeptical engineer, then promoting exposd.dev (a different SaaS product), then responding to feedback — c
  • Cross-promotion: u/Big_Employment1624's comments link to exposd.dev while the OP (u/Downtown_Pudding9728) avoids linking their tool in the post, creating plausible deniability
  • exposd.dev domain registered only 18 days ago, matching a rapid launch-and-funnel timeline typical of coordinated grift networks
  • All three comments scored 0 and show no organic voting pattern, consistent with artificial engagement scaffolding rather than genuine community interaction
  • The comment thread pattern: fake skepticism → product plug → gratitude acceptance — mirrors textbook astroturfed enthusiasm cycle

Automated flags

HIGHLinked domain exposd.dev is only 18 days old

The registry's RDAP record shows exposd.dev was registered on 2026-06-10. A marketing push running on a domain this young is the classic launch-and-burn pattern — by the time complaints accumulate, the operator has rotated to a fresh domain.

Evidence
  • registered 2026-06-10

Commenter patterns

Recent public Reddit activity for the OP and selected accounts, plus same-hand writing checks when the stylometry pass runs. These are coverage-limited evidence summaries, not identity or availability claims.

Reddit blocked the recent-activity fetch from Hugin's scanner during this run. Treat this as missing coverage, not a finding about the account.

Account age coverage

OP and scanned commenters are shown when Hugin recovered profile metadata or an oldest-public-activity age floor. Lower-bound ages are labeled as estimates; unknown age remains missing coverage, not a finding about the account.

Reddit blocked metadata
Reddit blocked metadata

Archived evidence

Snapshot of the post and comments at scan time. Preserved here so the evidence survives even if it gets deleted on Reddit.

Post body — by u/Downtown_Pudding9728
Last Christmas I was at my parent’s place, pretty bored just watching TV on the couch, and realised I wasn’t really satisfied with my life. My job wasn’t going anywhere, and I felt like I really had no direction in life. I had spoken with a friend around that time, who had vibe coded his website for his business, and it looked really cool. So I spoke with ChatGPT to see what i could possibly build that could be interesting, but done in an innovative way. As I worked in sales already, it suggested that I lean into my own experience, and build something for my own use case. I’d been using LinkedIn automation tools to help generate leads, but I kept getting warnings from LinkedIn from the tools I was using, so I wasn’t using them regularly. So, after a lot of back and forth conversation with AI, I realised that there was a big opportunity to create a tool that was safer than anything else out there; Every tool I’d been using operated either on the cloud or used plugins - there were almost none that simply operated on your desktop, and this would most likely remove my issue of getting warnings and appear natural to LinkedIn. So, I decided to build something for myself primarily, in the sales job that I was in - could I build something that would help me generate more leads without risking my account as much? Turns out, I could. It definitely wasn’t easy, there was a very steep learning curve in terms of learning how to build something with AI, as well as making complex design and architectural decisions. I also made a lot of mistakes at first with building new features without testing first. As a result, there were tonnes of errors and bugs at first, but I spent a huge amount of time on hardening the tool to ensure that it’s now highly unlikely to break, and even if it does, it’s quick/easy to diagnose and implement fixes. It was a complex build as it’s essentially two code bases - a web dashboard where people can control their campaign settings and messaging sequences, with an inbuilt CRM, unified inbox, analytics etc., along with building the software itself separately, which automates LinkedIn in a dedicated browser on people PC’s. And not only did I have to build it, but I had to make sure it actually worked effectively. So I used it myself on my own account throughout the testing phase. I made sure that the tool had strict daily limits on actions, randomised delays between connection requests and follow up messages, along with effective messaging, written by Claude Sonnet via API. And it worked - in my first campaign in my old job, I got a 40% acceptance rate and a 25% response rate. What I realised along the way though, was that working on the tool itself was much more enjoyable than my sales job, so, I decided to quit my job and go all in on building and working on the tool. I made it into a business and took a leap of faith. Now, the tool has had 260 signups to free trials, many of whom converted into paying customers, and so far hovering around $3.6k in total revenue since launching in April, completely bootstrapped. Not a life changing sum yet but the first few months have been very promising, and there’s clearly a demand for a tool that’s safe for LinkedIn accounts and effective at booking meetings. Anyway, I hope this story inspires people to follow your passions and keep going!
Comments captured (5)
  • Are these things really true? I have been a software engineer for 4 years, and I couldn't even get one paid user for my platform, and you are killing it. How did you crack your distribution channel and get your first customers?
  • Yes completely true. Distribution is definitely the hardest part and something I still struggle with - less so acquiring customers, but getting people to stay with the tool long term and renew consistently. I have many day 1’s that I still communicate with regularly, but as I said, retention is the much harder skill than distribution. If you’re not getting new users, it might be worth evaluating whether there’s really enough demand for what it is. My distribution channel is social media, and dogfooding my actual tool. I use ZenMode to sell ZenMode, and it works. Hope that helps!
  • I'm still in the process of figuring out the demand. What I'm building is a frontend vulnerabiliy scanner tool where a person can monitor their website for leaks. I've got like 150 free rreports till now, but I'm not able to get people to join the waitlist for the paid tool. You cantray generating a report for your website. https://www.exposd.dev/
  • This is free with trufflehog, sentry, and other repos that anyone can use. I’d suggest building something that solves a problem almost nothing else does.
  • You are right on solving a problem that I can solve better. I started it off as free tool but paid tool signals have been weak. Thanks for the feedback though

Original on Reddit: https://www.reddit.com/r/B2BSaaS/comments/1ugp47i/i_quit_my_job_to_vibe_code_a_linkedin_automation/ — “I quit my job to vibe code a LinkedIn Automation SaaS tool, with no Engineering background, and made ~$3.6k in the first 3 months”

Share this report

Share this link in a Reddit reply when the thread needs supporting evidence. The report stays public so anyone reading the thread can review the data themselves.

Share on X ↗

Reports like this stay free for everyone. Keep Hugin free →

Embed this report
options: ?theme=light · ?compact=1 (80px badge)

Last 90 days

r/B2BSaaS report pressure

2 reports in 90d.