Suspicious.
The post itself reads authentic and shows genuine product-market fit confusion, but the comment section is structurally suspicious: four different accounts (mohammad_razavi, Diyraxis_2448, Flat-Grapefruit6668, alexvanman) with minimal histories in r/SaaS all provided on-topic, helpful replies within hours, and all scored 0—suggesting coordinated staging rather than organic engagement. One account (alexvanman) shows a 2213-day dormancy gap, consistent with reactivation for this thread.
Hugin marked this suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 4 comments and 4 unique commenter accounts.
- Signal count: 1 high, 0 medium, 0 low flag; 1 coordination-class signal.
An account that sat silent for months and then suddenly wakes up to praise a promotional post is almost always a sold or recovered handle being weaponised for credibility.
Full evidence trailSources, public checklist, values lens, network map, account coverage, archive, and sharing tools.
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.
I built a calorie-tracking app before finding a real problem. What would you do next?
Source checks
4 public comments loaded for r/SaaS.
Public comment bodies were retained with the report snapshot.
5 public author records checked; 5 oldest-archived-activity lower bounds.
5 selected author histories checked; 4 partial, 5 archive fallback.
4 reply edges mapped.
0 same-hand writing pairs surfaced.
0 unique external identifiers extracted.
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.
Hugin marked this suspicious because at least one meaningful risk signal appeared, but the scan did not reach the stronger likely-scam threshold.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 4 comments and 4 unique commenter accounts.
- Signal count: 1 high, 0 medium, 0 low flag; 1 coordination-class signal.
- The scan crossed the caution threshold, but did not show enough stacked proof for likely scam.
What pushed risk up
An account that sat silent for months and then suddenly wakes up to praise a promotional post is almost always a sold or recovered handle being weaponised for credibility.
- u/alexvanman — sat dormant 2213d then lit up
1 author history showed drop-in, dormant, or cross-promotion behavior.
- u/alexvanman: dormant 2213d
What kept the rating lower
Hugin did not find a <7d-old commenter cluster among 4 scanned authors.
Hugin mapped 4 reply edges and did not find a mutual-reply clique.
The writing-style comparison ran and did not surface same-hand pairs.
- 5 author age values are a lower-bound estimate from oldest archived public activity, not an official Reddit account-created timestamp.
- Username shape alone is never treated as a finding; it is only context when stronger public signals also appear.
- 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 scans to slow down, inspect public signals, and keep uncertainty visible. Never use them to harass, shame, or flatten people into a verdict.
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?
What the post is doing
- Four accounts with sparse or adjacent r/SaaS histories all replied within the same 2-hour window with substantive, constructive advice, creating an artificial appearance of engagement
- All four comments scored exactly 0, despite topical relevance and effort—inconsistent with natural upvoting behavior in a 4-comment thread
- u/alexvanman shows 2213-day dormancy gap (longest gap in account history) followed by recent activity, typical of reactivated sockpuppet accounts
- Three of four commenters (mohammad_razavi, diyraxis_2448, flat-grapefruit6668) appear as 'adjacent subs' to r/SaaS with minimal posting history there, suggesting accounts created or repurposed for thi
- Comment content reads as a staged Q&A: each reply addresses a different hypothetical angle (read reviews → talk to users → check who pays → product-market fit strategy), resembling a scripted tutorial
Automated flags
An account that sat silent for months and then suddenly wakes up to praise a promotional post is almost always a sold or recovered handle being weaponised for credibility.
- u/alexvanman — sat dormant 2213d then lit up
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 or hub around one shared identifier are the structural fingerprints of a coordinated pod. This shows the most significant pattern found, not every commenter.
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 returned only part of this account's recent public activity during the scan.
- r/SneakerheadsIndia (14)
- r/IndianHomeDecor (4)
- r/soccercirclejerk (3)
- r/CarsIndia (2)
Reddit returned only part of this account's recent public activity during the scan.
- r/founder (2)
- r/SaaS (1)
- r/AIDeveloperNews (1)
- r/AiAutomations (1)
Reddit returned only part of this account's recent public activity during the scan.
- r/AskReddit (13)
- r/SaaS (1)
- r/NewTubers (1)
Reddit returned only part of this account's recent public activity during the scan.
- r/SaaS (20)
- r/automation (5)
- r/omad (7)
- r/trainerday (6)
- r/SaaS (5)
- r/ClaudeAI (2)
The writing-style pass ran and did not surface same-hand pairs.
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.
Archived evidence
Snapshot of the post and comments at scan time. Preserved here so the evidence survives even if it gets deleted on Reddit.
- u/mohammad_razaviscore 0Read reviews of existing apps!
- u/Diyraxis_2448score 0At such point. I would really try to connect with ppl in that field to find the real problem they face with the existing apps.
- u/Flat-Grapefruit6668score 0one thing worth asking yourself: is the person who tracks calories your actual customer, or is it a coach/nutritionist managing multiple clients? sometimes the real money is one layer up from the end user
- u/alexvanmanscore 0You have built a product without a problem. Now you are trying to find a problem to fit the product. This is all backwards. You can make it work but it's likely much harder. If you can really find a problem people have quickly ok maybe pivot to that problem. To stand out the wisdom is you need to be 10X better at least for some subset of users. That might be 20% of the price and 2X better features for some subset of users. It's the goal, not that you will always bet 10X better but if you are thinking 10-20% better you are likely not going to be able to differentiate yourself and grow.
Original on Reddit: https://old.reddit.com/r/SaaS/comments/1vkgz2r/i_built_a_calorietracking_app_before_finding_a/ — “I built a calorie-tracking app before finding a real problem. What would you do next?”
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.
Reports like this stay free for everyone. Keep Hugin free →