Executive summary

Choose a software licensing advisor by how they are paid, not by how they pitch, because the payment model decides whose side they are on. An advisor who earns a margin on the software you buy has a reason to want the deal larger, while an advisor paid by you to shrink the deal has a reason to want it smaller. The wrong choice can cost more than the engagement was ever meant to save, on Oracle, Microsoft, SAP, and every vendor in your portfolio. This paper sets out what an advisor does, how the buyer-side test works, the fee models and their trade-offs, the proof of expertise to verify, the scope options to scope correctly, and the selection scorecard that turns a vague search into a defensible decision.

Our advisors work the buyer side only and take no vendor commission. Across more than 500 enterprise engagements, the buyers we advise have negotiated over $2.4 billion in software and cloud contracts at an average saving near 38 percent, and our audit defence work averages a 72 percent reduction against the initial claim. The figures below frame the decision you are about to make.

1. What a licensing advisor actually does, and does not

A software licensing advisor exists to put a buyer on equal footing with a vendor that negotiates these deals every day. The vendor account team knows the price list, the discount thresholds, the audit clause, and the quarter-end math better than any customer who touches a renewal once every three years. An advisor closes that knowledge gap and stands between your team and the vendor playbook.

The work falls into a few concrete jobs. An advisor reconciles your deployed usage against your entitlement so you know your true position before the vendor tells you theirs. An advisor models the deal, the renewal, or the audit claim independently, so the vendor number is tested rather than accepted. An advisor sets the lever order, the timing, and the clause language that protect you over the life of the agreement.

The value is sharpest where the stakes are largest and the cadence is rare. A CIO may sign one Oracle renewal in three years and one Microsoft Enterprise Agreement true-up a year, while the account team on the other side runs hundreds. That asymmetry is the whole reason an advisor pays for itself. The buyer who walks in with a reconciled position, a modeled number, and a calendar has changed the contest from information to evidence.

What an advisor is not

An advisor is not a reseller, not a vendor partner, and not a software procurement outsourcer who is paid more when you spend more. An advisor is also not a research subscription that sells the same reports to you and to the vendor selling to you. The distinction matters because each of those roles has a reason to want a different outcome than the one you are paying for.

2. The buyer-side test: follow the money first

The single most important screen is how the advisor gets paid, because every other quality flows from it. An independent advisor takes a fee from you and no commission, rebate, or margin from any vendor. A reseller or vendor partner earns on the transaction, which means a larger contract pays them more, and that incentive sits underneath every recommendation they make.

This is not a claim that resellers are dishonest. It is a structural point. A reseller can be skilled and well intentioned and still be paid in a way that rewards the opposite of what you want. When the advice is to buy more, to renew early, or to accept a bundle, you cannot tell from the outside whether the advice serves you or the margin, so you remove the doubt by removing the conflict.

The same logic disqualifies one pitch that sounds like a strength. When a firm says it has a special relationship with the vendor, ask what that relationship is worth to the firm. A partner status, a rebate tier, or a co-sell arrangement is a payment from the vendor by another name, and it points the firm toward keeping the vendor happy. The relationship you want your advisor to protect is yours, not the vendor's.

Ask the question directly and get the answer in writing. Do you receive any payment, commission, rebate, referral fee, or soft benefit from any software vendor or reseller. A clean independent advisor answers no without hesitation and will put it in the engagement letter. Anyone who hedges that answer has told you where their incentive sits.

3. Fee models and the trade-offs you are choosing

Once the advisor is genuinely buyer side, the fee structure is a real decision with real trade-offs, not a formality. The four common models are a fixed project fee, a day rate, a retainer, and a contingency share of verified savings. Each aligns differently and suits a different kind of engagement.

A fixed project fee gives you budget certainty and a defined scope, which works well for a single renewal or a discrete audit response. A day rate suits open-ended or advisory-only work where the scope is hard to fix in advance. A retainer suits an estate with rolling renewals and a standing audit risk, where you want cover across the year rather than one project. A contingency fee, a share of the savings the advisor verifiably delivers, aligns the advisor tightly to the result but depends on an agreed, clean baseline so that the saving is measured honestly.

The contingency model deserves a closer look because it is the one most often misunderstood. The saving is only as honest as the baseline it is measured against. If the baseline is the vendor's opening quote, almost any negotiated number looks like a win. Agree the baseline as your realistic likely outcome without the advisor, document it, and the contingency fee becomes a fair measure rather than a number that flatters itself.

Keep the fee in proportion to the stake

A fee is only expensive against the wrong number. Measured against a seven-figure Oracle audit claim or a multi-year Microsoft commitment, an advisory fee is a small fraction of the exposure it is meant to reduce. Measured against a small, clean renewal, the same fee may not earn its place. Size the engagement, and the fee, against the money actually at risk, not against a flat sense of cost, and the decision becomes a simple return calculation rather than a budget line to defend.

4. Proof of expertise: what to verify before you sign

Licensing expertise is vendor specific and metric specific, so general experience is not enough. An advisor who is excellent on Oracle Database processor licensing may have never run a SAP indirect access defence or a Microsoft Enterprise Agreement true-up. Verify named experience with the exact vendors and the exact problems in front of you, not a generic claim of broad coverage.

Ask for the specifics. Which vendors do the named individuals on your account negotiate most. Have they worked your metric, whether that is Oracle Processor and Named User Plus, the Java SE Universal Subscription per employee, Microsoft E3 and E5 and the Enterprise Agreement true-up, SAP digital access and the S/4HANA conversion, or VMware per-core after the subscription change. The right answer names the mechanism, not the brand.

References that actually test the claim

Ask for references from engagements that resemble yours in vendor, size, and problem type. A reference for a small Microsoft renewal tells you little about an advisor's ability to run an Oracle audit defence across a virtualised estate. When you speak to a reference, ask what the advisor found that the buyer had missed, because that is the value an experienced advisor adds.

5. Scope the engagement to the problem in front of you

Licensing advisory is not one service, and scoping it correctly is half the value. The common engagement types solve different problems, and the right advisor will tell you which one you actually need rather than selling the largest package. Match the scope to the trigger that brought you here.

The cost of a bad scope runs both ways. Scope too small and the advisor cannot protect the clauses that bind you for years. Scope too large and you pay for work the problem does not need. A good advisor narrows the engagement to the levers that move your specific number and tells you plainly where outside help adds nothing.

When to keep the work in house

A good advisor will also tell you when you do not need one. A routine renewal with no metric change, a small estate on a single vendor, or a true-up that your software asset management team already measures cleanly may not justify an external fee. The honest answer protects the relationship for the deals that do need outside help, the audit with seven figures at stake, the ULA certification, the metric that no longer matches your deployment. Ask each candidate where they would decline to bid, because the firm that names those cases is reading your interest rather than its own pipeline.

6. Vendor-specific depth, and what good looks like

The phrase software licensing advisor covers very different bodies of knowledge, and the right advisor proves depth in the vendors that dominate your spend. Breadth across logos is useful, but the money is won in the detail of a single vendor's rules, so test for the detail rather than the brand list.

On Oracle, depth shows up as fluency in the Core Factor Table, the Processor versus Named User Plus decision, the soft partitioning argument, and the Java SE per-employee subscription. On Microsoft, it shows up in the Enterprise Agreement true-up, the E3 and E5 step-up math, Visual Studio subscriptions, and the Azure MACC commitment. On SAP, it is digital access and the indirect use exposure, the S/4HANA conversion credit, and the RISE migration terms. On the cloud side, it is the AWS EDP and the Azure MACC, where an over-commit locks in spend you may not use.

Ask each candidate to walk you through one of those mechanisms from memory, in plain terms, for the vendor that matters most to you. A genuine specialist explains the rule, names where buyers overpay, and tells you the clause that fixes it. A generalist describes the vendor in marketing language and moves quickly back to the pitch. The difference is audible in five minutes.

Depth also shows in what the advisor refuses to promise. A specialist will tell you which parts of your estate are already efficient and need no work, and will scope the engagement around the vendors and metrics where real money is on the table. That candour is itself a proof of expertise, because only someone who knows the rules can tell you where they do not apply to you.

7. The red flags that should end a conversation

Some signals tell you to stop before you sign. A few are obvious, and a few are quiet. The quiet ones do the most damage because they are easy to miss in a polished pitch. Treat the following as reasons to slow down and ask harder questions.

A refusal to put the no-vendor-money position in writing is the clearest signal. So is an advisor who pushes you toward a specific vendor product or a specific reseller, because a genuinely independent advisor is indifferent to which vendor you choose and is paid the same either way. A promise of a guaranteed saving percentage before anyone has looked at your estate is a sales line, not an analysis, because no honest advisor can quote a result before measuring the position.

Two softer signals deserve weight. The first is an advisor who talks only about discount percentage and never about clauses, because the percentage is the easy win and the clauses are where the multi-year money sits. The second is reluctance to name the people who will run the work, which usually means the engagement will be staffed below the level you were sold. Neither is fatal on its own, but together they describe a sales motion rather than an advisory practice.

Questions that surface the quiet problems

• Do you, or your firm, receive any payment from any vendor or reseller, in any form. Get it in writing.
• Who specifically runs my engagement, and what is their named experience with my vendors and metrics.
• How do you define and measure the saving, and against what baseline.
• What happens to my data and my contract terms after the engagement ends.
• Will you tell me when I do not need you, or when an internal fix is enough.

8. The conflict spectrum, illustrated

It helps to picture the choices on a single axis from most conflicted to least conflicted with your interest. The vendor account team sits at one end, paid to grow your spend. An independent buyer-side advisor sits at the other, paid to shrink it. The roles in between carry partial conflicts that are easy to underestimate. The index below is illustrative, with the fully aligned position set to 100, and is not a market benchmark.

Read the chart as a map of incentives, not of skill. A reseller can be more skilled than an independent advisor and still be pulled toward a larger deal by the way they are paid. The point of the buyer-side test is to remove that pull entirely, so that skill works only in your direction.

9. Timing: bring the advisor in early

The most common and most expensive mistake is hiring an advisor too late. The levers that matter, the structural clauses, the support cap, the renewal timing, and a credible walk-away, all exist before the vendor sets the deadline. An advisor engaged the week before signature can negotiate a discount and little else, because the moves that matter have already closed.

Bring an advisor in twelve to eighteen months before a major renewal, at the first audit or soft review letter, and well before a ULA, an AWS EDP, or an Azure MACC reaches its expiry. Early engagement is what lets the advisor reconcile your usage, set the timing against the vendor's fiscal close, and protect the clauses while there is still time to win them.

A well-run engagement has a shape. In the first weeks the advisor reconciles deployment against entitlement and builds your independent position. Over the following months that position becomes a strategy, with a target outcome, a lever order, and a walk-away that the vendor can believe. The closing phase aims the signature at the period end where the account team holds the most flexibility. Hire late and you arrive at the closing phase with none of the work behind it done, which is why the calendar, not the meeting, is where outcomes are decided.

Our recommendation: screen first on the payment model and get the no-vendor-money position in writing, verify named experience with your exact vendors and metrics, match the fee structure to the engagement and fix the baseline on any contingency, and bring the advisor in early enough to protect the clauses and the timing rather than only the discount. The advisor you choose is, in effect, choosing whose interest sits across the table from the vendor. Choose the one paid only to protect yours.

Sources: standard buyer-side advisory and procurement engagement models, as commonly structured at the time of review. Outcome ranges are Atonement Licensing advisory figures, indicative and deal-specific, not a quote.

Related reading: Software Audit Defense hub, Software Licensing Advisory, Renewal and Discount Strategy Playbook, and Enterprise Software Contract Clauses Playbook.