3 ms·
This is probably not the answer you'll like, but if you're really only talking about literally (only) hours of unpaid work, I'd suggest you just do it and chalk
by neltnerb 12y ago
This is probably not the answer you'll like, but if you're really only talking about literally (only) hours of unpaid work, I'd suggest you just do it and chalk it up to "customer service" and hope that you're commitment to helping them even when it's not your problem will get you a good reputation for future work.
I've seen this sort of thing too, and while it's frustrating when my code is blamed for user error or other people not reading the API I give them, I feel like it's more trouble than it's worth to stress out about it. Just give it a low priority, and do it when you have some down time in the interest of keeping future potential customers happy.
Granted, I'm not some pro freelancer, but doing this has let me cultivate many long term positive relationships, learn new skills on someone else's dime, and get new work with (potentially better) clients based on the recommendation.
- jonnyscholes 12y ago^^Solid advice. The only thing I might add is to record these hours somewhere and then in your future quotes include a portion of time called maintenance, bug fixes, testing or something similar that accounts for these unforeseeable problems. Some clients will use more than the allotted time, some less. Over time it will average out. You may have to explain to them why code \might\ need bug fixes etc but that generally leads to the client having a better overall understanding of the work required which never hurts :)