4 ms·

I'm not interested in developing a product that's too slow to grow. And if it is, I guess there is no point in keeping the code closed. We are trying big moves

I'm not interested in developing a product that's too slow to grow. And if it is, I guess there is no point in keeping the code closed. We are trying big moves and changes. Some of them will work. Will see. At least my integration partners really want my codebase open source :-)

dangus 2y ago
My gut feeling first impression is that your integration partners probably want your code open source so that you give away all the value that you’ve worked to create. They are looking at their best interests, not yours. I’m thinking that you’re not looking at how to change the product to solve more customer pain and therefore grow, you’re just interested in dumping your work into open source, hoping it brings more attention to your company like a marketing campaign, and then you want to build a new fad product (AI, LLMs) in the hope that it will be your high risk high reward high growth moonshot. Just be careful because LLMs aren’t well-suited to every single use case just like Blockchain and Big Data (which is why I brought up those fad technologies that used to make VCs salivate).
- MarkinK 2y ago
  Yes, I understand. But we've created a value that's too slow to grow. It doesn't make sense.
  - dangus 2y ago
    Going back to the original question of the thread, it’s starting to sound more like a grieving process than an answerable question. How do you open source the code? You flip it from private to public. That’s pretty much it. Well, okay, maybe an over-simplification. If the business is small and profitable but it’s not growing how you’d like then I’d probably be more interested in selling it if it was me. I am not sure you will be able to sell it if the code is all open source.
    - MarkinK 2y ago
      > it's starting to sound more like a grieving process Why? No grieving. Many products in the world are not growing as fast as their creators would like – it is OK. We just try new things and see what happens. Like what if you put all the code on the net :-)
      - dangus 2y ago
        I said grieving because it’s like you made something that is “dead” but you think you can save it via open source, when in reality it may just be “dead.” (Or not, I don’t know) Though, I like what someone else brought up in another reply to you about pain/dream/fix. It’s very similar to what you learn in programs like Force Management training where they teach frameworks like MEDDPICC. Finding business pain, demonstrating negative consequences to build urgency, etc. I don’t know if this is something you’ve already done or if the sales approach has been more like “if you build it they will come.”
  - gortok 2y ago
    if I were you I'd seek to sell it instead of open-source it. "pivoting to adding value with LLMs on top" is very expensive from a COGS standpoint; and will complicate your business economics, not simplify them. You don't seem to have a problem where open-source is the answer; the problem you seem to have is you built a business and a business model you weren't intending to build; and you don't solve that by open-sourcing. You can solve that a myriad of ways, but none of them are readily solved by open-sourcing your product.
    - MarkinK 2y ago
      I agree, but I don't see any point in selling it. I'd instead post the code and use it in all my other businesses without depending on the buyer. Besides, there is still a market for Odoo and Zoho integrators, and I think we can try to gather some of these people around our product.
      - gortok 2y ago
        After having looked over your product's website (ozma.io), it feels like the issue may be more ensuring you're being seen by your target customer and solving a problem they have that entices them to use your product. Your product's website is very 'feature' oriented, and not very 'Pain/Dream/Fix' formatted. https://sharpen.page/jtbd/copywriting/pain-dream-fix-and-jtbd/ https://sharpen.page/jtbd/copywriting/pain-dream-fix-and-jtb...
        MarkinK 2y ago
        Interesting, thank you!

dangus 2y ago

My gut feeling first impression is that your integration partners probably want your code open source so that you give away all the value that you’ve worked to create. They are looking at their best interests, not yours. I’m thinking that you’re not looking at how to change the product to solve more customer pain and therefore grow, you’re just interested in dumping your work into open source, hoping it brings more attention to your company like a marketing campaign, and then you want to build a new fad product (AI, LLMs) in the hope that it will be your high risk high reward high growth moonshot. Just be careful because LLMs aren’t well-suited to every single use case just like Blockchain and Big Data (which is why I brought up those fad technologies that used to make VCs salivate).

MarkinK 2y ago
Yes, I understand. But we've created a value that's too slow to grow. It doesn't make sense.
- dangus 2y ago
  Going back to the original question of the thread, it’s starting to sound more like a grieving process than an answerable question. How do you open source the code? You flip it from private to public. That’s pretty much it. Well, okay, maybe an over-simplification. If the business is small and profitable but it’s not growing how you’d like then I’d probably be more interested in selling it if it was me. I am not sure you will be able to sell it if the code is all open source.
  - MarkinK 2y ago
    > it's starting to sound more like a grieving process Why? No grieving. Many products in the world are not growing as fast as their creators would like – it is OK. We just try new things and see what happens. Like what if you put all the code on the net :-)
    - dangus 2y ago
      I said grieving because it’s like you made something that is “dead” but you think you can save it via open source, when in reality it may just be “dead.” (Or not, I don’t know) Though, I like what someone else brought up in another reply to you about pain/dream/fix. It’s very similar to what you learn in programs like Force Management training where they teach frameworks like MEDDPICC. Finding business pain, demonstrating negative consequences to build urgency, etc. I don’t know if this is something you’ve already done or if the sales approach has been more like “if you build it they will come.”
- gortok 2y ago
  if I were you I'd seek to sell it instead of open-source it. "pivoting to adding value with LLMs on top" is very expensive from a COGS standpoint; and will complicate your business economics, not simplify them. You don't seem to have a problem where open-source is the answer; the problem you seem to have is you built a business and a business model you weren't intending to build; and you don't solve that by open-sourcing. You can solve that a myriad of ways, but none of them are readily solved by open-sourcing your product.
  - MarkinK 2y ago
    I agree, but I don't see any point in selling it. I'd instead post the code and use it in all my other businesses without depending on the buyer. Besides, there is still a market for Odoo and Zoho integrators, and I think we can try to gather some of these people around our product.
    - gortok 2y ago
      After having looked over your product's website (ozma.io), it feels like the issue may be more ensuring you're being seen by your target customer and solving a problem they have that entices them to use your product. Your product's website is very 'feature' oriented, and not very 'Pain/Dream/Fix' formatted. https://sharpen.page/jtbd/copywriting/pain-dream-fix-and-jtbd/ https://sharpen.page/jtbd/copywriting/pain-dream-fix-and-jtb...
      - MarkinK 2y ago
        Interesting, thank you!