Finishing it FAST vs. Finishing it Slow

I would like to get some opinions on this. When you are given a task from your client (offline - real business) - say "adding a few lines of codes" or "moving his site to another server" for example.
Even tho these are very small tasks and easy for us to do, do you usually;

1. Do it fast, finish it quick to show you are extremely knowledgeable and impress him with speed
2. Do it slow, take your time. Let him know that this is 'advance stuff', and this is why he is paying you to do it because it is so technical that he probably wouldnt to find anyone else to do it but you.

Whats your point of view on this?

chris1025 said:

2. Do it slow, take your time. Let him know that this is 'advance stuff', and this is why he is paying you to do it because it is so technical that he probably wouldnt to find anyone else to do it but you.

you might get something wrong if you are over confident.

Click to expand...

Thats true, but there are times where the chance of getting it wrong is slim to none. Like making another email address on cpanel - how easy can it get?

I'd take exactly as much time as it'd take me. If you have to fix a script, and it takes a couple of hours, I'll take that and an extra half an hour to give myself some breathing space.

Generally, unless it's actually really technical (AI, ML, etc.), you can easily find a number of people to do the same thing (especially things like PHP, RoR, etc.). Sometimes, even though things aren't difficult, they are time consuming. So, either way, I'd just do it in the time it'd take with, without consciously trying to be too fast or too slow.