Software Licensing & Distribution
“Licensing is where intellectual property meets revenue. Get the license model wrong, and you either leave money on the table or create enforcement headaches that last for years. The terms have to match how the software actually gets used.”
— John Montague
Software licensing remains the legal backbone of the technology industry, even as delivery models evolve from on-premise installations to cloud-hosted platforms and hybrid architectures. John Montague has drafted and negotiated software license agreements across every major distribution model for over 15 years — from perpetual enterprise licenses and OEM distribution agreements to open source dual-licensing strategies and freemium models. His experience at Locke Lord LLP (now Troutman Pepper Locke), an AM Law 200 firm, gave him early exposure to complex multi-party licensing structures for major technology platforms, a foundation he has built upon throughout his career representing software companies from his offices in Fernandina Beach and Coral Gables (Miami), Florida.
Software licensing sits at the intersection of intellectual property law, contract law, and business strategy. John Montague’s accounting degree from Stetson University gives him an unusual ability to connect licensing structures with revenue recognition requirements — a critical consideration for software companies navigating ASC 606 and its impact on how license arrangements must be structured to achieve desired financial reporting outcomes.
What I Handle
Enterprise Software License Agreements. I draft and negotiate enterprise software licenses for both licensors and licensees. These agreements address scope of use (named users, concurrent users, site licenses, enterprise-wide), delivery and installation, acceptance testing, maintenance and support obligations, upgrade rights, and fee structures. For licensors, I focus on creating clear usage boundaries, effective audit rights, and protective IP provisions. For licensees, I negotiate favorable pricing, flexible usage terms, and meaningful performance warranties.
OEM and Distribution Agreements. When software is embedded in or bundled with another company’s product, the licensing relationship becomes significantly more complex. I draft OEM agreements, reseller agreements, VAR (value-added reseller) agreements, and distribution agreements that clearly allocate IP rights, support responsibilities, warranty obligations, and revenue sharing between the parties. These agreements must address branding, co-marketing, technical integration requirements, and the commercial relationship in parallel.
Open Source Licensing Strategy. Open source licensing is no longer optional for most software companies — it’s a strategic decision that affects community adoption, competitive positioning, and acquisition value. I advise companies on selecting appropriate open source licenses (MIT, Apache 2.0, GPL, AGPL, BSL, and others), implementing dual-licensing strategies, and managing open source compliance programs. This includes evaluating the compatibility of different open source licenses within a single codebase and assessing the copyleft implications of incorporating GPL-licensed components.
Channel and Marketplace Distribution. Distribution through app stores, cloud marketplaces (AWS Marketplace, Azure Marketplace, Google Cloud Marketplace), and channel partner networks introduces additional contractual layers. I negotiate marketplace listing agreements, channel partner terms, and co-sell arrangements that balance distribution reach with margin protection and customer relationship control.
Key Legal Considerations in Software Licensing
The legal framework for software licensing in the United States draws from both federal and state law. Copyright protection under the Copyright Act of 1976 (17 U.S.C. § 101 et seq.) provides the foundational IP rights that make software licensing possible — software is protected as a literary work, and the copyright holder controls reproduction, distribution, and the creation of derivative works. Patent protection may also apply to software-implemented inventions, although the scope of software patent eligibility has been significantly narrowed by the Supreme Court’s decision in Alice Corp. v. CLS Bank International (2014).
The enforceability of software license terms — particularly shrink-wrap and click-wrap agreements — has been established through a line of cases including ProCD, Inc. v. Zeidenberg (7th Cir. 1996) and Bowers v. Baystate Technologies, Inc. (Fed. Cir. 2003), though browse-wrap agreements remain more legally uncertain. John Montague ensures that license agreement formation mechanisms are designed to maximize enforceability under current law.
Revenue recognition under ASC 606 (Revenue from Contracts with Customers) directly affects how software license agreements must be structured. The standard requires companies to identify performance obligations, determine the transaction price, and allocate revenue across performance obligations. For software companies, the distinction between a “right to use” license (recognized at a point in time) and a “right to access” license (recognized over time) has significant financial reporting implications that must be considered when structuring the license terms.
John’s Tip
John’s Tip: If you’re building a software company, think about your licensing model as a product decision, not just a legal one. The license structure affects how customers perceive value, how your sales team sells, and how your finance team recognizes revenue. I work with founders to design license models that align all three — legal protection, commercial strategy, and financial reporting — from the start rather than trying to retrofit them after the product is in market.
Frequently Asked Questions
What’s the difference between a software license and a SaaS subscription?
A software license grants the customer rights to install and use a copy of the software, typically on the customer’s own infrastructure. A SaaS subscription provides access to software hosted and operated by the provider — the customer never receives a copy. This distinction affects IP ownership, data control, liability allocation, and how revenue is recognized. John Montague, Esq. advises companies offering both models on how to structure agreements that clearly delineate the rights and obligations under each.
Can I change my software licensing model after launch?
Yes, but it requires careful planning. Transitioning from perpetual licenses to subscription models, or from proprietary to open source, involves legal, financial, and customer relationship considerations. Existing license agreements may need to be amended, grandfather provisions created, and new standard terms drafted. Revenue recognition and valuation implications should also be evaluated before making the transition.
How do I protect my software from unauthorized use while keeping licensing terms customer-friendly?
Effective license compliance programs combine clear contractual audit rights with practical enforcement mechanisms. I draft license agreements that include reasonable audit provisions, clear usage metrics, and consequences for over-deployment — while avoiding terms so draconian that they deter legitimate customers. Technical measures like license key management and usage metering should complement, not replace, well-drafted contractual protections.
About John Montague, Esq.
John Montague, Esq. advises software companies on licensing strategy, distribution agreements, and IP protection from his offices in Fernandina Beach and Coral Gables (Miami), Florida. With a J.D. from the University of Florida and experience at Locke Lord LLP (an AM Law 200 firm), John brings both legal depth and commercial pragmatism to software licensing matters. He serves as a Visiting Professor of Entrepreneurial Law at UF’s College of Business.