Let me pose a scenario...
I do some web development for a paying client and deliver their finished product... everyone is very happy... lots of back-slapping and the invoice is paid. Several months later the client contacts me (because I seem to know about computers and the web) and asks why he can't see (say) google ad words or something (it's not really important exactly what... just the kinds of posts we get here regularly).
Judging by the replies in this (and other) forums... how long do you think the average computer professional is spending attempting to remotely troubleshoot problems like this? 1 hour? 4 hours? 1 day? More?
It appears these problems start as simple issues that get more and more complex as more and more things are tested in an attempt to fix the initial "simple" issue. It takes a lot of time online researching (sometimes) and it takes a lot of phone calls and emails between you and the client. Of course I don't have a service contract arrangement with the client... I'm just a web developer who did some work for them a while back.
So how do you charge for this? Do you just waive it as a cost of "keeping the client happy"? And if you do charge, how much do you feel justified in putting on the invoice? An accurate reflection of the hours taken to solve the issue? Do you even discuss this with them up front? If so... at what point do you break the conversation and start talking about money?
I'm never going back to technical support as a full-time career (did my time and moved on) but I know I will continue to be asked such questions until we successfully un-invent the computer. I'd appreciate any thoughts people have on the matter.
Cheers,
Jeff
[tt]Jeff's Page [/tt][tt]@[/tt][tt] Code Couch
[/tt]
What is Javascript? faq216-6094
I do some web development for a paying client and deliver their finished product... everyone is very happy... lots of back-slapping and the invoice is paid. Several months later the client contacts me (because I seem to know about computers and the web) and asks why he can't see (say) google ad words or something (it's not really important exactly what... just the kinds of posts we get here regularly).
Judging by the replies in this (and other) forums... how long do you think the average computer professional is spending attempting to remotely troubleshoot problems like this? 1 hour? 4 hours? 1 day? More?
It appears these problems start as simple issues that get more and more complex as more and more things are tested in an attempt to fix the initial "simple" issue. It takes a lot of time online researching (sometimes) and it takes a lot of phone calls and emails between you and the client. Of course I don't have a service contract arrangement with the client... I'm just a web developer who did some work for them a while back.
So how do you charge for this? Do you just waive it as a cost of "keeping the client happy"? And if you do charge, how much do you feel justified in putting on the invoice? An accurate reflection of the hours taken to solve the issue? Do you even discuss this with them up front? If so... at what point do you break the conversation and start talking about money?
I'm never going back to technical support as a full-time career (did my time and moved on) but I know I will continue to be asked such questions until we successfully un-invent the computer. I'd appreciate any thoughts people have on the matter.
Cheers,
Jeff
[tt]Jeff's Page [/tt][tt]@[/tt][tt] Code Couch
[/tt]
What is Javascript? faq216-6094