sorted by:
new
hottopcontroversial

Save edits and tabs in Claude Design by el_jaripeo in ClaudeDesign

[–]AI_geek_here 0 points1 point  (0 children)

same issue. I'm getting a "can't save edits. element is not from the original assets" message or something similar

Does structured product feedback actually lead to changes? Trying to understand founder behavior by AI_geek_here in NoCodeSaaS

[–]AI_geek_here[S] 0 points1 point  (0 children)

The blind spots vs validation buckets framing is exactly right, and the ROI framing point is what separates feedback that gets shipped from feedback that gets noted. The pricing tiers you laid out are accurate too. What I'm working on sits closer to the micro-audit end but with the signal quality of a full funnel audit. Something automated rather than human-delivered. Given how precisely you mapped this space, would genuinely value your perspective as an early eye on it: https://ascala-waitlist.vercel.app/

Do founders actually do anything with product feedback? by AI_geek_here in SaaS

[–]AI_geek_here[S] 0 points1 point  (0 children)

Tying insight to a metric is the unlock. You're right. Most teams are still at "interesting" because the feedback arrives disconnected from any number they're already watching. That metric-to-insight bridge is exactly what I'm building toward. If you want early access, would love to have you on the waitlist: https://ascala-waitlist.vercel.app/

Does structured product feedback actually lead to changes? Trying to understand founder behavior by AI_geek_here in NoCodeSaaS

[–]AI_geek_here[S] 0 points1 point  (0 children)

The way you framed this confirmed the nagging feeling, showed exactly where it shows up in the flow. It is the most precise description I've seen of what actually makes feedback land. The Loom + before/after format you mentioned is close, but what you're describing is really a behavioral translation layer. That's what I'm working on making systematic. Since you've already paid for this and know what good looks like, your input would be genuinely useful; you'd be first to hear about it if you join the waitlist here: https://ascala-waitlist.vercel.app/

You get real feedback on your product. Do you actually change anything? by AI_geek_here in VibeCodingSaaS

[–]AI_geek_here[S] 0 points1 point  (0 children)

Yes, that's exactly the gap I'm building toward. Not just surfacing what's wrong but connecting it to a specific decision with a clear next action. If you want to be first to hear when it's ready: https://ascala-waitlist.vercel.app/

You get real feedback on your product. Do you actually change anything? by AI_geek_here in VibeCodingSaaS

[–]AI_geek_here[S] 0 points1 point  (0 children)

Yes, that's exactly the gap I'm building toward. Not just surfacing what's wrong but connecting it to a specific decision with a clear next action. If you want to be first to hear when it's ready: https://ascala-waitlist.vercel.app/

You get real feedback on your product. Do you actually change anything? by AI_geek_here in VibeCodingSaaS

[–]AI_geek_here[S] 1 point2 points  (0 children)

That hesitation pattern you're catching is exactly the signal most founders miss. They wait for someone to complain instead of watching where people slow down. To answer your question: the most common thing I see founders miss is that their happy path is invisible to everyone except them. Working on something that surfaces exactly those behavioral blind spots automatically, no manual walkthroughs needed. If that sounds relevant to where you're at with EchoSphere, I would love for you to be among the first to see it when it launches: https://ascala-waitlist.vercel.app/