Blog › ICP guides
IP licensing attorney on retainer: IP licensing agreement advisory, technology transfer advisory, and cross-license and portfolio licensing advisory on monthly retainer
August 5, 2026 · ~22 min read
A semiconductor company receives a licensing demand letter from a consortium that holds a portfolio of standard essential patents (SEPs) covering the IEEE 802.11 Wi-Fi standard. The consortium claims that the company’s wireless networking modules infringe twenty-three SEPs in the portfolio and demands a royalty of 4.2% of net revenue from all wireless-enabled products. The company’s engineering team confirms that its modules implement the IEEE 802.11ax (Wi-Fi 6) standard and therefore necessarily use the patented techniques covered by the consortium’s declared SEPs. The company’s CFO asks whether the 4.2% rate is reasonable, whether the royalty base (net revenue from all wireless-enabled products rather than from the Wi-Fi module component) is appropriate, and what leverage the company has in negotiating the license.
The answers require an analysis of the consortium’s FRAND (fair, reasonable, and non-discriminatory) commitment under the IEEE IPR Policy. When the SEP owners declared their patents as essential to the IEEE 802.11 standard and committed to license them on FRAND terms, they accepted a constraint on the royalty rates they could demand from implementers of the standard. The FRAND commitment does not fix a specific rate but establishes a range within which the offered rate must fall, evaluated against comparable licenses granted by the same SEP holder to similarly situated licensees. The 4.2% rate applied to net revenue from all wireless-enabled products is potentially above the FRAND range for several reasons: applying the royalty to the full wireless-enabled product rather than to the smallest salable patent practicing unit (the Wi-Fi module component that actually implements the standard) inflates the royalty base beyond what FRAND analysis supports; and the consortium’s comparable licenses with other major implementers should be disclosed and compared to the offered rate.
IP licensing attorneys on monthly retainer — J.D.s with specialized experience in patent and copyright licensing, technology transfer, licensing agreement drafting, and licensing negotiation — do a substantial share of their highest-value work between the visible milestones of license signings, royalty audit results, and licensing disputes. This guide covers IP licensing agreement advisory, technology transfer advisory, and cross-license and portfolio licensing advisory: the legal frameworks behind each service area, the specific licensing structures and valuation methodologies that govern the advisory, and how to structure a retainer agreement that makes the ongoing IP licensing advisory work visible between transaction milestones.
IP licensing agreement advisory
IP licensing agreement advisory is the retainer function that advises on the structure, negotiation, and drafting of IP licenses governing the use of patents, copyrights, trademarks, trade secrets, and other intellectual property rights. Each licensing transaction requires advisory on the fundamental economic and legal terms that determine the value of the license to the licensor, the risk exposure of the licensee, and the ongoing compliance obligations of both parties over the life of the agreement.
Exclusive vs. non-exclusive license structure
The threshold decision in IP license structure is whether to grant an exclusive or non-exclusive license. An exclusive license grants the licensee the sole right to practice the licensed IP within the defined field of use and territory, excluding all other parties — including the licensor — from practicing the licensed IP within those defined parameters. A non-exclusive license grants the licensee a right to practice the licensed IP alongside other licensees who may receive the same or similar rights. Between these poles, a sole license grants exclusive rights to the licensee but does not exclude the licensor itself from continuing to practice the licensed IP.
Exclusive license advisory requires evaluating the commercial rationale for granting exclusivity: whether the licensee will invest sufficiently in developing and commercializing the licensed technology only if protected by exclusivity from competing licensees, whether the licensor’s technology is at a stage where exclusivity is necessary to attract a commercially capable licensee partner, and whether the licensor can structure the exclusive license with field-of-use and territory restrictions that protect the licensor’s ability to license the same IP in adjacent applications or geographic markets. The retained attorney advising on exclusive license structure evaluates the appropriate field-of-use definition — sufficiently specific to grant the licensee meaningful protection in its target market without foreclosing the licensor from licensing the same IP for other applications — and the appropriate term for exclusivity, which may be limited to a specific period (after which the license converts to non-exclusive) or conditional on performance milestones (with a provision allowing the licensor to convert to non-exclusive if the licensee fails to meet specified commercialization milestones).
Non-exclusive license advisory is appropriate where the licensor’s commercial interest is in maximizing revenue from multiple licensees in the same market, where the licensed IP is already licensed to multiple parties and the new licensee has no reasonable expectation of exclusivity, or where the licensor is licensing standards-essential IP under a FRAND commitment that requires non-discriminatory licensing to all implementers of the standard. The retained attorney advising on non-exclusive license terms evaluates whether to include a most-favored-licensee (MFL) clause guaranteeing the non-exclusive licensee that the licensor will not offer more favorable royalty terms to other licensees — MFL clauses can be commercially attractive to licensees who fear being competitively disadvantaged by lower royalty burdens paid by competitors under the same patent portfolio, but they constrain the licensor’s flexibility to negotiate differentiated rates based on volume, strategic partnership value, or settlement context.
Royalty structure and royalty base advisory
Royalty structure advisory covers the selection of the economic terms that govern the licensee’s payments for the right to practice the licensed IP. Running royalties (calculated as a percentage of net sales of licensed products) are the most common royalty structure for patent licenses. The royalty rate and royalty base together determine the effective economic burden of the license on the licensee: a rate that is moderate when applied to a narrowly defined royalty base (the component that actually implements the licensed invention) may produce the same royalty obligation as a lower rate applied to a broader royalty base (the finished product containing the component). The retained attorney advising on royalty structure evaluates both the royalty rate and the royalty base together to assess the total effective royalty burden relative to the economic value contributed by the licensed IP.
Royalty base and the entire market value rule is one of the most consequential licensing advisory issues in technology licensing. Under the entire market value rule (EMVR), a royalty may be calculated on the net revenue from the entire product rather than from the smallest salable component only where the patented feature drives customer demand for the entire product — where consumers purchase the product primarily because of the functionality provided by the licensed IP. Where the patented feature is one of many features in a complex multi-component product and is not the primary driver of customer demand, federal courts applying the EMVR in patent infringement damages cases have required that the royalty base be limited to the smallest salable patent practicing unit (SSPPU) — the smallest component of the product that can be sold separately and that practices the licensed patent claims. The retained attorney advising on royalty base in a patent license negotiation evaluates whether the licensor’s proposed royalty base is consistent with the SSPPU standard or includes non-patented features that should be excluded from the royalty calculation.
Milestone payments and minimum annual royalties provide the licensor with guaranteed revenue that does not depend solely on the licensee’s commercialization success. Milestone payments tied to specific commercialization events — regulatory approval, first commercial sale, reaching a revenue threshold — compensate the licensor for the exclusivity or capability granted in the license even if the licensee’s commercialization ramp-up is slower than projected. Minimum annual royalties (MAR) establish a minimum annual royalty floor that the licensee must pay regardless of its actual sales volume, ensuring that the licensor receives a minimum return on the exclusive license even during periods of low sales. The retained attorney advising on milestone and MAR structures evaluates whether the proposed milestones are realistic relative to the licensee’s commercialization plan, whether the MAR is calibrated to the value of the exclusivity granted rather than to projected royalties from expected sales volume, and whether failure to pay a milestone or meet an MAR triggers a conversion right allowing the licensor to convert the exclusive license to non-exclusive or to terminate the license.
Audit rights and sublicensing advisory
Audit rights provisions in patent license agreements give the licensor the right to audit the licensee’s books and records to verify that the licensee’s royalty reports accurately reflect the licensee’s net sales of licensed products and correctly calculate the royalties owed. Standard audit rights provisions specify: the scope of the audit (which books and records are subject to audit — typically revenue records for licensed products, records supporting deductions claimed against the royalty base such as returns, trade discounts, and taxes, and records of sublicensee royalty payments); the frequency of audits (typically once per calendar year for a running period following the royalty report date); the cost allocation for the audit (the licensor typically bears the cost of the audit unless the audit reveals an underpayment exceeding a threshold, such as 5% of royalties paid during the audit period, in which case the licensee bears the audit cost); the selection of the auditor (typically a licensed CPA or an independent accounting firm not regularly employed by the licensor); and the notice period required before an audit (typically 30 to 60 days written notice).
Sublicensing rights advisory governs whether the licensee can grant sublicenses to third parties under the licensed IP and, if so, the conditions for sublicensing including: whether sublicenses require the licensor’s prior written approval; whether sublicensee royalties must be reported to the licensor and included in the royalty base; what percentage of sublicensee royalties must be paid through to the licensor (the sublicensee royalty flow-through rate, typically 20% to 50% of net sublicensee royalties received by the licensee); and whether sublicenses survive termination of the head license (protecting sublicensees who have made investments in reliance on their sublicense rights). The retained attorney advising on sublicensing provisions evaluates whether the proposed sublicensing structure adequately protects the licensor’s economic interest in sublicensee activity and whether the sublicensee royalty flow-through rate is calibrated to the licensor’s economic contribution to the sublicensee’s commercial activity.
Technology transfer advisory
Technology transfer advisory is the retainer function that advises on licensing transactions involving the transfer of technology from one party to another — most commonly from universities and research institutions to commercial licensees, from one company to another in the context of an R&D partnership or joint venture, or from open source software projects to commercial software developers.
University technology transfer under the Bayh-Dole Act
The Bayh-Dole Act (35 U.S.C. §§200–212), enacted in 1980, allows universities, small businesses, and non-profit organizations to retain title to inventions made with federal funding and to license those inventions to commercial entities. Before Bayh-Dole, the federal government retained ownership of inventions made with federal research funding, limiting universities’ ability to transfer technology to the private sector. Bayh-Dole reversed the default ownership rule, allowing universities to take title to federally funded inventions, file patents, and license the patents to exclusive or non-exclusive commercial licensees, with the requirement that the government retains a non-exclusive, non-transferable, irrevocable, paid-up license to practice the invention and that the government can exercise march-in rights to require additional licensing if the licensee fails to commercialize the invention adequately or if the invention is needed to address a health or safety need.
March-in rights under Bayh-Dole Section 203 (35 U.S.C. §203) allow the federal funding agency to grant a license to a responsible applicant if the patent holder (the university or its commercial licensee) fails to achieve practical application of the subject invention within a reasonable time, fails to satisfy the health and safety needs of the public, or fails to meet requirements for public use as specified by federal regulations. March-in rights are rarely exercised in practice — the NIH has never exercised march-in rights despite numerous petitions requesting march-in to require pharmaceutical companies to license drug patents at lower prices — but the march-in risk affects the commercial value of an exclusive license under a Bayh-Dole patent because the government retains the right to override the exclusive license in specified circumstances.
Government license and flow-down obligations under Bayh-Dole require that exclusive licenses of federally funded patents be subject to the government’s retained non-exclusive license (so the licensee cannot exclude the government from practicing the invention), that the licensed products be manufactured substantially in the United States unless a waiver is obtained, and that sublicenses comply with the same Bayh-Dole obligations as the head license. The retained attorney advising on a Bayh-Dole technology transfer license evaluates how these obligations affect the licensee’s commercial plans (particularly the domestic manufacturing preference for commercial products derived from Bayh-Dole patents), whether any of the Bayh-Dole obligations have been waived by the funding agency, and whether the licensee’s planned business structure — including any offshore manufacturing or development activities — is consistent with the Bayh-Dole compliance obligations in the license.
Software licensing: SaaS, on-premises, and API licensing
Software licensing advisory covers the structure and terms of licenses governing the use and distribution of software products, which may be delivered as software-as-a-service (SaaS) over the internet, as on-premises software installed and operated on the licensee’s own hardware infrastructure, or through an application programming interface (API) that allows the licensee to build applications accessing the licensor’s software functionality.
SaaS license advisory for enterprise software covers the structure of cloud software subscriptions in which the licensee accesses software functionality over the internet without receiving a copy of the software code, which is hosted and maintained by the licensor on the licensor’s cloud infrastructure. SaaS licenses are typically structured as subscription licenses with annual or multi-year terms, per-seat or per-usage pricing, and service level agreements (SLAs) governing uptime, data availability, and incident response. The retained attorney advising on SaaS license terms evaluates: the scope of the license grant (what the licensee is authorized to do with the SaaS access, whether the license covers all features or only a defined feature set, whether the licensee can extract data from the SaaS platform for use in other systems); the data ownership and portability provisions (who owns the data the licensee uploads to or generates within the SaaS platform, and whether the licensee can export its data in a usable format upon license termination); and the liability and indemnification provisions (whether the licensor indemnifies the licensee against IP infringement claims from third parties who assert that the SaaS platform infringes their IP rights, and whether the licensor’s limitation of liability is capped at a commercially reasonable multiple of the fees paid in the prior twelve months).
Open source license compatibility analysis
Open source software licenses govern the terms on which open source components can be used, modified, and distributed. For software developers incorporating open source components into proprietary products, the critical advisory issue is whether the open source license’s copyleft provisions require the developer to release the proprietary software’s source code under the same open source license terms when the combined product is distributed to third parties.
GPL and AGPL copyleft analysis is the most consequential open source license compatibility advisory function. The GNU General Public License (GPL) versions 2 and 3 impose a copyleft obligation: any derivative work or combined work incorporating GPL-licensed code that is distributed to third parties must be distributed under the terms of the GPL, making the source code of the entire combined work available under GPL terms. The GNU Affero General Public License (AGPL) extends the copyleft obligation to cover software provided as a network service (SaaS): if a user interacts over a network with an AGPL-licensed program, the AGPL requires that the software’s source code be made available to the users. For a commercial SaaS company incorporating an AGPL-licensed component, the AGPL copyleft potentially requires releasing the proprietary SaaS platform’s source code to all users who access the service — an obligation that is commercially incompatible with a closed-source SaaS business model.
LGPL, Apache 2.0, MIT, and BSD license advisory covers open source licenses with weaker or no copyleft obligations. The GNU Lesser General Public License (LGPL) allows proprietary software to link to LGPL-licensed libraries without triggering the copyleft obligation, provided that the proprietary software does not incorporate the LGPL library as a combined work (by merging the library code into the proprietary codebase). The Apache 2.0, MIT, and BSD licenses are permissive licenses with no copyleft obligation: they allow incorporation of the licensed component into proprietary software without requiring release of the proprietary source code, subject only to attribution requirements. The retained attorney advising on open source license compatibility evaluates the specific interaction between the proprietary software and each open source component in the codebase — whether the open source component is used as a library linked to at runtime (LGPL-compatible), incorporated as a modified fork into the proprietary codebase (GPL-triggering if the component is GPL-licensed), or accessed as a separate process through interprocess communication (which may avoid GPL copyleft depending on the degree of integration) — and advises on whether any incorporation method is compatible with maintaining the proprietary software’s closed-source status.
Cross-license and portfolio licensing advisory
Cross-license and portfolio licensing advisory is the retainer function that advises on licensing transactions involving large patent portfolios, SEP licensing under FRAND commitments, portfolio cross-license negotiations between companies with overlapping patent portfolios, and portfolio valuation for licensing strategy and litigation support.
SEP/FRAND licensing advisory
Standard essential patents (SEPs) are patents that cover technology necessarily implemented by any product complying with a technical standard — such as the IEEE 802.11 Wi-Fi standard, the 3GPP 5G NR standard, the Bluetooth SIG standards, or the HEVC video codec standard. Companies whose patents are essential to a standard typically make licensing commitments to the standards body (ETSI, IEEE, 3GPP, Bluetooth SIG, or JEDEC) to license their SEPs on FRAND terms to any implementer of the standard. The FRAND commitment ensures that the standard can be broadly adopted without implementers facing hold-up by SEP holders who could otherwise demand supra-competitive royalties from companies who have made standard-specific investments.
FRAND rate evaluation requires the retained attorney to assess whether the SEP holder’s offered royalty rate is consistent with its FRAND commitment by evaluating: comparable licenses granted by the same SEP holder to similarly situated licensees (license comparables are the primary method courts have used to evaluate FRAND rates in FRAND litigation, including TCL Communication Technology Holdings, Ltd. v. Telefonaktiebolaget LM Ericsson (C.D. Cal. 2017) and In re Innovatio IP Ventures, LLC Patent Litigation (N.D. Ill. 2013)); the royalty base, evaluated against the SSPPU standard to avoid royalty stacking (where multiple SEP holders each applying royalties to the full product price collectively impose royalty burdens that exceed the total value of the standard to the product); and the aggregate royalty burden from all SEP holders in the standard (whether the sum of all FRAND royalties claimed from all SEP holders covering the standard is commercially reasonable relative to the value the standard adds to the implementer’s product).
ETSI IPR Policy advisory is relevant for clients licensing SEPs in the telecommunications and networking fields, where the European Telecommunications Standards Institute (ETSI) is the primary standards body and maintains an IPR Policy requiring members to commit to licensing their SEPs on FRAND terms. The ETSI IPR Policy does not define the FRAND rate, but ETSI’s FRAND commitments have been interpreted by courts in Europe and the United States as requiring rates that are non-discriminatory (the same licensor cannot offer materially better terms to similarly situated licensees without offering those terms to all similarly situated licensees), reasonable (not exploiting the standard-essentiality of the patent to demand above-market royalties), and fair (reflecting the actual contribution of the patented technology to the standard, not the lock-in value created by the adopters’ standard-specific investments). The retained attorney advising on ETSI FRAND compliance evaluates the licensor’s prior licensing history, disclosed licenses in the ETSI IPR database, publicly available information about comparable cross-licenses, and court decisions on FRAND rates for the relevant standard.
Portfolio license negotiation and valuation
Portfolio license negotiations involve the licensing of large patent portfolios covering multiple technologies, multiple product categories, or multiple standards — as distinct from single-patent or small-portfolio license negotiations where claim-by-claim infringement analysis is practical. Portfolio license negotiations are common between technology companies with large patent portfolios that have overlapping coverage of each other’s products, where a cross-license allows both companies to practice each other’s patents without the mutual infringement risk of competing portfolios.
Georgia-Pacific reasonable royalty factors are the fifteen factors established in Georgia-Pacific Corp. v. U.S. Plywood Corp., 318 F. Supp. 1116 (S.D.N.Y. 1970) for calculating a reasonable royalty in patent infringement litigation. Although the Georgia-Pacific factors are a litigation damages framework rather than a transactional licensing framework, they are widely used by IP licensing attorneys as a structured analytical tool for evaluating reasonable royalty ranges in licensing negotiations. The factors most significant in technology portfolio licensing include: the royalty rate that would result from an arms-length negotiation between a willing licensor and a willing licensee at the time of infringement (the hypothetical negotiation standard); the rates paid by the licensee for the use of other patents comparable to the licensed patents; the nature of the commercial relationship between the licensor and the licensee; the established profitability of the product made under the patent and its commercial success; and the portion of the realizable profit that should be credited to the invention as distinct from non-patented elements, the manufacturing process, business risks, or significant features added by the licensee.
Portfolio cross-license advisory in bilateral negotiations between companies with overlapping patent portfolios requires evaluating: the relative strength and breadth of each party’s portfolio covering the other party’s products; the economic value exchange implied by each party’s licensing-in of the other party’s portfolio relative to the cost and risk of patent infringement litigation in the absence of a license; and the appropriate balancing payment (often called a “royalty differntial” or “catch-up payment”) if one party’s portfolio is stronger or more valuable to the other party than vice versa. The retained attorney advising on portfolio cross-license strategy evaluates the client’s portfolio coverage of the counterparty’s core products through a portfolio mapping analysis, assesses the strength of the key patents in each portfolio (claim scope, validity risk, and likelihood of being declared essential), and advises on the negotiating position that maximizes the economic value of the cross-license for the client given the relative portfolio strength of each party.
Structuring an IP licensing attorney retainer for visibility
IP licensing attorney retainer work is inherently negotiation-intensive and milestone-driven: licensing term sheet negotiations that span weeks or months between term sheet proposal and signed license agreement, royalty report review cycles tied to quarterly or annual royalty payment schedules, audit exercise decisions tied to the audit trigger provisions in each license, and open source license compliance evaluations triggered by each new open source component incorporated into the engineering team’s codebase. Each of these advisory tasks produces a discrete finding — the licensor’s proposed royalty base exceeds the SSPPU for this technology, the royalty report for Q3 understates net sales by approximately 8% based on comparison to the licensee’s public revenue disclosures, the GPL-licensed component incorporated in the March engineering sprint triggers the copyleft obligation if the software is distributed to third parties — but the finding is invisible to the client’s business development, finance, and legal teams unless it is captured in a work log entry that connects the advisory task to the specific license or transaction, the legal framework evaluated, and the recommended negotiating position or compliance action.
The most effective IP licensing attorney retainer structures pair a defined monthly advisory scope (which licenses are under active advisory, what royalty audit evaluation coverage is included, whether open source compliance analysis and SEP licensing advisory are included in the monthly fee) with a shared work log that gives the client’s commercial and legal teams a running record of the licensing advisory activity between transaction signings and audit cycles. The work log serves as both the primary deliverable for the ongoing licensing advisory function and as the supporting documentation for the more visible discrete deliverables — the license agreement draft, the royalty audit trigger evaluation, the FRAND rate analysis memo, the open source license compliance matrix — that the retained attorney produces when licensing events or compliance triggers require action.
IP licensing attorneys on retainer who maintain detailed, transaction-specific work logs — capturing the specific royalty base analysis, FRAND rate comparables, and open source copyleft evaluations for each advisory task — give their technology clients a licensing advisory record that demonstrates the ongoing nature of the licensing relationship and the specific legal standards maintained between license signings and portfolio negotiations. HourTab gives IP licensing counsel a shareable, public-facing retainer dashboard where clients can see the current month’s advisory hours, the running work log with transaction-specific and FRAND-analysis entries, and the retainer progress bar — all without a client login or a separate portal. The retainer’s value is visible in the work log, not just in the license agreements and royalty audit results that the ongoing licensing advisory is designed to optimize.
Frequently asked questions
What does an IP licensing attorney on retainer typically do?
An IP licensing attorney on monthly retainer provides ongoing advisory across IP licensing agreement drafting and negotiation including exclusive vs. non-exclusive license structure, royalty base and audit rights advisory, technology transfer advisory under Bayh-Dole for university-licensed IP and open source license compatibility analysis for proprietary software development, and cross-license and portfolio licensing advisory including SEP/FRAND rate evaluation and portfolio cross-license negotiation strategy. See the FAQ section above for a detailed breakdown of each service area.
What IP licensing advisory work is most commonly underlogged?
The most systematically underlogged categories are license agreement structure advisory before the term sheet is drafted, royalty base and SSPPU analysis advisory during negotiations, royalty audit trigger evaluation sessions when quarterly royalty reports are received, open source license compatibility analysis when new components are incorporated into the engineering codebase, and SEP/FRAND rate evaluation advisory — each of which produces no visible deliverable to the client’s business development or finance team unless captured in a work log entry with the specific license, legal standard, and advisory conclusion.
What should an IP licensing attorney retainer agreement include?
IP licensing attorney retainer agreements should specify the licenses and transactions covered, the advisory scope (licensing agreement drafting, royalty audit evaluation, technology transfer, open source compliance, SEP/FRAND advisory, portfolio cross-license, or a defined combination), the applicable legal frameworks (35 U.S.C. Patent Act, 17 U.S.C. Copyright Act, Bayh-Dole Act, DOJ/FTC Antitrust Guidelines for IP Licensing, open source license terms, ETSI/IEEE/JEDEC IPR policies), the deliverables format, and the work log format. Monthly retainer amounts typically range from $4,000 to $18,000 per month depending on transaction volume, portfolio complexity, and whether active SEP licensing negotiations are in scope.
What are typical retainer rates for IP licensing attorneys?
IP licensing attorneys with 2 to 5 years of technology transfer and patent licensing practice typically bill at $250 to $375 per hour. Senior IP licensing attorneys with 6 or more years of SEP/FRAND licensing, portfolio cross-license, and complex technology transfer experience typically bill at $350 to $550 per hour. IP licensing partners with FRAND litigation and large-scale portfolio licensing experience typically bill at $475 to $750 per hour. Monthly retainer amounts range from $4,000 to $100,000+ depending on transaction volume and whether active FRAND arbitration or portfolio cross-license negotiations are in scope.
How should IP licensing attorney retainer hours be logged?
IP licensing attorney retainer work log entries should capture the license agreement or transaction being advised on, the specific licensing or technology transfer issue addressed, the legal framework or valuation methodology applied (royalty base SSPPU analysis, FRAND comparable license analysis, Bayh-Dole march-in risk evaluation, GPL copyleft analysis), and the advisory conclusion or recommended negotiating position. Entries that identify the specific royalty base issue, the FRAND comparable license range, or the open source license trigger transform the IP licensing retainer into a documented negotiating strategy record between license signings and royalty audit cycles.