For the majority of the work I use a flat rate e.g. XXX to re-image a pc XXX to install a server XXX to per ethernet drop
Then there is an established hourly rate for non flat rate work; If it's something non-standard , then per hr rates apply and any related charges get passed on i.e. Exchange server crashed, call to PSS was made , then its hourly rate + PSS charge. A lot of the work I do is remote, so the software (GTA/RADMIN/BOMGAR etc..) is a "record" if you will, of hours spent on a particular task. Jean-Paul Natola From: [email protected] To: [email protected] Subject: [NTSysADM] it contracts Date: Mon, 4 Aug 2014 10:07:24 -0400 Hi all, We provide IT support to customers on both a recurring (managed services) model and a non-recurring (break-fix and/or project) model. We have a nice complete contract covering all the bases for the managed services customers, but in the case of the break-fix customers, the only thing we make them sign are quotes (on the projects). Random one-off support items are not generally included under any kind of legal document. We’re about to do a big project for a break-fix customer, and we’re thinking it would be wise to accompany our quote with some boiler-plate legalese, too. Key parameters would probably include a limitation of liability clause (i.e. our financial liability is limited to the $$ paid us for the project or particular support we perform; we can’t be responsible for $$ lost due to lost business, etc.), force majeure; etc.. Do you all require a contract of some kind on your projects? Or even just your break-fix work? If so, what key parameters do you include? Thanks,Adam
