Suspicious.

Source checks

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.

Values lens

What the post is doing

• 4 aged accounts (longest dormancy 957d, 218d, 42d) reactivated in the last 24h to comment exclusively on this thread
• 6 insular accounts appear only in this thread's reply graph, creating artificial comment volume (28 comments in 2.5h, all score 0)
• johnwheelerdev, redvox27, and ok_mirror_832 all post repetitive 'first-person founder-story' titles across r/vibecoding, r/SideProject, r/SaaS, r/StartupSoloFounder — overlapping niche communities
• johnwheelerdev repeats the same image URL (i.redd.it/lf1v1y7oij8h1.png) across 2 subreddits; ok_mirror_832 repeats tenor.com/M1Ww.gif across the same sub
• High upvote ratio (0%) combined with 41 comments and dormant account reactivation pattern indicates vote/engagement manipulation independent of organic interest

Automated flags

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.

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.

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/johnwheelerdevscore 0
  Something about this doesn't sit right with me. It's just a little bit too good for it to be completely vibe-coded by a non-practicing engineer. If you're being honest, hats off to you, man.
• u/Head-Bench6270score 0
  I’ll honestly take that as a huge compliment, so thank you, especially from an actual engineer like you. To be fair, I don’t think I’d ever written a real line of code before this, aside from maybe typing print("hello world") in a high school comp sci class that I barely passed lol. For the past 6 months, though, I’ve been using Claude Code pretty much daily. I’ve been on the 5x Max plan most of the time, and when Fable dropped I upgraded to 20x for the month, which was painful because I only got like 3 days with it before it shut down. I’ve been constantly building random side projects and breaking things, but most of them never felt good enough to actually launch. Over time I think I just got better at understanding the workflow, knowing what to ask for, spotting when something is wrong, and communicating with the model in a way that gets useful output. It’s been a ton of trial and error, and I still get a lot wrong, I think fable also did a lot of heavy lifting for the structure of the site itself, I've never gotten a baseline as good of this, so I would give most of the credit there lol.
• u/johnwheelerdevscore 0
  The reason I bring it up is because sometimes, to get attention, people use the vibe coding narrative as a story in itself. The hook is: "Hey, I don't have any experience, but look how awesome this thing I created is" - with the hope that some people are at the intersection of being wowed by that and also needing a roofing app. So it'd be nice to know a little bit more about your experience, given that you have your comments and posts turned off. The issue is that people don't typically get those types of results, and so it can make them wonder why they're not getting them when you are - and it can make them feel bad. I'll be honest, it makes me feel a little bit bad. So what is your background? Is it product management? It's got to be something in tech. This is not your first time doing this. You're not a roofing contractor who's never touched a computer before. It really goes to show in the demo, the website, and the product itself - they're all just a little bit too pristine. I mean, you don't even have a flash of unstyled content on your website or anything. It just doesn't smell right, and being a good engineer, I can tell these things.
• u/Head-Bench6270score 0
  My actual background is not engineering. I’m currently a logistics manager for a roofing company, so my experience is more on the roofing/operations side: managing people, dealing with jobs, understanding workflows. That's pretty much how I interact with claude code as well, I treat it just as another employee and try and steer it in the right direction so to speak. I also started prompting claude by showing what the end product will be and why it helps and what I want it to do as an overarching goal. The reason this product probably looks more polished than a random first project is because I’ve used Roofr, which is basically this product’s competitor, pretty heavily for about a year and a half now. So I had a pretty clear idea of what I liked, what I didn’t like, what roofers actually need, and what the workflow should feel like before I ever started building RoofV. So yea, I’m not a roofing contractor who has never touched a computer before. I’m also not a software engineer or someone with a tech/product management background. I’m more of an operator in the roofing space who has spent a lot of time using the existing tools and obsessing over what I wish they did differently. I also have a bunch of failed side projects I can share that are way more obviously vibecoded lol. This one just happens to be the first thing where my industry knowledge, using Claude Code daily, and a lot of trial and error actually started coming together into something that felt launchable. I don’t want the takeaway to be that anyone can build anything with just an idea, because that's obviously not the case and that's what people are marketing claude/codex as. It’s more that I had a lot of domain knowledge, used a competitor daily, burned a lot of tokens, broke a lot of stuff, and kept iterating until it finally started looking decent.
• u/johnwheelerdevscore 0
  Yeah, really solid work man. I've been doing this for a long time and like I said, got me a little green. It really just goes to show in this new world, experience so much isn't the differentiator as is taste and where you source that taste from doesn't really matter --if it's from a competitor or whatever. It's noticing the details that matters.
• u/Head-Bench6270score 0
  I appreciate it man, I was actually pretty scared to share it. I don't know if you still get this but I didn't want to spend money on it in case there's an issue or bug or something that me or my friends didn't catch yet. But just on first impressions you saying that it looks like a engineer built it is calming my anxiety a bit haha
• u/Head-Bench6270score 0
  Also I say this in the post, and I think it's really useful information that more people vibe coding should do which is to have someone outside of yourself test the app, I think it's hard sometimes to properly vet your own work, so having someone that you know give a detailed breakdown of your project can be extremely helpful in tightening things up, you can ask AI to do it, and I have tried that in the past, but for the most part it's just a waste of tokens from my experience. /codex-adversial-review for every single plan is also really helpful, I would recommend people implement that into their vibe-coding workflow
• u/Head-Bench6270score 0
  Since people have been asking of how I made the video I'm creating a detailed breakdown of how I made the video. Use Chatgpt Image 2 for Image Generation (I've found it's better than nano banana at this type of image generation). Prompt claude code on your project to use pupeteer/chrome mcp tools to take screenshots of the most marketable/useful features of your website Take those screenshots upload it to chat, ask chatgpt to create professional grade asset images of the screenshots you made. (get 1920x1080 and 1080x1920 versions of those assets as well, chatgpt can pretty easily generate multiple variations using their in-built edit tool) Upload those generated assets to chatgpt and ask it to create a google veo omni prompt with @ in the prompt calling upon each asset to create a professional video promotion. Use those new generated assets upload it to google flow. Add the prompt and generate x4 versions for each different asset, there will 100% be some generations that are a lot better than others so getting a variation is good. If you don't have a lot of credits try going x1 to start to see if it's generating as you like, make sure to review the prompt that's created beforehand and adjust accordingly if there's anything missing. That's pretty much the workflow

Original on Reddit: https://www.reddit.com/r/vibecoding/comments/1ujvrit/i_vibe_coded_a_roofing_ai_app_and_somehow_its/ — “I vibe coded a Roofing AI app and somehow it’s becoming a real product”

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 →