Quote:
Originally Posted by Custard7A
Invoicing: Can I expect simple electronic transactions, or will I be suppose to send out something by mail, should signatures be involved, etc? I've heard that some clients can refuse to pay after work is done, and that initial deposits from the client are commonly requested. Is that something I should be concerned with?
|
Depends on the client. If you're doing a small site for a person's hobby, sending them an email "hey, drop me the $50 for that last update" is going to work. If you're doing a business site for a company, they will often want a paper invoice in the mail against which they can write you a check. Always do a portion of the payment before, with final payment after the site is delivered, regardless of the client.
Quote:
|
Correspondence: I suppose most smaller-scale clients would be content with an online-only relationship, email or instant messanger? Would many clients want voice chat or phone calls? I like to reserve my phone for friends only. What about giving out address, or other personal details, would many expect that?
|
Again, tailor it to the customer. I can't frankly imagine an online-only customer, for me it was typically phone meetings to get the major components hashed out, then emails back and forth over details. If you run a business, yes you should expect to give out a phone number, a physical address, etc. I don't know about Aus, but here in the USA stuff like business licenses, etc, is all expected for such things.
Quote:
|
Getting Hired: Obviously I have no experiance with web development jobs, as I'm looking to get started. I'm self-taught, so I have no real-world qualifications either. I've made some projects for my own amusement, and innumerable tests during my learning, but I have very little to offer in the way of a resume. Do I have much of a chance like this?
|
Yes, a good chance if you are the type to "network". Small web site needs are all over the place, with folks looking for them. Connect with friends, "networking groups", and let folks know you're doing web sites, and I bet work will come your way.
Quote:
|
Pricing: A rather large question-mark in my mind, I have no idea what sort of pricing system I should be expected to use. Would it be time-based, per-page, maybe complexity-based? Is there a standard sort of pricing table? If someone could give me a referance to prices involved in this sort of thing it would be very helpful to me.
|
See what compares in your area. Folks want a fixed price, so they know the bottom line. So "$XX for the original site as agreed, and $YY/hour for changes or ongoing support" is typical.
Two items you didn't mention:
A Scope of Work is a document that you write, that describes what you are (and aren't) going to do for the money. It is your way to get something on paper that says "for $XX I will do this". Stuff like who's going to generate the graphics, who pays for ancillary purchased software, will form data be validated, who pays for and owns the domain name, the list can go on and on.
A contract is a document you both sign that says "I will implement this job according to the attached Scope of Work, for $XX. Payment will be rendered as follows" (and any other contractual stuff either party deems important, like delivery dates, etc).
Dave