Establishing an IT Budget for a Small Business?
tirthas asks: "I am the Information Manager of a small (20 person) architecture firm and have recently been asked by my employer to prepare a technology spending budget. While I have a good handle on what I would like to spend vs. what I must spend, I am having some difficulty establishing a justifiable budgeting method. I have seen examples of 'per employee' methods and 'percentage of revenue' methods, but the dollars and percentages vary widely. What methods do you use to establish your departmental/company-wide budgets, what are your monetary amounts or percentages, and what successes or failures did you have in establishing your budgets?"
Per employee and percentage of revenue are great metrics to meausre your technology spending against other companies, but I wouldn't use either of them as a budgeting tool.
As for getting a budget approved, may I recommend presenting things in a menu-like manner along with an explanation of the benefits of making the investment and thre risks of not making the investment. ~
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
Wow... this is a whole can of worms. You're not going to get an appropriate answer on semi-anonymous web forum. I operate my own technology consulting firm who specializes (coincidently enough) in professional service firms such as yours. I earn my living, in part, by answering these types of questions.
I'll need to know the current technological state of your company. How close to capacity is your IT dept running, both in manpower and equipment/services? What are your company's growth expecations over the next two years? 5-10 years? In what role does your company see the IT department, cost center or profit center? In the case of the former, how might we turn that around? How does your utilization of technology come to others in your industry? Etc, etc...
Take the sound bites that you're going to get here with a grain of salt. You're going to need answers that are specific to your business itself. I know it's probably not what you want to hear, but you really should call in some outside help so you can learn how to do it right. Patching together piecemeal advice might cost you your job in the end.
Entrepreneur : (noun), French for "unemployed"
Whatever you do, don't forget to budget for ample supplies of chicken blood and other black magic staples. You know you will need it when the boss asks for those apps and hardware that magically do things that aren't possible in the natural realm.
At my company (14 employees-ish) the budgest for IT is just "Find out what we need, buy it, and give us the reciepts". Seriously. Our IT guy just does what he has to, and justifies it when asked about it. If he can't justify it, he either gets limits on what he can spend next month, or it gets returned for something cheaper. With small companies with extremely variable budgets (months our company actually get PAID result in much higher IT purchases), it's best to take it one month at a time, and document reasons for EVERYTHING!
I like to place meaningful quotes in my sig, so people will know that I know what meaningful quotes are.
I hate to say it, but a lot of your spending will depend on your clients. If your clients run Autodesk CAD software, then so should you, and that will make a huge dent in your bottom line. Our clients stagnated on AutoCAD 2000 for years, then just this month decided (and these are fortune-500 retailers, mind you) "oh, lets upgrade to AutoCAD 2006, so should YOU"...
I'm the sole IT person in a 50-person architecture/construction management firm. Our spending varies year-to-year but there are a certain amount of annual expenditures. Things like antivirus software (both at the server and desktop level, CAD upgrades (we stagger our and are getting onto Autodesk subscription... it hurts in the beginning but pays off after a couple of years).
I do my best to save on the software side and apply the savings to better hardware. By this I don't mean go out and pirate what you can't afford, I mean look for OSS alternatives to things you may think are a must-buy. I run sendmail with Mailscanner/spamassassin on FreeBSD and linux, instead of Exchange. I run supplemental Samba servers on quality HP servers. I do run a windows domain, because its just easier for me to manage than a Samba-based domain. Believe or not, MS stuff just works in my organization. Our industry-specific accounting software is windows-only also, so we're kind of stuck there.
Like someone before said, you need to take into account your corporate growth goals and decide if you want to invest in a lot of good hardware that should last a long time, or buy cheap initially and replace things when needed.
Don't stop with PC's and applications. Include phones, Internet access, printers, faxes, document repositories, paper, toner, CD's, you name it. If the business strategy is best supported by quill pens and parchment paper, though, don't be afraid to go low-tech.
The partners probably have an idea of how much they want to spend on you, your team, and what you and your team do. Find out.
Do not trifle with that step. If they think they can afford $30,000 a year on technology and you present a $300,000 budget, the next sound you hear will be the axe falling.
Never forget that your firm is in the business of architecting things. Having cool computers with the latest applications that do not contribute directly and measurably to the architecting of things is deadly.
First, ignore all the per-capita methods. They won't work.
Now, take your lists of what you need to spend and what you want to spend. Lay out the items, give each one a priority ranging from "must have" to "would be nice". Provide a justification for each one and for the priority you gave it. Give all justifications, not just the best one, with examples from reality (eg. the justification for the anti-virus software might make reference to actual virus infestations in the company in the previous year and how much they cost in money, time and resources). Be sure to account for recurring costs in future years (eg. the service contracts on equipment, anti-virus update services, etc.).
Once you've got your list, sit down with the Finance guys and figure out how far down the list the business can afford to go.
Realistic budgets aren't based on per-capita expenditures or percentages of revenues or profits, they're based on what the business actually needs to spend to stay in business.
Here's a 9 point, back of an envelope plan which sums up what the big consulting firms will tell you (in less words).
1. Review the Business Plan. What does it tell you? You expanding? You going all e-business? What? Wishes as well as reality.
2. What about trends in the architecture world? Trends in technology? Cheap storage, cheap bandwidth etc?
--> Try to work out what capabilities are suggested by all of this. eg - if your firm says they want to go e-billing then, hey, thats a capability. Show these to your firm and get them to rank them, score them whatever.
3. You haven't just started up, I suppose, so how does your current IT match up? Do a big list of capabilities you have identified and assess each one against your current apps/functionality.
4. What would a future IT system look like if it were to deliver all these capabilities? How could you leverage some of the technology trends you identified in to creating growth or profit? (invoices by pdf = save on printing and mailing etc. Recruit new staff just via the web = savings etc )
5. Can you decribe an optimal IT applications and technology architecture yet? Would that be an open accessable database feeding billing, web portal, collaboration, etc? Web based? Accesible in the move, laptops etc?
6. Now do a gap analysis of what you have versus what you want. Describe how you could move between those two states. Ie projects, dependencies etc - migrate this database, use a temporary TS server, then move to app x etc etc. remember culture (saving local vs contributing centrally - loss of power for the individual) - have a plan for selling culture changes too.
7. How could you pay for this - what levels of investment would it take? How will the changes be paced - what happens this year and what next. Will there be an investment phase of a few years then a leveling out. Talk business cases here - ROI.
8. Map the risks and critical success factors. Map your communications plan for the changes.
9. Present. You now know exactly what you want, why you want it and in terms that the rest of your staff team will understand - they nedd the capabilities not the software itself. Easy sell really.
We go though this every few years and it is an effective enough methodology.
There is a point to this (honest): IT often has to play in cost-benefit analysis against other corporate budgets, including facilities.
Liberty you never use is liberty you lose.
Your firm must be big enough to have an accountant, if so, time table a long meeting with him/her/it and thrash it out with them. You might as well, it'll only end up on their desk again anyway. Come up with a range of options that meet the requirements and the account will help you put figures on things, including your assessment of the liabilities in el cheapo solutions. Personally, I've had a good success level and good experiences with turning the "gatekeepers" into collaborators that way.
Plays violent online games as: Nerfherder76
I imagine if you're in charge of administering most of the daily tasks (backup, network maintenance, upgrades), there is no labor cost. This makes it very easy for you.
I would put something together where you talk about the existing infrastructure, and maybe some proposed changes. Rank these changes in priority from "Low" (we can live without them but they MIGHT provide efficiencies) to "Medium" (realistically these will be needed, provide a good benefit for the investment) to "Musts" (these have to be done in the next 12 months otherwise the business will not function as it does today).
For example, "Low" might be buying larger, better displays for the office and a plasma TV for the client presentation room. "Medium" might be to buy larger, better displays for some of the drafting people, if the current ones are already a bit old or unreliable. "Musts" might be the monthly costs of internet/voice service (make sure they're not double- or triple-counting anything) or replacing a monitor that you KNOW will be gone within three months.
Also, make an approximate tally of the current value of items in the office, as far as IT is concerned. What if a file server went down? How much is the replacement? How much would a new bells-and-whistles replacement be?
I would probably draft up a "recommended" budget:
Recommended Budget: Medium
Then, above and beyond that, ESTIMATE the "Oh, crap" budget, for example:
Clearly spell out that the first part is "in your control" and the other part is BEYOND your control. You may find that the "in control" budget is $11,000, while the "beyond control" budget is $25,000. Or the "in control" budget is $35,000 and the "beyond control" budget is only $7,000. Approach each of these scenarios differently.
Once this is all done, write a half-page summary on the front page. One paragraph explaining the "in control" budget and a realistic range, plus the benefits. Then a second paragraph with the "Oh, crap" stuff.
I'm making the assumption that your employer wants to know the following:
Succesfully and accurately answering the first three questions will make the fourth one easy.
Small potatoes make the steak look bigger.
Hi-
I'm the sysadmin at a ~25 person architecture firm, and an architect, too.
What I do for budgetting is to start with an inventory of every piece of equipment we own. Then I assign an approximate lifespan to each thing, based on experience. Couple that with when each item was purchased, and replacement times and potential budgetting scenarios start to emerge. There are a couple of policies I try to wedge in there to steer purchases, such as I like to put the new machines in front of the heaviest, most demanding users, which for us is the more billable staff. I'm forunate in that I have management's backing, so that there's never any whining from project managers when an intern gets a kick ass machine, and the PM gets the hand-me-down. By keeping the machines coming in, I can keep everyone pretty happy. In addition, whenever possible, I try to upgrade our software versions either every two or three years, on everything except the Microsoft hegemony, which I only upgrade through churn of new workstations.
Around the fairly regular annual purchases, I then stategize the big ticket items: new plotter, Autocad updates, expanding licenses of Photoshop/InDesign, implementation of a new accoutning system, or what-have-you. This helps even out the costs from year to year. None of it's rocket science; you just have to put your head into it and figure out what it would cost to maintain your company's current level of technical prowess (x machines per year, etc), and that what it would cost to further develop the skillsets (by getting new software, and doing more training).
FWIW, we spend ~$45k per year, which works out to be ~2.5 - 3.5 % of revenue. My bosses have never gone for a straight percentage method, but it's my preference, since it automatically adjusts itself for good times and bad. Instead, I develop a budget, they either say yes to the whole thing, or specifically exclude one or more items. Then I establish the priorities and give them an idea of at what points in the year I'd like to spend money. They coordinate that with the company's cash flow, and if the year turns sour, I just get reigned in on my spending.
Sorry if I'm rambling too much. OTOH, if you want more, post a response, and I'll give you my email address.
Joel
About a year ago, my company's IT department rolled out LCD screens to every employee and I was ecstatic. Not so much because I had been clamoring for a new screen (I hadn't even thought about it), but because it was an upgrade that actually made some kind of logical sense.
Think about it. What I do all day is mostly send e-mails and work in Microsoft Office. A traditional 'upgrade' would be to drop a new, faster computer with a big hard drive on my desk. But not only does that take a lot of work on behalf of IT, not only is it incredibly disruptive to my workday, but it doesn't really benefit me at all. I can probably store my entire work folder and all its accumulated contents since I began working here on a single USB keychain drive. My CPU needs were met and exceeded some generations of hardware ago.
On the other hand, a new LCD screen that's crisp, clear, and easy to read -- as opposed to some legacy, piece of junk CRT that's been getting blurrier and dimmer for years -- is something tangible that I look at and notice day in and day out. You might think it doesn't result in an increase in productivity, but I disagree completely. In fact, if someone had given me the choice between the monitor and a new CPU, I would have taken the monitor in a second.
Breakfast served all day!