Answer the question
In order to leave comments, you need to log in
What can be done so that a remote freelancer cannot take away the idea of a startup and appropriate the site's engine/scripts?
Please tell me how to hire a freelancer so that:
1) there is no complete control over my project.
2) so that the freelancer could not apply for this project, that is, he could not "take away" the unique script engine, developments and ideas.
Sometimes you can just copy scripts, register a new domain and get a similar competing project. That is, copyrights will be violated, the idea will be stolen ...
But at the same time, the programmer, in order to write some kind of additional module for CMS, needs full access to the database, scripts and the server.
The freelancer is remote, that is, it will not work physically to control. At the same time, the idea of the project is very unique and in its own way is a serious startup with great potential and future.
Do not mess with remote work, but open an office and hire off. programmer's work and control ? What do you advise?
Answer the question
In order to leave comments, you need to log in
In 99.99% of cases, no one needs it.
Spend time on things that will really move your project forward, not on things that can create problems. This is how you increase your chances of success from critical to probable - by working with reality, not probabilities. Pay attention to what is and you can definitely do, and not to what may or may not happen.
The answer to the question is an NDA and a property sharing agreement (everything he does belongs to you, is your secret and cannot be replicated in any way, applied in a modified form, etc.). There are forms on google.
Another option is to start testing a niche and earn money from it in alternative ways, without your application. If you don’t know how, most likely you shouldn’t go into business at all. Until you find out (Google is at hand?) And you can't.
1.1. Divide the project into several subprojects.
1.2. One performer per subproject.
1.3. They don't have to know each other.
2.1. Conclude a development agreement with the transfer of exclusive rights.
2.2. Parts of the system are not particularly needed by anyone, an already working system is needed.
2.3. Turn off the paranoia and live in peace :)
Usually, remote freelancers don’t have the resources and experience to launch a project, so they would just launch it
. In general, I have never met a situation when a freelancer took and implemented someone else’s idea himself in seven years of active freelancing
1. The freelancer is in a different business. He is not interested in your risks that the project will not take off , but you need to invest (at least in promotion). If a freelancer is experienced, then he earns well anyway.
2. The "divide and conquer" method has been known for more than one millennium.
Divide the project into components, give different people to work.
What is more expedient and for reasons that narrow qualifications mean better work.
3. If the project is simple - it's easier, without even looking inside it - to rewrite from scratch than to understand the insides of someone else's project.
4. If the project is mega-complex, you will still need several narrow specialists.
5. The one who will combine a large project into a single whole is better to have at hand, and not remotely. Or that he was well known to you.
the idea of the project is very unique and in its own way is a serious startup with great potential and future
a serious startup with huge potential and future
- - -
Yeah, straight idea for a million. Stop being paranoid. Follow the agreements and do not throw the employee.
In short
1) Register the idea as know-how
2) Work with a freelancer under a contract (where it says that he has no right to copy and that's all)
2.1) NDA
Another elusive Joe :)
If you want, we will give you the source code and you will understand that the desire to poke around in someone else's and sell someone else's is not the easiest way. If you can sell - great, your money! When a freelancer sells your super-duper mega idea to at least someone - rejoice :)!
Divide and conquer - known since ancient times.
Order work in pieces from different people. Some parts are purely technologically even easily divided (frontend vs backend).
The one who collects, of course, must be a trusted person or co-owner. But the assembly operation against the background of the rest is not so time-consuming.
Pay is ok.
Then, even if he tries, he eats all the rats and capitulates.
And the lack of sites associated with the need for full access is compensated by their dignity - it is impossible to really hide the developments from downloading them by you.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question