Got my first freelance job :)

[DrJohnZoidberg]

Although I deal with a lot of basic web programming at my day job it is not really in my job description (I do it to make my life easier).

I officially have my first freelance project for a client, doing some custom php/js/mysql for an existing web application. Now to finish the project on time

How do you guys normally deal with delivering projects to clients and making sure there are no issues with payment? Do you want the money upfront? Do you do demos for the client and then ask for payment?

In this case I have said I would do the work and then allow him to demo it, then once he's happy I would ask for the payment and then deliver the source code.

What works best in your experience? Take note that I don't really have any portfolio, it's something I do as a hobby right now.

 

[nahoR]

In my experience:

1) First write up a specification document, detailing what the client wants/what you the project entails. Make them sign it.
This is important to protect you against the client saying "I want x", you building x, and then the client saying "When I said x I actually meant y". Also this protect you against spec/scope/feature creep. Client saying at the end or half way through "I want x + y" without renegotiating the terms. Together with the specification document is the acceptance tests procedure document, which states how you will prove that you fulfilled every specification.

2) Then you quote the client on the specifications, and they issue a statement of work for this project. Accept the quote and specifications.

3) You do the work

4) Show the acceptance test results to the client. Usely you will do the test with someone from the client that can verify it. Make them sign it

5) Deliver the binary with an invoice. Once they've paid, deliver the source. But in your case there are no binaries i guess

 

[deweyzeph]

I've been freelancing for years in the .NET world. I usually structure payments like this:

1st Payment - 33% of total fee upfront as a deposit

2nd Payment - 33% of total fee half way through the project according the deliverables in the specification document

3rd Payment - 33% of total fee on completion of project and all deliverables

Note, this all depends on having a good specification upfront with clear deliverables. If you do not have a clear spec with clear deliverables it makes it very hard to collect payment because believe me you will have endless arguments with your clients about what should or should not be included in the project deliverables.

 

[Noseworthy]

I've been freelancing for years in the .NET world. I usually structure payments like this:

1st Payment - 33% of total fee upfront as a deposit

2nd Payment - 33% of total fee half way through the project according the deliverables in the specification document

3rd Payment - 33% of total fee on completion of project and all deliverables

Note, this all depends on having a good specification upfront with clear deliverables. If you do not have a clear spec with clear deliverables it makes it very hard to collect payment because believe me you will have endless arguments with your clients about what should or should not be included in the project deliverables.

Thats 99% payment?

 

[sp4ceman]

biggest thing is the after sales support. especially with web. make sure you specify upfront how that works or expect a call every 6 months for the rest of your life

 

[deweyzeph]

biggest thing is the after sales support. especially with web. make sure you specify upfront how that works or expect a call every 6 months for the rest of your life

That's why it's so important to get the spec down right and to get it signed off. Once you've done everything according to the spec there can be no argument as to what is a bug and what a new feature request after the project is complete. Expect to fix bugs for free, but do not hesitate to charge extra for any further changes to the project that go beyond the scope of the spec.