←back to thread

263 points 1ilit | 1 comments | | HN request time: 0s | source

One year ago I open-sourced my very first 'real' project and shared it here. I was a college student in my senior year and desperately looking for a job. At the time of sharing it i couldn't even afford a domain and naively let someone buy the one i had my eyes on lol. It's been a hell of a year with this blowing up, me moving to another country, and switching 2 jobs.

In a year we somehow managed to hit 26k stars, grow a 1000+ person discord community, and support 37 languages. I couldn't be more grateful for the community that helped this grow, but now i don't know what direction to take this project in.

All of this was an accident. But now I feel like I'm missing out on not using this success. I have been thinking of monetization options, but not sure if I wanna go down that route. I like the idea of it being free and available for everyone but also can't help but think of everything that could be done if committed full-time or even had a small team. I keep telling myself(and others) i'll do something if i meet a co-founder, but doubt and fear of blowing this up keeps back.

How would you proceed?

Show context
cduzz ◴[] No.43628295[source]
This seems like a really cool project.

Some observations...

First I'd get some legal advice for how to convert this idea / product into a thing that you own and have a stake in, but that's distinct from you. This means you'd be able to collect money and attribute that money to the product, you'd be able to sell it to someone else and walk away from it, etc. This legal construct is important; probably not _necessary_ but very useful.

You seem to have a reasonable community contributing to and using the project; that's your most valuable asset. Make up a brief roadmap of where you'd like to take the project in six and eighteen months, share that with the community. Think about how some projects, like Elastic.co, grew based on community feedback and how ultimately perhaps those companies felt they needed to change the company in ways that many in the original community disagreed with. There are lots of sides to that coin, and you as the founder need to think about how you'd want to develop the product.

Lastly, once you've got a clear accounting mechanism of how to track money from it and costs of it, you should just .... start asking people for money. "How much is a support contract worth for this?" "How much is it worth to you to focus on developing this feature instead of that?" Obviously -- be very cautious if people are offering money in exchange for fractional ownership of "the thing" but even that may be palatable... but make sure you've had someone representing your interests read the contract...

replies(1): >>43629134 #
admiralrohan ◴[] No.43629134[source]
Are you talking about incorporating a company? Why is this necessary at this stage before earning money? Can be a waste of money.
replies(2): >>43631524 #>>43632131 #
1. cduzz ◴[] No.43632131[source]
I'm suggesting that starting a project like this should involve consulting with an attorney and possibly an accountant.

It is important, generically, to be friends or at least have a relationship of some sort, with an attorney. This is all _really_ vanilla stuff and they should be able to assess the minimum requirements and financial outlay needed in less than 20 minutes.

You want to be very clear about what the thing is, where you stop and it starts, who owns it. If you're going to be taking money for doing the thing, you want to know how to pay taxes on it, and how to value it (now, when you create it, and later, in the event you plan on selling it).

Make a plan, talk to the attorney about the plan, and understand what steps need to be taken to protect yourself and the project.

You can certainly play fast and loose; it'll probably be fine. You may have to play fast and loose if you have no resources. But there are lots of people who have gotten very badly burned by not paying attention to the rules and fine print in the contract(s).

Examples of things going badly include Redis and CCR, just off the top of my head.