Creator
New Contributor
User Power
Value/Post Ratio
78%
- Feb 25, 2023
- 18
- 14
I recently learned about a need/problem in my market, as two of my security freelancing clients wanted to hire me to help develop this security solution for them.
They are planning to develop the solution and make it open source. What's in it for them is that they will get the solution as well as good PR and possibly free contributions.
The price they were willing to pay for help with a part of the solution was $15k. They would then need to internally develop the rest of it, which would cost them ~$30-45k.
I preliminarily accepted their offer, but they are getting funding for it in ~6 months. So not closed yet.
I had some down time from freelancing gigs and did some research of the solution they are after, as well as its market. I ended up developing a working PoC of the whole solution just out of curiosity.
Now I haven't told my clients nor published the PoC. The source code I don't want to publish. I am not sure this PoC contains all the features they are after, but I am confident it contains the most important ones.
I am interested in turning this PoC into a product and charging monthly for its usage. My plan is to give this PoC with essential functionality for free, to discourage anyone from creating an open source solution for it. And then have a pro version with extra functionality and support for a monthly price.
Doing the math, it would make sense for my clients to use the $60k for monthly payments and get a working product with updates and support from day one. I estimated that the price would be ~$300/month, which would mean over 16 years of usage for their money. Then they wouldn't get the good PR though.
However, I am afraid how my clients will react if I suddenly show up with a full solution, when they had the idea that they would do the lion's share of it themselves. Im any case I need their feedback to add the extra functionality to the pro version.
Should I just release the PoC, let them know and then ask for feedback?
How does my plan sound? How should I approach my clients about this?
They are planning to develop the solution and make it open source. What's in it for them is that they will get the solution as well as good PR and possibly free contributions.
The price they were willing to pay for help with a part of the solution was $15k. They would then need to internally develop the rest of it, which would cost them ~$30-45k.
I preliminarily accepted their offer, but they are getting funding for it in ~6 months. So not closed yet.
I had some down time from freelancing gigs and did some research of the solution they are after, as well as its market. I ended up developing a working PoC of the whole solution just out of curiosity.
Now I haven't told my clients nor published the PoC. The source code I don't want to publish. I am not sure this PoC contains all the features they are after, but I am confident it contains the most important ones.
I am interested in turning this PoC into a product and charging monthly for its usage. My plan is to give this PoC with essential functionality for free, to discourage anyone from creating an open source solution for it. And then have a pro version with extra functionality and support for a monthly price.
Doing the math, it would make sense for my clients to use the $60k for monthly payments and get a working product with updates and support from day one. I estimated that the price would be ~$300/month, which would mean over 16 years of usage for their money. Then they wouldn't get the good PR though.
However, I am afraid how my clients will react if I suddenly show up with a full solution, when they had the idea that they would do the lion's share of it themselves. Im any case I need their feedback to add the extra functionality to the pro version.
Should I just release the PoC, let them know and then ask for feedback?
How does my plan sound? How should I approach my clients about this?
Dislike ads? Remove them and support the forum:
Subscribe to Fastlane Insiders.