1
12 Comments

When Does a Side Project Deserve a Real Shot?

How do you decide when a side project is worth turning into a real product?

I keep coming back to this question.
A few users can be encouraging, but early excitement can also be misleading.

Do you look for repeated usage, paying customers, a painful problem, or something else before committing real time?

I’d love to hear the signals that helped you make the call—and the signs that told you to leave a project as a side project.

If you want to share a side project for context, you can also add it here: https://www.indieneed.com/submit

But I’m more interested in the decision process. What made you take your project seriously?

on September 22, 2026
  1. 1

    The test I'd trust is the one a buyer would use: would a stranger pay a multiple for it as it stands today? That forces you to separate recurring, verified revenue from launch-week spikes and your own unpaid hours, which is usually where early excitement falls apart. If the honest P&L only works when your time is free, it's a side project; if it still works with a hired operator's cost in it, it deserves the real shot.

  2. 1

    Interesting approach. What was the hardest part to get right?

  3. 1

    Curious how long it took before you saw the first real results?

  4. 1

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

  5. 1

    Interesting. How are you measuring whether it is working?

  6. 1

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

  7. 1

    Great breakdown. What feedback have you had from early users?

  8. 1

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

  9. 1

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

  10. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  11. 1

    Nice work shipping it. What has been the biggest challenge since launch?

  12. 1

    I’d look for evidence that gets stronger without founder energy: users return on their own, invite someone, or create a workflow or data investment that would be annoying to abandon. Payment matters, but a single paid request can still be custom work in disguise. A useful threshold might be three unrelated users repeatedly solving the same problem in roughly the same way, plus at least one paying without a special concession. The warning sign is engagement that disappears whenever outreach stops. How do you separate genuine pull from users simply being polite to the maker?

  13. 1

    This comment was deleted a day ago