Contract analysis

I. Executive Summary Calderwood & Harkness LLP ("C&H") has been engaged by Vantage Mobility Systems Corp. ("VMS" or "Vantage") to review and advise on the draft Master Embedded Software License and Services Agreement (the "MESLSA" or the "Agreement") proposed to be entered into between VMS, as licensee, and Meridian Code Technologies, Inc. ("MeridianCode" or "MCT"), as licensor. The draft MESLSA carries a proposed ef

II. Background A. The Parties Vantage Mobility Systems Corp. ("VMS"). VMS is a corporation organized under the laws of the State of Delaware, with its principal offices located at 4100 Industrial Parkway, Sterling Heights, Michigan 48312. VMS specializes in the design, manufacture, and distribution of adaptive mobility vehicles, including wheelchair-accessible vans and modified commercial fleet vehicles. For the fisc

III. Summary of Key Commercial Terms This section provides a high-level summary of the principal commercial terms of the draft MESLSA for reference. A comprehensive term sheet or deal-point summary will be provided separately if requested. A. Licensed Product and Scope The licensed product under the MESLSA is the ATLAS-RT™ embedded real-time operating system, Version 4.2, together with all subsequent minor updates (i

IV. Analysis of Key Risk Provisions This section provides our detailed analysis of the five provisions of the draft MESLSA that we have identified as presenting elevated risk to VMS. For each provision, we set forth a summary of the contractual language, an assessment of the risks presented, and our recommended negotiation position. A. Section 4.3 — "Use-It-or-Lose-It" Clause

Section 4.3 of the draft MESLSA imposes a requirement that VMS commence integration testing on at least two (2) of the five (5) designated vehicle platform configurations within eighteen (18) months of the Effective Date. Based on the proposed Effective Date of June 21, 2022, this requirement would need to be satisfied by December 21, 2023. The provision is structured as a condition subsequent to the continuation of

2. Risk Assessment We have identified several significant risk factors associated with Section 4.3 as currently drafted. Aggressive Timeline. The 18-month deadline is aggressive in the context of an enterprise-scale embedded RTOS integration program spanning five distinct vehicle platform configurations. Automotive embedded software development cycles are notoriously subject to delay, particularly in programs of this

3. Recommended Negotiation Position We recommend VMS pursue the following negotiation objectives with respect to Section 4.3: Broaden the Definition of "Commence Integration Testing." VMS should negotiate for a clearer and broader definition of the triggering activity. We recommend proposing language specifying that VMS shall be deemed to have "commenced integration testing" upon the earlier of: (a) commencement of f

Section 9.1 of the draft MESLSA provides that either party may terminate the Agreement for convenience upon 180 days' prior written notice to the other party. This mutual termination-for-convenience right is, in isolation, a standard provision in enterprise software licensing agreements. However, Section 9.1 includes a significant qualification: if the licensee (VMS) terminates the Agreement for convenience prior to

Section 9.1 represents the most significant financial risk provision in the draft MESLSA. The consequences of this provision merit careful consideration. Magnitude of Exposure. As of the signing date, VMS will have paid the $8,000,000 upfront license fee. This amount would be immediately at risk of forfeiture if VMS were to terminate for convenience at any point during the first 24 months. Within approximately 24 day

3. Recommended Negotiation Position We recommend VMS pursue the following negotiation objectives with respect to Section 9.1: Proportional Fee Recovery. The primary objective should be to replace the all-or-nothing forfeiture mechanism with a proportional recovery structure. Under this approach, the amount of prepaid fees subject to forfeiture would decrease ratably over the 24-month period. For example, if VMS termi

Section 7.2 of the draft MESLSA addresses the ownership and licensing of derivative works created during the course of the ATLAS-RT integration. As currently drafted, the provision establishes the following framework: (a) Any modifications, adaptations, or extensions to the ATLAS-RT source code created by VMS engineers during the integration process become jointly owned by VMS and MeridianCode. (b) MeridianCode retai

Section 7.2 is, in our assessment, a highly disadvantageous provision for VMS and warrants aggressive negotiation. Our concerns are as follows. Substantial VMS Investment at Risk. VMS's engineering team, under the direction of Lena Petrova (Director, Software Integration Engineering), will invest thousands of person-hours and substantial intellectual capital in creating derivative works during the ATLAS-RT integratio

3. Recommended Negotiation Position We recommend VMS pursue the following negotiation objectives with respect to Section 7.2, in order of priority: Primary Position: Sole VMS Ownership. VMS's preferred position should be that VMS retains sole ownership of all code created by VMS engineers during the integration process. Under this structure, VMS would grant MeridianCode a limited, non-exclusive license to use VMS-cre

Section 9.4 of the draft MESLSA establishes a "dormancy" mechanism addressing situations where VMS suspends active integration work. The key elements of the provision are as follows: (a) If VMS suspends active integration activities for more than 120 consecutive days without providing prior written notice to MeridianCode, MeridianCode may elect to convert the license to "Dormancy Status." (b) During Dormancy Status,

2. Risk Assessment The dormancy provisions of Section 9.4 present several risks and ambiguities that warrant careful attention. Short Trigger Period. The 120-day consecutive suspension trigger is relatively short in the context of an enterprise-scale automotive software integration program. Integration projects of this nature routinely experience periods of reduced activity or suspension lasting 120 days or more due

3. Recommended Negotiation Position We recommend VMS pursue the following negotiation objectives with respect to Section 9.4: Extended Trigger Period. VMS should negotiate an extension of the dormancy trigger from 120 days to 180 days. This aligns the dormancy trigger with the 180-day notice period for termination for convenience under Section 9.1, creating internal consistency within the Agreement. A 180-day thresho

Section 12.6 of the draft MESLSA provides that the assignment of the Agreement in connection with a change of control of VMS requires MeridianCode's prior written consent, such consent not to be unreasonably withheld. The provision does not define "change of control," though we expect this term to be defined elsewhere in the Agreement (likely in the definitions section or an exhibit). We will confirm the precise defi

2. Risk Assessment The change-of-control consent requirement is significant for VMS given its ownership structure and the probability of a future exit transaction during the MESLSA term. PE Sponsor Exit. VMS is a portfolio company of Kestrel Capital Partners, which acquired VMS in 2019 for approximately $380 million. Private equity sponsors typically target hold periods of three to seven years, with exit strategies i

3. Recommended Negotiation Position We recommend VMS pursue the following negotiation objectives with respect to Section 12.6: Notice-Only Obligation. VMS's primary position should be to eliminate the consent requirement entirely and replace it with a simple notice obligation. Under this approach, VMS would be required to notify MeridianCode of any change-of-control transaction within a specified period (e.g., 30 day

V. Additional Observations In addition to the five priority risk provisions analyzed above, we offer the following additional observations for VMS's consideration. A. Dispute Resolution — MAI Arbitration The binding arbitration clause, providing for arbitration under the rules of the Midwest Arbitration Institute seated in Detroit, Michigan, with a three-arbitrator panel for disputes exceeding $1,000,000 in controver