10
29 Comments

A stranger used my product today and didn't sign up. I'm counting it as progress.

A few weeks ago, I would've looked at today's numbers and called them a failure.

A handful of visitors.
No new accounts.
No revenue.

But something different happened.

Someone I didn't know found one of my posts, opened Ashive, went through the onboarding, hit the signup wall, and then took the time to tell me exactly where they got stuck.

No signup.

No payment.

Just feedback.

The interesting part is that the feedback immediately changed how I'm thinking about the product.

Before this, every opinion about Ashive came from me, friends, or people I already knew.

This was the first time a stranger interacted with it and showed me the gap between what I intended and what they experienced.

It made me realize something:

As founders, we often treat signups as the only signal that matters.

But before signups come understanding.

And before understanding comes observation.

Today I learned more from one person getting stuck than I did from thousands of content views.

Curious how other founders think about this.

At what point do you start counting feedback itself as progress?

on June 19, 2026
  1. 1

    Same kind of week here. A contributor opened a PR against my project's repo without me ever reaching out to them — felt like a bigger deal than anything from my Product Hunt launch. Small, unprompted signals like that seem to be the realest kind of validation, even if they don't move any dashboard number.

  2. 1

    This is such an underrated milestone.

    The first stranger who uses your product and gives real feedback often teaches you more than weeks of building in isolation.

    That's definitely progress.

  3. 1

    This is the right way to think about it. The signup is a trailing indicator — it measures trust, not value. Someone staying long enough to not sign up means they found the product real enough to try.

    I had a similar moment: checking session recordings and seeing a user who went through BugCapture's full flow, exported the markdown file, then left without creating an account. First instinct was 'failed conversion.' Then I realized: they got exactly what they came for. The tool worked. The conversion problem was that I hadn't given them a reason to want an account beyond the first use.

    A stranger using your product without signing up is a signal. The question worth asking is: what would make them want to come back?

  4. 1

    Honestly, a stranger using your product is validation in itself.
    Signups tell you people are interested.
    Usage tells you the problem might actually be real.
    I'd rather have 1 stranger try the product and leave than 100 friends tell me it's a great idea.

    1. 1

      Haha yeah, I agree on that too

  5. 1

    This is the right way to count it, and you already named why: a stranger getting stuck and telling you where is worth more than a thousand passive views, because it's the first time the gap between what you intended and what they experienced became visible. I'd go one further on your question of when feedback counts as progress. For me it started counting the moment the feedback came from someone who actually felt the problem, not someone being polite. A friend tells you it's nice. A stranger who hit the wall tells you exactly where the product failed them, and that person has no reason to soften it. That's the signal. The signup is downstream of getting that gap closed, so closing it is the real progress, and you just got handed the map for free. The one thing I'd watch: that person told you where they got stuck, which means the wall came before they understood the value. Worth asking whether the signup wall is sitting one step too early in the flow.

    1. 1

      That last point is actually the part I've been thinking about the most. My first reaction was maybe the signup wall is too early. But the more I think about it, the more I wonder if the real issue is exactly what you described which is that they haven't understood the value yet.

      The feedback I got wasn't I hate creating accounts, it was more that they wanted to keep going before committing. I'm trying to figure out whether the fix is moving the wall, removing the wall, or making the value clearer before someone reaches it.

      Have you run into that problem in your own products before?

  6. 1

    This reframe is something I needed to read today.
    I’ve been so focused on waitlist signups as the only metric that matters that I almost missed what the actual early signal is — someone caring enough to tell you where they broke.
    A stranger completing your onboarding and then writing you feedback is honestly a stronger signal than a signup. Signups can be curiosity. Detailed friction feedback is intent. That person wanted it to work.
    I’m in early validation right now and I’ve started treating every unsolicited response — even a “this confused me” — as a green flag. It means the problem is real enough that someone invested their time past the point of confusion.
    The progression you laid out — observation, then understanding, then signup — that’s the actual funnel nobody draws.
    How did you reach out back to that person? Did you close the loop with them? Those first strangers who give real feedback are worth treating like gold.

    1. 1

      Honestly, I didn't, and I kind of regret it.

      At the time I was so focused on the feedback itself that I forgot to investigate the behavior behind it.

      The weird thing is that after posting this, multiple founders asked me the same question: "Did you ask why they left?"

      And the answer was no.
      That was probably the biggest lesson from the whole interaction.
      Now I'm much more interested in understanding the drop-off than counting the visit.

  7. 1

    I had something similar with zer0email . Someone connected their inbox during onboarding, saw the auto-labeling kick in, then dropped off right before setting up their first routing rule. Turned out the rule builder assumed people already knew what they wanted automated, when most people connecting an email tool for the first time don't have that figured out yet. That one drop-off point told me more about the actual gap between "this looks useful" and "this fits my workflow" than any amount of traffic would have.

  8. 1

    That first anonymous use is underrated signal. For Kinetic Override I’m trying to separate curiosity from fit: if someone lands from “Android auto clicker” but bounces, the problem may be trust/permissions; if they land from “record tap sequence” and stay, the macro-recorder wording is probably doing its job.

  9. 1

    This is an underrated insight.
    Most founders treat signups as signals.
    But often the strongest signals appear before the signup.
    A user getting confused. A user hesitating. A user asking the same question others have asked before.
    One person getting stuck might be random.
    Ten people getting stuck in the same place is a pattern.
    And patterns are usually more valuable than metrics because they tell you why the metric exists.
    I'd count meaningful feedback as progress the moment it starts repeating.

    1. 1

      Yeah, I think that's what I'm starting to realize.

      Before this I'd mostly look at whether someone signed up or not. Now I'm paying way more attention to where they hesitate or stop.

      The challenge for me is figuring out which signals are actually patterns and which ones are just one person's preference.

      1. 1

        False positives are dangerous because they create confidence without understanding.
        One signup can validate a channel. A repeated friction point can validate a problem.
        The second signal is usually more valuable.
        TruthLoop AI — Find what you're avoiding.

  10. 1

    I’d count it as progress when the feedback changes the next test you run. A stranger getting stuck is useful, but the real signal is whether the friction maps to a repeatable pattern: unclear promise, too much setup, missing trust, or wrong timing. I’d turn this into one follow-up question and one product change, then watch whether the next stranger gets stuck at the same point. That gives you learning without pretending feedback is the same as demand.

    1. 1

      That's fair.

      I think my mistake was treating the feedback itself as the win.

      The real test is whether the next few people run into the same friction.

      If they do, then it's probably a product problem and not just one person's opinion.

      Thanks for your thoughtful reply

  11. 1

    The framing shift from "signups" to "understanding" is the right one, especially early. A signup from someone who doesn't understand what they're using is actually worse than a non-signup with a clear explanation of where they got stuck, the first one gives you a false positive, the second one gives you a map. Sounds like you got the more valuable outcome today.

    1. 1

      That's an interesting way to look at it.

      I was definitely treating the signups as the main goal.

      But you're right, someone explaining exactly where they got stuck probably gives me more to work with than a signup that never becomes active.

      1. 1

        Exactly. And the frustrating part is that the "false positive signup" actively hides the problem, your metrics look okay, nobody's complaining, but the real issue is just invisible. At least when someone gets stuck and tells you, you know what to fix.

        1. 1

          Yeah, that's probably what scares me the most tbh.

          A bad metric is obvious.
          A metric that looks okay can make you think everything's fine when it isn't.

          Right now I only have one person who mentioned the signup friction, so I'm trying not to jump to conclusions yet. But it's definitely something I'll be paying attention to with the next few visitors.

  12. 1

    The "before signups come understanding, before understanding comes observation" line is the whole post. Most founders treat feedback as a worse version of signups, when its actually the earlier version of them - just denominated in a currency we havent learned to value yet.
    Im in the exact same spot rn with my own thing - low signups, zero paid trials, but 3-4 strangers have taken the time to tell me where they got confused. A month ago id have called that a failure. Now i realise its the only signal that compounds. A signup tells u someone clicked. A stranger writing 5 sentences abt where they got stuck tells u why everyone else didnt.
    To ur question - imo feedback counts as progress the moment u stop being defensive about it. Thats the actual leading indicator, not the count of comments 🙌

    1. 1

      Thanks for your insight and honestly, looking back, I'd definitely call this a failure before because at the end of the day, they js visited, give feedback and left. No signups, no revenue or etc. But the more I realize now, the feedback itself worth more than random sign-ups that didn't give me anything to learn from.

  13. 1

    You really should investigate why they didn't sign up

    1. 1

      Yeah, that's fair.

      I was so focused on the fact that someone actually used it that I forgot to ask why they left. Looking back, that's probably the more valuable thing to ask.

      Thanks for your reply

  14. 1

    I'd rather have one stranger explain why they didn't sign up than five friends tell me the product looks great. Honest friction is usually more valuable than polite encouragement.

    1. 2

      I agree,

      The onboarding feedback I got yesterday was probably more useful than weeks of people telling me the idea sounded good.

  15. 1

    I've readed this story and it looks good
    can you add it to https://dev.us.kg/t/stories

    1. 1

      Thanks, man.

      Wasn't expecting anyone to find the story useful, I'll check the website later

Trending on Indie Hackers
I got my first $159 in sales after realizing I was building in silence User Avatar 52 comments Three Days Before Launch, I Let My Own Tool Tear Me Apart User Avatar 37 comments I thought I was building a news visualization tool. Users thought it was a catch-up tool. User Avatar 34 comments I got tired of rewriting the same content for 9 different platforms. So I built Repostify. User Avatar 30 comments I Rejected a $15K Acquisition Offer for My Multi-Agent IDE — Here's the Full Breakdown User Avatar 28 comments A pattern I keep seeing in EdTech: traffic isn't usually the problem. User Avatar 23 comments