Again, great work!
56 karma · joined June 29, 2019
Again, great work!
One tip: Focus on the printed version of the templates too. It's as important as the websites themselves, if not more. Job applications never ask for a link; they always ask for a PDF. I already have a website for my CV (https://cv.luanmuniz.com.br/) and use it as a source of truth that I keep up to date. When I need to, I just print the website and send it to the place I'm applying for. It would be kinda pointless without this feature, because otherwise applications always expect a LinkedIn link, and automated systems aren't programmed to accept people having their own websites as CVs; it's either PDF or LinkedIn specifically.
Good luck and keep building!
I opened the site to try as a user and my experience went kinda like this:
The thing at the top immediately confused me. I couldn't tell what language I was looking at. Then I discovered that the "NO" button somehow switches the site to English. That alone made the product feel amateur. The site have a very strong half-finished vibe-coded feeling. I use AI heavily myself, so I'm not saying "AI = bad." The problem is that your target audience is technical. The people who understand why they would want an audit like this are also exactly the people most likely to think, "I could throw this into Claude/GPT myself." You need the implementation and the resulting analysis to demonstrate why they can't get the same result from a simple prompt.
Right now it does the opposite.
I generated a report. The presentation isn't great, but the bigger issue is that the analysis itself is technically wrong in several places. If you're auditing modern websites, you need a real JS-capable crawler/rendering step, structured extraction, separate analysis for different categories, carefully designed prompts/evaluators for each area, and an architecture that produces deterministic evidence for the claims in the report. A generic "send some HTML to an LLM and ask for an audit" approach isn't enough here.
Another big issue: Because of the vibecoded nature of the website, I assumed the locked parts of the report might simply be visually hidden because of how the rest of the application was implemented. I opened DevTools and, sure enough, the supposedly hidden content was already sent to the browser. Anyone remotely technical can retrieve the paid result without paying. Given your target audience, I suspect a lot of users will notice this.
Basically:
1. The UI makes me question the quality. 2. That makes me inspect the implementation. 3. The implementation confirms my suspicion. 4. That makes me distrust the audit. 5. Reading the audit then gives me technical reasons to distrust the actual product.
And that's a shame, because I actually think the basic idea has potential, the domain is great, and your pricing feels correct too for what you giving;
If I were you, I wouldn't throw the idea away. I'd stop adding features and rebuild the core audit engine until the report is good enough that a technical user reads it and thinks, "Okay, this caught things I wouldn't have caught with a couple of prompts.". Work on your technical skills first, seems like your marketing skills are WAY ahead of your technical skills right now, you should switch focus for a bit.
You're doing the right thing by building things, shipping them, failing, and learning from them. That's how you get better. But for this particular product, your audience has a very high technical bullshit detector, so the quality bar is substantially higher.
Good luck. Keep building.
Think like this: Most people do not complain when a YouTuber reserves a few seconds of their video for their sponsor if they are clear about it. Take Linus Tech Tips, for example, they even made it into a funny thing. But people hate YouTube for using your personal watch history and Google data to push ads in your face at inconvenient times and places, sometimes preventing you from actually consuming the content you were there in the first place for.
My suggestion: find the correct time and place for your ads, serve a specific purpose, and be clear it's an ad, dont try to blend in organically. That will change depending on your business, but that's my suggestion.
> To design the drone, the Northwestern team first used a computational model to generate roughly 20,000 drone configurations capable of stable flight. Then, they used artificial intelligence (AI) and optimization algorithms to repeatedly rearrange the drones’ major components, including a motor, propeller, circuit board, counterweight and batteries. [...] “The design process was fully automated,” Rubenstein said. “Then, when we were confident that a drone met all our criteria, we built it.”
This, I think, is the really interesting part. Not the drone itselfIn my humble opinion, what's going to say whether the "backslash failed" or not is the numbers and reviews after a few weeks. We shall see
Edit: After reading the entire article (Thanks, user with the archive link), there is a lot of unrealistic exaggerations used as arguments, like tickets being sold for 1K USD, which is just absurd, and writing like "I myself travelled about an hour-and-change round-trip only to not see it." which makes no sense. Honestly, that makes me question the actual truthfulness of the things written in this article as facts. That said, from a reasonable perspective, I think my original point is still valid.
It's super frustrating that this is the only option to realistically deal with this issue, since all stories end up the same way: The cloud company just saying "f* you, we don't care, pay up." and legal fees are always expensive :(