Skip to content
Hugin
VerdictNone

Inconclusive.

The post describes a legitimate sales tactic (moving pricing from public page to guided presentation deck) with detailed operational context and honest caveats. However, the account's activity history is unavailable due to Reddit API limitations, and there is minimal comment engagement to verify authenticity signals. Without deterministic coordination indicators or grift markers, the thin data prevents a stronger rating.

Sources5/12checked
Flags00 high, 0 med
Work24 limits
People10 histories
Scan shape42% source coverage
High flags0
Medium flags0
Work signals2
Sources checked5
Decision path

Hugin marked this inconclusive because the available signals were mixed or incomplete, and missing author metadata keeps the clean-read confidence low.

  1. The final verdict text came from the AI verdict engine using the stored structural signal block.
  2. The scan reviewed 1 comments and 1 unique commenter accounts.
  3. Signal count: 0 high, 0 medium, 0 low flags; 0 coordination-class signals.
Author 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.

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
We pulled our pricing off the website during sales calls and walk people through a short pricing presentation instead. Calls got way easier.
Post age
2.2h
Commenters scanned
1
<7d-old accounts
0 (0%)
Removed comments
0
Median age
unknown

Source checks

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

1 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

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

1 reply edge 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

0 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 inconclusive because the available signals were mixed or incomplete, and missing author metadata keeps the clean-read confidence low.

  1. The final verdict text came from the AI verdict engine using the stored structural signal block.
  2. The scan reviewed 1 comments and 1 unique commenter accounts.
  3. Signal count: 0 high, 0 medium, 0 low flags; 0 coordination-class signals.
  4. The scan did not have enough clean metadata coverage to call the thread legitimate.

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 1 reply edge 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

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/Previous-Yak2574
Context: we sell a mid-ticket tool, deals land between $300 and $900 a month, mostly closed on a call. For a long time our sales call meant screen-sharing our pricing page and watching the prospect's eyes go straight to the biggest number. Every call turned into them defending their budget before they understood what they'd get. The pricing page made the conversation about cost first, value never. So we stopped showing the page on calls. Now we walk through a short pricing presentation, 4 slides, built for the call and not for the website. Slide one is their problem in their words, pulled from the discovery call. Slide two is what solving it is worth to them, roughly, in their numbers. Slide three is the plan that fits. Slide four is what happens in the first 30 days. Price shows up on slide three, after the worth is already on the table. What changed: people stopped flinching at the number. Same prices. We didn't discount. The number just stopped being the first thing in the room. A few honest notes. This only works if discovery was real, if I'm guessing at their problem on slide one the whole thing falls apart and they can tell. I kept the public pricing page up, self-serve buyers still want to see it. And one thing that backfired early: I made the pricing presentation too pretty and it read like a brochure, which made people suspicious, plainer slides converted better. Close rate on qualified calls went up noticeably over a quarter. Anyone else moving pricing off the page and into a guided pricing deck for calls?
Comments captured (1)
  • I 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.

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.