1
82 Comments

A month in: what actually worked vs. what I wasted time on

Launch (PH): silence. Posting everywhere: mostly silence. Chasing other builders in comments: some good conversations, zero buyers — makes sense, they're building too, not searching for a solution.

What actually moved something: stress-testing my own product before pushing it harder (found a real bug — 4/6 test emails mislabeled), then answering real, zero-competition questions on Quora where people are actively searching, not scrolling.

Still no confirmed sale. But for the first time this month, I know exactly which channel is worth doubling down on and which ones were just noise.

Free cheatsheet with the corrected prompt if useful: https://payhip.com/Noxoro

on September 23, 2026
  1. 1

    Good point. Did you test that with users before committing to it?

  2. 1

    Solid lesson. Which channel has worked best for you so far?

  3. 1

    Solid lesson. Which channel has worked best for you so far?

  4. 1

    Thanks for sharing the numbers, that makes it much easier to follow.

  5. 1

    Appreciate the honesty here, most people only share the wins.

    1. 1

      Thanks! I think the failures are often more useful to share than just the wins. I’m trying to document what actually worked, what didn’t, and what I’m changing because of it.

  6. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  7. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  8. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  9. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  10. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  11. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  12. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  13. 1

    Really relatable. How much time do you put into this each week?

    1. 1

      It varies quite a bit, but probably around 10–15 hours a week at the moment. Most of that is testing, distribution and talking to people rather than building.

  14. 1

    Thanks for sharing the numbers, that makes it much easier to follow.

    1. 1

      Glad it helps. I’ve started tracking the numbers more closely because otherwise it’s very easy to confuse “I’m getting attention” with “this is actually working.”

  15. 1

    Really relatable. How much time do you put into this each week?

    1. 1

      It varies quite a bit, but probably around 10–15 hours a week at the moment. Most of that is testing, distribution and talking to people rather than building.

  16. 1

    Interesting. How are you measuring whether it is working?

    1. 1

      Right now I’m mainly looking at qualified conversations, people actually trying the cheatsheet, and whether anyone is willing to pay. Traffic and impressions are useful, but they don’t mean much without those actions.

  17. 1

    Solid lesson. Which channel has worked best for you so far?

    1. 1

      So far, Quora has been the most promising. Not because it’s driving huge numbers, but because the people I find there are already looking for solutions to the exact problem I’m working on.

  18. 1

    Really relatable. How much time do you put into this each week?

    1. 1

      It varies quite a bit, but probably around 10–15 hours a week at the moment. Most of that is testing, distribution and talking to people rather than building.

  19. 1

    Clear and practical, thanks. Did anything surprise you along the way?

    1. 1

      Definitely. The biggest surprise was realizing how different “being visible” is from actually reaching people who have the problem. I expected posting more to eventually lead to interest, but the useful conversations came from people already asking about email overload and workflow problems. It also surprised me how much I learned from stress-testing the product itself, especially finding that 4/6 test emails were being mislabeled.

  20. 1

    Solid lesson. Which channel has worked best for you so far?

    1. 1

      So far, Quora has been the most promising. Not because it’s driving huge numbers, but because the people I find there are already looking for solutions to the exact problem I’m working on.

  21. 1

    Thanks for writing this up. Bookmarking it for later.

    1. 1

      Thanks, hope the next update is a little more interesting than “still no sales” 😅

  22. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  23. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  24. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  25. 1

    Makes sense. Are you planning to charge for it, or keep it free for now?

    1. 1

      The cheatsheet will stay free. The full product is paid, but right now I’m more focused on seeing whether the problem is actually painful enough for freelancers to pay to solve.

  26. 1

    Nice progress. What is the next thing you are focusing on?

    1. 1

      Getting 3 freelancers to actually try the free cheatsheet and tell me honestly whether inbox triage is a problem they’d pay to solve. That feels more useful right now than adding more features.

  27. 1

    This is useful. How are you finding your first users so far?

    1. 1

      Mostly by going where people are already talking about the problem. Quora has been the most interesting so far because people are actively looking for answers rather than just scrolling past another product post.

  28. 1

    Thanks for sharing the numbers, that makes it much easier to follow.

    1. 1

      Glad it helps. I’ve started tracking the numbers more closely because otherwise it’s very easy to confuse “I’m getting attention” with “this is actually working.”

  29. 1

    This is useful. How are you finding your first users so far?

    1. 1

      Mostly by going where people are already talking about the problem. Quora has been the most interesting so far because people are actively looking for answers rather than just scrolling past another product post.

  30. 1

    How did you decide this was worth building in the first place?

    1. 1

      I saw a pretty clear problem around email overload and forgotten follow-ups, but honestly, I’m still validating whether it’s painful enough for people to actually pay to solve. That’s what I’m focusing on now.

  31. 1

    Interesting. How are you measuring whether it is working?

    1. 1

      Right now I’m mainly looking at qualified conversations, people actually trying the cheatsheet, and whether anyone is willing to pay. Traffic and impressions are useful, but they don’t mean much without those actions.

  32. 1

    This is useful. How are you finding your first users so far?

    1. 1

      Mostly by going where people are already talking about the problem. Quora has been the most interesting so far because people are actively looking for answers rather than just scrolling past another product post.

  33. 1

    Thanks for sharing the numbers, that makes it much easier to follow.

    1. 1

      Glad it helps. I’ve started tracking the numbers more closely because otherwise it’s very easy to confuse “I’m getting attention” with “this is actually working.”

  34. 1

    What made you pick this stack over the alternatives?

    1. 1

      I wanted to keep the product as simple and accessible as possible, so I went with tools that don’t require users to install anything or pay for another subscription. The goal was to solve the workflow problem, not create another complicated system.

  35. 1

    Clear and practical, thanks. Did anything surprise you along the way?

    1. 1

      Definitely. The biggest surprise was realizing how different “being visible” is from actually reaching people who have the problem. I expected posting more to eventually lead to interest, but the useful conversations came from people already asking about email overload and workflow problems. It also surprised me how much I learned from stress-testing the product itself, especially finding that 4/6 test emails were being mislabeled.

  36. 1

    Clear and practical, thanks. Did anything surprise you along the way?

    1. 1

      Definitely. The biggest surprise was realizing how different “being visible” is from actually reaching people who have the problem. I expected posting more to eventually lead to interest, but the useful conversations came from people already asking about email overload and workflow problems. It also surprised me how much I learned from stress-testing the product itself, especially finding that 4/6 test emails were being mislabeled.

  37. 1

    My Friday pass is 30 minutes, max:

    1. Ending MRR / cash (no vibes)
    2. Three pipeline actions for next week
    3. Kill one thing that did not move anything

    If the review takes an hour, the system is the problem. I cut ceremony before I cut the product.

    Copyable version if you want it:
    https://eastwestkonnex.gumroad.com/l/friday-ops-checklist

    What do you refuse to track every Friday?

    1. 1

      Honestly, right now I don't track much on a fixed Friday cadence yet — still small enough that most of my signal comes from direct conversations rather than numbers. If I had to pick one thing to refuse to track though, it'd probably be vanity metrics like impressions; doesn't tell me anything about whether the actual problem I'm solving is real for someone.

      1. 1

        Direct conversations are the right primary signal at that size. The only number I forced myself to write down when I was still conversation-led: how many of this week's chats ended with a next date on the calendar. A chat without a next date usually means I was polite, not useful. Impressions can wait.

        1. 1

          That’s a really useful metric. I like the idea of tracking whether a conversation actually leads to a next step rather than just counting how many conversations happened. I’ll start tracking that this week.

  38. 1

    Clear and practical, thanks. Did anything surprise you along the way?

    1. 1

      Definitely. The biggest surprise was realizing how different “being visible” is from actually reaching people who have the problem. I expected posting more to eventually lead to interest, but the useful conversations came from people already asking about email overload and workflow problems. It also surprised me how much I learned from stress-testing the product itself, especially finding that 4/6 test emails were being mislabeled.

  39. 1

    Clear and practical, thanks. Did anything surprise you along the way?

    1. 1

      Definitely. The biggest surprise was realizing how different “being visible” is from actually reaching people who have the problem. I expected posting more to eventually lead to interest, but the useful conversations came from people already asking about email overload and workflow problems. It also surprised me how much I learned from stress-testing the product itself, especially finding that 4/6 test emails were being mislabeled.

  40. 1

    Nice, this makes a lot of sense. What's been the most surprising part of it so far?

    1. 1

      Probably that the platforms full of other builders (X, LinkedIn, even here to some extent) gave me conversations but zero buyers — makes sense in hindsight, everyone's building, not searching. The surprise was how much better a random Quora question with zero existing answers performed just by matching intent instead of audience size.

  41. 1

    This resonates a lot — how long did it take before you saw any real signal on it?

    1. 1

      Honestly, too early to say — started on Quora just today, so I don't have real signal yet, just the fact that the questions themselves have genuine search intent behind them (unlike a feed). Will know more once there's actual traffic or engagement to look at.

  42. 1

    Nice, this makes a lot of sense. What's been the most surprising part of it so far?

    1. 1

      Probably that the platforms full of other builders (X, LinkedIn, even here to some extent) gave me conversations but zero buyers — makes sense in hindsight, everyone's building, not searching. The surprise was how much better a random Quora question with zero existing answers performed just by matching intent instead of audience size.