Hacker News Reader

I'm wondering why you bothered to bring it to your company in the first place. I know it was built to address the specific need of your team, but it sounds like you want the freedom to sell it to a wider audience. It sounds like you protected yourself with how you developed the code, but why involve your employer now? Can you sell your product without using your current employer as customer #1? Are they going to be a paying customer?

View on HN

I originally looked at this as a need for our team which is why the company was involved in the first place, but as I developed the product and thought about it more, the idea evolved into seeing this as a need beyond just our company.

The reason I wanted to involve my employer now is because I want to test it in a controlled environment and see if it works/helps our team.

I'm not sure about selling the product, because my company policy claims that there can be no business ventures and freelance work conflicting or competing with their interests, which seems like standard protocol. This might technically make it a grey area, but I wouldn't assume that without legal guidance.

I have a good relationship with my company and would not make them a paying customer.

Reply on news.ycombinator.com