My only regret is that I spent a lot of money on legal fees and the company ended up not being …
… My only regret is that I spent a lot of money on legal fees and the company ended up not being profitable so a lot of the work went to waste. But now I can re-use the structure again if I wish to create a new venture.
Long story short, I'm building a new product and will likely launch it as a yearly SaaS with a permissive license. I'm later in my career and am mostly building it for fun, but I think it has potential to be a good, small business that I'd have fun fiddling with for a long time.
I went through and set up the usual LLC, but was curious about how I could set it up to be a member or worker-owned company. Has anyone done anything like that from the beginning? Should I just worry about this later?
With licensing, the typical model has been to make your core permissive, and keep the hosting / billing application private. Has anyone made even that part of their SaaS open? I know that would make is really easy to fork the business, but was thinking something like a time-gated Functional Source License (FSL) might work?
I'm open to ideas. I don't see this discussed commonly on HN, so figured it w…
Direct replies available in this import. Original-language excerpts.
SN
snideHN
That's interesting, but I was thinking something possibly even farther. That the members of the co-op are the people that pay for the SaaS itself. Essentially the yearly fee is "dues" towards the organization.
I wish more people know about profit sharing interests.
I was a part of a startup that offered profit sharing interests. When I joined the profit was X and left it was Y. I received a check for my percentage of the growth in profit. It felt pretty fair.
There was a relatively direct incentive to impact the company bottom line and I didn’t have to wait for the company to exit to get compensated.