Know your software licence position before it becomes a problem.
Proactive, independent licence reviews for OpenText and SAP customers, so you stay compliant, supported, and protected ahead of audits, patch windows, and contract renewals.
Enterprise software licensing is complex. The consequences of getting it wrong are not.
Many organisations are unknowingly running non-compliant environments - not through negligence, but because licensing models evolve faster than IT asset management processes do. The gap is most acute with vendors like OpenText and SAP, where metrics are complex, contracts are long, and audit exposure can materialise without warning.
Your patch and support access may already be at risk
Enterprise software vendors tightly link active licence compliance to security patch and support eligibility. If your installation is non-compliant - even partially - you may find yourself unable to access critical security updates at your next renewal. This is not theoretical: OpenText customers are already experiencing it, and the same dynamic applies to SAP customers approaching end-of-mainstream maintenance on older product versions.
Audits are becoming more frequent and more targeted
Many enterprise software vendors have sophisticated tooling to identify licence non-compliance across their customer base. Audits are no longer random events; they are increasingly triggered by specific signals. By the time you receive an audit notice, the cost of remediation is invariably higher than the cost of prevention.
How organisations end up out of compliance
Organic growth in deployments beyond licence entitlements. Connector or module additions that were never licenced. Third-party system integrations that trigger indirect access or digital access metrics. Mergers and acquisitions that brought in unlicensed installations. Version upgrades or platform migrations that reset licence obligations. Any one of these, common in a normal IT lifecycle, can create material exposure.
The gap between cost of prevention and cost of remediation
Customers who discover compliance gaps during a vendor audit face a very different negotiation than those who proactively remediate. The vendor has more leverage, timelines are compressed, and the cost typically includes backdated licence fees. A proactive review eliminates this dynamic entirely.
The OpenText licensing risks that matter most
OpenText's licence model has grown through acquisitions - Documentum, Hummingbird, Actuate, and others each brought distinct licensing frameworks. Maintaining a compliant, well-understood position across a complex OpenText estate requires more than keeping track of user counts.
Patch access is directly tied to licence compliance
OpenText's support framework makes security patch access conditional on active licence compliance. The link is in the contract terms: customers who are non-compliant - or whose support maintenance has lapsed - may not qualify for patches even if they exist. Given the pace at which AI tools are now finding vulnerabilities in closed-source software, this is no longer a theoretical risk. It's an exposure that compounds over time.
Audits are triggered by signals, not schedules
Many enterprise software vendors have sophisticated tooling to identify licence non-compliance across their customer base. For OpenText, this includes deployment data, connector usage patterns, and version telemetry. Audits are no longer random events; they are increasingly triggered by specific signals. By the time you receive an audit notice, the cost of remediation is invariably higher than the cost of prevention.
Backdated fees are built into OpenText's contract terms
OpenText's licence terms - including those inherited from Actuate and BIRT PowerDocs - explicitly permit the recovery of backdated fees where under-reported usage is identified, with interest provisions in some product schedules. This isn't a negotiating position; it's a contractual right that OpenText can and does exercise. Identifying and remediating gaps before an audit closes this exposure.
Most OpenText compliance gaps are structural, not accidental.
Organic growth, post-acquisition integration, and connector deployments that were never formally licenced are the most common root causes. The complexity is entirely normal - but the cost of discovering it during an audit rather than before one can be significant. A proactive review changes the negotiating dynamic entirely.
The SAP licensing risks that most customers don't see coming
SAP's licensing model is deliberately granular. User types, document-based metrics, and migration frameworks all create exposure that doesn't surface in a standard headcount review. My SAP advisory work focuses on the three areas that most consistently generate audit findings.
Third-party integrations may already be triggering document licence obligations
SAP's Digital Access model measures licence obligations by the volume of SAP documents created by third-party systems - purchase orders, sales orders, goods receipts - not just by named users. E-commerce platforms, supplier portals, IoT systems, and automation tools that connect to SAP can generate these documents at scale. Many customers don't know this exposure exists because it's invisible in a standard named-user audit.
Most SAP customers have at least some users on the wrong licence type
SAP's user hierarchy - Professional, Limited Professional, Employee, Developer, and others - defines what each user is permitted to do. The definitions are precise but not intuitive, and the gap between what users actually do and what they're licensed to do is the most common source of SAP audit findings. SAP's own measurement tools (USMM and LAW) are designed to surface this gap. Most customers have never run an independent assessment of whether their user classifications hold up under SAP's audit methodology.
Migrating to S/4HANA is a re-licensing event, not just a technical upgrade
Signing a RISE with SAP or S/4HANA transformation agreement involves accepting a new licence framework. Entitlements held under legacy contracts don't always carry forward automatically, new consumption metrics may apply that didn't exist before, and the package consolidation offered in migration deals often resolves less exposure than it appears to. Independent review before signing a migration agreement consistently pays for itself.
SAP audit notices typically arrive with a 90-day response window.
SAP provides a pre-populated findings document using its own measurement methodology as the baseline. Without independent expertise, it's very difficult to challenge whether the measurement approach was applied correctly - or whether your contract terms actually support SAP's findings. Most initial findings documents contain room for challenge. The window to exercise it effectively is before you accept SAP's framework as given.
The threat landscape is changing for unsupported enterprise software deployments
Being out of licence compliance doesn't just create a licensing problem; it increasingly creates a security one.
AI has found thousands of severe security flaws - and regulators are now taking notice
In April 2026, Anthropic published research showing that Claude Mythos Preview had autonomously discovered thousands of severe security flaws across all major operating systems, browsers, and closed-source software - often overnight, without human intervention. The findings were significant enough that Anthropic has since been asked to brief the Financial Stability Board, the global body of finance ministries and central banks, on the implications for systemic cyber risk. The IMF has separately warned that AI models of this capability could turn cyber vulnerabilities into a "macro-financial shock." Closed-source enterprise software sits squarely in scope. Anthropic research → Reuters / FT report →
Unsupported versions cannot ever be patched
When an enterprise software product version falls outside active support, security patches cease permanently. If a vulnerability is discovered in that version - by a researcher, an AI tool, or anyone else - there is no patch coming. The attack surface doesn't just exist; it grows over time as more vulnerabilities are found and published. Customers on non-compliant installations who have lost support entitlements are in the same position: even patches that exist are out of reach.
The compliance and security trap
Here's the bind: if you're out of licence compliance, you may not qualify for support entitlements, which means you can't access patches even when they exist. Non-compliant customers often find they're simultaneously exposed to audit risk and security risk, with no clean path forward without independent guidance.
Licence compliance and security posture are now directly connected, in ways that weren't true two years ago.
The emergence of AI models capable of finding zero-days in enterprise software at scale changes the risk calculus for every organisation running legacy or non-compliant deployments. If you're out of compliance, you can't access patches. If you can't access patches, every new vulnerability found - by anyone, using any tool - is permanent exposure. A licence review is no longer just a financial exercise. It's a security risk review.
Independent software licence advisory
I work exclusively on your side, independently of your software vendors, to give you an honest picture of your licence position and a clear path to compliance. My deepest expertise is in OpenText and SAP, but I advise across the enterprise software landscape.
Licence Position Review
A thorough, confidential review of your current licence entitlements against your actual deployment. I identify what's covered, what isn't, and where the gaps are - before your vendor does.
Compliance Gap Analysis
Once I know your position, I quantify the exposure. You'll receive a clear, prioritised assessment of compliance gaps, ranked by audit risk, support access impact, and financial exposure, so you can make informed decisions.
Remediation Roadmap
I don't just identify problems; I help you fix them. You'll receive a pragmatic, actionable remediation plan including licence restructuring options, renewal strategy, and timing recommendations.
Pre-Audit Preparation
If you've received an audit notice, or suspect one is coming, I can prepare you. I'll help you understand your position, identify your strongest negotiating points, and ensure you're not caught off-guard by the vendor's findings.
Renewal & Contract Review
Licence renewals and migration agreements are the ideal moment to optimise your position. I review your terms against your actual usage, identify over-licencing and under-licencing, and help you enter negotiations with full visibility.
Ongoing Licence Management
For organisations who want continued visibility, I offer ongoing licence monitoring, so your position stays clean between audits, renewals, and platform changes. Compliance as a habit, not a crisis response.
Simple, clear, and confidential
I designed the process to be low-friction and respectful of your time, with no obligation to proceed beyond any step.
Initial conversation (30 minutes)
A confidential call to understand your software environment: which vendors and products you're running, deployment scale, and any specific concerns around compliance, upcoming renewals, or an active audit notice. No commitment required; this is about understanding whether I can help.
Licence position review (3 to 5 business days)
I conduct a detailed analysis of your licence entitlements against your actual deployment profile. I work from the documentation you can provide: licence agreements, purchase records, and deployment reports. I supplement that with my own deep knowledge of your vendor's licensing model. You don't need everything to hand; I'll work with what you have.
Findings and recommendations
I present a clear, written summary of your licence position, including any compliance gaps, support access risks, and my recommendations for remediation. The report is yours to keep and act on independently. If you'd like my support putting the recommendations into practice, I'm available for that too.
Optional: ongoing support
Many clients choose to retain me on an ongoing basis for licence monitoring, renewal preparation, and periodic compliance checks. This is entirely optional; the initial review is a complete, standalone engagement if that's what you need.
What proactive licence optimisation looks like in practice
The following are illustrative scenarios based on the types of issues commonly encountered in OpenText and SAP environments. Details are anonymised.
Content Server deployment outgrew its licence and lost patch eligibility
A mid-size law firm had organically grown its Content Server deployment over five years. User counts had increased significantly beyond original licence entitlements, and a version upgrade had triggered new module licensing requirements that were never fulfilled. As a result, the firm had unknowingly lost eligibility for security patches at the previous renewal, without being notified.
Unlicensed xECM connectors discovered months before an audit cycle
A financial services firm had extended its xECM deployment with additional Salesforce and SAP connectors following an internal CRM migration. The connectors were deployed by the implementation partner without formal licence confirmation. An OpenText licence review flagged the exposure, but the firm had not yet received formal notice from OpenText.
Third-party integrations generating SAP documents triggered unexpected licence obligations
A manufacturing company had connected its supplier portal and logistics platform to its SAP estate through a systems integrator. Both integrations automatically generated SAP documents - goods receipts and inbound delivery notices - at a volume not reflected in the original licence position. SAP's internal tooling identified the document volumes during a scheduled licence verification exercise.
Deep expertise in OpenText and SAP licensing. Independent advice.
I'm an independent consultant with extensive hands-on experience across the enterprise software licensing landscape - with particular depth in OpenText and SAP, where licence complexity, audit exposure, and the cost of getting it wrong are highest.
I don't sell software licences. I don't have referral relationships with vendors. My only interest is in making sure you have an accurate, complete picture of your licence position, with a clear path to maintaining it.
"Most enterprise software customers I speak to are not knowingly non-compliant. They've simply grown, evolved, and integrated their platforms over time - without a mechanism to track whether their licence position has kept pace. A proactive review is not an admission of a problem. It's evidence of good governance."
Sean O'Callaghan, Enterprise Software Licence Consultant
Start with a confidential conversation
If you have questions about your OpenText or SAP licence position, or you're simply not sure where you stand, get in touch. There's no obligation, and the initial conversation is free.
I typically respond within one business day.
Not sure if you need a review?
If your OpenText or SAP environment has grown since your last licence review, you've added integrations or connectors, you're approaching a renewal, or you've received any communication from your vendor about compliance - it's worth a conversation.
Request a confidential review
Click to copy · or email directly