IP Agreements & Contracts Attorney — Austin, Texas
Your intellectual property is only as protected as the agreements that surround it in every business relationship — from customer contracts to supplier agreements to employee arrangements, each drafted with both the legal precision and the technical understanding that IP-rich technology companies require.
Home → Practice Areas → IP Agreements & Contracts
Technology License Agreements — Beyond the Patent License
Technology license agreements cover a broader commercial territory than pure patent licenses — they govern the transfer of technical know-how, trade secrets, software, and engineering data alongside or instead of patent rights. Many of the most commercially significant technology transfers involve combinations of IP types — licensed patents plus accompanying know-how, open source software plus proprietary modifications, foundry process technology plus design rules and simulation models — that require agreements carefully structured around the specific IP bundle being transferred rather than a standard patent license form adapted to fit.
The distinction between a patent license and a technology license matters commercially and legally in several important ways. A patent license grants permission to practice the claimed invention for the patent's remaining term — when the patent expires, the license expires with it. A technology license covering trade secrets, know-how, and engineering data can extend indefinitely as long as the licensed information remains confidential. A company receiving a technology license that covers both patents and trade secrets needs provisions addressing what happens to the trade secret components when the patents expire — specifically, whether royalty obligations for the trade secret components continue after patent expiration or whether the entire royalty structure is tied to the patent term.
For Austin technology companies licensing their technology to manufacturing partners, commercialization partners, or technology integrators, I draft technology license agreements that comprehensively address the full scope of technical information being transferred — mapping each category of licensed IP to specific license scope, confidentiality treatment, and royalty structure provisions. For companies receiving technology licenses from vendors, universities, or prior employers, I review agreements with particular attention to the provisions that affect future freedom to develop and the obligations that follow the licensee beyond the term of the primary relationship.
Field of use restrictions and improvements clauses deserve specific attention in technology license negotiations that standard templates rarely handle well. An improvements clause — governing whether improvements made by the licensee must be licensed back to the licensor — can effectively prevent a licensee from commercializing innovations built on the licensed technology without returning value to the original licensor. A grant-back that is structured as an exclusive license of improvements to the licensor effectively limits the licensee's ability to build a business around the licensed technology. I negotiate improvements clauses that protect each party's legitimate interests — ensuring that licensors receive appropriate recognition for foundational technology while ensuring licensees can build businesses on top of what they license without being trapped by broadly drafted grant-back provisions.
IP Indemnification — The Most Misunderstood Provision in Commercial Contracts
IP indemnification provisions — clauses in which one party promises to defend and hold harmless the other party against claims that the contracted goods or services infringe a third party's intellectual property — are among the most commercially significant and most widely misunderstood provisions in technology contracts. Almost every commercial technology contract contains an IP indemnification clause. Most parties sign them without fully understanding the scope of what they are promising or demanding, and without appreciating how the specific drafting choices affect the provision's practical value.
An IP indemnification given by a technology vendor to its customer promises that if a third party asserts that the vendor's technology infringes their patent, copyright, or other IP rights, the vendor will take responsibility for defending the claim and covering any resulting damages. The commercial value of this promise depends entirely on the scope of the indemnification — what it covers, what it excludes, what obligations it imposes on the indemnified party to cooperate and not make admissions, what remedies are available when the vendor cannot clear the infringement risk, and what financial limits cap the vendor's liability. A broadly worded indemnification with a cap equal to one month's fees has almost no commercial value when a significant patent infringement claim emerges. An unlimited indemnification from a financially substantial vendor with specific remediation obligations including replacement or modification of infringing components has genuine commercial value.
The exclusions from IP indemnification provisions are where most of the commercial negotiation occurs and where most of the risk actually lives. Standard exclusions typically include infringement caused by the customer's modification of the vendor's technology, infringement caused by combining the vendor's technology with third-party products not specified by the vendor, infringement that would not exist but for the customer's specific instructions or specifications, and infringement of patents that the customer owns or controls. For technology companies receiving indemnification from platform vendors, AI tool providers, or semiconductor IP licensors, I analyze the interplay of these exclusions against the company's specific deployment context — identifying whether the most likely infringement scenarios are actually covered by the indemnification or excluded by the fine print.
For technology companies providing IP indemnification to their customers, I draft indemnification provisions that are commercially reasonable — offering genuine protection against infringement claims arising from the company's core technology while limiting exposure for infringement scenarios outside the company's control. For companies in IP-sensitive technology areas — AI companies whose training data might be challenged, semiconductor companies whose chip designs may overlap with competitor patents, software companies in crowded technology spaces — the IP indemnification exposure in commercial contracts represents a significant business risk that requires both careful contracting and a patent clearance strategy that informs what can responsibly be indemnified.
Research, Development, and Collaboration Agreements — Structuring IP in Funded Innovation
Funded research and development agreements — whether between corporate sponsors and universities, between prime contractors and subcontractors, between co-development partners, or between companies and their contract research organizations — involve IP creation that must be explicitly allocated rather than left to statutory default rules that rarely serve anyone's interests. The range of R&D agreement types is broad, but the IP provisions they require share common elements that deserve careful attention regardless of the specific research relationship.
Sponsored research agreements between industry and universities are particularly complex IP instruments because they sit at the intersection of corporate IP interests, university IP policies, federal funding regulations, and academic publication norms. An industry sponsor that funds university research expects commercial access to the resulting innovations — but university IP policies typically vest ownership of employee-invented IP in the university, not the sponsor. The sponsored research agreement must bridge this gap by negotiating the sponsor's licensing rights, option rights to negotiate licenses, publication review periods, and patent cost responsibilities. These negotiations with UT Austin and other Texas research institutions involve specific institutional positions and standard negotiating terms that I understand from experience — giving industry clients a practical advantage in reaching favorable terms efficiently.
Contract research and development agreements — in which one company funds another to develop specific technology — require provisions addressing both foreground IP ownership and background IP access. The funding company typically wants to own all deliverables and to have assurance that the CRO is not incorporating third-party IP — open source code, licensed algorithms, or prior CRO innovations — into the deliverables without the funding company's knowledge and consent. The CRO typically wants to retain certain background IP rights and to maintain some ability to use its general know-how and development capabilities for other clients. Balancing these interests requires clear definitions of what constitutes deliverables, background IP, and improvements — the same definitional work that goes into a joint development agreement but structured for the asymmetric relationship of funded development rather than collaborative co-development.
Materials transfer agreements — governing the transfer of proprietary materials, biological samples, chemical compounds, or data sets between research organizations for research purposes — present specific IP provisions around publication rights, derivative materials ownership, and the use limitations that bind the recipient. For Austin's university spinout companies and biotech firms that regularly transfer research materials between academic and commercial settings, MTAs require attention to the IP chains they create — ensuring that downstream discoveries using transferred materials do not create unexpected obligations or restrictions on commercialization.
IP Provisions in M&A, Financing, and Strategic Transactions
The IP provisions in mergers and acquisitions, venture financing, and strategic partnership transactions are the highest-stakes IP contract work in business law — provisions that directly affect transaction value, deal structure, closing conditions, and post-closing liability. While these transactions are typically led by M&A or corporate finance attorneys, the IP-specific provisions within them require input from patent counsel who can assess the technical accuracy of representations and warranties, the adequacy of IP schedules, and the enforceability of IP-related covenants and conditions.
IP representations and warranties in acquisition agreements are the primary mechanism through which a buyer extracts accountability from a seller for the IP assets being acquired. Standard IP reps and warranties address ownership — the seller owns the IP free from encumbrances and competing claims; non-infringement — the seller's business as conducted does not infringe third-party IP rights; validity — the seller's patents are valid and enforceable; completeness — the IP schedule includes all material IP assets; and no pending claims — no IP-related litigation, disputes, or government proceedings are pending or threatened. The accuracy of these representations depends on the underlying IP due diligence work — and representations that are given without thorough due diligence support create closing risk and post-closing indemnification exposure.
Venture financing agreements — particularly at Series A and later — increasingly include specific IP covenants requiring startups to maintain their patent applications, preserve their trade secret programs, and notify investors of IP-related adverse developments. Preferred stock purchase agreements and investor rights agreements may include specific IP undertakings that restrict the startup's freedom to license its technology, grant security interests in IP without investor approval, or make IP-related business decisions without board consent. I review financing agreement IP provisions for Austin startup clients to ensure they understand the IP obligations they are accepting and that those obligations are commercially manageable given the company's actual IP situation.
Strategic partnership agreements — covering co-marketing arrangements, technology integration partnerships, go-to-market collaborations, and joint commercialization structures — often contain IP provisions that bind the parties more significantly than the transaction's apparent size suggests. A co-marketing agreement that grants a partner a right of first refusal to license any future IP in a defined field, or a technology integration agreement that grants the integrating party a license to the integrated technology that survives termination, can create IP encumbrances that affect subsequent fundraising or acquisition transactions in ways that the parties did not contemplate at signing. I review strategic partnership agreements for IP provisions with long-term implications — not just the provisions that are obvious on their face, but the provisions whose IP significance only becomes apparent when a subsequent transaction or technology development makes them operationally significant.
For companies preparing for fundraising or acquisition, I provide pre-transaction IP contract audits — reviewing all commercial agreements containing IP provisions to identify terms that could complicate the transaction, create unexpected third-party claims, or require specific representations that the company cannot accurately make. This proactive audit, conducted before the transaction process begins rather than during buyer due diligence, gives Austin technology companies the time to address IP contract issues while they still have the leverage to negotiate resolutions rather than discovering them at the closing table when options are limited.
[ IP Agreements & Contracts FAQs — Austin, Texas ]
Question: What is a master services agreement and how do its IP provisions differ from a standalone IP assignment agreement?
Answer: A master services agreement — the umbrella contract governing an ongoing service relationship between a technology company and a vendor or customer — typically includes IP provisions addressing work product ownership, license grants, and confidentiality across all work orders and statements of work executed under the MSA. Unlike a standalone IP assignment that transfers specific identified IP in a one-time transaction, an MSA's IP provisions are prospective — they govern IP created in all future work orders under the umbrella agreement, which may not be specifically identified at the time the MSA is signed. This prospective nature creates specific drafting challenges: the IP ownership provisions must be broad enough to address all possible work product that might be created under future work orders while being specific enough to clearly allocate ownership between the parties. I draft MSA IP provisions that are deliberately comprehensive — covering software code, documentation, data, processes, discoveries, and inventions that might arise in any future work order — with clear allocation of ownership based on the nature of the work rather than requiring separate IP agreements for each work order.
Question: What is an IP indemnification in a SaaS agreement and how should Austin SaaS companies structure it?
Answer: SaaS agreement IP indemnification is a commitment by the SaaS provider to defend and hold the customer harmless against claims that the provider's software infringes third-party IP rights. For Austin SaaS companies, IP indemnification provisions represent a significant ongoing liability exposure that must be balanced against the commercial necessity of providing it — enterprise customers routinely require IP indemnification as a standard contract term and many deals cannot close without it. Key structural decisions in SaaS IP indemnification provisions include: the scope of covered IP including whether copyright infringement and trade secret misappropriation are covered alongside patent infringement; the carve-outs excluding infringement caused by customer modifications, third-party integrations, or use outside the licensed scope; the indemnification process requirements including prompt notice, cooperation obligations, and control of defense; and the financial cap on indemnification liability, which SaaS providers should ensure is commercially proportionate to the contract value rather than unlimited. I structure IP indemnification provisions for Austin SaaS clients that provide commercially necessary coverage while managing the company's aggregate IP indemnification exposure across its customer base.
Question: What is a data license agreement and what IP issues are specific to data licensing in Austin's AI ecosystem?
Answer: A data license agreement grants permission to access, use, process, and build on data assets owned by the licensor — with IP provisions addressing the rights granted in the data itself, any derivative datasets created from the licensed data, and the models or products trained on the licensed data. Data licensing raises specific IP issues in Austin's AI ecosystem where training data is a critical competitive asset. Key provisions include: whether the licensee can use the licensed data to train AI models and whether those models are covered by the license or require separate licensing; whether derivative datasets created by the licensee's processing of licensed data are owned by the licensor, the licensee, or shared; whether the licensee can publish results or model performance metrics that effectively disclose information about the licensed data; and how data quality, accuracy, and completeness are warranted by the licensor given that data license disputes frequently arise from disagreements about data fitness for purpose. I draft data license agreements with awareness of the emerging legal landscape around AI training data licensing — including the copyright questions raised by recent litigation against AI training data uses — and structure provisions that provide appropriate protection for both data licensors and licensees.
Question: What is a technology escrow agreement and when should Austin software companies require one from their vendors?
Answer: A technology escrow agreement — typically a three-party agreement among a software licensor, a licensee, and an independent escrow agent — provides that the licensor deposits source code and technical documentation into escrow with the escrow agent, to be released to the licensee upon specified triggering events such as the licensor's insolvency, acquisition, failure to maintain the software, or other events that would threaten the licensee's ability to continue using the software. Austin technology companies that depend on mission-critical software from vendors should require technology escrow when: the software has no readily available substitute and migration would be prohibitively expensive; the vendor is a startup or small company with meaningful insolvency risk; the software is deeply integrated into the licensee's operations; or the licensee has invested significantly in customizing and integrating the software in ways that would be lost if the software became unsupported. I draft technology escrow agreements and negotiate escrow terms on behalf of licensees — specifically addressing what materials must be deposited, how frequently deposits must be updated, what constitutes a valid release trigger, and what the licensee can do with the released materials.
Question: What is a software development agreement's IP ownership provision and why does the work-for-hire doctrine not solve the problem?
Answer: The work-for-hire doctrine under US copyright law automatically vests copyright in the commissioning party for certain categories of works created by employees within the scope of employment or by contractors for specifically defined purposes. The critical limitation for software development agreements is that computer programs are not among the nine enumerated categories of works eligible for contractor work-for-hire status. A software development agreement with an independent contractor that relies solely on work-for-hire language — without an explicit copyright assignment — fails to transfer copyright in the developed software to the commissioning party. The contractor retains copyright despite the commissioning party's belief that they own the work they paid for. I draft software development agreements with explicit copyright assignment provisions that operate independently of and in addition to any work-for-hire language — ensuring that copyright transfer is effective regardless of whether the work-for-hire characterization is ultimately legally valid for the specific type of software developed.
Question: What is an interoperability license and when does Austin software company need one?
Answer: An interoperability license is a grant of rights — typically in patents and trade secrets — that allows a product to interface with, communicate with, or operate in conjunction with another company's proprietary technology. Interoperability licenses are needed when your software product must integrate with a third-party platform, API, file format, or protocol in ways that require access to proprietary technical specifications not publicly available, or in ways that might implicate the platform owner's patents on their interface technology. Austin software companies building on top of or integrating with enterprise platforms — Salesforce, Workday, ServiceNow, or industry-specific platforms — may need interoperability licenses to access the technical specifications required for deep integration beyond what public APIs provide. I assess interoperability license needs during product development planning — identifying integration approaches that require licensing versus those achievable through public APIs that do not implicate proprietary rights.
Question: What is a non-compete provision in an IP agreement and how does Texas law specifically affect its enforceability?
Answer: Non-compete provisions in IP agreements — including technology license agreements, consulting agreements, and employment agreements — restrict the parties from competing in defined business areas during and after the agreement term. Texas enforces non-compete agreements under the Texas Covenants Not to Compete Act, which requires that a non-compete be ancillary to an otherwise enforceable agreement, supported by adequate consideration, and reasonable in scope, geographic area, and duration. Texas courts reform rather than void overly broad non-compete provisions — reducing the scope to what the court deems reasonable rather than striking the provision entirely. For IP agreements specifically, non-compete provisions in licensing agreements between companies — rather than between employer and employee — are analyzed under a different framework than employment non-competes, with antitrust implications applying when the parties are competitors in a market. I draft non-compete provisions in IP agreements with Texas law specifically in mind — ensuring enforceability through proper agreement structure and consideration while avoiding the antitrust issues that can arise from non-competes between competitor companies.
Question: What is a license agreement's automatic renewal provision and what should Austin technology companies watch for?
Answer: Automatic renewal provisions in IP and technology license agreements — sometimes called "evergreen" provisions — cause the agreement to renew automatically for successive terms unless a party provides advance written notice of non-renewal by a specified deadline before the renewal date. These provisions are common in software licenses, data licenses, and technology license agreements and can create unexpected multi-year financial commitments if the notice deadline passes unobserved. Austin technology companies should specifically calendar automatic renewal notice deadlines for all material license agreements and conduct periodic portfolio reviews — license portfolio audits — to identify upcoming renewal points and assess whether continued licensing on existing terms remains appropriate. I advise clients to negotiate automatic renewal provisions with explicit calendaring requirements and reasonable notice periods — 90 days rather than 30 days — that provide adequate time to evaluate and act on renewal decisions before the deadline passes.
Question: What is a technology development agreement versus a technology license agreement and when does the distinction matter?
Answer: A technology development agreement governs the creation of new technology — specifying what technology will be developed, by whom, on what timeline, with what resources, and who will own the results. A technology license agreement governs access to existing technology — specifying who can practice what rights in already-existing technology, on what terms, and in what markets. The distinction matters because they address fundamentally different risk allocations. Development agreements involve performance risk — the technology may not be developed as specified, development may be delayed, or the results may not meet commercial requirements — and must address how those risks are allocated between the parties. License agreements involve IP quality risk — the licensed technology may be invalid, may not perform as represented, or may infringe third parties — and must address how those risks are allocated. Many technology relationships involve both — a development agreement for creating new technology that transitions into a license agreement for commercializing the resulting IP — and the transition from development to license creates specific contractual considerations that require deliberate planning.
Question: What are the IP provisions in a term sheet or letter of intent that could bind an Austin company before formal agreements are signed?
Answer: Term sheets and letters of intent for technology company investments and acquisitions typically contain a mix of binding and non-binding provisions — and IP-related terms can fall on either side of that line depending on how the term sheet is structured. Binding IP-related provisions in term sheets sometimes include: exclusivity provisions preventing the company from negotiating with other potential investors or acquirers during the diligence period; no-shop provisions restricting the company from soliciting competitive offers; and specific IP representations about the company's ownership of key assets that become binding commitments before full due diligence establishes their accuracy. Non-binding IP provisions — which cannot be directly enforced but influence subsequent agreement negotiation — include IP warranty scopes, indemnification caps, and representations about the IP's commercial significance. I review term sheet IP provisions for Austin clients specifically to identify which provisions are binding before the definitive agreements are negotiated and whether any binding commitments create IP-related obligations that need to be managed carefully during the diligence and negotiation period.
Question: What is a clickwrap agreement and are its IP terms enforceable against Austin technology companies?
Answer: A clickwrap agreement is a software license or terms of service agreement accepted through an affirmative user action — clicking an "I Agree" button, checking a box, or completing a registration process that expressly incorporates the terms. Courts have consistently found that properly implemented clickwrap agreements create enforceable contracts — including their IP terms — when the user had reasonable notice of the terms and took an affirmative action indicating acceptance. For Austin technology companies whose operations depend on cloud services, SaaS platforms, and software tools governed by clickwrap agreements, the IP terms buried in those agreements can significantly affect the company's rights. Particularly important are provisions governing ownership of data the company submits to the platform, the platform's right to use the company's data to train AI models, restrictions on reverse engineering, and limitations on the company's ability to export its own work product from the platform.
Question: What is an OEM agreement and how does it allocate IP ownership between the component supplier and the finished product manufacturer?
Answer: An original equipment manufacturer agreement governs the relationship between a component supplier — who manufactures specific components incorporating proprietary technology — and a manufacturer who incorporates those components into finished products sold under the manufacturer's brand. OEM agreements require specific IP provisions addressing several ownership questions that the relationship's commercial structure creates. The supplier's existing IP in the component technology is typically licensed to the manufacturer for incorporation into the finished product — not assigned. The manufacturer's product-level innovations — the specific way components are integrated, the system architecture that combines components into a finished product — are typically owned by the manufacturer. Joint innovations made during the component development process require specific ownership allocation rather than the default joint ownership that leaves both parties with unsatisfactory rights. For Austin semiconductor and electronics companies on either side of OEM relationships, the IP provisions in OEM agreements directly affect the commercial value of the relationship.
Question: What is a white-label agreement and who owns the IP in the branded version of someone else's technology?
Answer: A white-label agreement allows one company — the reseller — to rebrand and sell another company's product or technology under the reseller's own brand name. The IP ownership in a white-label arrangement is typically straightforward: the underlying technology remains owned by the original developer, who licenses it to the reseller for sale under the reseller's brand. What becomes more complex is the IP in the customizations, integrations, and modifications made to the underlying technology for the specific reseller's market — and what happens to the relationship between the reseller's brand and the underlying technology when the white-label agreement terminates. Austin SaaS companies that white-label their platforms to enterprise customers frequently encounter disputes about who owns the customer-specific configuration work, workflow customizations, and data integrations built during the relationship. I draft white-label agreements that address these ownership questions specifically rather than leaving them to the default rules that typically do not reflect either party's commercial intent.
Question: What is a distribution agreement's IP dimension and how does it affect an Austin software company's relationship with its channel partners?
Answer: A distribution agreement governing the resale of software or technology products through channel partners contains IP provisions that are often more commercially significant than the distribution economics themselves. Key IP provisions include: the scope of the trademark license granted to the distributor — specifically what branding the distributor can use and what restrictions apply to co-branding; the scope of the software license flowing through to end customers — whether end customer licenses are granted directly by the original developer or sublicensed through the distributor; confidentiality obligations protecting the developer's technical information shared with the distributor for support purposes; the prohibition on reverse engineering or modification of the distributed software; and what happens to end customer licenses when the distribution agreement terminates — whether end customers retain perpetual licenses or whether their access depends on the ongoing distribution relationship.
Question: What is a platform terms of service agreement and what IP rights does an Austin developer give up by building on a third-party platform?
Answer: When an Austin technology company builds an application, integration, or extension on a third-party platform — Apple's App Store, Salesforce AppExchange, Shopify's app ecosystem, or any similar platform — the platform's developer terms of service govern what IP rights the developer retains and what rights the platform acquires. Key IP provisions in platform developer agreements typically include: the developer's license to use the platform's APIs and SDKs — which may be revocable if the developer violates platform policies; the platform's rights in the developer's application — including whether the platform can review, copy, or distribute the application for its own purposes; restrictions on what technologies the developer can incorporate into their application; data ownership provisions governing information generated by the application's users; and the platform's ability to create competing functionality based on observed usage patterns. For Austin software companies building significant business value on third-party platforms, understanding these IP terms before building — rather than after — is one of the most commercially important IP reviews I conduct.
Question: What is an IP provision in a vendor agreement and how does it affect ownership of customizations an Austin company pays a vendor to build?
Answer: When an Austin company pays a vendor to build custom functionality — a custom Salesforce implementation, a proprietary data integration, a bespoke reporting system — the default IP ownership rules produce an outcome most companies do not intend: without an explicit IP assignment provision, the vendor owns the copyright in the custom work they built. The company that paid for the development receives a license to use the custom work — often an implied non-exclusive license — but not ownership. This distinction becomes commercially significant when the company wants to hire a different vendor to maintain or extend the custom work, when the company is acquired and the acquirer needs clean IP title in all technology the company uses, or when the vendor goes out of business and the license becomes uncertain. I review vendor agreements for Austin technology companies with specific attention to this ownership gap — ensuring that every vendor agreement either includes an explicit IP assignment or specifically addresses the license scope to confirm that the company can maintain, modify, and transfer the custom work without vendor consent.
Question: What is a revenue sharing agreement that involves IP rights and how should it be structured?
Answer: Revenue sharing arrangements in technology contexts — where one party contributes IP and another contributes distribution, marketing, or commercial infrastructure in exchange for a share of resulting revenue — require specific IP provisions that generic revenue sharing agreements frequently omit. Critical IP provisions in technology revenue sharing arrangements include: clear identification of what IP each party is contributing and what rights are licensed to the other party to enable the revenue-generating activity; ownership of jointly developed IP created during the commercial relationship; what happens to each party's IP license if the revenue sharing arrangement underperforms and one party wants to exit; minimum revenue guarantees or performance milestones that maintain each party's incentive to contribute; and post-termination restrictions preventing one party from using the other's IP to replicate the revenue-generating activity independently after the arrangement ends. For Austin technology companies with distinctive IP and limited commercial infrastructure, revenue sharing arrangements can be an effective commercialization strategy — when the IP provisions are structured to protect the IP holder's long-term interests.
Question: What is an IP agreement's governing law provision and why does the choice of Texas law versus Delaware law matter for Austin technology companies?
Answer: The governing law provision in an IP agreement determines which state's contract law applies to interpretation and enforcement disputes — a choice that can significantly affect how the agreement's IP terms are construed in litigation. Texas and Delaware are the two most common governing law choices for Austin technology companies. Texas contract law generally favors straightforward enforcement of written agreement terms, applies specific rules under the Texas Covenants Not to Compete Act for non-compete provisions, and has specific trade secret law under TUTSA that may differ from Delaware's approach. Delaware contract law — which applies many large technology company agreements and most venture-backed startup agreements — has a highly developed body of commercial contract case law from the Delaware Court of Chancery that provides predictable outcomes for standard commercial IP agreement disputes. For IP agreements between parties in different states, I advise on governing law selection based on the specific provisions at issue and the jurisdiction whose law most clearly supports the parties' intended outcomes — rather than defaulting to the choice that a larger counterparty's standard form agreement presents.
Question: What is a content licensing agreement and what IP issues arise when Austin media and technology companies license third-party content?
Answer: Content licensing agreements govern the use of text, images, video, music, data, and other creative works owned by third parties in an Austin company's products, services, or marketing. IP issues in content licensing arise in several dimensions that non-IP-trained business teams frequently handle inadequately. The scope of the license — what uses are permitted, what platforms are covered, what geographic territories are included, and what term the license runs — defines the boundaries of lawful use and any use outside those boundaries constitutes copyright infringement regardless of the licensing relationship for other uses. Sublicensing rights — whether the licensee can incorporate licensed content into products that customers then use — are frequently needed but not always included in standard content licenses. Moral rights in content created by international authors may give those authors ongoing rights in the content even after the license is granted. And the consequences of license termination — whether the licensee must immediately remove licensed content from all existing products and marketing materials or receives a sell-off period — can be commercially disruptive if not negotiated in advance.
Question: What is a manufacturing agreement's IP provision regarding tooling, molds, and process-specific equipment?
Answer: When an Austin company engages a contract manufacturer to produce its products, the manufacturing process requires creation of tooling, molds, dies, jigs, and fixtures that are specific to the company's product. The IP ownership of these manufacturing tools is frequently undefined in standard manufacturing agreements — and the default result when ownership is not specified can leave the Austin company without ownership of tools it paid for and cannot reclaim when changing manufacturers. Manufacturing agreement IP provisions should specifically address: who owns the tooling and molds created specifically for the Austin company's products; whether the manufacturer can use that tooling to produce competing products for other customers; what happens to the tooling if the manufacturing relationship terminates; and whether the company's payment for tooling development constitutes purchase of the tools or simply payment for the manufacturer's service using tools the manufacturer retains. For Austin companies with proprietary product designs manufactured externally, tooling ownership provisions are among the most commercially important IP terms in manufacturing relationships.
Question: What is an API terms of service from an IP perspective and how do they affect Austin developers who build on third-party APIs?
Answer: API terms of service — the legal agreements governing access to and use of a third-party application programming interface — contain IP provisions that directly affect what an Austin developer can build with the API and what rights they retain in applications that depend on it. Key IP provisions in API terms of service include: the scope and revocability of the license to use the API — most commercial API licenses are revocable, meaning the API provider can terminate access at any time under specified conditions; restrictions on how API data can be stored, redistributed, or used in derivative applications; ownership of applications built on the API — whether the API provider claims any rights in developer applications that use the API; and competitive use restrictions preventing developers from using the API to build products that compete with the API provider's own commercial offerings. For Austin software companies whose products depend on third-party APIs — payment processors, mapping services, communication platforms, or AI model APIs — the revocability of the API license is a significant business continuity risk that should be addressed in the company's overall IP and business strategy.
Answer: Franchise agreements are fundamentally IP licensing agreements — the core commercial substance of a franchise is the franchisor's grant to the franchisee of a license to use the franchisor's trademarks, trade dress, operating systems, and proprietary business methods in a defined territory. The IP provisions in franchise agreements govern: the scope of the trademark license — which marks the franchisee can use, in what formats, and subject to what quality control obligations; the system standards that define the operating methods the franchisee must follow — which are typically trade secrets of the franchisor; the prohibition on the franchisee developing or using competing systems or brands; the ownership of any improvements or innovations the franchisee makes to the franchisor's system — franchise agreements typically require franchisees to assign any improvements back to the franchisor; and the IP provisions on termination — requiring the franchisee to immediately cease using all licensed IP, return all proprietary materials, and de-identify the location from the franchise brand.
Question: What is a franchise agreement's IP dimension and how does a franchisee's use of franchisor IP create ongoing legal obligations?
Question: What is an IP indemnification carve-out and why do they matter more than the indemnification itself in some Austin technology agreements?
Answer: An IP indemnification carve-out is an exclusion from the indemnification obligation — defining specific circumstances where the vendor does not indemnify the customer against IP infringement claims even though the broader indemnification provision would otherwise apply. In many technology agreements, the carve-outs are more commercially significant than the indemnification grant itself because they define the realistic scenarios where IP infringement risk is most likely to arise. Standard carve-outs typically exclude infringement caused by: the customer's modification of the vendor's technology; the customer's combination of the vendor's technology with third-party products the vendor did not specify; the customer's use of the technology outside the licensed scope or for uses the vendor did not contemplate; and the customer's specifications that required the vendor to implement a specific approach that turned out to infringe. For Austin technology companies accepting IP indemnification from vendors, I analyze the carve-outs specifically against the company's actual deployment context — to determine whether the most likely infringement scenarios in their specific use case fall within the indemnification or outside it in a carve-out.
Question: What is a perpetual license versus a subscription license and what happens to IP access rights when a subscription terminates?
Answer: A perpetual license grants the licensee the right to use the licensed IP indefinitely — even after making a one-time payment — regardless of whether the licensor continues to support the technology or remain in business. A subscription license grants the right to use the licensed IP only during the subscription term — when the subscription ends, the license ends and continued use constitutes infringement. The commercial significance of this distinction has grown dramatically as software delivery has shifted from perpetual licenses to subscription models. For Austin companies that have built significant operational dependence on subscription software — integrating it deeply into their workflows, training their teams on it, and structuring their processes around its specific capabilities — subscription termination can be operationally disruptive in ways that go well beyond simply losing access to a tool. Technology agreement negotiation should specifically address: what happens to the licensee's data when the subscription terminates; whether the licensee receives any transition period to export data and migrate to alternative systems; and whether the licensee has any right to continue using the software in a read-only capacity after termination to access historical records.
Question: What is a software escrow trigger condition and how should Austin companies negotiate release conditions that actually protect them?
Answer: A software escrow agreement is only as valuable as its release conditions — the specific events that entitle the licensee to receive the escrowed source code from the escrow agent. Poorly negotiated release conditions make escrow protection illusory: conditions that are too narrow — requiring a formal bankruptcy adjudication before release is permitted — may not trigger in time to be useful, since by the time bankruptcy is formally adjudicated the licensor's development team has dispersed and the code may be months out of date. Well-negotiated release conditions for Austin technology company licensees should include: insolvency filing rather than just bankruptcy adjudication — protecting against the period between financial distress and formal proceedings; cessation of product support or maintenance obligations for specified periods; material breach of the license agreement that remains uncured; and acquisition by a competitor that results in discontinuation of the licensed product. Each trigger condition should be defined with sufficient specificity that the escrow agent can determine objectively whether it has occurred — vague trigger conditions create disputes about release eligibility at precisely the moment when the licensee most needs access.
Question: What is a technology transfer agreement in the context of an Austin company acquisition and how does it differ from a standard IP assignment?
Answer: A technology transfer agreement — used in acquisition contexts where the acquirer wants to receive specific technology assets rather than acquiring the entire selling entity — involves a more complex transfer structure than a simple IP assignment because it addresses not just ownership transfer but also the knowledge, personnel, and operational context needed to effectively deploy the transferred technology. A standard IP assignment transfers legal title to the IP. A technology transfer agreement additionally addresses: the transition assistance the seller provides to help the acquirer understand and deploy the transferred technology — typically through a defined transition services period with specific knowledge transfer obligations; the employees with critical knowledge of the technology and whether they will be offered employment by the acquirer; the documentation and operational materials that accompany the IP — source code repositories, technical specifications, deployment guides, and development environment configurations; and the handling of ongoing customer relationships that depend on the transferred technology. For Austin technology company acquisitions where specific product lines or technology platforms are being carved out and transferred, the technology transfer agreement's operational provisions are as commercially important as the IP assignment provisions.
Question: What is a cross-license agreement and when is it the right structure for resolving IP disputes between Austin technology companies?
Answer: A cross-license agreement is a mutual IP licensing arrangement where each party grants the other licenses to their respective patent portfolios — typically used to resolve mutual infringement exposure between companies that each hold patents covering technology the other practices. Cross-licenses are most common between operating companies with substantial patent portfolios in overlapping technology areas — semiconductor companies, wireless technology companies, and software platform companies regularly enter cross-licenses as an alternative to mutually destructive patent litigation. For Austin technology companies, cross-licensing opportunities arise when a company receives a patent assertion from a competitor that also practices technology covered by the Austin company's own patents. Rather than paying a one-way royalty to the asserting party, the Austin company can leverage its own portfolio to negotiate a cross-license that balances the parties' mutual exposure. The commercial terms of a cross-license — whether it is royalty-free or involves a balancing payment, what portfolios are included, how future patents are handled, and whether field of use restrictions apply — depend on the relative strength and commercial coverage of each party's patent portfolio.
Question: What is a patent non-assertion covenant and how does it differ from a patent license in an IP agreement?
Answer: A patent non-assertion covenant — sometimes called a covenant not to sue — is a promise by a patent holder not to assert specific patents against a defined party, category of parties, or activities, without granting a formal license to practice the patents. The legal distinction between a license and a covenant not to sue has practical consequences. A license is an affirmative grant of permission to practice the claimed invention. A covenant not to sue is a promise not to assert — it does not affirmatively authorize anything but removes the threat of patent enforcement. For commercial purposes the practical effect is often similar — neither the licensee nor the covenant recipient faces patent enforcement risk — but the legal basis differs in ways that affect how the protection is interpreted, assigned, and enforced. Covenants not to sue are common in open source contexts — where contributors to a project covenant not to assert their patents against users of the project — and in standards-setting contexts where SEP holders covenant not to sue implementers pending FRAND license negotiation. For Austin technology companies evaluating whether to accept a covenant not to sue in lieu of a license, I assess whether the covenant provides equivalent commercial protection for the specific activities at issue.
Question: What is a license agreement's improvement clause and how should Austin licensors negotiate it to protect their long-term interests?
Answer: An improvement clause in a patent or technology license agreement addresses what happens when the licensee makes improvements to the licensed technology — whether those improvements must be licensed back to the licensor, on what terms, and with what effect on the licensee's ability to commercialize their own innovations. Improvement clauses range from the relatively benign — a non-exclusive license back to the licensor of improvements made using the licensed technology — to the commercially damaging — an exclusive license of improvements that effectively allows the licensor to capture all value created by the licensee's investment in developing the technology further. For Austin licensors negotiating improvement clauses with technology company licensees, the key objectives are: ensuring that improvements made to the core licensed technology are available to enhance future versions; preventing licensees from using the licensed technology as a platform to develop competing innovations without recognizing the licensor's foundational contribution; and maintaining the licensor's ability to license the improved technology to other parties. For Austin licensees, the objective is the opposite — ensuring that the improvement clause does not create obligations that prevent commercializing innovations built on top of the licensed technology.
Question: What is a license agreement's anti-assignment provision and how does it affect an Austin startup's ability to be acquired?
Answer: An anti-assignment provision in a patent or technology license agreement restricts the licensee's ability to transfer their license rights to a third party — including through acquisition, merger, or asset sale. For Austin startups that hold important inbound licenses — to university technology, to foundational platform technology, or to specific IP that enables their core product — anti-assignment provisions in those licenses can create significant obstacles to acquisition transactions. An acquirer who purchases an Austin startup discovers in due diligence that the startup's most important license cannot be assigned to the acquirer without the licensor's consent — consent that the licensor may withhold or use as leverage to renegotiate license terms at precisely the moment when the startup has the least negotiating leverage. Change of control provisions — which trigger the anti-assignment restriction not just for explicit assignment but for any transaction that transfers control of the licensee entity — are particularly common and particularly problematic in acquisition contexts. I advise Austin startups to negotiate anti-assignment provisions when entering important inbound licenses — specifically seeking consent-not-to-be-unreasonably-withheld language and explicit carve-outs for acquisition transactions rather than accepting blanket anti-assignment provisions that could prevent or complicate future exits.
Question: What is a source code license and when should Austin technology companies require access to vendor source code rather than just the executable software?
Answer: A source code license grants the licensee access to the human-readable programming code underlying a software product — rather than just the compiled executable that end users run. Most commercial software licenses are executable-only — the licensee receives the right to run the software but not to read, modify, or maintain the underlying code. For most software use cases this is commercially adequate. Source code licenses become commercially necessary when: the Austin company needs to modify the software to meet specific technical requirements that the vendor cannot or will not address; the Austin company's regulatory environment requires the ability to audit the software's security practices at the code level; the software is deeply integrated into mission-critical systems where the ability to maintain and update the software independently of the vendor is operationally essential; or the software will be embedded in the Austin company's own products and the company needs the source code to comply with open source license obligations in the underlying code. Source code licenses should include specific provisions addressing what the licensee can do with the source code — whether modification is permitted, whether derivative works can be distributed, and what confidentiality obligations apply to the source code itself.
[ Schedule a Free Consultation ]
IP Agreements & Contracts Services
The IP provisions in your commercial agreements determine what your company actually owns, what rights you have actually granted away, and what obligations follow you long after the contracts are signed and filed. Most technology companies discover these provisions matter when it is already too late to address them — in due diligence for a funding round, in a dispute with a vendor whose agreement left ownership ambiguous, or in an acquisition negotiation where a platform license turns out to encumber IP the buyer thought was unencumbered.
I offer a free 30-minute phone consultation to discuss your specific IP contract situation — whether you need a technology license agreement drafted, a SaaS agreement reviewed for IP ownership implications, an R&D agreement structured around a university collaboration, or a commercial contract audited before a transaction.
My 17 years of patent prosecution experience combined with a physics degree from the University of Texas at Austin and seven years of semiconductor manufacturing engineering give me the technical foundation to engage with IP contract provisions at the level of what they actually mean for the specific technology involved — not just what they say as abstract legal language.
Every IP provision I draft or review reflects genuine understanding of the technical assets it governs, the commercial relationship it structures, and the business consequences it creates. For Austin technology companies at every stage — from seed-stage startups structuring their first platform agreements to growth-stage companies managing complex multi-party technology relationships to corporate IP teams reviewing vendor and partner agreements — I provide IP contract services calibrated to the technical sophistication that Austin's innovation economy demands.
Call or text (512) 293-0710, email sconnolly@austin-patent-attorney.com, or fill out the form to schedule your free consultation. Consultations are available Monday through Friday, 1:00pm to 4:00pm Central Time.
All discussions are confidential under attorney-client privilege. No obligation.
Phone: 512-293-0710
Email: sconnolly@austin-patent-attorney.com
Location: Austin, Texas
Serving Austin, Round Rock, Cedar Park, Georgetown, and all of Central Texas.
USPTO matters are federal — I work with clients throughout Texas and nationwide.
[ Related Services ]
Clients structuring IP agreements often also work with me on:
[Patent Licensing Agreements] · [IP Assignment Agreements] · [Joint Development Agreements] · [Non-Disclosure Agreements] · [IP Due Diligence]
Software Agreements — Ownership, Customization, and the SaaS Complication
Software agreements — including development agreements, professional services agreements, SaaS subscription agreements, and platform access agreements — contain IP provisions that determine one of the most commercially consequential questions in technology transactions: who owns the software, the customizations, and the data when the relationship ends. For technology companies on both sides of software relationships — those building software for others and those deploying software built by others — getting these provisions right at the beginning of the relationship determines the company's IP position for its entire commercial life.
The work-for-hire doctrine — which automatically vests copyright ownership in the party that commissioned a work under specific qualifying categories — applies to some software development but not others. Software created by employees within the scope of employment is automatically owned by the employer. Software created by independent contractors qualifies as work for hire only for certain enumerated categories under the Copyright Act — and computer programs are not on that list. A software development agreement with a contractor that does not contain an explicit IP assignment provision may leave copyright ownership with the contractor rather than the company that paid for the development, regardless of how clearly everyone involved understood the work was being done for the company's benefit. I review software development agreements and professional services agreements specifically for this ownership gap and ensure it is addressed through express assignment language that is not contingent on contested work-for-hire characterization.
SaaS agreements create a specific IP ownership complication that has become increasingly consequential as cloud-delivered software has become the dominant enterprise software model. When a company customizes a SaaS platform — building workflows, integrating data, developing extensions, or training AI models within a vendor's environment — who owns those customizations and configurations? The answer depends entirely on the SaaS agreement's IP provisions, which in most standard vendor agreements favor the vendor. Customizations may be treated as derivative works of the vendor's platform that the vendor owns, or as customer data that the customer owns but the vendor can use, or as jointly owned improvements — each structure having dramatically different implications for the customer's ability to switch vendors, recover their investment in platform customization, and control their own business processes. I review SaaS agreements for Austin technology companies with particular attention to customization ownership, data portability, and the IP implications of platform dependency.
The IP Dimension of Every Business Contract
Every significant commercial agreement a technology company executes has an intellectual property dimension — and most of those agreements are reviewed and signed without anyone examining that dimension carefully. Technology license agreements govern what a licensee can do with licensed IP and what happens when the technology evolves. Software agreements determine who owns customizations and improvements built on a vendor's platform. Research and development agreements establish ownership of what gets discovered during funded work. Vendor agreements determine who owns tooling, molds, and process innovations developed for the relationship. Employee agreements determine whether the company actually owns what its engineers build. None of these IP dimensions are automatically addressed correctly by standard commercial agreement templates — they require deliberate, technically-informed drafting that accounts for the specific technology involved and the specific business relationship being structured.
The cost of inadequate IP provisions in commercial agreements is rarely visible at signing. It surfaces later — when a company tries to enforce rights it assumed it had but never actually acquired, when an acquisition collapses because a key vendor agreement left IP ownership ambiguous, when a platform customer discovers they own nothing when they switch providers, when a contract manufacturer claims ownership of manufacturing innovations developed specifically for one customer's product. These discoveries are expensive. They are also almost entirely preventable by ensuring IP provisions are drafted with the same technical precision applied to the underlying patent work itself.
My approach to IP agreements and contracts reflects 17 years of patent prosecution experience combined with a semiconductor engineering background and a physics degree from the University of Texas at Austin — a combination that produces IP provisions grounded in genuine understanding of the technical assets being protected rather than generic contract boilerplate inserted without connection to what the technology actually is. For Austin's technology companies — operating in semiconductor, software, AI, health technology, and advanced manufacturing — I provide IP contract drafting and review that addresses the full range of commercial agreements containing IP dimensions, not just the specialized instruments like patent licenses and NDAs that IP attorneys typically focus on.
