SAM Should Build Your Independence, Not Your Dependency

What if the goal of your SAM services partner wasn't to keep you as a client forever, but to make you capable of managing SAM yourself?

This is an important question for any organisation considering a long-term Software Asset Management services relationship.

The traditional SAM managed services model is often built around a multi-year relationship. A provider takes responsibility for some or all of the organisation's SAM activities, and over time the scope can expand: more software publishers, more data, more reporting, more processes, more technology and more managed services. There can be significant value in that model. But there is also a risk.

The more of your SAM capability you outsource, the more difficult it can become to bring that capability back in-house.

Knowledge sits with the provider. Processes are operated externally. Technology may be managed by the provider. Internal teams may become dependent on external resources to understand their own software estate.

Eventually, the organisation may have a sophisticated SAM service, but not necessarily a sophisticated SAM capability of its own.

We believe there is a better approach.

SAM should create capability, not dependency

Our philosophy is simple:

A SAM services partner should leave a customer more capable than when they arrived.

That means our role isn't simply to operate SAM on behalf of a customer.

It is to help the customer build the people, processes, governance, data, technology and knowledge required to operate a successful SAM practice themselves.

That might include:

• Designing the SAM organisational structure

• Defining roles and responsibilities

• Developing SAM policies and governance

• Establishing repeatable operating processes

• Building data standards and quality controls

• Creating Effective License Position methodologies

• Establishing subscription and entitlement management practices

• Implementing and optimising SAM technology

• Developing reporting and management information

• Training internal teams

• Documenting processes and procedures

• Establishing continuous improvement practices

The objective isn't simply to deliver today's SAM requirements.

It is to create an organisational capability that the customer owns.

Managed services should be a choice, not a necessity

We aren't against managed services.

There are many situations where they make perfect sense.

An organisation may not have enough internal resources. It may need specialist expertise that would be difficult to maintain internally. It may be dealing with a complex vendor audit, a major transformation or a significant renewal.

It may simply decide that certain SAM activities are better delivered externally.

All of those are valid choices.

The distinction is whether managed services are being used because they provide the best business outcome, or because the organisation has become unable to operate without them.

We believe customers should always have a choice.

You should be able to say:

"We want you to manage this for us."

rather than:

"We have no idea how to do this without you."

That difference matters.

Build the practice, not just the service

A successful SAM programme is about much more than collecting software data and producing reports.

It needs an operating model.

People

Who owns SAM?

Who is accountable?

What skills are required internally?

How should SAM interact with IT, Procurement, Finance, Security and Legal?

Processes

How are new software and subscriptions introduced?

How are deployments reconciled?

How are renewals managed?

How are unused subscriptions identified?

How are vendor audits handled?

Governance

Who makes decisions?

What requires approval?

How are risks escalated?

How does management understand the organisation's software position?

Data

What information is required?

Where does it come from?

Who owns it?

How is data quality measured?

How do you turn technical data into a reliable commercial position?

Technology

What should be automated?

Which systems should provide source data?

How should SAM tools be configured?

How does the organisation retain control and understanding of its own data?

These are the building blocks of a sustainable SAM capability.

A managed service can perform these activities for you.

An enablement-focused partner helps you learn how to own them.

The insource journey

We see SAM capability as a journey rather than a binary decision between "outsource" and "do it yourself."

An organisation might begin with significant external support:

External expertise

↓

Shared delivery

↓

Knowledge transfer

↓

Internal capability

↓

Customer-owned SAM practice

The balance can then evolve.

You might bring day-to-day SAM operations in-house but retain external support for complex vendors. You might employ your own SAM team but use a specialist partner for audits and major negotiations. You might manage most publishers internally but outsource specific areas where specialist expertise is difficult to maintain. Or you might decide that a managed service continues to make commercial sense. There is no single right answer.

The important thing is that the customer owns the decision.

What happens when your customer becomes capable enough to leave?

This is where our philosophy becomes particularly different.

If we help an organisation build an excellent internal SAM practice and, several years later, they decide they no longer need a managed service, we don't see that as failure. We see it as success.

If the customer hires people we helped develop, takes ownership of its processes, operates its own technology and manages its own SAM practice, then we have delivered what we set out to do.

And there may still be reasons for them to work with us.

• They may want specialist expertise.

• They may need additional capacity.

• They may need support during a complex vendor audit.

• They may want an independent assessment.

• They may need help with a major subscription negotiation or optimisation exercise.

• The relationship becomes based on choice and expertise, rather than dependency.

The same principle applies to technology

We believe SAM technology should work the same way.

A platform should make your organisation more capable, not create a black box that only your service provider understands.

You should know:

• What data is being collected

• How it is being normalised

• How subscriptions and entitlements are mapped

• How the ELP is calculated

• What assumptions are being made

• Where risks exist

• How recommendations are generated

Automation should reduce effort and improve consistency.

It shouldn't reduce your understanding of your own SAM environment.

A different definition of success

For a traditional managed service, success can be measured through contract value, scope expansion and renewal.

We believe there are better measures.

Can your organisation operate its SAM processes?

Does your team understand its software and subscription position?

Do you have effective governance?

Can you produce reliable data and reporting?

Can you manage renewals and vendor engagements confidently?

Can you identify and reduce commercial and compliance risk?

Could you operate your SAM practice without us if you chose to?

If the answer eventually becomes yes, we consider that a success.

The choice should belong to you

We believe the role of a SAM partner is to bring expertise, build capability, transfer knowledge and help establish a sustainable practice.

Not to create a permanent dependency.

Your organisation should be able to decide which capabilities it wants to own, which it wants to outsource and where specialist external expertise creates the most value.

That might mean working with us every day. It might mean working with us occasionally. It might mean bringing the capability entirely in-house.

All three can be successful outcomes. Because the real value of a SAM partner isn't measured by how long you need them.

It's measured by what your organisation is capable of because they were there.

Is your SAM service building capability — or dependency?

If you're currently using a SAM managed service, ask yourself:

• Could we operate our SAM processes without our provider?

• Do we own the knowledge and methodology, or does our provider?

• Could our internal team explain and defend our subscription position?

• Do we have documented processes and governance?

• Could we change providers without losing critical capability?

• Are we paying for a service because it delivers value — or because we have become dependent on it?

If the answers concern you, that's not necessarily a reason to terminate your managed service. It may be a reason to change what you expect from it.

We help organisations assess their current SAM operating model and build the capability, governance, processes, data and skills needed to take greater ownership of SAM.

If your objective is to build a SAM capability that your organisation owns — rather than one it has to continually outsource — let's talk.

We can help you understand where you are today, where you want to be, and what it would take to move from provider dependency to organisational capability.

Your SAM partner should give you more options, not fewer.

Talk to us about building a SAM capability you control.