Contracting/Freelancing
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
If you go it alone, do not forget to charge for overhead. Stating out on your own is where the term networking comes in. My suggestion would be try consulting through an agency for a while, noting how the agency handles things. But that is just me. Good luck.
-
Richard MacCutchan wrote:
It never will; they expect the moon on a stick for a few dollars.
I've noticed that. I can't believe what they put on there for a budget less than $250. Even worse, they get tons of bids.
If it moves, compile it
loctrice wrote:
Even worse, they get tons of bids.
From people who immediately post in Q&A.
Binding 100,000 items to a list box can be just silly regardless of what pattern you are following. Jeremy Likness
-
loctrice wrote:
I don't know which term to use [contracting/freelancing].
They are basically the same thing; as a freelancer you would work for yourself by fulfilling a contract between yourself and your customer.
loctrice wrote:
I've no idea where to start.
Read Pete O'Hanlon's Articles[^] on the subject. Find out which agencies in your area deal with contract work. Try some local businesses to see if they have any requirements for freelance work.
loctrice wrote:
I've tried a website or two where you bid on jobs.
It never will; they expect the moon on a stick for a few dollars.
Binding 100,000 items to a list box can be just silly regardless of what pattern you are following. Jeremy Likness
Richard MacCutchan wrote:
It never will; they expect the moon on a stick for a few dollars.
If it makes things any easier, Vilmos has a stick[^].
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
Well...I have heard there's good money to be made down at the docks... doing..."favours" for sailors...
Every man can tell how many goats or sheep he possesses, but not how many friends.
And squrrie the squirrel went neep neep neep and they all went to bed.
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
All excellent advice. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
Very good advice.
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
Right on track!!!!
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
Get out there physically. Cold call on likely businesses, in person, with a portfolio. If you cannot face this, then you have small hope 'going it alone'.
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
It helps if you widened your contacts network. You usually do that by working on full-time jobs and making connections with companies that are client to the one you work for. There are several ways to know the right people, but in my point of view the easiest way to get in is to show off your good work. Once you know the right people, you can offer them services as a consultant/freelancer.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
If you work for an agency you are considered a contracted consultant. If you work independently you are a freelance consultant. Either way you are a consultant. As consultant you are a "mercenary" for the highest bidder. We have no loyalties except to our ourselves and our fellow colleagues. Those that show loyalties to a company are most often just shills for "the man" and have no reason to be a consultant. We are looked down upon by companies and somewhat envied by our peers who are still working as employees. Most agencies\recruiters are only interested in you as long as you can be billed out. However, if you work for an agency long enough you can develop fruitful relations with the recruiters since they know you are reliable. If you want to work independently you can do that as well through many agencies that will provide corp-to-corp contracting. As a consultant, you usually do not get sick-time or vacation pay, especially as an independent. You only get paid for the hours you are billed out for. However, there are agencies that will provide incentives such as holiday pay and 1-year bonuses. Some agencies may still pay for a standard 2-week vacation but I haven't heard of that in a while. Many agencies will not offer health-care benefits. However, there are good plans with the Freelancers Union that you can take advantage of. Single person coverage goes for about $495 a month and a family for about $700.00. These are decent rates when you consider the cost of health-care today. You can take advantage of this insurance whether you are an independent or a w2-contractor. I strongly suggest you join the organization and make a donation. It is worth it since they have done a lot for consultants recently. As an independent you will not be eligible for unemployment insurance so if you go this route, make sure you put away enough funds to get you through the lean times. If you are a contracted consultant with an agency you will most likely be a W2 so you will be eligible for unemployment insurance. Be prepared to work long hours at times while also studying. The best way to keep your skills intact is to do projects on your own either as open-source or for sale. Its a lot of work, I know but in the end you do not have the political connection to an employer which is what most of as consultants find the most offensive after many years in the field. As a result, you are not included in any of a company's frivolities, meetings, and what-not. Some may include you though but most won
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
Those web sites where you bid on jobs pay a meager wage. They're probably best for people living in Bangladesh or Bulgaria who are comfortable with lower wage expectations. If you live in the US, Dice and Monster have plenty of contract work. Hard to find jobs paying more than about $50/hr there even if you're pretty senior. In seattle, craigslist often has very good opportunities if you're the right fit. (I'm working today at a contract job I found on craigslist). This only works if you live in a city craigslist covers. The most successful contractors are very senior people with networks of contacts they draw on, or they have a project (a code library or application) that brings in some revenue that they work on between gigs. My personal experience is that looking on job sites is not a reliable means of finding jobs.
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
What's your specialty? Email me a resume and your strengths and favorite thing to build.
Jon Atkins jonatkins57@gmail.com
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
V. Good advice. what i would say is that when i checked out some 'bid' sites, the prices quoted by some developers (especially in asian countries where the cost of living is cheaper) were ridiculously low and not worth the bother if u wanna make a living out of them.