Suspicious.
The post itself reads as a genuine complaint, but the comment section shows structural signs of coordination. Two accounts (u/ninadpathak and u/nandavegg) share distinctive writing patterns—conversational parentheticals, run-on sentences with conjunctions, and complaints framed around specific spending figures—suggesting same-hand operation. Combined with a burst of 23 comments in 2.5 hours, all scoring 0, the thread appears artificially seeded to create the illusion of engagement and legitimacy around what may be an organized outreach effort.
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 23 comments and 21 unique commenter accounts.
- Signal count: 0 high, 2 medium, 0 low flags; 1 coordination-class signal.
Organic engagement ramps slowly. Posts that hit 8+ substantive comments within hours of going live are usually seeded — either by the OP's network or by paid services.
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.
Our SaaS just crossed the $35k/month token burn mark yet Anthropic still ghosts us 😔
Source checks
31 public comments loaded for r/Anthropic.
Public comment bodies were retained with the report snapshot.
22 author age values were unavailable; 17 not attempted after hosted metadata fallbacks were exhausted.
1 selected author history checked; 1 unavailable.
23 reply edges mapped.
1 same-hand writing pair surfaced.
2 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 23 comments and 21 unique commenter accounts.
- Signal count: 0 high, 2 medium, 0 low flags; 1 coordination-class signal.
- The scan crossed the caution threshold, but did not show enough stacked proof for likely scam.
What pushed risk up
Organic engagement ramps slowly. Posts that hit 8+ substantive comments within hours of going live are usually seeded — either by the OP's network or by paid services.
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/ninadpathak ↔ u/nandavegg — Both use parenthetical asides with conversational tone ('I guess', 'Although'), both structure complaints about customer service with specific spending figures and enterprise context, both exhibit longer run-on sentence patterns with connecting conjunctions rather than periods.
1 commenter pair had medium-or-higher stylometry similarity.
- u/ninadpathak / u/nandavegg: medium - Both use parenthetical asides with conversational tone ('I guess', 'Although'), both structure complaints about customer service with specific spending figures and enterprise context, both exhibit longer run-on sentence patterns with connecting conjunctions rather than periods.
What limited confidence
22 scanned authors had unknown account age. Hosted profile metadata and archive fallbacks were exhausted, so Hugin stopped after 5 failed fetches and left 17 profile lookups unattempted. Absence of young-account signals is lower confidence.
What kept the rating lower
Hugin mapped 23 reply edges and did not find a mutual-reply clique.
- 22 author account ages were unavailable; 17 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.
- 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
- u/ninadpathak and u/nandavegg exhibit medium-confidence stylometric match: identical use of parenthetical asides ('I guess', 'Although'), similar complaint structure around enterprise spending, and sh
- All 12 sampled top comments score exactly 0 points despite 31 total comments—atypical score distribution suggesting vote suppression or artificial downvoting
- 23 comments in first 2.5 hours with near-zero engagement (0 score) on most visible replies indicates possible comment-seeding to artificially populate and legitimize the thread
Automated flags
Organic engagement ramps slowly. Posts that hit 8+ substantive comments within hours of going live are usually seeded — either by the OP's network or by paid services.
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/ninadpathak ↔ u/nandavegg — Both use parenthetical asides with conversational tone ('I guess', 'Although'), both structure complaints about customer service with specific spending figures and enterprise context, both exhibit longer run-on sentence patterns with connecting conjunctions rather than periods.
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.
- 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.
- u/ninadpathak / u/nandavegg medium confidence - Both use parenthetical asides with conversational tone ('I guess', 'Although'), both structure complaints about customer service with specific spending figures and enterprise context, both exhibit longer run-on sentence patterns with connecting conjunctions rather than periods.
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/bakanoacescore 0It probably gets automatically filtered until you add at least 2 more zeroes
- u/ninadpathakscore 0you're burning 35k a month and they still won't talk to you, that's a pretty clear sign they're not interested in your business right now, maybe it's time to stop filling out that contact form and try something else
- u/vanwal_jscore 0Like posting on Reddit? 😬
- u/ali-hussainscore 0I built an AWS constultancy in the 2013-19 time. The reason I'm bringing it up is that before in the early stages AWS professional services was limited to just their biggest fortune 500 customers. 35k monthly- 400k annually, you wouldn't have been a named account. I'm not familiar with Anthropics tiers. Although you would have had a customer rep and if you tried you could get a hold of them on AWS but Anthropic is a far younger company. The one thing Anthropic has really started doing is invest in their partner network. Which to me is a sign that they're getting ready to take their full customer base seriously. If there is a partner that you start working with they may have access to the person that can actually help you. We did that frequently for our customers in cut through the red tape. But at that time, the partner managers were very eager to help. I can't say what that'll be for Anthropic. Sorry for the argument for analogy but I hope that gives you some comparison points.
- u/vanwal_jscore 0Yeah, I think you’re right, what’s interesting is that OpenAI seems to have a completely different strategy: we got someone to talk to within our first $1k of spend there.
- u/ali-hussainscore 0OpenAI is losing in Enterprise.
- u/NandaVeggscore 0OpenAI did the same (zero human customer support and random banning for Enterprise accounts every few months) in the past before their share gets eaten alive by Anthropic and others. I guess competition is always good. Actually got an OAI rep inquiring why our workplace account's usage downed in the past months, but because that account was randomly suspended for biological weapons or some nonsense. It was a good chuckle though.
- u/MGXMilkscore 0Just show up to their headquarters with bagels and coffee and you will solve your own issue
Original on Reddit: https://www.reddit.com/r/Anthropic/comments/1uj0ivm/our_saas_just_crossed_the_35kmonth_token_burn/ — “Our SaaS just crossed the $35k/month token burn mark yet Anthropic still ghosts us 😔”
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 →