That's why I don't take up freelancing... Even more so, not living from it, freelancing is a highly unreliable source of income. If you're lucky now, a client comes along and there are no problems, then there's no guarantee that in six months' time it will be the same.
There is no time limit in the rules, no specifics that one would want to read and settle down and not write a memoir on the forum.
And if you have these terms of confirmation separately negotiate with the customer and possible actions, without relying on arbitration?
How about if you talk to the client about these confirmation deadlines and possible actions, without relying on arbitration?
The most important thing for the customer is to receive the product, and in most cases the customer does not care what happens to his money after he has entered it, he thinks that he has already given it away, and he is not particularly interested in where it is (whether it is frozen or not). He is anxious to hurry to play his genius invention in the tester, and to start withdrawing money from Forex.
And everything should be very simple - there are rules, there are regulations. The developer must do what the customer wants, and the customer must accept the work. Well, this is ideal, of course.
And in general, my post has already solved the problem.
Thanks to arbitrage, for the prompt decision !!!
The most important thing for the customer is to receive the product, and in most cases the customer does not care what happens to his money after he has entered it, he thinks that he has already given it away, and he is not particularly interested in where it is (whether it is frozen or not). He is anxious to hurry to play his genius invention in the tester, and to start withdrawing money from Forex.
And everything should be very simple - there are rules, there are regulations. The developer must do what the customer wants, and the customer must accept the work. Well, this is ideal, of course.
But in general, my post has already solved the problem.
Thanks to arbitrage, for the quick solution !!!
A piece of advice for the future: as long as the work is not completed, give a closed code with restriction on work for N days. The one who is missing will come to you. And the one who is not missing will not even notice the restriction.
After last confirmation and payment to your account (seven days do not count) - give the finished work.
Advice for the future: Until the job is finished, give a closed code with a limit of N days of work. The missing person will come running to you. The non-missing one won't even notice the restriction.
After the last confirmation and payment to your account (seven days do not count) - give the finished work.
Hmmm...interesting, how to do this? The developer must hand over the finished work and source code and only then the customer accepts. And in general, I wrote a long time ago, that the responsibility for the time limit should apply to both sides. Try to delay the wages in the real world...The prosecutor's office is right there...And here the contractor, a working man and practically without rights.
Hm...interesting, how do you do that? The developer must hand over the finished work and the source code and only then does the customer accept. And in general it has long been written that the responsibility for the timing should apply to both sides. Try to delay the wages in the real world...the prosecutor's office is right there...and here the contractor, a working man and practically without rights.
I just made an agreement with the customer - I give him at once - without any picture-mockups - working code that can be tested, but it will work with restrictions. The functionality will be added in parts. Each part he can test, give his assessment / comments, and I will correct if necessary - it is a mutual work. At the last step I would give everything ready and without limitation. But the customers have never been away for so long either. They were always there at the time of handover. I was not even chasing delays - if one of us was late, so be it. A person sees that the work is going on, I see that the person is interested in quality, and I communicate every day. There are difficulties that need to be discussed and overcome. It takes time that is not foreseen. It has always been with understanding.
Therefore, giving the code with restrictions - its confirmation - payment - giving the code without restrictions has always been quick and without the hassles described here. But everything is consensual.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
I'm a developer, I only make freelance money on this site, I'm not looking for other work and don't want to, as I'm happy here and have enough to live on.
I have run into the following problem.
One of my regular customers has ordered a job from me and disappeared, disappeared for a month, but I completed the work. A month later, turning a blind eye to the almost fraternal relationship after many joint projects, I went to arbitration. And here I was in for a nasty surprise, if before you could read the answers from a live representative of the arbitration, now everything became fully automatic, without any live control from the arbitration. That is, the inscription "Wait until the Employer confirms the completion of the work" well, I was not satisfied, as the customer simply did not enter the work for more than a month. Well, that's alright, if we are patient and wait for another month... And now the customer shows up. HOORAY! It would seem..., but no, the client simply presses the "I do not confirm" button, without any explanation and disappears again. Buttons appear in my office:
- close the job again;
- cancel arbitrage;
- cancel the job and return the money to the client.
Of course, I also write to the client in the job and in person, but there is no response. Ok, I think the price of the job is not critical to me, I decide to cancel the job and return the money to the customer. But again, the same "rake" in the end: "Wait until the customer confirms ....". I am a patient person, not a meanie, I thought that it's ok, let the customer take the money back when he wants.
In the meantime, work is boiling over, new clients... new jobs. Another client, satisfied with the work done, writes that all is well, that we are closing the job and confirm the penultimate stage and that's it... I write that there is still a final stage to be confirmed by the customer, but alas... ...the trail goes cold... Well I'm still patient, 3 days later in arbitration, again "Expect...".
Meanwhile, the work continues. And once again, another customer, who does not know about the last stage, disappears with the finished work. So arbitration again.... and again "Stand by".
We could let it slide, but judging by the looks of things, the limit of 7 jobs will be exhausted sooner or later. And even a signature in each message (to remind the last stage for completion), and trial versions of products, and issuing source code only after completion - all this does not give a 100 percent guarantee that the customer will not disappear.
So what was the point of all that I wrote?
My suggestion is the following: we should write conditions of this automation of arbitration in arbitration rules, because automaton somehow doesn't work clearly. The rules are not specified in terms, there is no specifics that I would like to read and calm down and not write memoirs on the forum.
Thank you for your attention.