As many people in the business community are trying very hard to make the most out of a year when all the cards seemed to be stacked against us, it is easy to put off the task of figuring out what we will spend next year to move our businesses forward again.  While budgeting for technology can seem daunting at times, it is the best way to make sure that you take into account all of the things that will help your business run most efficiently with minimal downtime.

We must first consider the standard operational items such as preventative maintenance and support - which every business should have in place.  There are also a myriad of other items that often get overlooked during the budgeting process that can pop up during the year causing undue stress on the budget and the management.  Some things to consider include  software renewals,  such as anti-virus or backup software.  You should also review your current hardware to determine what is out of warranty.  Based upon the function of the device, a warranty renewal or hardware replacement may be in order.

For those of you who have already considered the items above, congratulations!  You are ahead of most businesses at this point.  There are a few more strategic items you might consider,  a new business resumption plan or updates and testing to the one you have to ensure its viability.  Also, in today’s world of hackers and viruses, many businesses are being proactive about auditing their network and web site security to protect their valuable business data.

While this all may seem overwhelming, it doesn’t have to be.  You can use a budgeting template much like the one we use for our clients or simply hire a technology company to review and plan all of this for you.  We have seen many cases where our involvement early in the process has helped our clients plan better and avoid unexpected expenses during the year.

Download the Technology Budget Planning Worksheet

I was opening my email one morning and noticed that the “out of office” message from an IT Manager of a local small business that said he was out of the office for the next two months. This was a company I had called on 8 months earlier and the company’s president had referred me to the IT Manager as their technology resource, so I looked up the company president’s name and gave him a call.

The President took my call. He explained that the IT Manager had been in an auto accident, and would be out for at least two months, and maybe longer. They didn’t have anyone else internally that knew the network, and he was concerned, but wasn’t sure what to do. He couldn’t replace an employee who would be coming back at some point, but what would he do if an issue came up in the meantime?

I suggested a Network Health Review to allow us to get an overview of his setup and any initial concerns without any cost or obligation. We both agreed that this would be a good starting point. I set up a review for the following day, and two days later, sat down with the management team to go over the findings. Overall, things were in decent shape. We identified some potential issues that we could easily fix, including:

• Incomplete backups which included data, but not the system state (registry and other system information that needs to be restored in the event of a hardware loss)
• Battery backup software was not configured to shut down the server gracefully in the event of a prolonged power outage.
• Lack of system documentation – No network diagram, no inventory of hardware/software, no master password list, etc.

We also came up with some other questions that no one in the room knew the answer to. This discussion led to us assigning a systems engineer to the company on a weekly basis for the duration of the IT Manager’s sick leave. We addressed the issues we had uncovered in the review, we found the answers to the questions about how the network was configured, and what the contact and account number information was for their key vendors. We set up Help Desk coverage for his staff so they had a resource to resolve issues on the days when we were not on site. This was critical to maintaining their productivity since they were accustomed to having someone else to ask for help and were not IT savvy.

About 3 months later, the IT Manager was ready to come back part time. He was able to quickly come up-to-speed on the changes we had made from our documentation. The management team was so pleased with the information that we provided to them, the level of support, and our ability to work well with their IT Manager that they decided to keep us on board with a scaled back schedule. Now they know that they have a backup resource when needed who is familiar with them and their setup.

8 months earlier when I contacted the President of the company, he was all set, he had someone handling his network. You never know when things could change, but you can be prepared by knowing where you stand BEFORE it happens.