Opening the Door — Quick Context to Get Us Started

• What's your role and which team will own any licensing decision? Options: VP Legal / General Counsel, Head of IP / Patent Counsel, Chief Product Officer, VP Finance, CEO / President, Other
• Have you engaged with licensing conversations like this before (with us or another party)? Options: Yes—this portfolio/licensor, Yes—other licensors, No, first time, Unsure / need to check
• How soon do you expect to need a clear decision about licensing vs. contesting claims? Options: Immediate (weeks), Near-term (1–3 months), Quarterly (3–6 months), Longer term (>6 months), Unsure
• What would make this discovery conversation feel valuable to you today?
• Who should be included from your side to make this discussion practical and who will be the final sign-off owner?

Why Keep Doing This the Hard Way?

• If you keep handling patent assertions the way you do today, what new or recurring cost do you expect to keep accepting? Options: Higher litigation spend, Distraction of engineering/time, Uncertain product roadmap, Royalties that creep up later, Reputational risk, Other
• How have past licensing demands or suits materially disrupted product launches, timelines, or partnerships? Tell us a specific example.
• When you picture your team under pressure from patent issues, what worries you most emotionally (e.g., anxiety about timelines, fear of precedent, internal blowback)? Options: Timeline delays, Profit margin impact, Setting a costly precedent, Internal stakeholder friction, Public/legal exposure, Other
• How long have you been tolerating your current approach to resolving patent claims before deciding to change it? Options: A few months, 1–2 years, Several years, Always reactive, never fixed
• Which parts of the current process feel most broken or unfair to you right now (e.g., discovery opacity, one-sided audit terms, unclear scope)?

If Licensing Solved One Big Thing, What Would It Be?

• What single commercial or strategic outcome would make you actively choose a license over contesting claims? Options: Predictable royalty burden, Clear scope covering our roadmap, Strong covenant not to sue, Minimized audit exposure, Favorable FRAND benchmark, Other
• Describe the success signals you would want to see within 90 days of a license being agreed (concrete milestones, not vague promises).
• What absolute conditions must be true before your executive team would accept a license (e.g., per-unit cap, exclusion of certain SKUs, fixed term)?
• How would a successful deal change how your product teams plan features or roadmap for the next 12–24 months? Options: Enable new features faster, Remove need for workarounds, Allow broader market access, No change, Other
• Which KPIs will you use to judge whether the license delivered on those success signals (e.g., margin impact, litigation cases avoided, time-to-market saved)? Options: Gross margin impact, Number of disputes avoided, Time saved in development, Customer uptime/continuity, Legal spend reduction, Other

Where the Numbers Actually Matter — Money, Margins, and Tradeoffs

• What is the maximum royalty burden (as a percent of product margin or per-unit amount) that would still allow you to move forward without killing the product line? Options: <0.5% of revenue, 0.5–1.5%, 1.5–3%, 3–5%, >5%, Need to calculate/unsure
• Do you have internal FRAND benchmarks, comparable license references, or board guidance we should align to when proposing rates? Options: Yes—benchmarks available, Yes—comparable licenses, No formal benchmarks, Prefer not to share yet
• What budget or range is realistically allocated for resolving this kind of IP exposure through settlement or licensing? Options: Dedicated licensing budget exists, Ad-hoc funds per deal, Covered by legal OPEX, No budget—requires approval, Unsure
• How would you prefer royalties to be structured: per-unit, percentage of revenue, fixed milestone, or hybrid? Options: Per-unit, Percentage of revenue, Fixed fee/milestone, Hybrid, Open to discussion
• If litigation becomes necessary, what is the most you’d expect to spend before deciding to settle? (If unknown, describe the decision threshold.)

Who Needs Convincing — Mapping the People and Politics

• Who are the absolute decision-makers and influencers for IP deals in your organization, and how do they typically prioritize tradeoffs?
• Which stakeholder groups are likely to oppose a license and why (engineering, procurement, sales, board)? Options: Engineering—technical integrity, Finance—cost, Sales—commercial constraints, Legal—precedent concerns, Executive—strategic optics, Other
• How do internal approvals work—what sign-offs are required and how long do they typically take? Options: Legal then Finance, Legal → Product → Exec, Board/Executive Committee approval, Ad-hoc depending on deal size, Unsure
• If we were preparing a one-page memo to get faster buy-in, what three facts or assurances would you need on that page?
• How do external partners (manufacturers, distributors, OEMs) influence your tolerance for license terms or disclosures?

Deal Drivers — What Would Make You Say Yes Right Now?

• Which of these deal elements would most accelerate a yes from your team if offered: capped royalties, limited scope, short-term pilot license, strong covenant not to sue, or expedited onboarding? Options: Capped royalties, Limited scope (specific SKUs), Short pilot/license term, Covenant not to sue, Expedited onboarding/support, Other
• Are there specific patent families, product lines, or filing dates that must be excluded or included for the deal to be acceptable?
• Would you consider a staged approach (pilot license for a subset of products, then expand) and what guardrails would you require? Options: Yes—open to pilot, Maybe—depends on terms, No—need full coverage, Unsure
• What auditing or reporting constraints would feel fair versus intrusive (frequency, sample size, confidentiality protections)? Options: Quarterly limited reporting, Annual comprehensive reporting, On-demand with notice, Third-party auditor only, No audits
• List your top three non-negotiables (deal-breakers) that would prevent you from taking a license regardless of other concessions.

Threats We Should Calm — Risks, Precedent, and Legal Appetite

• If this portfolio sought to set public precedent against your company, how prepared are you to fight in court versus settling quickly? Options: Prefer to settle quickly, Prefer to defend in court, Case-by-case, Unsure
• How concerned are you that accepting a license could invite additional claims from other holders? How would that concern affect your decision-making? Options: Very concerned—wouldn't license, Somewhat concerned—needs limits, Not concerned—standard practice, Unsure
• What evidence or technical disclosures do you need from us to feel confident the patents map to your actual implementations? Options: Claim mapping to SKUs, Test logs / firmware evidence, Third-party technical report, Source-level explanations, Other
• How much runway (weeks/months) do you need to perform internal technical validation before committing to a commercial discussion? Options: Immediate (0–2 weeks), 2–6 weeks, 6–12 weeks, >12 weeks, Unsure
• What would make you feel we’ve done enough to remove the fear of surprise enforcement down the road?

A Realistic Path Forward — Tiny Experiments, Clear Signals

• Which of these next-step options feels most practical to you right now: a technical claim mapping review, a scoped pilot license, a commercial term draft, or a confidential workshop with stakeholders? Options: Technical claim mapping review, Scoped pilot license, Commercial term draft, Confidential stakeholder workshop, Other
• Who on your side should we bring into the next call, and what would you like each person to accomplish in that meeting?
• What would a short timeline to a meaningful milestone look like (e.g., mapping done in 3 weeks, initial terms in 6 weeks)?
• What concerns would cause you to pause after the next milestone, and how can we proactively address them?
• Finally, what would make you comfortable sharing sensitive product or sales data under NDA so we can produce accurate mappings and a fair commercial proposal? Options: Standard mutual NDA, NDA + limited data escrow, Redacted samples only, Third-party verification, Prefer not to share yet

• Current State & Evidence Alignment
• Claim-to-Product Mapping Workshop
• FRAND Scenario Review & Commercial Impact Modeling
• Commercial vs Litigation Outcome Simulation & Path Decision

• If contest chosen: Customer to engage litigation counsel and set litigation budget and preservation tasks.
• Identify and document all evidentiary gaps and disputed facts with clear owners.
• Obtain customer validation on high-confidence mappings to reduce ambiguity before rate discussions.
• Produce a prioritized list of products and claims for financial scenario modeling.
• Host to deliver the mapping spreadsheet with linked evidence and confidence ratings within 48 hours.
• Customer product owners to resolve or annotate any functional disputes and supply missing firmware/samples.
• Technical leads to produce short demonstration artifacts (screenshots, packet captures) for contested mappings.
• Schedule FRAND Scenario Review with finance and legal attendees after mapping finalization.
• Recap Validated Scope & Future State
• Provide the customer with quantified FRAND scenarios using their mapped scope and sales data.
• Clarify the tradeoffs between each commercial offer and the expected litigation pathway.
• Elicit a preferred scenario or a clear set of decision criteria to use in negotiation.
• Agree on any additional sensitivity runs or alternative scope permutations required.
• Host to deliver a scenario workbook with NPV, cash flows, and sensitivity tabs using customer inputs.
• Customer finance to provide 3-year sales forecast and discount rate for final modeling.
• Legal to review sample covenant language implications for each scenario.
• Set date for the Commercial Decision & Path Simulation meeting to finalize choice.
• Introductions & Meeting Objective
• Shared: Assign negotiation or litigation leads and schedule the Mutual Commit meeting.
• One‑Sentence Validation: Current State, Consequence, Future State
• Select a clear path (license negotiation, contest, or hybrid) based on validated simulations and decision criteria.
• Translate the selected path into specific next steps with owners and timelines.
• Ensure alignment across legal, finance, and product on the chosen approach and communication plan.
• Document any outstanding analyses required before final commitment and assign them.
• If license chosen: Host to prepare a draft term sheet and proposed FRAND benchmark language.
• Host to produce a one‑page decision memo summarizing simulations, chosen path, and next actions.
• Produce a single-sentence current state that all stakeholders agree is accurate.
• Quantify the business and legal consequences (high-level $/timeline/risk) of each path.
• Agree a one-sentence future state that will define success for the experience.
• Collect a complete evidence inventory and assign owners for missing items.
• Customer to deliver SKU matrix, sales volumes, and firmware/software variant list.
• Product team to provide BOM traces and functional descriptions for top 10 SKUs.
• Legal to state litigation appetite and acceptable royalty impact range.
• Host to prepare a template 'one-sentence current state' and 'future state' for validation at the next meeting.
• Recap: Current State, Consequence, Future State
• Create a claim-to-product mapping with a confidence rating for every in-scope SKU.
• FRAND Benchmarking & Rationale
• Licensed Path Simulation (Milestones & Timelines)
• One‑Sentence Current State
• Mapping Methodology & Confidence Scale
• Litigation Path Simulation (Costs, Timeline, Likely Outcomes)
• Consequence Quantification
• Scenario A — FRAND Floor (Conservative)
• Live Mapping — High Exposure Products
• Scenario B — Median/Proposed Rate
• Side‑by‑Side Customer‑Specific Simulation
• Live Mapping — Remaining Product Set
• Future State Statement
• Decision Criteria & Risk Tolerance Check
• Scenario C — Upper Bound / Litigation Settlement Equivalent
• Evidence Inventory Review
• Capture Disputes & Assumptions
• Confirm Path & Define Concrete Next Steps
• Side‑by‑Side Financial & Timeline Comparison
• Gap & Assumption Log
• Validation Checkpoint
• Closure & Communication Plan
• Prework & Next Steps for Mapping
• Agree Deliverables & Owners
• Sensitivity Analysis & Decision Triggers

• Deliver patent claim charts mapped to product components
• Issue draft license agreement with standard and optional clauses
• Negotiate and finalize license economic and field-of-use terms
• Execute signed license and deliver certificate of licensed rights
• Provide FRAND-based royalty rate schedule with supporting comparables
• Grant covenant not to sue for licensed activities
• Activate royalty reporting portal and reporting templates
• Invoice royalties and process licensee payments and reconciliations
• Conduct royalty compliance audits per contract provisions
• Apply rolling patent addendum to include future filings
• Deliver technical implementation documentation and claim support
• Publish SKU-to-claim mapping to define licensed product scope
• Facilitate cross-license or patent-pool introductions and coordination

Deliver patent claim charts mapped to product components

• Which product lines and SKUs should be evaluated for claim mapping?
• What level of mapping detail do you require? Options: High-level (feature-to-claim), Component-level (module-to-claim), BOM/line-item level (chip/part-to-claim)
• Do you have firmware, software binaries, or hardware schematics to support mappings? Options: Yes – firmware/software, Yes – hardware/BOM, No, need on-site collection, Partial
• Please list evidence types you can provide (e.g., datasheets, screenshots, test logs, build manifests).
• Which patent families or application numbers should be prioritized for mapping?
• What is your preferred deliverable format for claim charts? Options: Editable spreadsheet, Redline-enabled PDF, Structured XML/CSV, Private portal publication

Issue draft license agreement with standard and optional clauses

• Which optional clauses are you likely to require in the draft license? Options: Audit rights, Field-of-use carve-outs, Sublicensing terms, Indemnity, Caps on royalties, Termination for convenience, Confidentiality enhancements
• Which governing law and venue do you prefer for the agreement? Options: Delaware, California, London (England & Wales), Singapore, Other
• Do you prefer a licensor-drafted template or a neutral/third-party template for initial redline? Options: Licensor-drafted, Neutral template, Licensee provides initial draft
• Who is the legal contact and estimated review timeline on your side (name, role, typical SLA)?
• Are there non-standard commercial protections you need included (e.g., most-favored-nation, rate parity, confidentiality ring)? Options: Yes, No
• Do you require clause-level explanations or playbooks for negotiators? Options: Yes – detailed playbook, Yes – brief explanations, No

Negotiate and finalize license economic and field-of-use terms

• Which fields-of-use and product categories should the economic terms cover? Options: Consumer devices, Network infrastructure, Semiconductor/chipsets, Cloud services, Automotive/embedded
• What royalty basis do you prefer for negotiation? Options: Per unit (SKU), Percentage of product revenue, Percentage of component value, Per device class (tiered), Lump-sum/annual minimum
• Do you have target FRAND or benchmark rates (or comparable licenses) to share? Options: Yes – will share comparables, Yes – will share target range, No
• Do you prefer upfront payment, running royalties, or a hybrid? Options: Upfront only, Running only, Hybrid (upfront + running), Royalty holiday then running
• What territory scope should the license cover? Options: Worldwide, North America, EMEA, APAC, Custom list
• Are there required economic concessions (e.g., volume discounts, royalty caps, carve-outs for internal use) we should draft?

Execute signed license and deliver certificate of licensed rights

• Who is the authorized signatory for the license on the licensee side (name, title)?
• Do you accept e-signature execution (DocuSign/equivalent) or require wet ink? Options: E-signature accepted, Wet ink required, Depends on corporate policy
• What effective date and initial term length do you expect?
• To whom should the certificate of licensed rights be delivered and in what format? Options: PDF via portal, Signed hard copy, Both
• Do you need the license to include immediate public notice of licensing (e.g., press release or public listing)? Options: Yes, No, Case-by-case
• Are there internal compliance checkpoints required post-signature (e.g., onboarding team, reporting owner)? Options: Yes, No

Provide FRAND-based royalty rate schedule with supporting comparables

• Which product groups should be separately priced in the FRAND schedule?
• Preferred royalty expression for schedule? Options: Per-unit USD, Percentage of revenue, Per-chipset, Tiered bands by volume/value
• Do you want full supporting comparables and redacted license summaries included with the schedule? Options: Yes – full comparables, Yes – redacted summaries only, No
• Are there specific industry benchmarks or third-party valuations you accept as FRAND comparators?
• What is your timeline for receiving the FRAND schedule and comparables? Options: 1 week, 2-4 weeks, 4-8 weeks, Custom
• Do you require an expert opinion or affidavit to support the FRAND schedule? Options: Yes, No, Maybe – depending on scope

Grant covenant not to sue for licensed activities

• Which patent sets should be covered by the covenant not to sue? Options: Current granted patents, Pending applications included, Future filings via rolling addendum, Specific patent families (list)
• Should the covenant extend to affiliates, sublicensees, and distributors? Options: Yes – affiliates and sublicensees, Affiliates only, Licensee only
• Are there exclusions you need in the covenant (e.g., competitive products, authorized third-party activities)? Options: Yes, No
• Do you require a contractual trigger or material breach carve-out that allows licensors to suspend the covenant? Options: Yes, No, Define specific triggers
• Is a public joint statement or notifying customers of the covenant desirable? Options: Yes, No, Private agreement only
• Do you require reciprocal non-assertion or mutual covenant language? Options: Yes, No

Activate royalty reporting portal and reporting templates

• What reporting cadence will you use? Options: Monthly, Quarterly, Semi-annual, Annual
• Which fields must appear on each report (e.g., SKU, units sold, revenue, region)?
• Preferred portal access method? Options: User accounts + password, SAML/SSO, API-based reporting, Manual upload only
• Do you need a test sandbox and validation checks before go-live? Options: Yes, No
• What file formats do you require for reporting templates? Options: CSV, Excel, JSON/API
• Who will own reporting on the licensee side (name, role, contact)?

Invoice royalties and process licensee payments and reconciliations

• Preferred billing frequency and terms? Options: Monthly net 30, Quarterly net 45, Annual prepayment, Other
• What payment methods are acceptable? Options: Wire transfer, ACH, Credit card, Check
• Do you require purchase orders or specific remittance references? Options: Yes – PO required, No PO required
• How should short pays or disputed amounts be handled and reconciled?
• Do you need automated invoice delivery via portal/email and accounting codes? Options: Yes, No
• Are bank fee allocations or currency conversion rules required? Options: Licensee pays bank fees, Licensor absorbs fees, Split

Conduct royalty compliance audits per contract provisions

• What scope of records must be available for audit (financial, product, systems logs)? Options: Full financial & transactional, SKU-level production & sales, Limited samples
• Acceptable auditors and independence requirements? Options: Big 4/accounting firm, Licensed third-party auditor, Internal audit with independent oversight
• Preferred audit notice period and frequency? Options: 30 days, 60 days, Announced only, Once per contract year
• Onsite vs remote audit preference and data security safeguards? Options: Onsite, Remote, Hybrid
• Who bears the audit costs if discrepancies exceed an agreed threshold? Options: Licensee, Licensor, Split by agreement
• Which years should be eligible for audit look-back (e.g., last 3 years)? Options: Last 12 months, Last 3 years, Contract term

Apply rolling patent addendum to include future filings

• Should future filings be automatically included or require notice and opt-in? Options: Automatic inclusion (rolling), Notice + consent required, Case-by-case
• Should continuations, divisionals, and CIPs be treated as included by default? Options: Yes, No, List exceptions
• What notice period is acceptable for adding new patents to the agreement? Options: Immediate, 30 days, 60 days, 90 days
• Do you require a review period to dispute inclusion of a newly added patent? Options: Yes, No
• How should royalties for newly added patents be calculated (retroactive, prospective)? Options: Prospective only, Retroactive to filing/grant date, Negotiated on inclusion
• Are there maximum scope limits or exclusions for future filings (e.g., unrelated tech areas)? Options: Yes, No

• License Agreement
• Royalty Schedule & Rate Card
• Statement of Work (SOW)
• Covenant Not to Sue & Scope Confirmation
• Audit & Reporting Addendum
• Payment Terms & Invoicing
• FRAND Benchmark & Comparable Appendix
• Dispute Resolution & Governing Law
• IP Portfolio Scope & Future Filings Coverage
• Confidentiality & Data Protection Addendum
• Change Control & Amendment Procedure
• Execution & Signatures

• Compliance Confirmation Review
• Royalty Reconciliation & Accounting
• Open Issues & Remediation Planning
• Change Request & Enhancement Governance
• Success Review & Continuous Improvement

• Operationally enable the shared channel and document retention practices for traceability.
• Settle agreed payment via wire/CAP within the confirmed payment window and confirm remittance details by email.
• Purpose & Issue Triage Criteria
• Produce a prioritized backlog of open issues with assigned owners and committed due dates.
• Agree remediation acceptance criteria and evidence required to close each issue.
• Establish a rapid-escalation path for items that threaten compliance or significant financial exposure.
• Owners to create ticketed remediation plans in the shared tracker with milestones and evidence checkpoints.
• Schedule weekly short-cadence standups for high-priority remediation items until closed.
• Collect and upload closure evidence (logs, test results, signed attestations) to the shared workspace when ready.
• Governance Objectives & Use Cases
• Adopt a single change-request workflow with an agreed submission template and SLAs.
• Define the triage committee, decision authority, and pricing approach for changes that alter scope or royalties.
• Introductions & Objectives
• Publish the finalized change-request template and SLAs in the shared CustomerNode workspace.
• Create the change-request intake queue and add nominated triage committee members with defined roles.
• Log the first three anticipated change requests as pilots to validate the workflow.
• Opening & Success Metrics Overview
• Confirm current compliance health and financial reconciliation posture using agreed KPIs.
• Agree a prioritized set of process improvements with owners and pilot timelines to reduce future friction.
• Establish a recurring success review cadence and assign owners to maintain the shared channel and improvement backlog.
• Deliver a consolidated Success Report (KPIs, reconciliations, open issues) to all stakeholders within 5 business days.
• Launch one prioritized pilot (e.g., automated reporting feed or standardized evidence upload) and report pilot results at the next review.
• Schedule the next quarterly Success Review and circulate agenda and required pre-reads two weeks in advance.
• Confirm the accuracy of the licensee's current compliance reporting and secure formal sign-off where no exceptions exist.
• Identify, prioritize, and assign remediation actions with clear owners and dates for all exceptions.
• Establish an evidence checklist and criteria required to close each remediation item.
• Licensee to deliver transaction-level sales evidence and build/firmware delivery logs for disputed SKUs within 7 business days.
• Licensor to produce a verification summary documenting any technical discrepancies and recommended remediation steps.
• Create remediation tracker entries with owners, deliverables, and target close dates.
• Meeting Objectives & Reconciliation Scope
• Agree on a single reconciled royalty amount for the period under review with documented adjustments.
• Establish a clear payment schedule and required artifacts for accounting and audit trails.
• Define handling of any unresolved disputed items, including timelines for escalation or external review.
• Issue revised invoice/credit note reflecting agreed adjustments and send to accounts payable within 3 business days.
• Licensee to provide transaction-level source files (in agreed format) for all disputed entries within 5 business days.
• Financial & Operational Variance Review
• Change Request Submission Template
• Walkthrough of Licensee Reconciliation
• Summary of Submitted Compliance Materials
• Review Open-Issues Register
• Triage & Decision Criteria
• Verification Findings Review
• Prioritization Exercise
• Licensor Review & Variance Analysis
• Customer Feedback & Pain Points
• Exceptions & Root Cause Discussion
• Remediation Plan Development
• Commercial Handling & Pricing Approach
• Improvement Opportunities & Pilot Plans
• Disputed Items: Root Causes & Resolutions
• Escalation & Dispute Path
• Remediation Actions & Timelines
• Agreed Payment & Accounting Entries
• Operationalizing the Shared Channel
• Cadence & Governance Commitments
• Next Steps & Documentation
• Compliance Sign-off & Next Steps