![]() That will really depend on how many can be classified as Team Members. ![]() If it's truly 400 users (not employees) then the cost scales accordingly. This is for a company with around $500M in annual revenue. I pulled this example from real-world, average monthly billing of one of my manufacturing clients with around 400 employees and a similar breakdown to what I described. ![]() With a breakdown like this and an average amount of secondary costs, you'd be looking at around $20k per month. If you're saying your org has 400 employees, then it might breakdown like this:ΔΆ90 don't need Dynamics at all (think shop floor production workers) It's best to plan for this to be higher in years 1-2, then you can start scaling it back in some areas, like eliminating extra test environments and using locally hosted DEV environments. This is a category you can actively manage. Much of the secondary category can be considered "Azure usage". ![]() ![]() Secondary options - increased performance in Production, Azure usage, cloud hosted DEV environments, additional test environments, data warehousing, advanced analytics Types of users - Finance, SCM, Team Members, those who don't need Dynamics at all It really depends on two factors: which type of users you have and what secondary pricing options you need. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |