If you’re a founder sitting on technology that works, but you’re not ready to build a full sales force, manufacturing operation, or foreign subsidiary around it, licensing of technology is often the first serious path to revenue. It lets you keep ownership while giving someone else the right to use, develop, or commercialize what you’ve built.
At Mayo Law, we help businesses in Toronto, the GTA, and across the border handle deals like this, with licensing that often touches both U.S. and Canadian law. The issue usually isn’t whether a deal can be signed. It’s whether the deal still makes business sense a year later, when product timelines slip, support requests pile up, and each side realizes they assumed different things about territory, exclusivity, and who is responsible for getting the technology market-ready.
In practice, that is where good deals separate from expensive mistakes. The licensing market is large and mature. In the U.S. alone, technology transfer activities generated $3.6 billion in license income in 2023, and universities and research institutions launched over 700 new commercial products, according to the AUTM 2023 Licensing Survey.
What Is the Licensing of Technology
Licensing of technology is a contract in which the owner of technology gives another party defined rights to use, develop, make, sell, or distribute it, while the owner keeps title to the underlying intellectual property. The license can cover patents, software, know-how, confidential information, and related materials needed to make the technology usable in practical applications.
For a startup founder, the easiest analogy is renting versus selling. If you sell the house, it’s gone. If you license the technology, you still own it, but someone else gets limited rights under agreed conditions.
That distinction matters because many young companies don’t want a full assignment of their IP. They want market access, channel partners, development support, or foreign reach without giving up the asset itself.
A lot of founders also assume a license is just a patent permission slip. It usually isn’t. The actual agreement often includes documentation, source materials, training, technical specifications, and confidential know-how. That is why a patent-only mindset causes problems later, especially in software and technical manufacturing.
The business case for licensing isn’t theoretical. A Stanford analysis of fifty years of university technology licensing found that among inventions generating more than $10 million in net income, all were self-licensed by the inventors’ own startups, as reported in the Stanford study on technology licensing and startups. Founders should also understand how licensed know-how differs from registered IP rights, especially when choosing between secrecy and disclosure in a deal involving trade secrets and patents.
Core Components of a Technology License Agreement
A good technology license doesn’t start with royalties. It starts with the grant of rights. If that clause is fuzzy, the rest of the contract won’t save you.
What the license actually gives
The first question is simple. What can the licensee do?
Can they manufacture? Can they modify the software? Can they distribute in Canada but not the U.S.? Can they sublicense to an affiliate? Can they use the technology only in one vertical, such as medical devices, but not in industrial automation?
Those aren’t drafting details. They’re the economic core of the deal.
WIPO’s licensing guidance makes an important point. A technology license is broader than a patent license because it may need to package patents, confidential know-how, software, design files, training materials, and support. WIPO also notes that the patent alone often doesn’t provide enough information to make the technology commercially usable, as explained in the WIPO guide on licensing technology.
Practical rule: If the licensee can’t actually use what you licensed without calling you every week, the legal grant may be valid but the commercial package is incomplete.
Exclusive rights versus shared rights
Most first-time licensors focus too heavily on the word “exclusive” without testing what it costs them later.
| Factor | Exclusive License | Non-Exclusive License |
|---|---|---|
| Market control | One licensee controls the defined market | Licensor can work with multiple licensees |
| Upfront value | Often supports stronger commercial commitment | Usually preserves flexibility |
| Founder risk | Higher if licensee underperforms | Lower because channels stay open |
| Future partnerships | More restricted | Easier to add later |
| Enforcement pressure | Licensee may demand stronger protections | Usually stays more centralized with licensor |
| Exit impact | Can complicate acquisition diligence | Often easier for later investors to assess |
For many startups, a limited exclusive license is better than a broad exclusive license. You can narrow it by territory, field of use, channel, or term. For example, a license might be exclusive only for hospital use in Canada, while the founder keeps U.S. rights and all non-healthcare applications.
Clauses founders often under-negotiate
Three clauses routinely get less attention than they deserve:
- Sublicensing rights: If the licensee needs distributors, contract manufacturers, or foreign affiliates, they may need sublicensing authority. If you allow it, control the form, notice requirements, and who remains liable.
- Improvements ownership: If the licensee adapts or improves the technology, who owns that work product? This gets messy quickly in software and industrial process deals.
- Termination and reversion: If they stop developing, stop paying, or breach confidentiality, what comes back to you, and how fast?
Founders sometimes borrow language from a generic assignment form and don't realize they've effectively transferred more than they intended. That's one reason to distinguish a license from a full transfer or assignment of contract rights.
A license should leave you with optionality. If it leaves you trapped with a non-performing partner, the contract was too permissive.
Structuring Royalties and Financial Terms
The money side of a license should match the actual commercial path of the technology. Founders often ask for a large royalty percentage without looking at adoption risk, implementation burden, or whether the licensee needs years of development before real revenue appears.
Common payment structures
A workable deal often combines more than one payment method:
- Upfront payment: Useful when the licensor has already built significant value and needs immediate cash.
- Running royalty: Ongoing payment tied to sales, usage, or another measurable commercial output.
- Milestone payments: Triggered by technical or commercial events, such as prototype completion, regulatory filing, or first commercial sale.
- Minimum payments: Protect against a licensee that signs the deal and then lets the technology sit.
The mistake is treating these as interchangeable. They aren't. An upfront fee pays for access. Milestones reward progress. Running royalties share long-term upside. Minimums create pressure to perform.
How do you determine a fair royalty rate for technology
There isn't a universal fair rate. The number depends on what is being licensed, how complete it is, how much support the licensor must provide, the expected margin in the end product, whether the deal is exclusive, and how much development risk remains.
In practice, I look first at the business model, not the percentage. A license for a nearly market-ready software module is different from a license for an early-stage process that still needs engineering, testing, and regulatory work. If the technology still needs substantial buildout, milestone payments and minimum performance obligations usually matter more than arguing over a headline royalty.
A useful negotiating move is to separate access value from execution value. If the licensee wants broad exclusivity now, ask for stronger upfront compensation, tighter milestones, or both. If they want flexibility, preserve your right to work with others.
What works and what usually fails
A startup with limited runway often needs some cash at signing. But taking only an upfront payment can leave a lot of future value on the table if the product succeeds.
On the other hand, a pure royalty deal can become dead money if the licensee never launches.
That is why founders should pay attention to contingent rights too. A right of first offer can be useful in adjacent markets or later territories, but only if the trigger, timetable, and scope are clear. Otherwise it becomes a drag on future deals without producing real value.
Don't confuse a signed term sheet with a finance plan. If the payment structure doesn't support development, enforcement, and post-signing support, the deal will strain the company even if the royalty headline looks attractive.
Protecting and Enforcing Your Intellectual Property
A technology license is also an enforcement document. It decides who maintains registrations, who pays for filings, who controls infringement claims, and who carries the risk if the technology depends on confidential know-how.
Who is responsible for patent infringement in a license agreement
The answer depends on the contract. A license should say who handles third-party infringement claims, who controls the defense, who decides whether to sue outsiders, and who pays for that work.
If the agreement is silent, each side may assume the other will act. That is a bad place to be once a competitor copies the product or sends a demand letter. The licensor may own the patent, but the licensee may be the party losing market share in real time. Aligning incentives early matters.
Confidentiality is not boilerplate
Many technology licenses fail at the know-how layer. The contract grants rights, but the confidentiality terms are too thin for the information being exchanged.
That problem is worse when the value sits in process details, implementation steps, source code, test data, calibration methods, or customer-specific deployment knowledge. If those materials leak, patent rights may not solve the commercial damage.
Mayo Law works with companies across the GTA and on cross-border matters. Joseph Mayo is licensed in Ontario and New York, so clients with U.S. ties coordinate their legal work in one place rather than juggling two firms. On the business side, that often means lining up contract drafting with trade secret controls, internal handling protocols, and response planning for trade secret misappropriation disputes.
Two recurring founder mistakes
- They assume ownership language covers improvements. It often doesn't. Improvement rights need their own drafting.
- They rely on broad NDAs without operational controls. If engineers, contractors, or channel partners all touch the technology, the contract should reflect who may access what, and on what restrictions.
One common scenario involves a Canadian startup licensing software and implementation know-how to a U.S. distributor. The distributor then hires a developer to localize the product. If the license doesn't control derivative work ownership, confidentiality flow-downs, and subcontractor access, the startup may discover that key product improvements now sit in a legal gray zone.
Another involves a U.S. founder licensing a process package into Canada. The patent rights are clear, but the operating parameters are delivered informally in email and calls. Once the relationship sours, both sides dispute what was licensed, what was support, and what remained confidential.
Navigating Cross-Border Licensing Between the U.S. and Canada
Cross-border licensing looks simple from a distance. Two companies. One contract. Royalty payments. However, U.S.-Canada deals frequently encounter friction points: tax treatment, export controls, governing law, local compliance, and post-signing execution.
The sign now solve later problem
A founder in Ontario licenses software to a U.S. company. The term sheet looks fine. It mentions exclusivity, royalties, and a launch target. Nobody spends enough time on where disputes will be heard, whether the U.S. party can transfer the deal to an affiliate, or whether technical data shared during onboarding raises export-control issues.
Six months later, product adaptation starts in a different state, payments are delayed, and each side points to a different interpretation of the same sentence.
That happens because cross-border deals need more than commercial alignment. They need legal architecture.
What to check before signing
- Governing law and forum: Decide whether disputes go to court or arbitration, and where. If you don't set this cleanly, early procedural fights can consume the advantage you thought you had. A clear forum selection clause is often worth more than pages of abstract boilerplate.
- Tax treatment of royalties: Royalty flows across the border can trigger withholding and reporting issues. Founders should review treaty and withholding rules with tax counsel and the relevant government guidance, including IRS information on withholding for payments to foreign persons and the Canada Revenue Agency materials on payments to non-residents.
- Export and sanctions compliance: Some software, encryption, technical data, and industrial know-how can raise export-control questions. For U.S. deals, founders should at least assess whether the technology touches BIS export administration regulations guidance before sharing detailed technical packages.
- Public health and public-interest obligations: In health technology deals, access and public-benefit issues may affect how exclusivity, sublicensing, and territory should be handled. WHO's 2024 briefing note states that technology licensing is central to the health-sector R&D, production, and distribution environment and that access requires integrated, equitable licensing approaches, as set out in the WHO briefing note on health technology licensing.
Cross-border licensing gets expensive when business teams assume tax, compliance, and dispute clauses can be cleaned up after signing. They usually can't.
A practical cross-border split
In process-industry deals, the technical package is often sequenced after signing. A design conference confirms the design basis, then the licensor provides a Technology Manual and later a Process Design Package. The plant may need to be built in strict accordance with that package for performance warranties to remain valid, while the buyer still handles local codes and site conditions, as described in this process-industry licensing overview.
That sequence is useful beyond heavy industry. It shows a larger rule. The more the licensor controls the design basis, the easier it is to enforce performance obligations. The less detail the licensor provides, the more integration risk shifts to the buyer.
For U.S.-Canada startup deals, I usually want that allocation stated plainly. If the Canadian licensee is responsible for localization, local regulatory adaptation, and customer implementation, say so. If the U.S. licensor must deliver detailed specifications, support hours, validation data, or training, say that too.
Can you license technology across the border without setting up a foreign company
Often, yes. A license doesn't always require a foreign subsidiary. But the lack of a local entity doesn't remove local law, tax, or enforcement issues.
It can also affect collections and dispute strategy. If the other side has no local assets where you sue, your paper rights may be harder to enforce. That doesn't make the deal impossible. It means the contract needs better security around payment, audit rights, termination, and post-termination use restrictions.
Due Diligence and Negotiation Tactics for Startups
Most bad licensing deals don't fail because the concept was wrong. They fail because the founder was rushed, flattered by the other side's brand name, or overly focused on the royalty number.
Do I need a lawyer for a technology license agreement
If the deal involves valuable IP, exclusivity, cross-border performance, or confidential know-how, yes. Generic templates rarely address field-of-use limits, improvements ownership, sublicensing controls, cross-border tax language, or what happens if development stalls.
That matters because shelving is a real risk. Stanford's licensing guidance notes that provisions such as mandatory sublicensing and milestone-based incentives can address technology flipping and improve eventual product availability, and NIH requires license applicants to describe their development and commercialization plans in support of public benefit, as discussed in Stanford's licensing principles paper.
A startup checklist that actually helps
- Know what you own: Confirm whether the technology includes open-source components, contractor-built code, university-origin IP, or third-party data restrictions.
- Stress-test the buyer's plan: Ask who will develop, sell, support, and fund commercialization. Vague enthusiasm is not a commercialization plan.
- Tie exclusivity to performance: If they want exclusivity, require milestones, reporting, and termination rights for non-performance.
- Control sublicensing: Downstream deals should not become a back door that strips you of control.
- Plan the breakup before the wedding: Define what happens to confidential materials, inventory, customer support obligations, and transitional use after termination.
One founder I advised had a promising cross-border partner with strong distribution but no technical implementation team. The partner wanted exclusivity immediately. The right answer wasn't "no." It was "not yet." The deal became viable only after exclusivity was phased in based on concrete launch obligations.
Another startup had the opposite issue. Their prospective licensee wanted broad rights to "future versions" of the platform. That phrase was too loose. In a software company, future versions may represent the next business entirely.
Frequently Asked Questions
What's the difference between a technology license and an IP assignment
A license gives another party defined rights to use the technology while you keep ownership. An assignment transfers ownership itself. For most startups, that difference is critical because investors, acquirers, and future partners will want to know whether the company still controls its core IP or merely retained limited residual rights.
How much does a technology license agreement cost to negotiate
Legal cost depends on scope, complexity, and whether the deal is domestic or cross-border. A short non-exclusive software license is very different from an exclusive U.S.-Canada deal involving know-how, support obligations, and tax review. The practical point is that early drafting is usually cheaper than later litigation over exclusivity, payment rights, or misuse of confidential information.
How long does it take to complete a licensing deal
Simple deals can move quickly if the business terms are already aligned. Cross-border deals take longer when the parties haven't resolved tax treatment, sublicensing, compliance, governing law, or technical delivery obligations. Delays usually come from unresolved business assumptions, not from the signature process itself.
Which law should govern a U.S.-Canada technology license
There isn't one universal answer. The better choice depends on where each party is located, where the technology will be used, where payment and enforcement risk sit, and whether arbitration or court proceedings make more sense. The key is to choose deliberately rather than leaving the contract with vague or conflicting dispute language.
What is the biggest risk for a startup licensor
The biggest risk is often underperformance by an exclusive licensee. If the startup gives up territory or market access without hard milestones, reporting duties, audit rights, and strong termination language, the license can block growth instead of creating it. In practice, founders usually regret overbroad exclusivity more than they regret a tougher negotiation.
Conclusion and Next Steps
A first licensing deal often looks straightforward until the redlines start. A U.S. customer wants exclusivity in Canada, your team assumes support is out of scope, and nobody has pinned down withholding tax, currency, or who owns improvements. Those issues can turn a promising deal into a margin problem, a control problem, or both.
For startups and SMEs, a technology license should be treated as an operating plan, not just an IP document. The agreement needs to match how the product is sold, supported, updated, and enforced across two countries. If the commercial model depends on channel growth, reserve rights carefully. If the counterparty is asking for exclusivity, tie it to measurable performance. If payments cross the border, confirm the tax treatment before signing, not after the first invoice goes unpaid or disputed.
The costly mistakes are usually visible early. Founders often spot them during negotiation and still paper over them to get the deal done.
If you're weighing a first licensing deal, Mayo Law advises startups and SMEs on cross-border contracts, IP-related business terms, and U.S.-Canada deal structure in plain English.
How Mayo Law Can Help
Mayo Law advises startups and SMEs on technology licensing matters involving Ontario, New York, and broader U.S.-Canada business activity.
That work usually starts before the first draft is marked up. Founders often come in with a term sheet that looks commercially reasonable, but the legal and operational points are still misaligned. The license scope may be too broad for the price. The territory may not match the sales plan. Support, data rights, improvements, enforcement control, and payment mechanics may be sitting in different emails instead of the contract.
We help clients close those gaps early, while there is still room to negotiate.
For cross-border deals, that often means translating business objectives into contract language that holds up on both sides of the border, spotting issues that local counsel on only one side may miss, and keeping the agreement practical enough for a startup team to administer after signing. The goal is not a longer contract. The goal is a deal you can operate without recurring disputes over scope, invoices, renewals, or ownership.
Disclaimer
This article is for informational purposes only and does not constitute legal advice. Every situation is different. Consult a licensed lawyer about your specific circumstances. Mayo Law provides legal services through Mayo Law PC in Ontario and Joseph Mayo PLLC in New York.
Related Articles
