# Marcus Delgado, Co-Founder and CEO at Fleetly | read of Vibe Code Analyzer, June 19 2026 > 7 years in B2B sales at a mid-size logistics company, then 2 years ago I quit and built a fleet management tool for HVAC contractors using Bolt.new. Six people now. Talking to angels. I coach my son's little league on Saturdays and I still don't fully know how my own database is structured. --- ## How I got here Someone dropped a link in the "Non-Technical Founders" channel in a Slack group I lurk in. The message was "this might be useful before your next investor call" and I clicked it on my lunch break. I was specifically googling something last week about how to explain to an investor what happens when a new technician gets added to the system, and I ended up on a bunch of Stack Overflow threads I didn't understand. So the timing felt right. ## What I clicked first The paragraph that starts "You asked an AI to build your product. It delivered in days. But now when engineers ask you questions, you're lost." That stopped me. Literally described a call I had with a contractor last Thursday where I said "the system handles that" and then immediately prayed he didn't ask how. And this line: "When you pitch investors, you cannot articulate how your own app actually works." Yes. That is my life. I bookmarked the page before I even finished reading it. ## Where I paused The "Dual Reports: Founder + Engineer" section. That's the one genuinely interesting thing on this page. The idea that the same scan produces a jargon-free version for me and a technical deep-dive for a CTO I'm about to hire -- that is actually a real problem I have. I need to hand something to a technical co-founder candidate and also be able to walk an investor through it myself. If that actually works, I'd pay for it today. That's where I slowed down and started re-reading. ## What I distrusted Three things, in order of how much they bothered me. First, there's a line on the page that reads "Unsplash: Founder reviewing code architecture with clarity" -- that's the image caption. It is literally the alt text or the filename or something rendered as a caption. That is a production bug on a product page for a tool that is supposed to show me I can trust it with my codebase. Not a great first impression on credibility. Second, the scoring section. Midway through a product page I see "64/100 Adoptability," "$-12,494 Year-1 take-home (Fermi)," and "1 in 5 Meaningful-success odds." I stared at this for a solid 20 seconds. Those numbers are telling ME that this product is unlikely to make money and has a 20% chance of meaningful success. Why is that on the page? I eventually figured out this is a "startup idea marketplace" thing, where they're also trying to sell me the business idea, not just the tool. But that realization took work. If I'm a founder coming here with a pain, that section reads like the product is warning me it might not survive long enough for me to need it. Third, and this is the big one: "Honest disclosure: we don't have live customers on this idea yet." So the "Start Free Analysis" button -- does it actually run a scan? Or is that a form that captures my email? Because if I click that and it doesn't actually analyze anything, I'm done. That button is doing a lot of work on this page. ## What would convince me One real report. Show me what Fleetly's actual output would look like -- or something close. Pick a generic Node.js + Stripe + Postgres app similar to mine and show me the actual plain-English architecture summary it generates. Not a mockup screenshot with fake text. A real one, even if it's a demo app. I can tell the difference. Also: one founder quote with a company name I can Google. Not a logo. Not an anonymous testimonial. A name. "Sarah Chen, CEO of Parcelmint, used this before her Series A." That's it. That's the thing that would make me click the $5 unlock. ## What I'd ask in an email reply 1. When I click "Start Free Analysis," does it actually scan my code right now, or is that collecting signups for a beta you haven't built yet? I need to know if I'm buying a live tool or a roadmap. 2. The risk report claims it can identify "unprotected endpoints." How does it know what's protected? My auth is Clerk middleware -- does it understand context like that, or is it just flagging anything without a visible auth check in the route file? 3. The page says "under 90 seconds" for the scan. What's the ceiling? My repo is about 40,000 lines across 200-ish files. Does that change the estimate? ## Verdict: on-the-fence The pain section is the most accurate description of my situation I've read on any product page in the last six months. But I genuinely cannot tell if there's a working product behind this page or if I'm buying into an idea that someone is still building. If the "Start Free Analysis" button does something real, I would try it today. --- *Memo by skeptic persona, generated 2026-06-19. Studio breaks own self-grading loop.*