One of the most annoying things you'll ever come across is a new client who doesn't "own" the software on their systems. Their hardware is not registered to them. They have no warranties. The services that must be registered are not in the names or emails of anyone in the company.
In most cases, this client has no documentation.
So the former consultant disappears one day, or gets fired. You come in and look around. You can't log into the firewall or the server. Eventually you have to replace the firewall, crack into the server, sell the client a bunch of legal software and new hardware. You get the idea.
In end, you have to charge the client thousands of dollars for the goods and services they supposedly already bought from someone else. It's a horrible, despicable situation.
This kind of behavior makes me ashamed to be in the same business as these consultants. They are thieves and low life scum. But we see this again and again.
One of the reasons I developed the documentation that eventually became The Network Documentation Workbook is to guarantee to my clients that I would never leave them in such a situation. As I say in that book, the client owns the software, the hardware, the network, and the documentation. It is dishonorable and dishonest to leave them in the situation described above.
Your policies around software and hardware should focus on more than the basic rule that you should act honorably. Your policies should be clear, honest, and provide a sustainable process that contributes to the smooth operation and future profitability of your client.
Here are some basic policies we use to manage software and hardware with out clients.
Software Policies
- Installation
When we sell software to a client, we always install that software. Unless there are extreme circumstances, we install the software and we charge the client for it. Our managed service agreement states that all software must be installed by us. In addition, it states that all labor necessary to fix machines after someone else (including the client) installs software is billable.
It may not seem to you or your client that software installation is a skill worthy of a $125/hr technician. But it is. If you don't believe me, watch three or four of your clients install software. They put things in strange places. They don't choose the right options. They do it differently every time.
This is what you do for a living, and you will be careful to make sure that you can support the software you install. If the client does it, you don't know what actions they took or decisions they made. That can make it more expensive for you to support.
- Activation
We always activate software. Whatever the process, we make sure that this is taken care of. Some clients react favorably to a popup that asks them to activate software. Others will call on the phone or even log off their computer. It is a simple thing to activate the software and make it a non-issue.
This also eliminates the question of whether the installation is complete, so you can check the last box on the installation checklist!
- Registration
We generally do not register software unless it is required for support services. Normally, registration benefits the manufacturer and not the purchaser. It results in spam but few benefits, if any.
Of course, if product activation requires it, then we do register the software.
- Licensing
All licenses must be legally registered/recorded in the client's name. They paid for it. It's their's.
Hardware Policies
- Registration
As with software, all hardware that needs to be registered should be registered in the client's name. The same arguments apply.
- Lifespan
It is our core belief that a business class machine’s useful life is 3 years. Even if it is in perfectly working condition after three years, it's truly "useful" life is over. It is slow by today's standards. The hard drive is too small. It doesn't have enough memory. It doesn't have the latest ports and hardware options.
- Upgrading Hardware
We do not upgrade hardware in machines that are more than 3 years old. It has been our repeated experience that either there will be a significant loss of time vs. profit just getting the correct parts from our supplier, or some other hardware issue will exacerbate the scenario such as the motherboard failing after the memory is installed.
The only two possible exceptions are:
1) A retrofit (not upgrade) of a business critical machine in an attempt to keep it alive long enough for its replacement to come on line.
2) We have explained our position to the client and the client is willing to pay for the time to find the correct parts, plus all time for installation and troubleshooting of issues arising from that installation.
It is highly unlikely that any one client would ever be so endeared to a machine that they would select option 2.
Documentation
All hardware must have a Machine Specifications ("Machine Spec") sheet filled out and placed in the The Network Documentation Binder.
All licenses, software, warranties, and hardware registration information should be documented in the Network Documentation Binder and in the PSA system (under "configurations").
Storage
For every machine (server, desktop, printer, firewall, etc.) there is a pouch-type folder. If there is physical media for an application, it is stored in a folder for the machine on which it is installed. The same is true of warrantie and license information.
If there is electronic media, such as a downloaded application or update, those files must be saved in either the C:\!Tech or the D:\!Tech directory. See the SOP Friday article on The !Tech Directory.
The Most Important Process
The most important process regarding software and hardware is that it should be registered to the email address Administrator@[client_domain].com. If a human name is absolutely required, you can enter in the primary contact. But the email must be the administrator account for the client's domain.
Sometimes we think the primary contact will always be there. Maybe it's the owner. But time and time again, something happens so that the email changes, the company gets bought, the contact gets another job, etc. It is therefore critical that software (warrantees, etc.) be registered to an email address that you will always have access to. That way, you will always be able to deal with renewals or other issues, even if the primary contact is on vaction or gets hit by a bus.
All registration information must be recorded in the Network Documentation Binder and in the PSA system.
Implementation Notes
Implementing these policies follows a familiar pattern. First you need to decide on your policies. Then you need to write up your policies. After that, you'll meet with your staff and make sure they understand your policies.
These processes include policies on how you register software and hardware; storing physical media; storing electronic media; upgrade policies; and more. Don't think that this is a simple little policy. These inter-related policies affect sales and long-term goals as well as simple documentation.
When you have properly registered and documented software and hardware for your clients, you provide them with much more than the basic "proof" of ownership. When properly documented and stored, you'll have everything you need to recover or replace the client's systems in case of flood, fire, theft, or some other insurance-related incident. In fact, you'll have documentation you can fax right to the insurance company. For licenses, you'll save the client thousands of dollars because you won't have to re-buy licenses for damaged or stolen machines.
Over the long run, having all of this information properly registered will make upgrades easier to manage.
It will also make it easier for you to "retire" old equipment without leaving all kinds of software and paperwork behind. Because everything related to a specific machine is where it belongs, and where you can find it, cleaning up is easy.
How cool is it to donate old machines to a charity and include all the relevant paperwork and documentation?
As you can see, this simple-sounding process works its way into a great deal of the smooth operation of your business. Over the long run, this will make both your business and your client's business run more smoothly and profitably.
Your Comments Welcome.
- - - - -
About this Series
SOP Friday - or Standard Operating System Friday - is a series dedicated to helping small computer consulting firms develop the right processes and procedures to create a successful and profitable consulting business.
Find out more about the series, and view the complete "table of contents" for SOP Friday at http://www.smallbizthoughts.com/events/SOPFriday.html.
- - - - -
Next week's topic: Hiring Your First Employee
:-)
In most cases, this client has no documentation.
So the former consultant disappears one day, or gets fired. You come in and look around. You can't log into the firewall or the server. Eventually you have to replace the firewall, crack into the server, sell the client a bunch of legal software and new hardware. You get the idea.
In end, you have to charge the client thousands of dollars for the goods and services they supposedly already bought from someone else. It's a horrible, despicable situation.
This kind of behavior makes me ashamed to be in the same business as these consultants. They are thieves and low life scum. But we see this again and again.
One of the reasons I developed the documentation that eventually became The Network Documentation Workbook is to guarantee to my clients that I would never leave them in such a situation. As I say in that book, the client owns the software, the hardware, the network, and the documentation. It is dishonorable and dishonest to leave them in the situation described above.
Your policies around software and hardware should focus on more than the basic rule that you should act honorably. Your policies should be clear, honest, and provide a sustainable process that contributes to the smooth operation and future profitability of your client.
Here are some basic policies we use to manage software and hardware with out clients.
- Installation
When we sell software to a client, we always install that software. Unless there are extreme circumstances, we install the software and we charge the client for it. Our managed service agreement states that all software must be installed by us. In addition, it states that all labor necessary to fix machines after someone else (including the client) installs software is billable.
It may not seem to you or your client that software installation is a skill worthy of a $125/hr technician. But it is. If you don't believe me, watch three or four of your clients install software. They put things in strange places. They don't choose the right options. They do it differently every time.
This is what you do for a living, and you will be careful to make sure that you can support the software you install. If the client does it, you don't know what actions they took or decisions they made. That can make it more expensive for you to support.
- Activation
We always activate software. Whatever the process, we make sure that this is taken care of. Some clients react favorably to a popup that asks them to activate software. Others will call on the phone or even log off their computer. It is a simple thing to activate the software and make it a non-issue.
This also eliminates the question of whether the installation is complete, so you can check the last box on the installation checklist!
- Registration
We generally do not register software unless it is required for support services. Normally, registration benefits the manufacturer and not the purchaser. It results in spam but few benefits, if any.
Of course, if product activation requires it, then we do register the software.
- Licensing
All licenses must be legally registered/recorded in the client's name. They paid for it. It's their's.
Hardware Policies
- Registration
As with software, all hardware that needs to be registered should be registered in the client's name. The same arguments apply.
- Lifespan
It is our core belief that a business class machine’s useful life is 3 years. Even if it is in perfectly working condition after three years, it's truly "useful" life is over. It is slow by today's standards. The hard drive is too small. It doesn't have enough memory. It doesn't have the latest ports and hardware options.
- Upgrading Hardware
We do not upgrade hardware in machines that are more than 3 years old. It has been our repeated experience that either there will be a significant loss of time vs. profit just getting the correct parts from our supplier, or some other hardware issue will exacerbate the scenario such as the motherboard failing after the memory is installed.
The only two possible exceptions are:
1) A retrofit (not upgrade) of a business critical machine in an attempt to keep it alive long enough for its replacement to come on line.
2) We have explained our position to the client and the client is willing to pay for the time to find the correct parts, plus all time for installation and troubleshooting of issues arising from that installation.
It is highly unlikely that any one client would ever be so endeared to a machine that they would select option 2.
Documentation
All hardware must have a Machine Specifications ("Machine Spec") sheet filled out and placed in the The Network Documentation Binder.
All licenses, software, warranties, and hardware registration information should be documented in the Network Documentation Binder and in the PSA system (under "configurations").
Storage
For every machine (server, desktop, printer, firewall, etc.) there is a pouch-type folder. If there is physical media for an application, it is stored in a folder for the machine on which it is installed. The same is true of warrantie and license information.
If there is electronic media, such as a downloaded application or update, those files must be saved in either the C:\!Tech or the D:\!Tech directory. See the SOP Friday article on The !Tech Directory.
The Most Important Process
The most important process regarding software and hardware is that it should be registered to the email address Administrator@[client_domain].com. If a human name is absolutely required, you can enter in the primary contact. But the email must be the administrator account for the client's domain.
Sometimes we think the primary contact will always be there. Maybe it's the owner. But time and time again, something happens so that the email changes, the company gets bought, the contact gets another job, etc. It is therefore critical that software (warrantees, etc.) be registered to an email address that you will always have access to. That way, you will always be able to deal with renewals or other issues, even if the primary contact is on vaction or gets hit by a bus.
All registration information must be recorded in the Network Documentation Binder and in the PSA system.
Implementation Notes
Implementing these policies follows a familiar pattern. First you need to decide on your policies. Then you need to write up your policies. After that, you'll meet with your staff and make sure they understand your policies.
These processes include policies on how you register software and hardware; storing physical media; storing electronic media; upgrade policies; and more. Don't think that this is a simple little policy. These inter-related policies affect sales and long-term goals as well as simple documentation.
When you have properly registered and documented software and hardware for your clients, you provide them with much more than the basic "proof" of ownership. When properly documented and stored, you'll have everything you need to recover or replace the client's systems in case of flood, fire, theft, or some other insurance-related incident. In fact, you'll have documentation you can fax right to the insurance company. For licenses, you'll save the client thousands of dollars because you won't have to re-buy licenses for damaged or stolen machines.
Over the long run, having all of this information properly registered will make upgrades easier to manage.
It will also make it easier for you to "retire" old equipment without leaving all kinds of software and paperwork behind. Because everything related to a specific machine is where it belongs, and where you can find it, cleaning up is easy.
How cool is it to donate old machines to a charity and include all the relevant paperwork and documentation?
As you can see, this simple-sounding process works its way into a great deal of the smooth operation of your business. Over the long run, this will make both your business and your client's business run more smoothly and profitably.
Your Comments Welcome.
- - - - -
About this Series
SOP Friday - or Standard Operating System Friday - is a series dedicated to helping small computer consulting firms develop the right processes and procedures to create a successful and profitable consulting business.
Find out more about the series, and view the complete "table of contents" for SOP Friday at http://www.smallbizthoughts.com/events/SOPFriday.html.
- - - - -
Next week's topic: Hiring Your First Employee
:-)
Check Out Erick Simpson's Network Operations Center Operations Guide The Best NOC and Service Desk Operations Book Ever! by Erick Simpson Ships from stock right now! |
No comments:
Post a Comment
Feedback Welcome
Please note, however, that spam will be deleted, as will abusive posts.
Disagreements welcome!