Just for comparison. 1,000 employees but that does not seem to be a large factor in the support model. We train and leverage department subject matter experts to be the primary contact point for "How do I?" and for keeping the organizational decisions consistent. That group can escalate to 1 level 1 support person working SharePoint about 30% of the time. That person can escalate to 1 level 2 developer or a level 2 administrator both working on SharePoint issues less than 30% of the time.
Hope that helps.

I can tell you I was the local IT support provider for General Cable Corp. a company of over 6,000. Most Sharepoint issues stopped with me. Either I googled it, or found it out through "higher forces". Since then, I've become kind of my own Sharepoint Pro, except that I have a hard time understanding it's MAJOR limitation of 1,000 levels/in a list. That seems to render it almost useless? Even if you have a seperate portal/DB for every facility... still, it gets bogged down quickly. Seems to pale in comparison to SQL, all you have to do is pay a company like mine to create you a custom interface.

Sharepoint is cumbersome and overcomplicated for most end users. Don't get me wrong, I suggest it to companies all the time. It's versioning and doc control is out of this world, and interfacing with AD, Outlook scheduling, all of that. I just wish they moved to a model that could be sustainable on a large scale.

I'll give you an example. HR wanted a "Vacation Request Form" to be on a KIOSK for mfg workers to enter. I designed the form in infopath with a data connection to our sharepoint portal, and from there initiated an approval workflow that dumped the info back into an API I could use for Kronos, our time clocking software. To an average end user, that's beyond greek, it's more like piglatin. So, for extended functionality, you need to have a well trained facilitating team in a large organization.