ServiceNow Software Asset Management Professional for Professional Services

Software Asset Management Professional in a professional services firm reconciles licences against engagements rather than headcount, because the same product is deployed again and again at different clients. This page covers client engagement tracking and project software inventory, vendor licensing models and compliance, billable software and project economics, maintenance contracts, optimisation and renewal planning, the licence models that cause the most trouble in consulting work, an ordered reconciliation before each renewal, deciding who owns a licence bought for a single client, and when a full estate reconciliation is not worth the effort.

Client Engagement Tracking and Project Software Inventory

Create a SAM Professional record for each significant client engagement. Track which software is deployed at the client site, which licenses are consumed, and the engagement timeline. When the engagement concludes and software is removed, update SAM Professional to release the licenses.

This tracking enables better resource planning for future engagements. If a new client project requires software you have already licensed at another site, you can move the license (if the vendor permits) rather than purchasing new licenses. If demand for a software product is high across clients, you can negotiate enterprise licensing arrangements with vendors.

Vendor Licensing Models and Compliance

Professional services firms work with diverse vendor licensing models. Some vendors charge per user, others per-installation, others per-project, and others per-revenue-share. SAM Professional should capture the specific licensing model for each product, the consumption metrics, and compliance requirements.

Track which client engagements consume licenses under each model. Maintain audit trails so you can quickly demonstrate compliance to vendors. If a vendor audits your licenses, produce reports from SAM Professional showing: which licenses you own, where they are deployed, and that consumption does not exceed licenses owned.

Billable Software and Project Economics

Some software costs in professional services are billable to clients; others are internal costs. When a client engagement requires specific software, determine whether the software cost is billable. If billable, track it separately in project accounting. If internal cost, charge it to your firm’s overhead.

SAM Professional can tag licenses as billable or non-billable, making it easier to allocate costs correctly. When a project concludes, generate a report of billable software consumed and provide it to project accounting for client invoicing. This integration between SAM Professional and financial systems improves project profitability visibility.

Maintenance Contracts and Support Planning

Software deployed to client sites usually requires ongoing support and maintenance. Track maintenance contracts in SAM Professional linked to deployed software. When maintenance is about to expire, notify project managers so they can decide whether to renew support or plan for client transition.

For critical software, maintaining support contracts is essential—vendors often require support to issue patches or provide assistance. For non-critical software, allowing maintenance to lapse may be acceptable if the software is reaching end-of-life. SAM Professional tracking helps make these decisions deliberately rather than by default.

License Optimisation and Renewal Planning

Use SAM Professional data to optimise licensing spend. Analyse which software is deployed most frequently across client engagements. Negotiate site licenses or enterprise agreements with top vendors—these often offer significant discounts versus per-project licensing. Plan license renewals so your firm always has adequate licenses for sales pipeline.

Periodically review deployed software across all client engagements. If a particular software is being replaced by newer alternatives or becoming obsolete, plan for transition. If adoption is lower than expected, negotiate with the vendor for price reduction or license return. These optimisations directly improve project profitability.

Professional services organisations benefit from tracking historical software deployments across engagements. This history shows which software is commonly used (indicating broad applicability and continued business value) versus which is rarely used (indicating it may be approaching obsolescence or specific use cases only). Use these trends to negotiate enterprise-wide agreements or decide which software to retire from your standard offerings.

Reconciling Licenses Against Engagements, Not Only Against Headcount

A software estate in a consultancy does not look like one in a product company. The firm may hold a modest set of enterprise agreements, but each engagement adds its own tools, its own temporary accounts, and sometimes a license the client bought and expects the consultant to use inside the client’s tenant. The usual reconciliation method counts installed copies against purchased seats. In this sector that method misses the question that matters most: which license is being used for which piece of client work, and who would pay if it were audited.

This section is for the software asset manager, the operations lead who approves tool purchases, and the finance partner who has to explain a renewal invoice. It covers the reconciliation step that many firms skip, the decisions about who owns each license, and the failure modes that surface at renewal.

License Models That Cause the Most Trouble in Consulting Work

The license model determines what gets counted. A named-user license counts the person, a concurrent license counts simultaneous sessions, and a consumption model counts something the engagement generates. Each one behaves differently when a consultant moves between projects or when a subcontractor is given access. The table sets out the models that appear most often in professional services estates and the mistake each one invites.

An Ordered Reconciliation Before Each Renewal

The renewal conversation is the moment the firm has the most room to negotiate, and it is wasted if the estate has not been reconciled first. The following sequence produces the list the firm needs before the vendor’s sales team sends a proposal.

1. Export the list of active accounts for each product, with the account type, the owner and the date of last activity.
2. Match each account to a current engagement or to the employee record. Anything that matches neither goes on a removal list.
3. Separate client-owned deployments from the firm’s own estate, and confirm with each client’s sponsor which licenses they are paying for.
4. Calculate the peak use over the last full cycle for concurrent and consumption products, not the average, because the peak is what the contract will be measured against.
5. Identify licenses that are bought for a single engagement and check whether that engagement is still live. A license for a closed project is usually a candidate for non-renewal.
6. Pass the reconciled list to finance so the renewal budget reflects real use, and record any license that will be reassigned to a client engagement.
7. Agree a removal date for every account on the removal list, and record who approved it.

Deciding Who Owns a License Bought for One Client

Sometimes a license is bought specifically for one client’s project. The firm can hold it, pass it through to the client, or let the client buy it directly. Each choice shifts cost and risk in a different direction. Holding the license keeps administration in the firm but leaves the firm with the cost after the engagement ends. Passing it through is clean if the client’s contract allows it and the client understands the commitment. Letting the client buy directly takes the cost off the firm’s books but requires the consultant to hand over administration cleanly.

The practical rule is to make the decision at the point the license is requested, and to write it on the order. A license that is bought first and allocated later usually ends up in the firm’s estate by default, and the firm then pays for it through the next renewal cycle.

When a Full Estate Reconciliation Is Not Worth the Effort

A firm with a small set of tools, all held on a single enterprise agreement and used by the same group of people, does not need a per-engagement reconciliation every cycle. A simple annual check of active accounts against the employee record is enough. The full process earns its cost when the firm uses many client-specific tools, works with subcontractors, or has been surprised by a true-up. Start with the products that carry the largest renewal values, and extend the method to the rest once the first reconciliation is trusted.

Signs the License Position Is Under Control

• Every active account can be traced to a current engagement, a current employee or an approved subcontractor.
• Renewal figures match the reconciled list, and finance can explain any difference from the previous cycle.
• Client-owned deployments have a named license owner on the client side who has confirmed the arrangement in writing.
• No vendor audit or true-up has come as a surprise in the last cycle.

Common Questions About Licensing in Professional Services

Who is liable if a consultant uses a personal license for client work?

The firm often carries the risk in practice, even when the license belongs to the individual, because the work was done for the firm’s client. Personal licenses should be prohibited for client delivery in the firm’s policy, and any exception should be recorded and reviewed.

Do subcontractors need to be included in the firm’s software asset records?

Yes, because their accounts consume licenses and generate exposure. Record the subcontractor, the contract reference, the products they can access and the end date of their access, so that the account can be removed when the contract ends.

How should a consultant’s license be handled when they move to another engagement?

Reassign it if the new engagement needs the same product and the vendor terms allow it. If the vendor restricts reassignment or the product is not needed, remove the account. Do not leave the seat assigned to a person who is no longer working on any engagement that uses it.

What should a firm carry into a renewal negotiation?

A reconciled list of real use, with peak figures for concurrent and consumption products, and a clear view of which licenses are no longer needed. A vendor’s proposal built on the firm’s own numbers is easier to challenge than one built on assumptions.

Next Step for Software Asset Management in Professional Services

The IT asset management guide for professional services covers how technology deployed to clients is tracked and how license compliance is managed, which the reconciliation depends on. The asset lifecycle article covers the stages an asset passes through from intake to disposal, including retirement.

SAM Professional for Professional Services: Start With an Entitlement Map

A software asset management engagement for a professional services firm should start with an entitlement map: one register that ties each contract the firm holds to the metric it is measured on and to the client engagements where that licence is in use. Install counts and headcount come later. Firms that begin with a discovery scan usually end up with a long list of installs that nobody can tie to a contract, and that list does not show whether they are compliant.

The first pass is a contract read, not a tool run. Collect the order forms, enterprise agreements and any client-side terms that mention the firm’s software. For each one, record the licence metric, the renewal date, the support tier and any clause about transfer to a client or a subcontractor. Most surprises in this work come from clauses that were skimmed at signing.

Next, match contracts to live work. Pull the list of active engagements and tag each one with the products it runs on. A licence that appears on no active engagement and no employee record is the strongest candidate for release. A licence that serves three engagements at once needs a written decision about which engagement owns it, otherwise the cost drifts to whichever client invoice is open.

Where teams go wrong is treating the register as finished once it is built. Engagements close, people rotate and clients take software in-house, so the register can go stale quickly. Set a recurring task that compares it with the engagement list and logs each change with a date and a name.

A register also makes the renewal conversation shorter. A vendor discussion that starts from contracts, metrics and live engagements goes differently from one that starts from an export of accounts. For the tooling side, the ServiceNow Software Asset Management Professional guide is the place to start, and the software license optimization guide covers comparing entitlements against actual use. Firms that want the ongoing work handled for them can look at our software licensing and optimization support.

ServiceNow SAM Professional: What It Does and When a Services Firm Needs It

ServiceNow SAM Professional is the software asset management application on the ServiceNow platform. It holds your software entitlements, compares them with what is installed or consumed, and shows where you are short or paying for licences that no engagement uses. A services firm typically needs it once contracts, client tenants and live engagements grow beyond what one spreadsheet can keep current before each renewal.

The question to answer first is whether your licence position can be read from one place on any given day. If it cannot, the gap usually shows up in one of three ways:

• a product is measured by more than one vendor metric at the same time
• subcontractors and short-term consultants hold accounts that nobody reviews
• a renewal has already produced a true-up invoice that nobody expected

Spreadsheet register or the application

In most implementations the difference comes down to data quality rather than features. An export of purchase records that skips the licence metric and the transfer terms produces a tidy register that is still wrong. On your own instance and release, check which discovery and import options are available and how they treat client-owned deployments, because these vary by configuration. The integration patterns for licence optimisation data show how that information usually reaches the rest of the estate.

A simple test helps. If every active licence can be traced to a live engagement or a current employee in a single sitting, a well-kept spreadsheet is enough. If the trace takes weeks of chasing account owners, the application usually justifies its setup effort. The reconciliation steps above still apply either way, because the application automates matching but does not decide who owns a licence.

Upkeep is where most registers fail. Engagements close, people rotate and clients take software in-house, so the record needs a recurring comparison against the engagement list. Once the data is clean, the compliance workflows for software licences are the natural next step for turning that register into routine checks.