Inconclusive.
The post reads as a genuine founder question about prioritization with real microSaaS numbers, but the 0% upvote ratio, zero score despite 11 comments, and unavailable author metadata across 9 accounts create structural uncertainty. The comment section itself appears organic and substantive (no vote-ring or sock-puppet patterns visible in the replies), but the absence of authentication data prevents a confident legit verdict.
Hugin marked this inconclusive because the available signals were mixed or incomplete, and missing author metadata keeps the clean-read confidence low.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 9 comments and 8 unique commenter accounts.
- Signal count: 0 high, 1 medium, 0 low flag; 1 coordination-class signal.
Not conclusive, but the writing-style overlap is enough to warrant skepticism — especially when these same accounts are also new or copy-pasting praise.
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.
Built a microSaaS to $360 MRR and now facing a difficult founder decision.
Source checks
11 public comments loaded for r/microsaas.
Public comment bodies were retained with the report snapshot.
9 author age values were unavailable.
1 selected author history checked; 1 unavailable.
9 reply edges mapped.
1 same-hand writing pair 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 inconclusive because the available signals were mixed or incomplete, and missing author metadata keeps the clean-read confidence low.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 9 comments and 8 unique commenter accounts.
- Signal count: 0 high, 1 medium, 0 low flag; 1 coordination-class signal.
- The scan did not have enough clean metadata coverage to call the thread legitimate.
What pushed risk up
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/camppofrio ↔ u/forge-website — Both use the exact phrase '$360 MRR' as a reference point and adopt a similar analytical tone discussing valuation multiples and opportunity cost without filler vocabulary or colloquialisms.
1 commenter pair had medium-or-higher stylometry similarity.
- u/camppofrio / u/forge-website: medium - Both use the exact phrase '$360 MRR' as a reference point and adopt a similar analytical tone discussing valuation multiples and opportunity cost without filler vocabulary or colloquialisms.
What limited confidence
9 scanned authors had unknown account age, so absence of young-account signals is lower confidence.
What kept the rating lower
Hugin mapped 9 reply edges and did not find a mutual-reply clique.
- 9 author account ages were unavailable.
- 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
- Author metadata unavailable for 9 accounts including OP — cannot verify account age, activity pattern, or crossover with other reports
- Post has 0% upvote ratio and 0 score despite 11 substantive comments — unusual engagement signature suggests possible early downvoting or vote manipulation
- Heuristic flag: 1 additional pair with similar style signals — indicates pattern matching to known grift copy, though post content does not obviously fit a monetization angle
Automated flags
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/camppofrio ↔ u/forge-website — Both use the exact phrase '$360 MRR' as a reference point and adopt a similar analytical tone discussing valuation multiples and opportunity cost without filler vocabulary or colloquialisms.
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 did not return recent public activity for this account during the scan. Treat this as missing coverage, not a finding by itself.
- u/camppofrio / u/forge-website medium confidence - Both use the exact phrase '$360 MRR' as a reference point and adopt a similar analytical tone discussing valuation multiples and opportunity cost without filler vocabulary or colloquialisms.
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/camppofrioscore 0$360 MRR is ~$4k ARR, so a 3x multiple lands around $12k. The documented TikTok/Reddit process might be what a buyer pays for more than the revenue itself.
- u/appbuilderdailyscore 0That's the part we're still trying to figure out. The revenue is what it is today, but the acquisition side is heavily documented at this point, so someone coming in wouldn't be starting from zero. Interesting to hear multiple people focus on the TikTok/Reddit side rather than the revenue itself.
- u/Agreeable-Bicepscore 0Honestly, focus is one if the most valuable resources you have as a founder. 360 is not a lot of MRR. The only way I‘d hold onto this was if I saw a viable path to grow this 10x or more. So if this thing is draining your focus and only makes 360 MRR, I would either go back to growing it with lots of determination or get rid of it fast. Put it up for sale, use the proceeds to fund the new project.
- u/appbuilderdailyscore 0That's pretty close to how we're thinking about it. The opportunity cost is the main factor. $360 MRR isn't enough to change anything financially, so the question becomes whether the next few months are better spent scaling this or putting that effort into something with a larger upside. Appreciate the perspective.
- u/Agreeable-Bicepscore 0Exactly. Obviously getting to 2.2k users is a major achievement and getting even some revenue out of it is huge. Congrats to you on this! And if this is your first project to reach this size, there‘s probably an emotional component too. It can be hard to let go of a baby. Still, taking care of things in parallel will slow you down. Better take what money and experience you can use from a sale and use your learnings for the next project.
- u/RodrigoPoloTscore 0If your app already is giving you monthly revenue it’s because people actually want it , if it not scaling that well maybe you need more feedback and to push a little bit more on it , you said it yourself I just put a few hours on it. Off course you can focus on your bigger project , but what if you run into the same problem , are you abandoning that as well for a bigger one . That first baby may not be the best but surely pays couple of meals for you, DONT THROW IT AWAY , make it better , push it harder , give it one month just to make it better from feedback , deep research , create that new momentum and scale it a little bit more , maybe you can have then more than one success and run multiple microsaas but better than that the confidence you will gain knowing exactly how to scale small things into something it’s just priceless. Continue and be bigger , just don’t toss the progress achieved.
- u/AWESOMESHRIscore 0keep pushing to hopefully in next 3 months 500-1000 MRR
- u/Deepak-AvairAIscore 0At a startup I co-founded, the second product was always the siren song. The thing I'd tell my past self: don't sell to free up time for the new thing. Sell (or pause) because the existing one genuinely stopped teaching you anything. If you're still learning from it weekly, it's not the time.
Original on Reddit: https://www.reddit.com/r/microsaas/comments/1uebyss/built_a_microsaas_to_360_mrr_and_now_facing_a/ — “Built a microSaaS to $360 MRR and now facing a difficult founder decision.”
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 →