Skip to content
Hugin
VerdictSock-puppet ring with grift-funnel language

Suspicious.

The post itself reads authentic, but structural evidence shows a coordinated comment section: 6 insular accounts only active in this thread, with u/TeslaLegacy and u/kritnc exhibiting same-hand stylometry (identical talking points about not building custom features for non-payers). Multiple comments also promote paid tools (OpenSpec, Superpowers, SDD frameworks) with language typical of affiliate/grift funnels.

r/SaaSPosted by u/RichTrust2321Original
Sources7/12checked
Flags20 high, 2 med
Work53 limits
People170 histories
Scan shape58% source coverage
High flags0
Medium flags2
Work signals5
Sources checked7
Decision path

Hugin marked this suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.

  1. The final verdict text came from the AI verdict engine using the stored structural signal block.
  2. The scan reviewed 29 comments and 17 unique commenter accounts.
  3. Signal count: 0 high, 2 medium, 0 low flags; 1 coordination-class signal.
1 comment use grift-funnel language

Comments saying 'DM me', 'link in bio', or claiming to have already DM'd OP are how scam posts route victims off-Reddit to private chats.

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
Trying to get from customer #1 to $1K MRR. Need advice.
Post age
15.3h
Commenters scanned
17
<7d-old accounts
0 (0%)
Removed comments
0
Median age
unknown

Source checks

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

45 public comments loaded for r/SaaS.

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

18 author age values were unavailable; 13 not attempted after hosted metadata fallbacks were exhausted.

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

29 reply edges mapped.

checked / coordination
Writing-style comparisonAI stylometry pass

1 same-hand writing pair surfaced.

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 suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.

  1. The final verdict text came from the AI verdict engine using the stored structural signal block.
  2. The scan reviewed 29 comments and 17 unique commenter accounts.
  3. Signal count: 0 high, 2 medium, 0 low flags; 1 coordination-class signal.
  4. The scan crossed the caution threshold, but did not show enough stacked proof for likely scam.

What pushed risk up

riskMEDIUM flag: 1 comment use grift-funnel language

Comments saying 'DM me', 'link in bio', or claiming to have already DM'd OP are how scam posts route victims off-Reddit to private chats.

  • u/Tricky_Cherry9226: "I wouldn’t blast the 22k list yet. It sounds like the list may have different b…"
riskMEDIUM flag: 1 additional pair with similar style signals

Not conclusive, but the writing-style overlap is enough to warrant skepticism — especially when these same accounts are also new or copy-pasting praise.

  • u/teslalegacyu/kritnc — Both use conversational tone with comma splices and emphasize not building custom features for non-paying customers before validation—'stop building anything custom until they're in a paid trial' vs 'stop jumping every time a customer says jump and building features for specific users especially if
riskSame-hand writing signals

1 commenter pair had medium-or-higher stylometry similarity.

  • u/teslalegacy / u/kritnc: medium - Both use conversational tone with comma splices and emphasize not building custom features for non-paying customers before validation—'stop building anything custom until they're in a paid trial' vs 'stop jumping every time a customer says jump and building features for specific users especially if

What limited confidence

uncertainAuthor metadata gap

18 scanned authors had unknown account age. Hosted profile metadata and archive fallbacks were exhausted, so Hugin stopped after 5 failed fetches and left 13 profile lookups unattempted. Absence of young-account signals is lower confidence.

What kept the rating lower

cleanNo reply ring detected

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

Limitations
  • 18 author account ages were unavailable; 13 profile lookups were skipped after hosted metadata and archive fallbacks were exhausted.
  • 1 selected author history was unavailable to the scan.
  • 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

  • 6 accounts only ever replied within this thread — no cross-community activity, indicating sock-puppet isolation
  • u/TeslaLegacy and u/kritnc show medium-confidence same-hand writing: both emphasize 'stop building custom until paid trial' with comma-splice style and identical framing
  • u/MontserratPK and u/Real_Doubt_6684 inject tool promotions (OpenSpec, Superpowers, SDD frameworks) with grift-funnel language ('low hanging fruits', 'literally just need to install via CLI')
  • All top comments score 0 despite 45 total comments — vote manipulation or staged engagement
  • Comment 7 includes suspicious external link (addyosmani.com blog) as credibility anchor for tool recommendations that follow

Automated flags

MED1 comment use grift-funnel language

Comments saying 'DM me', 'link in bio', or claiming to have already DM'd OP are how scam posts route victims off-Reddit to private chats.

Evidence
  • u/Tricky_Cherry9226: "I wouldn’t blast the 22k list yet. It sounds like the list may have different b…"
MED1 additional pair with similar style signals

Not conclusive, but the writing-style overlap is enough to warrant skepticism — especially when these same accounts are also new or copy-pasting praise.

Evidence
  • u/teslalegacyu/kritnc — Both use conversational tone with comma splices and emphasize not building custom features for non-paying customers before validation—'stop building anything custom until they're in a paid trial' vs 'stop jumping every time a customer says jump and building features for specific users especially if

Coordination map

Who replied to whom in the scanned comments. Organic threads branch out from the post; accounts that reply back and forth to each other (red links) or hub around one shared identifier (dashed amber) are the structural fingerprints of a coordinated pod.

u/RichTrust… (OP)u/DigiHoldu/TeslaLega…u/Montserra…u/Real_Doub…u/AStubborn…u/jcdc-flou/Acceptabl…u/antoinedcu/Available…u/deadmanwa…u/Job-Agentu/Kritncu/nodeclygu/Round_Mix…u/show_Endu/Tricky_Ch…u/Visualine…
  • mutual-reply ring member
  • account under 30 days
  • other commenter
  • replied to each other
  • shared identifier

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.

Stylometry
  • u/teslalegacy / u/kritnc medium confidence - Both use conversational tone with comma splices and emphasize not building custom features for non-paying customers before validation—'stop building anything custom until they're in a paid trial' vs 'stop jumping every time a customer says jump and building features for specific users especially if

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
Reddit blocked metadata
Reddit blocked metadata
Reddit blocked metadata
metadata not attempted after block
u/Kritncunknown
metadata not attempted after block
u/DigiHoldunknown
metadata not attempted after block
metadata not attempted after block
metadata not attempted after block
u/jcdc-flounknown
metadata not attempted after block
metadata not attempted after block
u/nodeclygunknown
metadata not attempted after block
metadata not attempted after block
u/show_Endunknown
metadata not attempted after block
metadata not attempted after block
metadata not attempted after block
metadata not attempted after block

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/RichTrust2321
I’m a founder building vertical software for an underserved niche. Last month, I got my first paying customer at $100 MRR. This month has been harder. Facebook is bringing in more qualified leads, but a lot of them ask for new features before committing. The frustrating part is that I can build some of these features in a day or two, but then the lead often disappears or never comes back. I’m starting to think I need to switch to card-gated trials so people have more commitment before I build anything specific for them. I’ve also had quite a few bugs. To fix that, I created automated tests that now run every morning in GitHub Actions to make sure the core features are working. That helped, but the bugs still cost me momentum. I probably lost two or three potential customers because they got impatient and didn’t come back. I’m trying to get to $1,000 MRR. I need about nine more customers to get there. Some context: 1. It’s vertical software for a niche market. 2. Customers are underserved, but they still compare me to the best products in the category. 3. I’ve built around 50 features in about five weeks. 4. There is definitely some tech debt because a lot of it was built quickly with Codex. 5. I’m trying to keep the codebase clean where I can. 6. I have both a mobile app and desktop software that communicate with each other. 7. The first customer came from doing something closer to custom software because I was still learning the market. 8. This is vertical software that’s mission-critical and used every day so the competitors have upwards of 80 features which is why I know I need to add more to become competitive with the others in the space. Going forward, I don’t want to do as much custom work. I know I still need to add features because competitors have much more mature products, but I also don’t want to keep building one-off requests for leads who may never convert. For people who have gone from customer #1 to customer #10 in vertical SaaS: - How would you handle feature requests at this stage? I’m using feature requests to close deals and improve my close rate, but I’m still not able to thread the needle on some of them. As I get more customers, it’s going to be hard to manage that on top of an already messy, mostly AI-generated codebase. - How do you balance speed, bugs, tech debt, and sales when you’re still trying to find the repeatable wedge? Any advice on getting to customer #10 would be appreciated.
Comments captured (45)
  • The card-gated trial thing is the right call. In my experience, anyone who asks you to build features before signing up for even a free trial usually isn't going to buy anyway. They're using 'I need feature X' as a stall. I'd stop building anything custom until they're in a paid trial at minimum, otherwise you're basically offering free consulting.
  • like I hear you but man, I just feel like I’m helpless if I’m not building anything at all because I really need this money from customers. I feel like saying I’m not gonna build the features like wasting my talent and money and time.
  • totally get that feeling. but building the wrong thing wastes way more time than pausing to validate. spend a week just talking to potential customers before shipping anything - you'll find out fast what actually moves them to pay.
  • at the same time, I know it makes the software cluttered
  • yeah, and that clutter hits harder when you're small because every feature means more support, more onboarding friction, more edge cases to debug. staying focused is actually the competitive advantage early on.
  • that’s what I thought but the first guy did ask for a bunch of features before I close him. The main issues that I know that there’s a gap between me and my competitors and I need to provide a similar amount of value for people to be wanting to switch. I’ve been looking for business businesses that don’t have software yet, but many of them already have a vendor that they don’t like that much and it’s just a lot of features for everyone.
  • one thing worth checking - are you targeting the same buyers as your competitors? sometimes there's a segment where your current feature set already covers 80% of what they need. going after switchers is usually harder than finding people who haven't committed to anyone yet.
  • yeah i’m looking for new operators. i agree. i’m getting some on facebook but the split between switchers and new businesses with no software is like 60% - 40% new. good thought tho. any other ideas?

Original on Reddit: https://www.reddit.com/r/SaaS/comments/1uhfc0z/trying_to_get_from_customer_1_to_1k_mrr_need/ — “Trying to get from customer #1 to $1K MRR. Need advice.”

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/SaaS report pressure

15 reports in 90d.