A field-tested LOI framework built for buying managed service providers and IT support businesses — covering MRR quality, key man protections, earnout structures, and SBA financing terms in the $1M–$5M revenue range.
An LOI (letter of intent) in an IT services or MSP acquisition is your first binding stake in the ground — and getting it right matters more than in most industries. Unlike a retail or manufacturing business, an MSP's value is almost entirely intangible: it lives in recurring contracts, client relationships, technical staff expertise, and vendor certifications. A poorly drafted LOI can lock you into a valuation that ignores one-time hardware revenue inflating EBITDA, fail to protect you if the owner-operator walks out the door post-signing, or leave you exposed to undisclosed cybersecurity liabilities. This guide walks through every section of a standard IT services LOI, with example language tailored to MSP deal structures, negotiation notes specific to the sector, and the most common mistakes buyers make before due diligence even begins. Whether you are an owner-operator acquiring your first MSP platform, an independent sponsor building a recurring-revenue roll-up, or a PE-backed platform completing a tuck-in, this template gives you a practical starting point for a defensible, deal-ready offer.
Find IT Services Businesses to AcquirePurchase Price and Valuation Methodology
Establishes the proposed total enterprise value and the methodology used to arrive at it, including how EBITDA was calculated and what revenue streams were included or excluded in the multiple applied.
Example Language
Buyer proposes to acquire 100% of the issued and outstanding equity interests of [Target MSP, LLC] for a total enterprise value of $[X], representing approximately [5.0x] trailing twelve-month adjusted EBITDA of $[X]. For purposes of this valuation, EBITDA has been calculated to include only monthly recurring revenue (MRR) from managed services contracts and exclude one-time hardware resale revenue, project-based implementation fees, and any non-recurring vendor rebates. Final purchase price is subject to adjustment based on findings during due diligence, including verification of MRR composition, customer churn rates, and any undisclosed cybersecurity liabilities.
💡 MSP sellers frequently present EBITDA that blends high-margin MRR with low-margin hardware resale and one-time project revenue. Insist on disaggregating revenue streams before agreeing to a multiple. A business with 80% MRR deserves a 5.5x–7x multiple; one with only 40% MRR and significant hardware revenue should be priced at 4x–5x. If the seller resists this breakdown, treat it as a red flag and consider making the purchase price explicitly contingent on MRR verification.
Deal Structure and Payment Terms
Outlines how the purchase price will be funded, including the allocation between cash at close, seller financing, SBA loan proceeds, and any equity rollover or earnout component.
Example Language
The proposed purchase price of $[X] shall be funded as follows: (a) approximately [80%] funded via SBA 7(a) loan proceeds; (b) approximately [10%] paid in cash equity by Buyer at closing; (c) approximately [10%] in the form of a seller note, subordinated to the SBA lender, bearing interest at [6%] per annum with a [24]-month term, subject to a standby period as required by the SBA lender. Buyer reserves the right to propose an earnout of up to $[X] tied to MRR retention and net new contract bookings during the [12]-month period following close, in lieu of or in addition to a portion of the seller note.
💡 SBA 7(a) financing is widely available for MSP acquisitions and reduces the buyer's cash-at-close requirement significantly. However, SBA lenders will require the seller note to be on full standby for 24 months, which sellers sometimes resist. Frame the seller note as validation of the seller's confidence in a smooth transition. For earnout structures, tie metrics exclusively to MRR retention — not gross revenue — to avoid disputes over one-time project spikes inflating earnout calculations artificially.
Monthly Recurring Revenue Representation
Requires the seller to formally represent the composition, contract status, and trailing churn rate of MRR as of the LOI signing date, creating a baseline for due diligence verification.
Example Language
Seller represents that as of [LOI Date], the business generates monthly recurring revenue (MRR) of not less than $[X], derived from [X] active managed services contracts with terms of no less than [12] months. Seller further represents that customer churn (measured by MRR lost to cancellations and downgrades) has not exceeded [5%] on an annualized basis over the trailing 24-month period. Buyer's obligation to proceed to closing is contingent upon verification of these representations during due diligence, including review of all underlying contracts, billing records, and PSA platform data.
💡 This is the single most important representation in an MSP LOI. Many sellers casually represent MRR without distinguishing between month-to-month agreements and multi-year contracts. Push for a contract-by-contract MRR schedule at the LOI stage — not just a top-line number. If the seller is reluctant to provide it pre-LOI, negotiate a 30-day due diligence window specifically for MRR verification before the exclusivity period fully activates.
Key Man and Seller Transition Obligations
Addresses the seller's role post-close, including the duration and structure of any transition support, employment or consulting agreement, and restrictions on the seller competing or soliciting clients after departure.
Example Language
As a condition of closing, Seller agrees to enter into a [24]-month transition services agreement or employment agreement with Buyer, commencing on the closing date, providing technical, client relationship, and operational support at a mutually agreed compensation rate. Seller shall not, during the term of such agreement and for a period of [3] years following termination, directly or indirectly compete with the business within [50] miles of its primary service area, or solicit any clients, employees, or vendors of the business for any competing IT services venture. The structure and compensation of Seller's post-close role shall be negotiated in good faith prior to the execution of definitive purchase agreements.
💡 Key man risk is the most acute post-close risk in MSP acquisitions. If the seller is the primary client relationship holder or the only senior technician, a 24-month transition period is a minimum, not a maximum. Consider structuring a portion of the earnout as a retention incentive for the seller to remain actively engaged during the transition. Non-competes in IT services are generally enforceable in most U.S. jurisdictions but must be reasonable in scope — a 50-mile radius and 3-year term is typically defensible.
Due Diligence Scope and Timeline
Defines the scope of buyer's due diligence investigation, the timeline for completion, and the seller's obligations to provide access to information, systems, and personnel.
Example Language
Buyer shall have [45] business days following execution of this LOI to complete due diligence, including but not limited to: (a) review of all managed services contracts, SLAs, and customer correspondence; (b) access to PSA platform (e.g., ConnectWise, Autotask) and RMM platform (e.g., Datto, NinjaRMM) for ticket history, device counts, and customer activity data; (c) trailing 24-month billing records and MRR churn analysis; (d) review of all cybersecurity policies, incident response logs, and any history of breaches or client notifications; (e) interviews with key technical staff and account managers, subject to Seller's reasonable discretion; and (f) review of all vendor, licensing, and partner agreements including Microsoft, Cisco, and other material technology vendors.
💡 Unlike most lower middle market industries, IT services due diligence requires access to operational platforms — not just financial records. Insist on direct access to the PSA and RMM tools, as these contain the ground truth on customer activity, ticket volume, and service delivery quality. A seller who refuses PSA access is often concealing customer churn or service quality issues. Also require a cybersecurity self-assessment or third-party penetration test report — undisclosed breaches or open vulnerabilities can create material post-close liability.
Exclusivity and No-Shop Period
Grants the buyer an exclusive negotiating period during which the seller agrees not to solicit, entertain, or accept offers from other potential acquirers.
Example Language
In consideration of Buyer's commitment to dedicate resources to due diligence and transaction costs, Seller agrees to an exclusive negotiating period of [60] days from the date of execution of this LOI (the 'Exclusivity Period'), during which Seller shall not, directly or indirectly, solicit, encourage, initiate, or participate in discussions or negotiations with any other party regarding the sale of the business or any material portion of its assets or equity. Buyer may request a [30]-day extension of the Exclusivity Period upon written notice if due diligence is materially incomplete due to delays in information delivery by Seller.
💡 60 days is a reasonable exclusivity window for an MSP acquisition, but only if the seller is responsive with document delivery. Build in an explicit extension right triggered by seller-caused delays — it is common for owner-operators to underestimate how long it takes to compile 3 years of financials, customer contracts, and vendor agreements. Do not agree to a fee payable if you walk away during exclusivity unless the seller is receiving multiple competing bids and demands it as a condition of exclusivity.
Conditions to Closing
Enumerates the material conditions that must be satisfied before the buyer is obligated to close the transaction, including financing, due diligence satisfaction, and key contract assignments.
Example Language
Buyer's obligation to consummate the transaction shall be subject to, among other conditions: (a) completion of due diligence to Buyer's reasonable satisfaction, including verification of MRR composition and customer concentration; (b) receipt of SBA 7(a) loan approval and commitment letter from Buyer's lender; (c) written consent or assignment of all material managed services contracts representing not less than [80%] of trailing MRR, to the extent such contracts require consent to assignment; (d) execution of employment or transition services agreement with Seller; (e) no material adverse change in the business, customer base, or key personnel between the LOI date and closing; and (f) evidence that all cybersecurity vulnerabilities identified during due diligence have been remediated or adequately disclosed.
💡 The contract assignment condition is critical in MSP deals. Many small MSPs use evergreen managed services agreements with auto-renewal provisions that technically require client consent to assign to a new owner. Request a customer contract audit early in due diligence to identify which contracts require affirmative consent. For large clients representing 10%+ of MRR individually, consider requiring written assignment consent as a hard closing condition rather than a best-efforts obligation.
Confidentiality and Non-Disclosure
Confirms that both parties are bound by confidentiality obligations regarding the transaction and any proprietary information exchanged during the LOI and due diligence process.
Example Language
Each party acknowledges that information exchanged in connection with this LOI and the contemplated transaction, including customer lists, contract terms, pricing structures, technology stack details, and financial information, constitutes confidential and proprietary information. Each party agrees to hold such information in strict confidence, use it solely for purposes of evaluating the contemplated transaction, and not disclose it to any third party without the prior written consent of the disclosing party, except to advisors, lenders, and counsel bound by equivalent confidentiality obligations. These confidentiality obligations shall survive termination of this LOI for a period of [3] years.
💡 In IT services, the customer list and pricing structure are crown jewels — a competitor with access to this data can directly poach accounts. If a mutual NDA was not executed prior to LOI, include robust confidentiality language here and specifically prohibit the buyer or its affiliates from directly soliciting the seller's clients or employees for [24] months if the deal does not close. This is especially important if the buyer is a competing MSP conducting a strategic acquisition.
MRR Definition and Verification Methodology
Buyers and sellers frequently disagree on what counts as monthly recurring revenue. Sellers may include auto-renewed month-to-month agreements, inconsistently billed project retainers, or hardware refresh contracts in their MRR figure. Negotiate a precise written definition of MRR — contracts with terms of 12 months or greater, billed at a fixed monthly rate, with documented renewal history — and require PSA platform export to verify it independently before finalizing valuation.
Earnout Structure Tied to MRR Retention
If a meaningful portion of the purchase price is deferred via earnout, fight to define the metric as net MRR retention rather than total revenue. MSP sellers may attempt to substitute lost recurring contracts with one-time project engagements during the earnout period to hit revenue targets artificially. A net MRR retention earnout protects the buyer by ensuring the underlying recurring contract base — which justifies the valuation multiple — is actually preserved post-close.
Seller Transition Period Length and Compensation
Sellers often want to exit within 90 days of close. Buyers acquiring MSPs with significant owner involvement in client relationships and technical delivery should push for 18–24 months of active transition support, not a nominal consulting arrangement. Negotiate the seller's post-close compensation as a fixed monthly amount tied to measurable transition milestones — client introductions completed, documentation delivered, staff trained — rather than a vague time-and-availability retainer.
Cybersecurity Indemnification and Escrow
Undisclosed cybersecurity incidents — including prior breaches, open vulnerabilities, or regulatory compliance gaps — represent a unique liability in MSP acquisitions because the MSP may owe contractual indemnification to its own clients for incidents affecting their environments. Negotiate a specific indemnification carve-out for pre-close cybersecurity incidents, backed by an escrow holdback of 10–15% of the purchase price for 18–24 months post-close, to fund any client claims that surface after the transaction.
Customer Concentration Adjustments to Purchase Price
If due diligence reveals that one or two clients represent 30% or more of total MRR, the purchase price should reflect the concentration risk explicitly. Negotiate a purchase price reduction mechanism — for example, a dollar-for-dollar reduction in enterprise value for any MRR from a single client exceeding 20% of total MRR — or require the seller to obtain a multi-year contract renewal from the concentrated client as a closing condition before the full purchase price is released.
Find IT Services Businesses to Acquire
Enough information to write a strong LOI on day one — free to join.
MSP and IT services businesses in the $1M–$5M revenue range typically trade at 4x–7x adjusted EBITDA, with the multiple heavily influenced by MRR quality. A business with 70%+ of revenue under multi-year managed services contracts, low customer concentration, and a capable team that does not depend on the owner can command 6x–7x. A business with 40% MRR, significant hardware revenue, and an owner-operator doing everything themselves is more realistically priced at 4x–5x. The LOI should explicitly state the multiple and the EBITDA base it was applied to, with MRR clearly disaggregated from project and hardware revenue.
Earnouts are common in MSP acquisitions, particularly when there is uncertainty about MRR retention post-close or when the seller's valuation expectation exceeds what current financials fully support. The key is to structure the earnout around net MRR retention — not gross revenue — so the metric directly tracks the health of the recurring contract base that justifies the purchase price multiple. Tie earnout payments to 12-month and 24-month MRR milestones, cap the total earnout at 10–20% of enterprise value, and include anti-manipulation provisions preventing the seller from substituting project revenue for lost managed services contracts during the earnout period.
Address it directly in the LOI by conditioning a portion of the purchase price on the seller executing a binding transition services or employment agreement with a minimum term of 18–24 months. The LOI should specify the general structure of this arrangement — compensation range, availability requirements, specific transition deliverables — so there are no surprises during definitive agreement negotiation. Consider tying 5–10% of the purchase price to the seller meeting defined transition milestones, such as completing client introductions, delivering documented SOPs, and training successor technical staff. This converts key man risk from a valuation discount into a structured incentive.
Yes, IT services and MSP acquisitions are generally SBA 7(a) eligible provided the business meets standard SBA size and financial requirements. The SBA program is well-suited to MSP acquisitions because recurring revenue provides the debt service coverage ratio lenders require. Typical structures involve 80% SBA financing, 10% buyer equity injection, and a 10% seller note on full standby. One important nuance: SBA lenders will scrutinize customer concentration heavily — a business where one client represents 40% of revenue may face lender resistance or require additional collateral. Address this in the LOI by noting that the purchase price is contingent on SBA lender approval, and begin lender conversations in parallel with LOI negotiation to avoid timeline surprises.
The LOI should include a seller representation that, to the seller's knowledge, the business has not experienced any material cybersecurity incidents, data breaches, or regulatory compliance violations affecting client environments in the trailing 36 months. It should also establish that the buyer's due diligence scope includes review of all security policies, incident response logs, endpoint protection configurations, and any client-facing indemnification obligations. Most importantly, negotiate an indemnification escrow holdback — typically 10–15% of the purchase price held for 18–24 months — specifically covering pre-close cybersecurity liabilities. MSPs are high-value ransomware targets and their contracts often include client indemnification provisions that can create significant post-close liability if a pre-close breach surfaces after the transaction closes.
More IT Services 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