11
14 Comments

What can I do about this idea?

Hello Everyone,

I recently started to work on an idea that I would like to turn into a product. It all started with wanting to build a CLI tool, and now I have built a JavaScript version and am finalizing the Python version. They will be published for public use as modules or packages. The task of this tool is to fetch either issues or PRs from git and store them in a JSON file or text file (you will decide).

The main product is going to be the web version of this tool, with more features.
For example, The CLI can only export in two formats, but the web version will export more than that.

I currently need advice or contributions on how to market when I'm done building, any fun features to add, etc. I have nothing concrete for the web version yet because I am still wrapping up the CLI tools. Here are the repositories:

  1. JavaScript: https://github.com/lennyAiko/git-orca

  2. Python: https://github.com/lennyAiko/git-orca-python

Thanks.

on September 17, 2023
  1. 3

    Hi Lennox, while the idea is fine, I think it's better to concentrate on things that generate more business value if you are trying to do Indiehacking. I write about a lot of SaaS Ideas and you can checkout.

    But if you want to still work on this, you can further enhance this to a SaaS that can generate social content to share based on PR comments with a screenshot/related text so that it can help builders post it to social media in their buildinpublic journey.

  2. 3

    Hi Lenny, what is the use case of the product? Why would someone want to store their PRs/issues like this – and why wouldn't they use the existing github cli or api?

  3. 2

    Hey Lennox 👋

    My advice would be to identify your primary audience for your product, and speak directly to them. Show them what you're working on, get their feedback, find out what existing features align directly with their goals and pain points, and in that same breath, you should uncover problems that you're not yet solving, but could.

    Marketing is generally much more effective when the brand knows the value their product brings, through the problems it solves, for the audience it's made for.

    Good luck with it all!

  4. 1

    Great, i must say and thanks for sharing this informative post.I am really impressed that there is so much information about this subject that have been uncovered and you’ve done your best.

  5. 1

    Hey Lennox, What are the usage scenarios of this product?

  6. 1

    I thing that you should be aiming is word of mouth, as developer will often talk about how great and cool the tool they are using. ( you are developer I think you understand this ).

    Thats mean if you product is good and able to impress developers, it will have a good future.

    Reddit and twitter will be your main place to talk about this as most of these people will hangout here. And some forum out there where people are talking about programming will be a good place to try.

    Another method is maybe you can do "how to git" class for newbie and try to teach them from early on to use your tool, which as developer usually we stick to how we learn to do it.

    Alternatively you can also find anybody talking about learning programming and dm them if there want to use your tool.

    You can also try writing blog with good seo that is related to your tool. This will work very well if you do it right with right topic and keywords. would recommend to use creativeblogtopic.com to automate SEO research for your.

    If you want to learn more about acquiring customer from thin air, here are two things you can watch and read. The first one is a talk give by Kathryn Minshew founder of the Muse. And the second one is an article about tips to get customer out of nothing:

    1. Kathryn Minshew, Acquiring Your First Users Out of Thin Air, The Lean Startup Conference 2013
    2. Acquiring Your First Users Out of Thin Air
  7. 1

    Hey Lennox,

    I have some general advice, You can really opt for a design agency to do the UI part of your web application and see what fun elements can be added before the development phase.
    It will really help determine the look and feel of the application and it can be enhanced by UI.
    Also for marketing, once you have the basics of the web App clear you can start with short explainer videos.

    I hope this provides some clarity :)

  8. 1

    Hi Lennox! Some more general advice:

    • I am also an engineer and I completely understand the desire to jump directly into code when you have an interesting idea. However, after building a few products that no one cared about, I've realized that the quality of your engineering is not at all the determining factor for the success of your product (at least in the early stages).
    • I recommend that you follow a version of the "lean methodology", where you prioritize quick cycles of iteration combined with customer feedback. In short, build a small feature and validate if your potential customers want it.
    • These days I would even go a step further: when I have an idea that I think is "good", I reach out to my perceived ideal customer profile (I recommend determining this ASAP when starting a business) and act as if I've already built a version-0 (pre-MVP) of it. If they are interested in learning more and actually trying the product, you know that you have something worth pursuing.
    • Lastly, don't get discouraged! Entrepreneurship and especially indie hacking is very hard but I want you to remember something: "You cannot lose if you do not quit!"
      (I stole this last bit from Alex Hormozi lol, I recommend looking into him if you are interested in learning more about business + marketing)

    Hope this helps :)

    Parsa

    1. 1

      I would go further on this and say that DON'T follow lean and follow a more modern approach. Lean says to build an "MVP" and it's a small version of the full product you will build.

      The problem with this is that users now a days have gotten use to GREAT products like MACos Airbnb and Instagram to name a few. They have little tolerance for products (and even websites) that look like shit, load slow, or aren't fully functional.

      So what should you actually do - you should focus instead of Minimal viable product. to build minimal viable test (MVT's)

      These are small test that you run to the assumption that "this must be true for my product to work" you could be testing a specific feature all the way through and build one at a time.

      Do things that don't scale. Test ruthlessly. Quick iteration cycles. Mom test with users.

  9. 1

    I fail to see the value proposition in this.

  10. 1

    I fail to see the value proposition in this.

    It replaces a manual step of going to a PR on the web, with another manual step of fetching the PRs? What's the why? Why would people do this? Why would they use it?

  11. 1

    I think that's a GOOD Idea!

  12. 1

    So how do you expect people to give advice or contributions if you don't show anything ? Do we have to mentally imagine the all thing ?

    Pedro

    1. 1

      Apologies about that, I currently do not have something concrete for the web version, I only have repos to the CLI applications. I will add them to the post. Thanks for pointing that out.