Onboarding a Client Who Is Not Technical
August 28, 2026
A client who hired you to handle the technical work is, by definition, not going to enjoy learning the technical work.
The usual onboarding — a document with terminology in it and a call where they nod — produces somebody who cannot do anything without you, which is bad for them and eventually bad for you.
Teach tasks, not systems
Nobody outside your field wants to understand your CMS. They want to change the phone number on the contact page.
Frame everything as the task they want done, named in their words. "Update your opening hours" rather than "editing a content block".
Assume nothing about the vocabulary
- Cache, deploy, staging, DNS -- all meaningless, and all cause people to stop reading.
- Show the click rather than naming the menu, since they cannot map a name to a screen.
- One task per walkthrough, because a combined one is where they lose the thread.
- Include what "done" looks like, so they can tell whether it worked.
Expect to be the fallback anyway
Some clients will not do it themselves regardless of how good the material is, and that is a legitimate choice on their part.
The material still pays for itself, because it turns "can you explain this again" into "can you do this for me" — which is a request you can price rather than absorb.
Do not make them feel stupid
Onboarding material written by an expert often reads as slightly impatient, and a client who feels patronised stops asking questions rather than stops having them.
Show the whole click path including the obvious parts. What is obvious to you is the step they will get stuck on.
Frequently asked questions
- How do I onboard a non-technical client?
- Teach tasks rather than systems, named in their words -- "update your opening hours" rather than "editing a content block" -- with one task per walkthrough and a clear picture of what done looks like.
- What language should I avoid?
- Cache, deploy, staging, DNS and similar. They are meaningless to the client and cause people to stop reading rather than ask. Show the click instead of naming the menu, since they cannot map a name to a screen.
- What if the client will not learn it anyway?
- That is a legitimate choice, and the material still pays for itself: it turns "can you explain this again" into "can you do this for me", which is a request you can price rather than absorb.
Keep reading
This is what Demorta does
Click through it — the same kind of demo you can record of your own product.
Try it on your own product
Record your first interactive demo free.
Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.
Start free →