As others are pointing out, I think your issue is being able to communicate effectively. But then, you might ask what is effective communication especially in y

As others are pointing out, I think your issue is being able to communicate effectively. But then, you might ask what is effective communication especially in your context? Clearly, your client is not as tech. savvy as you might want him to be. So instead of mentioning Github directly for example, you need to think about the end goal that you want to achieve. In your example, I believe you wnat your client to agree to use Github for tracking the code changes, communication etc. But instead of saying that directly, you could say "Hey as you mentioned that the site needs periodic updates, I propose using a tool that will reduce the time and error to put a fix and update your site regularly. This tool is available online and can be accessed both by you and me anywhere through internet. We can do it without this tool but it will increase the time to make changes to the site and ultimately cost you more" Now you have given the "what" to the client and not the "how". The "what" is thte importance of using the tool (github) but you don't want to say that directly. The client will see that you are giving them an option to reduce their risk/time to update the site which is the end goal, not github. Github is just a medium that u decide for the client. The next question from the client could then be "Ok so what would it take to get this tool up and running. how much? how long? " But now, you are already half way through.