Can you tell us whether we are over-licensed?

Often, yes, but assignment data alone is not enough to decide. We look at what the person is responsible for, the capability they need, their security roles and actual usage, then check it against current Microsoft terms. Somebody who rarely uses a feature may still need it for something important. That call belongs to the business owner, with our analysis in front of them.

How much could we save?

We will not put a percentage in front of you before we have seen your estate, and we will not present a forecast as a result. Recommendations are shown as potential saving until the change is made in your agreement, at which point it becomes realised.

Do security roles really affect licensing?

Yes. Entitlement often follows the capability a role exposes, so a broad role granted for convenience can carry a commercial cost as well as a control weakness. That is why we review security design and licence design together rather than one after the other.

How often should we review?

Day to day, licence position is best kept honest through joiner, mover and leaver, not an annual clean-up. A fuller review makes sense ahead of your own renewal and contract dates. We will not suggest arbitrary timing that ignores your agreement.

Can Power Platform increase our costs?

It can. Premium connectors, Dataverse, external users, environment design and AI capability all carry commercial consequences. This is why architecture and commercial design are best considered together, before the build rather than after the invoice.

Licensing and commercial optimisation

Renewal is coming
and nobody can explain
the number.

Microsoft licensing gets complicated quietly. People join and leave, roles change, Power Platform grows, and one day the renewal quote arrives with a total nobody can account for. The way out is not a discount hunt. It is knowing what people actually do, what you already own, and what you can safely stop paying for.

See how a review works

The right licence follows the work someone does, not the title they happen to have.

Sound familiar?

Licence cost rarely grows on purpose.

These are the things finance and IT leaders describe before a licensing review starts.

Renewal is coming and nobody can explain the number
The quote arrives, the total has gone up again, and the reason sits somewhere in a spreadsheet nobody owns.
We are paying for people who left
Leavers keep their licence because nothing in the joiner and leaver process removes it.
We think we are over-licensed, but nobody will sign it off
Everyone suspects there is waste. Nobody wants to be the person who took away access somebody needed.
Power Platform cost keeps appearing
Premium connectors, Dataverse and AI capability turn up on the bill after the build, not before it.
Somebody mentioned indirect access
An integration or a portal touches Dynamics data, and nobody is certain where that leaves you.
Two people doing the same job have different licences
Assignment grew by habit rather than by what the role actually requires.

How a review works

Start with the work. The licence follows.

Six steps, and a written position you can put in front of finance.

Stage 1 of 6

Start with the work, not the licence

What we do

What does this person actually have to do? The licence follows the job, not the job title.

Every recommendation names a source and a date, because the rules change.

What customers say

People who have been through it.

Around 80% of our business comes from existing customers and referrals. These are their words, not ours.

80%

of our business comes from existing customers and referrals.

All customer stories

The best I’ve ever experienced in over 20 years of collaboration.
Programme Manager, Hill & Smith Plc

Four decisions

What you are approving, and when.

Four points where a licensing change has to justify itself, in language a board can follow.

Gate 1Before any conclusion

Can we even answer the question?

If the evidence is not there, we say so rather than producing a confident number built on assumptions.

Confirmed at this gate

Who your users are and what is assigned to them
Security roles, environments and capacity
Usage evidence, where it exists
Your agreement dates and commercial data, where you can share them

Decision

Proceed
Get more evidence
Cannot conclude yet

Gate 2Before recommending

Does the entitlement follow the work?

Every recommendation is traced back to a business responsibility and a current Microsoft source.

Confirmed at this gate

What the role genuinely needs to do
The licence that capability requires
Security role design and segregation of duties
Anything involving indirect access, external or device users

Decision

Validated
Investigate further
Redesign the role

Swipe, drag or use the arrow keys to move between decisions.

Check the fit

A few questions before a licensing review is scoped.

A routing aid rather than a quote. Your answers come with you into the conversation, so nothing has to be repeated.

Question 1 of 4

0 of 4 answered

1. What is the current situation?

Select one option.

Common questions

Questions leaders ask about licensing.

Part of the InteliSense Delivery System

Licensing is part of how we deliver, not an afterthought.

Licence and commercial design belong alongside architecture, security and adoption, so the running cost of a decision is visible while it can still be changed. Our delivery approach explains where licensing sits in the wider system.

How we deliver

A conversation, not a pitch

What does the renewal look like?

Tell us what is worrying you: a number that has grown, licences you suspect are unused, or a Power Platform bill that keeps changing shape. We will tell you what we would look at first.

Renewal is coming
and nobody can explain
the number.

Licence cost rarely grows on purpose.

Renewal is coming and nobody can explain the number

We are paying for people who left

We think we are over-licensed, but nobody will sign it off

Power Platform cost keeps appearing

Somebody mentioned indirect access

Two people doing the same job have different licences