Just a few thoughts in the space permitted.
1. Configuration management: you have to ensure compatibility at all stages of growth. This is easy if the purchasing decisions go through an IT-savvy central authority. Enforcement is a bit tougher,particularly with unapproved software that employees will want to install. If you design your hardware and software architecture for each stage of growth, based on known or projected numbers, you will be able to make smart buying decisions and better manage the configurations.
2. Tech support: you have to support the users at all the different sites. If you can afford it, I recommend a centralized system (Intel LANDesk is pretty good) which will let you do config management and some troubleshooting from a central location. You must weigh the cost of keeping techs at the remote sites, sending the techs out as needed, or contracting out the remote site technical support. Recommend you track your tech support jobs so that you can build data to reevaluate this choice periodically and justify tech support growth.
3. Security: my personal favorite, it gets difficult when you split your operations over several sites. Security is a risk assessment: look at the risk of damage ortheft and use enough security to match the level of risk. Too much security is expensive and can make things tough for users which gets in the way of business functions. In other words, security is about making the thieves and saboteurs look elsewhere rather than spending all your effort trying to keep them out. Consider the security implications inherent in more users and more locations. There are many ways to provide security for traffic between the main site and the remote sites, and I don't have space to go into them here.
Good fortune,
Don