The key phrase is "an educated client". Who is going to educate them, an article in a magazine or the integrator, or I would suggest it should be both.
Automation systems really do require a little more understanding on the clients part because of the "code" issues.

People can go out and buy an expensive car, they know there is an engine that makes it go, but most have little to no interest in all the details of what makes the engine work. They don't need to know, the car comes with a warantee so any problems in the first few years are covered, and they also know that they can take their car to any number of places to have it serviced, modified or whatever. If they decide they don't like the place they bought it from they will not need anything special to go anywhere else.

From all that has been posted here the automation system without the code almost locks them into dealing with only the company that sold them the system, even though Crestron / AMX and others are large companies with dealers everywhere.

I know that the car dealer didn't "build" the engine to the clients specifications and thats what makes this such a tough issue to resolve. You as the programmer have customized work to protect, yet without a good education the client typically will have the perception that there are many of you out there just like there are many car dealers / shops and he should be able to go to any other programmer and get "service", without having to build an new engine.