Forum Moderators: LifeinAsia
Although you should have probably given more time for the project, you weren't given what you asked. The freelancer was confident he/she could get the job done.
Should you still pay the freelancer? A reduced rate? Full hours worked?
Thanks for any advice.
M
How much of the work is salvagable? How much will you have to pay someone else to complete the job? Or is it a complete wash since it wasn't completed? Are you taking any kind of financial hit because you didn't deliver a finished product on time?
Why was such a short amount of time given to complete the project? Was that from procrastination on your part or his?
Although you should have probably given more time for the project
Be a mensch.
Pay up, and/or work out a fair compromise.
You know that you "probably" should have given more time for the project. Sure, you've gotten him on a technicality, but you know that you are also at fault.
How did you complete the job? Or did you? Was he not available after the 6 hours were up? Did you just revert and now you have to start over again?
A little more detail would be helpful.
Should you still pay the freelancer? A reduced rate? Full hours worked?
Depends what kind of contract you have.
Did you:
a) Contract on a per hour basis (in which case you have a moral and legal obligation to pay them in full - but no obligation to use them again in future).
or
b) Contract on a project basis, i.e. "we'll pay you $x to complete this project", in which case you don't have an obligation to pay them in full if they didn't complete the work.
That's how I see it, anyway.
If you don't *know* what kind of contract you've made with them - because it was all very casual and didn't go into detail - then my judgement would be that you should pay them in full (and make sure to get a written agreement in future specifying exactly what you're paying them for). But in this case it's a judgement call and reasonable people could well disagree.
hth, a.
It's the risk they take when they offer more then they can deliver
It's also the risk you (the person hiring) take when you don't plan your projects out carefully and demand something spectactular in a few hours...(and an all nighter at that)...
...work out a good faith payment and send him/her on their way...keep some goodwill alive as you move forward...this can bring some serious dividends in the future as you work with others...
From what you posted I am guessing you expected all three, which is a reflection of your unrealistic expectations. Pay the person what you owe them. In the future, change your expectations. If you expect high quality work on a close deadline, be prepared to pay a significant premium. Else, give adequate leadtime.
WBF
By experience, I know that there are tasks that are easy technically speaking, but when you find out that either the code or the site structure you have to work on is nothing like you were expected, well, then the easy job becomes a total nightmare.
That's why I request a preview of the code I have to work on before accepting a job.
That's the kind of things you always learn the hard way.