How to work with clients and payment

If you are using php then it is not so difficult,
you can publish the site in space that the client does not have access to and let the client see/test it, as with php the client will see only the html resulting from the php they cannot copy the files and "steal" it from you. All they will be able to do is "view source" and copy the html, which if the site relies on executing php scripts & databases won't be much use to them.
If the site has lots of graphics that you designed, put some watermarks on top of them for demo purposes.
You can also put together 2-3 pages & send them screenshots asking for their approval & a deposit before you continue.
Get them to sign a contract that says all the work is copyrighted by you and that they do not have permission to use it until you have received payment in full.

Good luck

Mika

Depending on the size and scope of the website I either ask for half or a third of the development estimate. It is a pretty standard practice. I also don't upload the finished site to the client server until I get receive what is due upon completion.

If you are looking for a sample contract I have mine online. Anyone is welcome to it, modify as needed. It has been reviewed by attorney's in Wisconsin, Iowa, and California.

This is the really tricky part about dealing with clients. I have always gone for a half half approach. Getting half of the estimated cost off them at the start of development.

A friend of mine made a VB app for a business and placed a timer function in it to countdown to the date final payment was meant to be made. As soon as this date triggered the function, the timer counteed down 90 days and at that point would disbale the functions of the program. Upon final payment , my friend then uploaded a file to terminate the countdown. That is a very sneaky way of ensuring final payment, however if this was true and the payment was late resulting in termination of the programs functions, I think my friend would have had some legal issues to face...

Always best to have the finished product in a development area, only open to testers and management, then as soon as payment is made, upload it to the production server.......

Likewise, I bill 50/50.

I actually upload the site and then bill my final 50%, thereby taking some risk. I have to keep some of my idealistic faith in folks. After all, they are taking a similar chance on the first 50%. I've yet to be burned.

On larger contracts, I've occasionally acquiesced to a 3 thirds schedule - beginning, middle, end. Just make sure that the "midpoint" is predefined.

When I bill in thirds I break it down into hours......

If it is a 120 hour project then

Payment one (the retainer) 40 hours @ $XX per hour
Payment two 40 hours of work @ $XX per hours is due after 80 hours of work is completed
Payment three....the balance.

This system works pretty good for me but I keep very detailed logs for the time I spend on each project. I use Open Air to manage my projects.

It is always better to create a proper contract along with full project/design specs and a partial payment, before you start any work. Otherwise, you are bound to have problems with most projects.