Establishing secure connection…Loading editor…Preparing document…

Software License Addendum

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

SOFTWARE LICENSE ADDENDUM

This Software License Addendum ("Addendum") is made effective as of by and between Licensor Name: with principal place of business at and Licensee Name: with principal place of business at (each a "Party" and collectively the "Parties").

RECITALS

WHEREAS, the Parties entered into a Software License Agreement titled: dated (the "Agreement"); and

WHEREAS, the Parties desire to amend certain terms of the Agreement to reflect changes to licensed modules, fees, support obligations, and term; and

WHEREAS, capitalized terms used but not otherwise defined in this Addendum have the meanings given to them in the Agreement.

NOW, THEREFORE, in consideration of the mutual covenants contained herein and other good and valuable consideration, the receipt and sufficiency of which are acknowledged, the Parties agree as follows:

1. AMENDMENTS TO AGREEMENT

1.1 Amendment Scope. The Agreement is hereby amended only as explicitly set forth in this Addendum. Except as expressly amended herein, all terms, covenants, and conditions of the Agreement shall remain in full force and effect.

1.2 Licensed Modules. The licensed software is amended to include the following additional modules and components:

1.3 License Grant Modification. Section titled "License Grant" of the Agreement is amended to read in full as follows: Licensor grants to Licensee a Non-exclusive Exclusive license to use the Software solely for Licensee's internal business operations as further limited by the Agreement and this Addendum.

2. FEES AND PAYMENT

2.1 Additional Fees. In consideration for the amendments set forth in this Addendum, Licensee shall pay Licensor a one-time modification fee of and recurring fees as described below.

2.2 Payment Terms. All sums due under this Addendum shall be due within days of invoice. Late payments shall accrue interest at the lesser of 1.5% per month or the maximum rate permitted by law.

3. TERM; TERMINATION

3.1 Extended Term. The Term of the Agreement is extended through unless earlier terminated in accordance with the Agreement.

3.2 Termination for Material Breach. Either Party may terminate this Addendum upon written notice if the other Party materially breaches this Addendum and such breach remains uncured after thirty (30) days following written notice.

4. SUPPORT, MAINTENANCE AND DELIVERABLES

4.1 Support Services. Licensor shall provide support and maintenance for the added modules at the service level described here:

4.2 Delivery. Any deliverables described in this Addendum shall be delivered in accordance with the delivery schedule:

5. INTELLECTUAL PROPERTY

5.1 Ownership. Except for the limited license expressly granted herein, nothing in this Addendum transfers to Licensee any right, title, or interest in Licensor's intellectual property, including but not limited to source code, object code, documentation, and know-how.

5.2 Derivative Works. Any enhancements, modifications, or derivative works created by Licensor under this Addendum shall be owned exclusively by Licensor unless otherwise agreed in a written instrument signed by both Parties.

6. CONFIDENTIALITY

6.1 Confidential Information. Each Party shall treat as Confidential Information all non-public information disclosed by the other Party in connection with this Addendum and shall not disclose such information except as permitted by the Agreement.

7. REPRESENTATIONS, WARRANTIES AND DISCLAIMERS

7.1 Mutual Representations. Each Party represents and warrants that it has the full right, power, and authority to enter into this Addendum and to perform its obligations hereunder.

7.2 DISCLAIMER. EXCEPT AS EXPRESSLY SET FORTH IN THIS ADDENDUM OR THE AGREEMENT, LICENSOR DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

8. INDEMNIFICATION AND LIMITATION OF LIABILITY

8.1 Indemnification. Each Party agrees to indemnify, defend and hold harmless the other Party from and against any third-party claims arising out of the indemnifying Party's breach of this Addendum, negligence or willful misconduct, subject to the notice and mitigation obligations in the Agreement.

8.2 Limitation of Liability. Except for liability arising from breach of confidentiality, gross negligence, willful misconduct, or indemnification obligations, neither Party's aggregate liability for claims arising out of this Addendum shall exceed the aggregate fees actually paid by Licensee to Licensor under this Addendum in the twelve (12) months preceding the claim.

9. NOTICES

All notices under this Addendum shall be given in writing to the addresses set forth below and shall be effective in the manner provided in the Agreement.

10. MISCELLANEOUS

10.1 Governing Law. This Addendum shall be governed by and construed in accordance with the laws of the jurisdiction of without regard to its conflict of laws principles.

10.2 Entire Agreement. This Addendum and the Agreement constitute the entire agreement between the Parties with respect to the subject matter hereof and supersede all prior and contemporaneous agreements, whether written or oral, relating thereto.

10.3 Severability. If any provision of this Addendum is found to be invalid or unenforceable, the remaining provisions shall continue in full force and effect and the invalid provision shall be reformed to the minimum extent necessary to make it enforceable.

10.4 Amendments; Waiver. Any amendment to this Addendum must be in writing and signed by authorized representatives of both Parties. No waiver of any breach shall constitute a waiver of any other breach.

10.5 Counterparts and Electronic Signatures. This Addendum may be executed in counterparts, each of which shall be deemed an original. Signatures delivered by electronic means shall be binding and enforceable and shall have the same effect as original signatures.

LICENSOR

Printed Name:

By:

Date:

LICENSEE

Printed Name:

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What the Software License Addendum Is and When It Applies

A Software License Addendum is a supplemental agreement that modifies, clarifies, or extends terms of an existing software license or master services agreement. It typically narrows or expands scope, updates pricing or payment schedules, adjusts permitted use or deployment territories, and documents additional deliverables such as modules, integrations, or support levels. Addenda are used to record negotiated changes without redrafting the full license; they should reference the base agreement, state any superseding provisions, and include effective dates and signature blocks for all parties to ensure enforceability.

Why Use a Software License Addendum

An addendum preserves the original license framework while recording discrete changes, reducing ambiguity and avoiding wholesale contract reformation. It creates a clear, dated record of mutual amendments and protects IP, limits liability, and specifies payment adjustments.

Why Use a Software License Addendum

Who Typically Prepares or Signs an Addendum

The following roles commonly prepare, review, or approve software license addenda depending on organizational structure and transaction size.

  • Software vendors and product managers who need documented changes to license scope or pricing.
  • Corporate legal counsel and outside attorneys responsible for contract review and risk allocation.
  • Procurement, vendor management, and IT leaders who approve deployment terms and operational requirements.

Different signatories may be required for commercial versus government deals; confirm signatory authority and required approvals before circulation.

Essential Elements to Include in a Professional Addendum

A clear addendum uses focused sections to avoid conflict with the base license and to make intent and obligations explicit for both parties.

Reference Base Agreement

Identify the original agreement by title, effective date, and parties so the addendum clearly amends the correct contract and avoids ambiguity or competing documents.

Amendment Scope

Describe precisely which clauses, schedules, exhibits, or deliverables are changed, added, or removed, using section numbers where possible to prevent interpretive disputes.

Term and Effective Date

State the effective date of the amendment and whether the change is retroactive, temporary, or permanent; specify any interim reporting or transition obligations.

Payment and Fees

Spell out new fees, payment schedule, invoicing instructions, and any proration or refund mechanics tied to the amended scope or delivery milestones.

Intellectual Property

Clarify ownership of new code, integrations, customizations, and whether the license includes assignment, work-for-hire, or restricted-use provisions.

Termination and Remedies

Detail how the amendment affects termination rights, cure periods, audit rights, and remedies for breach specific to the new provisions.

Required Information and Fields at a Glance

Parties' Legal Names: Full registered entity names
Effective Date: MM/DD/YYYY format
Software Details: Product name and version
License Scope: Users, seats, territories
Compensation: Fees and payment terms
Signatory Authority: Name, title, capacity

Step-by-Step: How to Complete the Addendum

Follow these sequential steps to prepare, review, and execute the addendum efficiently while preserving the original license context.

  • 01
    Draft: Reference base agreement and insert specific amended clauses.
  • 02
    Review: Legal and product teams verify scope, fees, and IP language.
  • 03
    Approve: Obtain internal approvals and confirm authorized signers.
  • 04
    Execute: Circulate for signature and retain the signed copy in the contract repository.

How to Configure an Online Signing Workflow

Set clear workflow parameters to reduce back-and-forth and ensure legal and operational requirements are met during e-signature.

Field Configuration
Signature Order Sequential or parallel routing per negotiating parties
Authentication Email link, SMS code, or stronger KBA when required
Required Fields Make party names, dates, and amounts mandatory
Retention Automatic storage in secure repository with audit trail

Where to Send and How Signed Addenda Are Returned

Routing should reflect who must sign, who must retain a copy, and the final storage location for auditability.

  • Primary Signer: Send to the authorized representative who will sign first
  • Counterparty: Then route to the counterparty for signature and date
  • Legal Counsel: Optional copy to internal or external counsel for records
  • Contract Repository: Store executed PDF and audit trail in the contract system

Digital Signing and File Format Requirements

Choose a platform that produces tamper-evident PDFs, preserves an audit trail, and supports common integrations for storage and ERP systems.

  • File Formats: PDF or Word DOCX preferred for archival fidelity
  • Audit Trail: Must capture timestamp, IP, and signer attribution
  • Integrations: Connect to contract repository, ERP, or cloud storage

Ensure the chosen solution supports required authentication strength (email, SMS, or KBA) and exports signed documents in ISO-compatible PDF for long-term storage.

Key Timing Considerations and Deadlines

Be explicit about dates, milestone windows, and how late or missing signatures affect obligations and billing.

Effective Date:

Date when the amendment’s rights and duties begin

Signature Window:

Specify any deadline for all parties to sign

Billing Start:

When new fees or proration take effect

Notice Periods:

Times for termination, cure periods, or change notices

Delivery Milestones:

Deadlines for deliverables or integration acceptance

Common Mistakes to Avoid When Preparing an Addendum

  • Failing to reference the exact base agreement—creates ambiguity about which contract the addendum modifies and can invalidate the change.
  • Using vague scope language like 'as needed' without measurable metrics—leads to disputes about deliverables and fees.
  • Omitting signatory authority or title—signed by an unauthorized person can render the addendum unenforceable.
  • Neglecting to align effective dates and billing start dates—causes invoicing confusion and possible double-billing.

Penalties and Business Risks of an Incorrect Addendum

Enforceability Risk: Improperly executed
IP Exposure: Ambiguous ownership
Financial Loss: Unclear fees or missed billing
Regulatory Breach: HIPAA or sector rules
Operational Delay: Integration or deployment hold
Litigation Cost: Dispute resolution expenses

eSignature Vendor Comparison for Executing an Addendum

Compare typical price and capability dimensions when choosing an eSignature provider for executing and storing addenda; signNow appears first in the vendor column as required.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial Yes, 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Real-World Examples of Addendum Use

Practical examples show how addenda handle scope changes, new modules, or revised pricing without rewriting the primary license.

Optica Ventures (Brian Fitzgibbons)

When adding a new reporting module, Optica referenced the master license and attached a short addendum to document scope and fees.

  • The addendum specified module deliverables and a prorated fee for the remainder of the term.
  • The team reported quicker approvals and cleaner audit trails because the base agreement remained intact and only discrete terms were modified.

Fertility Centers of Illinois (John Butler)

A privacy-related addendum updated data hosting locations and controls to meet client requirements.

  • It included amended security obligations and an execution schedule.
  • The signed addendum provided clear operational steps for migrating data, preserved the original license structure, and ensured consistent obligations across multiple facilities.

Frequently Asked Questions About Software License Addenda

Answers to common legal and execution questions to help reduce risk and speed completion of addenda.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.