Granted, this is a generalization about clients. I’m saying most client I’ve worked with over the last decade have a common theme. They find technology superficially interesting, but rarely what to know how exactly you coded your super cool solution. Some clients may humor you, but read their eyes: If you see them glazing over, stop geeking out.
Pro tip for tech people – your clients generally don’t care about HOW you got work done, they care WHEN the work is done.
So don’t yammer on about implementation details (and don’t for the love of god DON’T say the word ‘implementation’). All you’re going to do is bored them, or worse, make them feel dumb.
Instead, say less, and use high level details. For example ‘You site works now’ is a perfectly fine one liner! Such a line is usually followed by your client saying ‘good’, or ‘thank you’, or “great, here’s more work since you’re easy to work with (and not a total nerd bag)”.
That said, emailing a copy of all the work details along with your invoice is a good idea.
A jargony checklist of tasks completed shows you actually did do technical work worth spending money on. Remember, to non tech people, it’s all magic (and that’s why you have a job). Clients usually have no idea how difficult (or easy) things are to do. However, everyone can comprehend a list with lots of items with check marks next to them.
With a checklist, your client has the options to skim the list, and remember they don’t want to do those tasks themselves, while giving them the option to research the tasks as well if they choose.
After breathing a sigh of relief that the cryptic list of tasks has been completed, your client will gladly write a check for the balance for your invoice for making their lives so much easier.