> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/user-guide/software-metering.md). # Software Metering ## Software Metering at a glance Software Metering tracks how employees use desktop and web applications and helps you identify licenses that are quietly costing your organization money. You can monitor usage by application, department, or entity, and use this visibility and the insights you gather to develop a tailored license optimization strategy that reduces unnecessary software spending. ![](https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-6e54cef7d5ed1a394b9c3ed5a181ab0197ebbff4%2Fsoftwaremetering-1700148793.png?alt=media) ## Key benefits and use cases ### Cut unnecessary software license costs Unused licenses quietly drain your IT budget every renewal cycle. Software Metering shows exactly which applications your employees use and which ones sit idle, so you can reclaim or downsize licenses with confidence instead of relying on guesswork or inaccurate employee reports. ### Prioritize renewal and procurement decisions with usage data Contract renewals are hard to negotiate without proof of real usage. Track adoption trends before a renewal date arrives, and use actual usage patterns to decide what to renew, downgrade, or cut. ### Identify underused desktop and web applications and improve adoption strategy In some organizations, managers believe employees have adopted certain applications, but the software remains untouched. This can result from change management issues, unclear benefits, or insufficient training. Compare desktop and web usage side by side to identify employees who have access but rarely open an app. Then, improve your adoption strategy using accurate data from users who could benefit from it. ## Get started with Software Metering ### Monitor software usage through the Software Metering dashboard Select **Software Metering** from the main menu to view usage broken down by **application**, **department**, or **entity**, and drill into any meter for a closer look. Refer to [**Getting started with Software Metering**](/platform/user-guide/software-metering/working-with-software-metering.md) for a full walkthrough of the dashboard. ### Extend Software Metering with Nexthink Library packs Install packs from the Nexthink Library to turn your Software Metering data into cost-savings actions. Available packs include unused application detection, software reclaim campaigns, and SaaS usage analysis. Each pack works alongside your existing software meters rather than replacing them. Refer to the [**Nexthink Library Pack**](/platform/library-packs.md) page for more information. ### Create your first software meter From the Software Metering navigation panel, click **New** to configure your first software meter. Choose the applications to track, set a license type, and define an underusage threshold. Refer to [**Setting up and managing Software Metering**](/platform/user-guide/software-metering/managing-software-metering.md) for the full configuration steps. ### Read the Software Metering FAQ Find answers to common questions about Software Metering on the [**Software Metering FAQ**](broken://pages/hsjIoEn5U5VBUTe6KF4y) page. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nexthink.com/platform/user-guide/software-metering.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.