October 10, 2018

I have the very first issue on Github and I'm happy. Now what?

Hello indiehachers,

today somebody posted the very first issue on my project (https://github.com/SaaS-Idea/saas-boilerplate) and I feel so happy. Why? Because I see the power of the community. People look into your code and find bugs, suggest improvements etc.! It's so impressive.

Now here is the question, how to make money.

My first idea was to create 2 versions of the product - one is for free and the second one is paid, it would have more functionality (like the integration of payment system). But now I have some doubts about it. First of all, it's not easy to support 2 different versions (I'm currently working alone). Secondly, the paid version would probably not have a feedback, or am I wrong?

I have a couple of ideas on how I would sell some services integrated into the project (scaffolding can be one of them) but generally, I'm still in doubts. Can you suggest some ways to monetize the open source project like mine?

Thanks!


  1. 2

    Fellow open sourcer here :) Congrats on getting your first issue, I think I've got a bit to go before I get there.

    I do find it a bit strange that you're offering a SaaS boilerplate, but your license says you can't use it for commercial purposes.

    Here's some ideas (some I'm planning to do for my project, others just off the top of my head):

    • SaaS your saas haha. Provide a hosted solution that gets them up and running quickly.

    • Offer a one-time install for a fee.

    • Affiliate programs for various services (you mentioned e-mail and postgresql services in your repo).

    • Build a plugin architecture, so you can build add-ons and sell them individually.

    • Likewise, if the project lasts a while, you could end up building plugins that make it possible for certain types of SaaS to be built without requiring a developer. Think specific niches like bookings, forums, etc.

    • Partner with a template provider you like to Vue-ify the templates and sell them as plugin themes.

    • Provide a bigger architecture like saas landing page/site + your saas boilerplate for a better quick start.

    • Provide additional dev services.

    • Donate button.

    • Build a community site or area to get direct feedback, let people work together, and find ideas for paid services based on common discussion points.

    Good luck!

    1. 1

      SaaS your saas haha. Provide a hosted solution that gets them up and running quickly.

      I'd love to see if there's a way we can work together on this part @Zencentric

      1. 1

        I don't know! What is your proposal?

    2. 1

      Hi,

      thanks a lot for a great feedback.

      I do find it a bit strange that you're offering a SaaS boilerplate, but your license says you can't use it for commercial purposes.

      Have you found it strange because SaaS is a commercial product by nature, or there is another reason? I did it just to restrict using - like you can try before you buy it. You think, I'm wrong?

      Here's some ideas (some I'm planning to do for my project, others just off the top of my head):

      Thanks for your ideas! Many of them I have in my list, some are pretty new.

      1. 1

        I too find the licensing strange. I was expecting more like a lite version and a full featured paid for version.

        1. 1

          Yeah... I see your point. It makes sense, thanks.

      2. 1

        Ah, I think it just wasn't stated up front so I assumed it could be used for anything. I only noticed the license section because I looked for a LICENSE file to see which oss license you chose :)

        1. 1

          Right. I probably will review it. Thanks.

  2. 1

    You could implement it as a PaaS- get people to pay you to host it for them

    1. 1

      Thanks!

      I thought about this too...