# Daniel Reyes, Senior Engineer / Aspiring Indie Founder at Oportun (350 people) — read of Crodox, June 26, 2026

> "9 years writing Python APIs, three dead SaaS side projects, one 14-month-old who ate my last idea's launch window. I spend BART commutes reading indie hacker newsletters looking for the thing I actually build."

## How I got here

Someone in a Slack group I'm in (called Build Slow, a bunch of burned-out engineers with day jobs) dropped a link with zero context: just "seen this?" I opened it on my phone standing in the Embarcadero station. I expected a working dev tool. I did not get that.

## What I clicked first

The tagline "Extract components, not repos" hit immediately. I've wasted three hours this quarter trying to yank a charting component out of a client's monorepo to reproduce a bug. So that pain is extremely real. I scrolled expecting a download button or a VS Code Marketplace link.

Then the page shifted into scoring metrics and Fermi estimates and I had to reread the whole thing to understand what was actually being sold here.

## Where I paused

The "Honest disclosure" block stopped me cold: "we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations."

That's a genuinely disarming sentence. Most idea-validation products bury this or spin it. Here it's just sitting there in the open. I read it twice. Either this is a calculated trust move by someone smart, or it's a cover for the fact that nobody has validated whether developers will actually pay for this. Both things can be true at the same time.

## What I distrusted

The scoring axes are doing a lot of work here. "buyer clarity: 10/10" and "distribution ease: 10/10" feel like the scorecard was built to flatter the idea. If distribution were genuinely 10/10 for a VS Code extension in a crowded dev tools market, Wishdeal would have live customers already, not a Fermi estimate. The "financial upside: 1/10" is at least honest, but it makes the 10/10s feel like they're compensating.

Also: "Each extraction gets a unique URL. Perfect for code review, PR feedback, agent handoff." The "agent handoff" drop feels bolted on. Like someone updated the copy in March 2025 when every product needed an AI angle. If the agent handoff use case is real, I want to see what that actually looks like, not a three-word mention.

And the specifications are written in future tense dressed up as a table. There's no screenshot, no GIF, no 30-second Loom of the thing working. The spec says "One-click extraction" but I cannot tell if this exists or if it's a description of what the $99 code starter will eventually be.

## What would convince me

A two-minute screen recording of someone actually using the VS Code extension. Not a demo of what it WOULD do. Someone in a real TypeScript monorepo, selecting a component, and seeing the isolated output. If that video showed the dependency resolution catching something surprising (a circular dep, a forgotten utility import), I'd believe the pain is solved.

On the business side: I don't need a customer count. I'd take one conversation. A Reddit thread where someone said "I need this." A tweet the founder screenshot'd from a developer saying "I can't believe there's nothing that does this." Just one piece of evidence from outside the building.

## What I'd ask in an email reply

1. The VS Code extension is listed as a feature. Does it exist right now as a working extension I can install and test, or is it part of what the $99 code starter gives me to build?

2. You scored financial upside at 1/10, which implies lifetime customer value is low and it's probably a freemium or one-time thing. What's your actual monetization model assumption? Is this a $9/month subscription or a one-time $49 purchase, and how did you get to -$12,800 Year 1?

3. You say "includes only what runs" for dependency mapping. How does it handle components that import from a global store like Zustand or Redux? That's where every extraction tool I've tried falls apart.

## Verdict: on-the-fence

The pain is real and the disclosure is unusually honest. But I can't tell if I'm buying a strategy doc for an imagined product or a working starter kit, and that confusion is killing the conversion. Fix the hero section to make that clear in one sentence and I'd probably spend the $5 to read the dossier.

---
*Memo by skeptic persona, generated 2026-06-26T00:00:00Z. Studio breaks own self-grading loop.*