Inside the department it was widely regarded as the stupidest idea any of us had heard in about 5 years. Some of the problems that we discussed with doing this where:
1 - IT consultants make more than IT staffers, and there were no plans to increase IT salary for doing this work
2 - we all signed on to design, engineer and manage a single network, not a bunch of smaller networks for other companies
3 - while management (outside IT) had this strong belief that we were over staffed, inside the department we knew that we all worked far more than 8 hours a day
One question that management was never able to answer (and most probably couldn't) was what the IT department/consulting group would do when our companies internal systems had a problem, and a paying customer had a problem at the same time? Where we supposed to let our 2000+ internal users lose time and money due to the problems, or telling our paying customers that we couldn't help them right now?
I'm not going to tell you not to do this (it's your funeral after all) but I will give you a list of what happend with us:
1 - all of our internal developers quit (they didn't want to get pulled into outsourced development for other companies)
2 - our intranet developer/manager walked (same reason as the developers)
3 - our director of server engineering left (he'd worked supporting servers for other companies before, and knew what a bad idea doing that is to begin with)
4 - our next 2 seniormost server engineers left (see # 3) leaving us with 1 very junior engineer (and now I can't find a decent senior engineer to save my life)
5 - our VP of IT left (he didn't want to be responsible for the mess that was going to happen)
6 - our top 2 oracle staff left
7 - the implication that everybody in IT just sat around all day and had time to spare during which they could be working elsewhere became partially true (the part that became true was that IT no longer had any motivation to work for the company, so they just sat around the office all day quoting "office space")
8 - everyone in the department was told that doing great things for the company was something they should want to do, and money shouldn't be a factor - they should in fact want to work from 7 to 7 everyday (problem was, the guy that told them this had just sold a bunch of his options for about $3million in profit, cancelled IT department raises and salary restorations, and was in the building for about 5 hours a day)
The sad end result of all this? One of the best groups of IT staff that I've ever worked with was decimated, the company decided it was bad idea (too late to make any difference to everyone leaving) and fired the guy that tried to do it, and left the remains of a department that is understaffed to this day, undermotivated, and will probably not recover fully for at least another year. IT lost years of knowledge about the company and it's systems, and didn't make a penny out of the deal.
And if you think that this was done because the company was in desperate straights for revenue, they were making about $400 million a year then, and had been extremely profitable for the last 9 quarters. It was just a bad idea, made by people who had (and still have) no idea how IT works.
Like I said, I'm not going to tell you not to do this, but just wanted to let you know what happend to us when it was tried at another company.