Protect yourself: what prospects you need to watch out for
 

When you find a person offering to provide a project or ongoing work, watch out for these warning flags. They indicate a significant risk for the development team or coder.

I am fortunate to have learned these lessons not too late, but I wish someone told me these things when I got started.

I'm not saying every prospect is like this -- every situation is unique -- but things like this are very common and if avoided, save you both a lot of headache.

• Cloudy requirements, clear budget: If someone isn't clear on exactly what they want but list a budget, and after a few correspondences you can't get a hard picture of what you will be delivering, do not take on the project.
  
  Otherwise, you give the prospect an opportunity to add whatever they want as you are working -- with possibly no corresponding additional compensation, and if there is, it's a haggle and done at their discretion.

• Clear requirements, unclear budget: If someone is willing to give you a 10-paragraph essay on what they want but don't include congruently clear elaboration on compensation for the work (not even 3 sentences), giant red flag.
  
  It can even be said that this prospect has some disposition to not compensating you. It requires deliberate omission if the rest post is otherwise 100% crystal clear.
  
  This isn't always, but often done by aggressive low-ballers. They'll pretend to be tentative on their budget when they have a clear picture in mind or want to haggle down to $2.
  
  Their common defense to being unclear about budget is they don't want to be ripped off. Truth is, they are under no obligation to even work with you -- there are plenty of options for them. Simply steer far away.

• Code n' Dash: a.k.a. "Won't pay anything until I get the working product". This comes from a reasonable place... 10 years ago. This type of prospect is the one that will point to how many times they have been "ripped off" by programmer XYZ via PayPal placing no responsibility on themselves. There are several project platforms with Escrow services such as Elance and Freelancer.com.
  
  In these places, milestones can be set in a mediated enviroment and funds can be released based on progress. Have a web-accessible test board so the prospect in question can see what they are paying for live, and you don't have to release the code -- both of your needs are met.
  
  Anyone that can't agree to that is trying to rip you off, plain and simple. Stay away from these prospects.

• Easy Project, Ongoing Work, Et al.: Common passive-agressive lowballer tactic -- they will do some combination of a subtle note about how easy the project is, a $2 budget, and promise of ongoing work -- they might even joke with "more" money.

Buyers get adequate warnings about all the bad coders out there. It's only fair that coders are warned as well.

moved to General Articles

Very solid points.

I agree that many clients are unsure about the time and money it takes to do some projects, but I've also seen several "vbulletin gurus" over bid and under deliver on work.
I've suggested to those looking for work to look around, do background checks on your freelancers. And to those looking to provide work, to showcase what you've done, get recommendations if you can, be upfront and honest about what type of work you do best. For example, I don't care for graphics work; I mention that first thing and offer others who are graphics people to those clients so they can go check them out.

Good tips OP

It was meant to be in paid requests to be used as a sort of checklist like filburt's thread :(

I agree -- especially on the background checks and only providing services only where your absolute strengths are.

I just have few troubles with scam also, online business every day is getting much and much theives and hackers, facebook made it like hell...
Anyone online should now be more cautious than ever !

regarding payment, examples can be numerous also... like when you "agree" to do the job, the client comes with X reasons not to pay you the day it is signed, but have to delay it for anything possible... stop it. when someone want a project to be done, the first thing is to ensure to have the budget to do it, no matter the situations... no money no candy.

"my father died"... ok, but the money was supposed to be in your credit card anyway, and your father is not the holder...

"my kids need to eat"... yeah, mine too, and i was supposed to be paid by you to do so!

"the bank stopped my payment"... that's a no way possible... even in Bengladesh, the banks are not blocking you just because you pay someone else... that's where they do profits.

"my partners are unsure of your work and will not pay you right away"... ok, that's not of my business if you can't be solid in front of your partners... i deal with you and you only...

etc... there is so much possible situations where we, coders, get scammed... hopefully, we can release our stuff in other means if the work was interesting anyway.

I had a case like that some months ago (claimed that they did not have enough money to pay the bills ) and it was very annoying to listen to all their whining and excuses when the the time came to pay me for the work I did. They should think about it before they hire someone to work on their sites and not after.

In these days abounded devious tricks and techniques to trick users online projects have no basis
Therefore the user must be sure confidence in the company or person to make sure his credibility
Thanks vbresults :)

thanks for sharing it