- Filip Lauwereys, ASIST
- Josef Hans Lara, Licensing Guru at Big Bang Innovation Services Inc.
- Paul DeGroot, Principal Consultant at Pica Communications
- Karl O’Doherty, CEO at SAM360
- 2 anonymous contributors
- Microsoft licensing is complicated. Often the same software can be licensed a number of ways. It’s difficult to know which edition and licensing model is best.
- Licensing and features often change with the release of new software versions, compounding the problem by making it difficult to stay current.
- In tough economic times, IT is asked to reduce capital and operating expenses wherever possible. As one of the top-five expense items in most enterprise software budgets, Microsoft licensing is a primary target for cost reduction.
- Focus on needs first. Conduct a thorough needs assessment and document the results. Well-documented needs will be your best asset in navigating Microsoft licensing and negotiating your agreement.
- There’s no turning back. Once you’ve committed to the cloud, it’s difficult to go back to on-premises licensing. Be certain the cloud is a good fit before executing.
- If the cloud doesn’t fit, it’s time to start making room. Most organizations are still at a stage where they can keep their on-premises licensing. But this will likely change over the next couple of years – the cloud is imminent, if not inevitable. If the cloud doesn’t make sense now, start thinking about how you might make it work in the future.
Impact and Result
- Understand what your organization needs and the business requirements. It’s always easier to purchase more later than try to reduce your spend.
- Complete cost calculations carefully as the cloud may end up costing significantly more for the desired feature set. In some scenarios, it may be more cost efficient for organizations to license in the cloud.
- If there are significant barriers to cloud adoption, discuss and document them. You’ll need this documentation in three years when it’s time to renew your agreement.
This guided implementation is a ten call advisory process.
Guided Implementation #1 - Evaluate licensing options
Call #1 - Review product options.
Call #2 - Review licensing rules.
Guided Implementation #2 - Evaluate agreement options
Call #1 - Review contract option types.
Call #2 - Review vendors.
Guided Implementation #3 - Negotiate and purchase licenses
Call #1 - Determine negotiation points.
Call #2 - Discuss license management.
Call #3 - Evaluate and develop a roadmap for future licensing.
Call #4 - Finalize the contract.
Guided Implementation #4 - Negotiate and purchase licenses
Call #1 - Assess the current state.
Call #2 - Determine licensing compliance position.
After each Info-Tech experience, we ask our members to quantify the real time savings, monetary impact, and project improvements our research helped them achieve. See our top member experiences for this Blueprint, and what our clients have to say.