There is a moment in every software licensing engagement that determines what happens next. It is not the moment the audit begins, and it is not the moment the settlement is reached. It is the moment the publisher decides whether they are delivering a finding or starting a conversation.

Those two things look similar from the outside. Both involve presenting data to a customer. Both require accuracy, preparation, and commercial judgement. But they produce entirely different outcomes, and the gap between them is where most publisher revenue programmes either build lasting value or quietly stall.

What a finding looks like

A finding is a statement of fact. The audit has identified a gap in the customer's licence position. The data is accurate. The methodology is defensible. The commercial exposure is quantified. The publisher presents the finding, the customer receives it, and a negotiation begins.

Findings are necessary. Without them, there is no commercial basis for the engagement and no mechanism to recover value that is genuinely owed. A publisher that cannot produce accurate, defensible findings cannot run a credible programme at scale.

But a finding, on its own, is also the end of something. Once the data is presented and the settlement is reached, the publisher typically disengages. The customer is left with a number to pay and no structured support to ensure the position does not rebuild. The relationship, such as it is, has served its purpose.

Publishers who operate purely at the level of findings are running a programme that is structurally designed to repeat itself. The finding surfaces the gap. The settlement closes it commercially. And then, without remediation or ongoing visibility, the gap reopens. The programme returns to the same account in a few years and finds the same problems.

That is not a programme built for growth. It is a programme built for repetition.

What a conversation looks like

A conversation starts from the same place as a finding. The data is still accurate. The methodology is still defensible. The commercial exposure is still quantified. But the publisher does not stop there.

Instead of presenting a number and opening a negotiation, the publisher uses the data as the starting point for a different kind of dialogue. What does this licence position tell us about how the customer is actually using the software? Where are the gaps between what they have deployed and what they are getting value from? What would a genuinely accurate and sustainable position look like for this customer going forward?

These questions change the nature of the engagement. They shift the publisher from the role of auditor to the role of advisor. And they open access to a different kind of buyer relationship, one that is not limited to the compliance and asset management team but extends to the commercial, procurement, and technology leadership who make decisions about long-term software investment.

The conversation does not diminish the commercial outcome of the finding. It builds on it. A customer who understands that the publisher's engagement is designed to leave them in a genuinely better position is more likely to settle constructively, more likely to invest in the right licence position, and more likely to remain a partner worth growing.

Why independence makes the difference

There is a reason this shift is harder than it sounds. A publisher presenting its own audit findings is, by definition, a party with a commercial interest in the outcome. The customer knows this. Even when the data is entirely accurate and the methodology is entirely sound, the relationship starts from a position of asymmetry.

The customer is being told by the publisher that the customer owes something. That framing, however professionally handled, creates friction. It makes the finding feel adversarial even when it is not, and it makes the conversation that follows harder to have.

Independence changes that dynamic. When a neutral third party presents the findings, the data carries different weight. The customer is not receiving a claim from a party with a financial stake in the number. They are receiving an accurate assessment from a party whose credibility depends on being right, not on maximising the settlement.

That is the foundation of trust. And trust is what makes a finding the beginning of a conversation rather than the beginning of a dispute.

What this means for how publisher programmes are built

The distinction between a finding and a conversation is not just a matter of tone or relationship management. It is a structural question about what a publisher programme is designed to produce.

A programme designed around findings will invest heavily in audit methodology, data collection, and settlement negotiation. Those capabilities matter and they should be best in class. But they are the entry point, not the destination.

A programme designed around conversations will layer advisory capability on top of that foundation. It will invest in the product knowledge and commercial insight that allow a licensing specialist to speak credibly with a renewal lead or a procurement director, not just a compliance manager. It will build the ongoing visibility into customer usage that makes those conversations substantive rather than transactional.

The publishers who make that investment consistently outperform those who do not, on renewal rates, customer lifetime value, and the depth of the commercial relationships they are able to build and sustain.

The finding is where the programme earns the right to enter the room. The conversation is what determines whether the publisher gets to stay.

---

Connor Consulting helps software publishers build the capability to move from audit to advisory. To learn more, visit connor-consulting.com/software-publisher-services

‍