A deal-tested LOI framework for buyers and sellers navigating recurring revenue, hardware obligations, and earnout structures in the $1M–$5M fleet telematics market.
An LOI in a fleet GPS and telematics acquisition does far more than establish price — it sets the ground rules for how recurring revenue will be verified, how hardware liabilities will be allocated, and whether an earnout will be tied to ARR retention or new customer growth. Because telematics businesses straddle hardware and SaaS economics, a generic LOI creates dangerous ambiguity. Buyers need specific language protecting them from hardware obsolescence risk, undisclosed churn, and customer concentration. Sellers need clarity on how their subscription revenue will be valued and what post-close obligations they're accepting. This guide walks through every major LOI section with example language and negotiation notes tailored specifically to fleet GPS, ELD compliance, and managed telematics platform transactions in the lower middle market.
Find Fleet GPS & Telematics Businesses to AcquireTransaction Overview and Purchase Price
Establishes the headline purchase price, valuation basis, and the split between cash at close, seller financing, and any earnout component. In telematics deals, price is almost always expressed as a multiple of ARR or adjusted EBITDA — and the definition of each must be nailed down here before due diligence begins.
Example Language
Buyer proposes to acquire 100% of the equity interests of [Target Company] ('Company') for a total purchase price of $[X], calculated as [5.0x] trailing twelve-month Adjusted EBITDA of $[X] / [4.5x] ARR of $[X]. The purchase price shall be structured as follows: (i) $[X] in cash at closing, (ii) $[X] in seller financing evidenced by a promissory note bearing interest at [6]% per annum with a [4]-year amortization schedule, and (iii) up to $[X] in earnout payments contingent on ARR retention as described herein. For purposes of this LOI, 'ARR' means annualized monthly recurring subscription and managed service revenue as of the last day of the most recently completed calendar month, excluding one-time hardware sales, installation revenue, and professional services fees.
💡 Sellers should push for the ARR definition to include managed service contracts and multi-year prepaid subscriptions. Buyers should insist on excluding month-to-month accounts with fewer than 6 months of continuous billing history from the ARR calculation to avoid overpaying for at-risk revenue. If the business blends hardware resale with subscription revenue, agreeing on a blended EBITDA multiple versus a pure ARR multiple is a common compromise — but get this resolved in the LOI, not at the purchase agreement stage.
Recurring Revenue Representation and Baseline
Defines the minimum recurring revenue threshold the business must maintain from signing through close, and establishes the customer cohort that will serve as the baseline for any earnout calculation. This section is uniquely important in telematics because churn can accelerate during a sale process as customers sense instability.
Example Language
Seller represents that as of [Date], the Company's monthly recurring revenue ('MRR') is no less than $[X], comprised of software subscription fees, managed telematics platform fees, and cellular data service pass-through revenue net of carrier costs. Seller agrees to provide Buyer with a monthly MRR dashboard within 10 business days of the end of each calendar month during the exclusivity period, showing new logos added, churned accounts, and net MRR movement. In the event that MRR declines by more than [8]% from the baseline figure prior to closing, Buyer reserves the right to renegotiate the purchase price or terminate this LOI without liability.
💡 Buyers should specify that the MRR report must be broken down by fleet vertical (e.g., trucking, construction, municipal) and contract type (month-to-month vs. annual vs. multi-year). This protects against a situation where a large stable government fleet contract masks deteriorating commercial trucking revenue. Sellers should negotiate the MRR decline threshold upward if the business has seasonal billing patterns — for example, construction fleet customers often pause service in winter months.
Due Diligence Period and Access
Specifies the length of the due diligence period, what information will be made available, and which advisors will have access. In telematics transactions, due diligence must include a technical review of the platform stack and a hardware inventory audit — both of which take longer than financial review alone.
Example Language
Buyer shall have [60] days from the date of this LOI ('Due Diligence Period') to complete financial, legal, technical, and commercial due diligence. Seller shall provide access to: (i) three years of financial statements including revenue disaggregated by hardware, subscription, and professional services; (ii) all customer contracts, renewal terms, and churn records by cohort; (iii) hardware vendor agreements, cellular carrier contracts, and any white-label platform provider agreements; (iv) documentation of ELD mandate compliance status for all applicable customers; (v) source code repository access and IP ownership documentation for any proprietary platform components; and (vi) a complete hardware inventory with device model, firmware version, cellular generation (4G/5G), and estimated remaining useful life. Seller shall designate a single point of contact to coordinate due diligence requests within 48 hours of receipt.
💡 Buyers should budget for a third-party technical due diligence firm to review the platform architecture, assess 5G readiness of installed hardware, and evaluate open-source license exposure. This typically costs $8,000–$20,000 but is essential for any telematics business running a proprietary platform. Sellers should resist providing source code access until an NDA and IP protection agreement are in place, and should clarify upfront whether white-label platform agreements are assignable without vendor consent — a deal-killer discovered late.
Exclusivity
Grants the buyer an exclusive negotiating window during which the seller cannot solicit or entertain competing offers. Standard in lower middle market deals, but the length and scope should reflect the complexity of telematics due diligence.
Example Language
In consideration of Buyer's commitment of time and resources to due diligence, Seller agrees to negotiate exclusively with Buyer for a period of [75] days from the date of this LOI ('Exclusivity Period'). During the Exclusivity Period, Seller shall not, directly or indirectly, solicit, encourage, or enter into discussions with any third party regarding the sale of the Company or its material assets. If Buyer has not delivered a definitive purchase agreement within the Exclusivity Period, the parties may mutually agree to a [15]-day extension upon written notice.
💡 75 days is appropriate for telematics deals requiring hardware audits and platform technical review. Sellers with multiple interested buyers should resist exclusivity periods exceeding 60 days without a meaningful deposit or break-up fee — typically $25,000–$75,000 in lower middle market deals. Buyers using SBA financing should note that lender processing timelines often push deal closings beyond 90 days from LOI, so build in extension provisions.
Earnout Structure
Details the contingent payment tied to post-close performance, including the metric, measurement period, payment schedule, and buyer obligations to support the earnout target. Earnouts in telematics deals are almost always tied to ARR retention or new customer acquisition — not EBITDA, which is too easily manipulated post-close.
Example Language
Buyer agrees to pay Seller up to $[X] in contingent earnout payments structured as follows: (i) $[X] if the Company's ARR on the 12-month anniversary of closing equals or exceeds [95]% of the Closing Date ARR Baseline; and (ii) an additional $[X] if ARR on the 24-month anniversary of closing equals or exceeds [105]% of the Closing Date ARR Baseline, reflecting net new customer growth. For purposes of earnout calculation, Buyer agrees not to intentionally restructure customer contracts, accelerate churn, or merge Company customer accounts into Buyer's existing platform in a manner that would artificially reduce the Company's standalone ARR measurement without Seller's written consent. Earnout payments, if earned, shall be paid within 30 days of the applicable measurement date.
💡 Sellers should insist on language requiring the buyer to maintain the telematics platform as a standalone product offering for at least 12 months post-close — platform sunsetting is the most common way earnouts are gamed in roll-up acquisitions. Buyers should cap total earnout exposure at 20–25% of total deal value and tie measurements to independently verifiable ARR reports rather than internally produced figures. If the seller is staying on as a transition consultant, define clearly whether their post-close sales activity counts toward the new logo targets.
Customer Concentration Carve-Out
Identifies specific large-fleet customers that represent meaningful concentration risk and establishes what happens to the purchase price if those customers do not renew or transfer their contracts post-close.
Example Language
The parties acknowledge that the following customers ('Key Accounts') represent more than [10]% of the Company's total ARR individually: [Customer A] ([X]% of ARR), [Customer B] ([X]% of ARR). Seller represents that each Key Account has an active written contract with a remaining term of no less than [12] months from the projected closing date and has not provided written or verbal notice of non-renewal. In the event that any Key Account representing more than [10]% of ARR provides notice of non-renewal or terminates service prior to closing, Buyer may elect to reduce the purchase price by [1.5x] the annualized revenue attributable to such Key Account or terminate this LOI without liability.
💡 Buyers should request copies of Key Account contracts as a condition of signing the LOI, not as a due diligence deliverable — customer concentration is a go/no-go issue, not a price adjustment issue discovered at close. Sellers should push back on price reduction multipliers above 4x for individual account departures, as the 1.5x–3x range is more typical in telematics deals where replacement revenue through new fleet onboarding is achievable within 6–12 months.
Hardware Obligations and Inventory
Allocates responsibility for existing hardware inventory, device upgrade obligations related to 5G transitions, and any lease or financing arrangements on installed hardware at customer sites.
Example Language
Seller shall provide Buyer with a complete hardware inventory schedule ('Hardware Schedule') no later than [15] days after LOI execution, identifying all customer-installed devices by make, model, cellular generation, and ownership status (company-owned, customer-owned, or subject to financing arrangement). Seller represents that no more than [X]% of installed devices are operating on 3G or legacy CDMA networks scheduled for carrier decommission within [24] months of closing. Any device upgrade obligations arising from carrier network sunsets prior to closing shall be Seller's responsibility. Post-closing hardware upgrade obligations shall be assumed by Buyer as disclosed in the Hardware Schedule. Buyer shall have the right to reduce the purchase price by the estimated net cost of any undisclosed pre-closing upgrade obligations discovered during due diligence.
💡 The 4G-to-5G transition is the single most financially material hardware issue in telematics acquisitions right now. Buyers should engage a network engineer or telematics hardware specialist to audit the installed device fleet during due diligence and model replacement costs. Sellers who have already completed a 5G upgrade cycle have a significant valuation advantage and should document this prominently. If the business resells hardware on thin margins, clarify whether post-close device upgrade projects will be sold at cost-plus or included in subscription pricing — this affects EBITDA materially.
Seller Transition and Non-Compete
Defines the seller's post-close transition obligations, consulting period, and geographic and temporal scope of the non-compete agreement. In founder-operated telematics businesses, customer relationships are often personal — this section protects the buyer's investment while keeping the seller engaged through handoff.
Example Language
Seller agrees to provide transition assistance for a period of [12] months post-closing, initially full-time for the first [90] days and thereafter available for up to [10] hours per week for the remainder of the transition period, at a consulting rate of $[X] per month. Seller further agrees that for a period of [3] years following the closing date, Seller shall not, directly or indirectly, own, operate, consult for, or be employed by any business providing fleet GPS tracking, telematics software, ELD compliance solutions, or managed fleet technology services to commercial fleets operating within [Seller's primary service geography] or to any customer of the Company at the time of closing. Seller's transition consulting compensation shall be structured as $[X] per month for 12 months, included within the deal economics and not treated as additional purchase price.
💡 Buyers should ensure the non-compete covers not just direct telematics services but also fleet management software and ELD compliance consulting — sellers with deep carrier relationships can effectively compete by feeding leads to competitors even without a direct service offering. Sellers should negotiate geographic limits that reflect their actual market footprint rather than national scope, particularly for regional resellers serving specific metro areas or states. A 3-year non-compete is standard; 5 years is aggressive and may face enforceability challenges in certain states.
Conditions to Closing
Lists the conditions that must be satisfied before either party is obligated to consummate the transaction, including financing contingencies, regulatory approvals, and third-party consents required to assign key contracts.
Example Language
The obligations of Buyer to consummate the transactions contemplated herein are conditioned upon: (i) Buyer's receipt of SBA 7(a) loan commitment or alternative senior financing on terms acceptable to Buyer in its reasonable discretion; (ii) assignment or reissuance of all customer contracts and hardware vendor agreements without material adverse modification; (iii) written consent from [White-Label Platform Provider] to assign the platform license agreement to Buyer, or alternatively Buyer's determination that the platform is replaceable within [12] months post-close; (iv) no material adverse change in the Company's MRR, customer base, or key employee roster prior to closing; and (v) satisfactory completion of Buyer's due diligence in all material respects. Seller's obligation to close is conditioned upon receipt of the cash portion of the purchase price and execution of the seller financing note and transition consulting agreement.
💡 The white-label platform consent condition is frequently overlooked and can kill telematics deals at the last minute. Buyers must identify platform provider consent requirements early — some agreements have anti-assignment clauses or require the licensor's approval before transfer. Sellers should proactively contact platform providers before LOI signing to understand consent requirements and timelines. SBA financing contingencies are reasonable and expected, but sellers should negotiate a drop-dead closing date of 120 days to avoid indefinite limbo.
ARR Definition and Exclusions
The definition of Annual Recurring Revenue is the single most contested term in telematics LOIs. Buyers want to exclude month-to-month accounts, hardware pass-through revenue, and any customer on a notice-of-cancellation period. Sellers want to include managed service contracts, cellular data revenue, and multi-year prepaid accounts. Agree on the exact formula in the LOI — not during purchase agreement negotiations.
Hardware Liability Allocation
Determine clearly whether pre-close device upgrade obligations (particularly 5G transitions), inventory write-downs, and customer-installed hardware under financing arrangements are Seller liabilities or post-close Buyer responsibilities. This is often worth hundreds of thousands of dollars in a fleet with aging 4G devices across thousands of vehicles.
Earnout Metric and Anti-Gaming Protections
Tie earnout to ARR or MRR retention rather than EBITDA, and include explicit language preventing the buyer from sunsetting the platform, migrating customer accounts to a competing product, or restructuring pricing in ways that artificially suppress the Company's standalone revenue measurement during the earnout window.
Key Account Contract Transfer Mechanics
For the top 3–5 fleet customers by revenue, negotiate whether their contracts must be formally novated to the new entity or whether an assignment with customer notification is sufficient. Some government fleet contracts and large enterprise agreements require customer consent to assignment — failure to secure this pre-close can trigger immediate termination rights.
Working Capital Peg and Hardware Inventory Treatment
Establish a normalized working capital target that excludes hardware inventory from the working capital peg, or alternatively agree on a separate inventory purchase price. Telematics businesses often carry $200K–$1M+ in hardware inventory that buyers and sellers treat very differently — buyers want to haircut aging models, sellers want full cost recovery.
Non-Solicitation of Employees
Beyond the standard non-compete, negotiate a mutual non-solicitation provision protecting both parties from poaching the Company's support, NOC, and account management team during and after the transition period. Field technicians and fleet account managers are the relationship glue in regional telematics businesses — losing them post-close directly impacts churn.
Seller Financing Subordination Terms
If seller financing is part of the deal structure (common in SBA-financed telematics acquisitions), nail down the subordination agreement terms in the LOI. SBA lenders require seller notes to be fully subordinated during the loan term — sellers should understand that this means no payments on their note if the business breaches SBA covenants, which can last 10 years.
Find Fleet GPS & Telematics Businesses to Acquire
Enough information to write a strong LOI on day one — free to join.
Fleet telematics businesses in the $1M–$5M revenue range typically trade at 3.5x–6x trailing EBITDA or 3x–5x ARR, depending on recurring revenue quality, customer retention, and platform proprietary-ness. Businesses with 80%+ recurring revenue, multi-year contracts, sub-10% annual churn, and a proprietary platform with ELD or vertical-specific integrations command the high end of the range. Hardware-heavy resellers with month-to-month billing and a single OEM dependency trade closer to 3x–4x EBITDA. The fastest way to understand where your business falls is to build a clean MRR dashboard and let the recurring revenue story do the valuation work.
Earnouts are very common in telematics acquisitions, typically representing 15–25% of total deal value. They should always be tied to ARR or MRR retention — not EBITDA. Post-close integration costs, platform migration expenses, and shared overhead allocations from the acquiring company make EBITDA earnouts nearly impossible for sellers to achieve. An ARR-based earnout with explicit anti-gaming protections (preventing the buyer from sunsetting the platform or migrating customer accounts during the earnout window) is the seller-friendly standard. Measurement should be based on independently verifiable billing records, with payments due within 30 days of each anniversary date.
This is one of the most common closing-stage crises in telematics deals. Many enterprise fleet contracts and virtually all government fleet agreements require the customer's written consent for assignment. If a Key Account representing more than 10% of ARR won't consent, most buyers will either reduce the purchase price by 1.5x–3x the annualized revenue value of that account or exercise a termination right if the account is large enough to materially change deal economics. The best practice is to identify all contracts with assignment restriction clauses during the first two weeks of due diligence and initiate customer consent conversations early — not at closing.
The cellular network transition is a material valuation and liability issue that must be addressed directly in the LOI. Buyers should require a complete hardware inventory schedule showing device model, cellular generation, and estimated remaining useful life as a condition of the due diligence period — not as a post-signing deliverable. Any devices on 3G or legacy CDMA networks already decommissioned by carriers should be treated as a pre-close seller liability. The cost to upgrade a mixed 4G/5G fleet across thousands of installed devices can reach $300K–$1M+ for mid-sized telematics businesses, which directly affects purchase price. Sellers who have already completed their 5G transition should document this prominently in their CIM as a valuation premium driver.
Yes — fleet GPS and telematics businesses are generally SBA 7(a) eligible, and most lower middle market deals in this sector use some form of SBA financing given the strong recurring revenue profiles. Lenders look favorably on telematics businesses with 80%+ recurring revenue, multi-year customer contracts, and EBITDA margins above 20%. The main SBA-specific issues to address in the LOI are: (i) seller financing must be fully subordinated to the SBA note, typically meaning no payments to the seller during the loan term if covenants are breached; (ii) lenders may require third-party appraisals of proprietary software and hardware inventory; and (iii) if the seller is retaining any equity stake post-close, SBA rules limit this to no more than 20% under specific conditions. Budget 90–120 days from LOI signing to closing when SBA financing is involved.
Post-LOI price renegotiation — sometimes called 'price chipping' — is unfortunately common in telematics acquisitions when buyers discover hardware obsolescence issues or churn data they claim wasn't fully disclosed. Sellers have the strongest protection when the LOI is specific about what representations have already been made (current MRR, Key Account contract status, hardware generation breakdown) and includes a clear materiality threshold for price adjustments. If a buyer attempts to renegotiate based on issues that were disclosed in the LOI or early due diligence materials, sellers can credibly push back by pointing to the specific LOI language. If chipping is persistent and not tied to a genuine discovery, sellers should consider re-engaging backup buyers — which is why maintaining backup interest until LOI exclusivity is firmly in place is strategically important.
More Fleet GPS & Telematics Guides
More LOI Templates
Get enough diligence data to write a confident LOI from day one.
Create your free accountNo credit card required
For Buyers
For Sellers