Awkward conversations after a computer repair fails
Last month I had a three-day battle with a broken RAID setup. I eventually brought it back to life, returned it to the client and, after a few days, sent an invoice. Then, a couple of days ago, it broke again. They called me in.
It's a tough one. It could be the power supply throwing the occasional wobbly. It could Random Motherboard Kak with the RAID chip. It could be user error. It could be something totally unrelated. Most of which are difficult to diagnose, and would involve trial and error see-if-it-lasts-this-time. They've decided to get a new computer instead. They also said they'd pay for my previous work, but made it clear they aren't happy about doing so, as it "wasn't repaired". I think it unlikely they'd use me again.
Ugh. I hate these situations. I can see their point. But I did, in fact, get it working, and there was nothing to suggest the problem would recur. I didn't charge anything extortionate, either. I'll talk about it with a more knowledgeable friend to see whether there's anything technical I should done differently, but that's kinda irrelevant - there are certainly situations where this could happen through no fault of my own.
I suppose from my perspective they're paying me to attempt a repair, but to them they're paying for a repair. I tend to assume people are aware of the former, and although I try to explain what I'm doing, maybe I need to be much more explicit about it. 95% of the time they amount to the same thing, and of the remainder it's usually something I can tell them about pretty quickly, and charge a nominal fee. But in this kind of situation, the difference becomes important. Maybe I need to get a properly-written contract, so I'm covered. I'm probably leaving myself wide open without one, to be honest.
In the end I caved and offered to fit a couple of components into a separate machine for no extra charge, which mollified them somewhat. But I still feel like I've messed up, one way or another.

September 10th, 2008 - 14:50
You haven’t messed up. The only thing you might have suggested would be that they should back up and move all their data to other devices. Indeed, I have a hard-learned rule: if it fails once then never trust it again. I have boxes of expensive and probably functional bits that’ll never go near a production server again (but they’re handy to have around for testing purposes or just to mess about with).
I think that’s the whole point of that kind of job: clients should pay you for rescuing their data. What happens next is up to them. They should be grateful to you for your helping them to walk away from one un-backed-up disaster. Everyone should get one for free—before they devise a proper data strategy.
September 10th, 2008 - 15:09
Thanks
I find it difficult to get perspective on this kind of thing. I did tell them the recovered Windows install might be flaky. I’d patched it up, but a reinstall would be better, and they said they knew how to do that themselves. I don’t think they lost anything vital this time, thankfully.
September 11th, 2008 - 16:18
It’s funny, we were just talking about no fix, no fee guarantees on http://www.technibble.com/the-no-fix-no-fee-guarantee/. We’re computer techs too, we bill for our time. Not everything is appropriate to fix, somethings take a little longer than we’d like. We’d have looked at the array again to resolve the issue (probably wouldn’t have charged for the additional services to come to the final resolution), but we’d still charge none the less. If the customer decides to pursue another avenue, that’s their prerogative, but you still have a right to bill for services rendered.