Taking on remote contract work
-
I have an opportunity to take on some contracting work from a company I worked for years ago. I'm seeking work, so I've got time, I have the tools, but I'm not sure how to outline how to get paid for my time (rate of GBP 35) rather than artifacts. The customer clearly wants deliverables, which is fine, but how do I make sure I do not get shafted by things like scope creep. Anyone got good resources for things like * a contract outline, * free/cheap online project/collaboration tools * and any experience on doing work remotely. For instance I want to send an invoice at least every 2 weeks, but what is an acceptable payment period?
Conrad - The world waits for you to stick your neck out, it's not easy. But once you actually stand up, you do get noticed. http://www.plcsimulator.org/
-
I have an opportunity to take on some contracting work from a company I worked for years ago. I'm seeking work, so I've got time, I have the tools, but I'm not sure how to outline how to get paid for my time (rate of GBP 35) rather than artifacts. The customer clearly wants deliverables, which is fine, but how do I make sure I do not get shafted by things like scope creep. Anyone got good resources for things like * a contract outline, * free/cheap online project/collaboration tools * and any experience on doing work remotely. For instance I want to send an invoice at least every 2 weeks, but what is an acceptable payment period?
Conrad - The world waits for you to stick your neck out, it's not easy. But once you actually stand up, you do get noticed. http://www.plcsimulator.org/
Bill weekly on short-terms, NET 15 days. Deliver binaries only. Deliver full source after completion and payment. Remember, payment terms are negotiable. And if you use the word standard in your contract 99/100 times they will just agree to it.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
I have an opportunity to take on some contracting work from a company I worked for years ago. I'm seeking work, so I've got time, I have the tools, but I'm not sure how to outline how to get paid for my time (rate of GBP 35) rather than artifacts. The customer clearly wants deliverables, which is fine, but how do I make sure I do not get shafted by things like scope creep. Anyone got good resources for things like * a contract outline, * free/cheap online project/collaboration tools * and any experience on doing work remotely. For instance I want to send an invoice at least every 2 weeks, but what is an acceptable payment period?
Conrad - The world waits for you to stick your neck out, it's not easy. But once you actually stand up, you do get noticed. http://www.plcsimulator.org/
The easiest way to avoid getting shafted by scope creep is to bill by the hour. Of course, clearly defined objectives (in writing) with specific and unambiguous requirements (in writing) will help you avoid the other aspect of scope creep, a client who's unhappy that you're going to charge him more money since he changed the scope. The net 15 advice is excellent, and I recommend billing weekly until you reach a point of mutual trust. Including not only the hours worked but a report outlining what was accomlished with these hours is another good way to build client satisfaction. Regarding contracts, it's important to understand that their usefulness is limited to clearly spelling out expectations so that both parties (hopefully) understand exactly what they're getting. As a tool of legal enforcement, especially in your unfunded situation, they're useless. If you think that it's a magic tool that will generate money should the client refuse to pay as agreed, think again. In such disputes, he who can afford to pay his lawyer the longest wins. With this in mind, I prefer contracts that are brief and spelled out in precise but human readable form. For my speaking and copywriting work, I just use a simple letter of agreement as it accomplishes the same objectives without all the legal mumbo jumbo. If they want to screw you, a contract won't help. If they're sincere, a clear description of the agreement is all you need. This, coupled with weekly billing (at least in the beginning) helps you minimize your risk, i.e. the time you invest without payment. And by the way, if they hand you their "standard contract," don't be afraid to delete or change paragraphs that are inequitable. They may argue with you, but there's no such thing as a contract that's written in stone. In general, whether it's local or remote, sucess is all about building relationships. If you show an honest client that you truly care about giving them excellence for their money and are enjoyable to work with, you'll do just fine. Should your benevolent efforts not be matched on their end, walk away as soon as you realize it. Beyond that, it's just coding. :)
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes
-
Bill weekly on short-terms, NET 15 days. Deliver binaries only. Deliver full source after completion and payment. Remember, payment terms are negotiable. And if you use the word standard in your contract 99/100 times they will just agree to it.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
My 5, too. Good solid advice all the way around.
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Copywriting Services
-
I have an opportunity to take on some contracting work from a company I worked for years ago. I'm seeking work, so I've got time, I have the tools, but I'm not sure how to outline how to get paid for my time (rate of GBP 35) rather than artifacts. The customer clearly wants deliverables, which is fine, but how do I make sure I do not get shafted by things like scope creep. Anyone got good resources for things like * a contract outline, * free/cheap online project/collaboration tools * and any experience on doing work remotely. For instance I want to send an invoice at least every 2 weeks, but what is an acceptable payment period?
Conrad - The world waits for you to stick your neck out, it's not easy. But once you actually stand up, you do get noticed. http://www.plcsimulator.org/
-
For online collaboration - TeamViewer[^] ... works around firewalls/NATs out of box and on slow-speed connections... awesome tool.
I have also found http://www.pivotaltracker.com/learnmore[^] , I used this last year.
Conrad - The world waits for you to stick your neck out, it's not easy. But once you actually stand up, you do get noticed. http://www.plcsimulator.org/
-
I have also found http://www.pivotaltracker.com/learnmore[^] , I used this last year.
Conrad - The world waits for you to stick your neck out, it's not easy. But once you actually stand up, you do get noticed. http://www.plcsimulator.org/