A practical LOI framework built for MSP and IT support acquisitions — covering MRR protections, staff retention clauses, cybersecurity liability carve-outs, and earnout structures that reflect how these deals actually close.
A Letter of Intent (LOI) in an IT helpdesk or managed services acquisition is more than a formality — it is the document that locks in your negotiating position before expensive due diligence begins. For MSP acquisitions in the $1M–$5M revenue range, the LOI must address issues unique to this industry: the split between monthly recurring revenue and break-fix billing, the risk of key technicians walking after announcement, inherited cybersecurity liability from client environments, and the condition of the PSA and RMM technology stack. Buyers using SBA 7(a) financing will also need the LOI to reflect deal structures acceptable to their lender, including seller equity rollover and transition consulting agreements. This guide walks through each section of a well-drafted MSP LOI, provides example language, and flags the negotiation points that most often derail IT support deals at the letter-of-intent stage.
Find IT Helpdesk & Support Businesses to AcquireParties and Transaction Overview
Identifies the buyer entity, seller entity, and the general structure of the proposed transaction — asset purchase or stock purchase — along with the target business name, primary service location, and a brief description of the business being acquired.
Example Language
This Letter of Intent is submitted by [Buyer Entity Name], a [State] [LLC/Corporation] ('Buyer'), to [Seller Entity Name] ('Seller'), the owner and operator of [Business Trade Name] ('Company'), a managed IT services and helpdesk provider located in [City, State]. Buyer proposes to acquire substantially all of the assets of the Company, including all managed service agreements, PSA and RMM system data, customer contracts, equipment, intellectual property, trade names, and goodwill, through an asset purchase transaction structured as described herein.
💡 Most MSP acquisitions under $5M are structured as asset purchases to allow the buyer to step up asset basis and avoid assuming unknown liabilities, including pre-closing cybersecurity incidents. Sellers often prefer stock sales for tax efficiency. Clarify structure early — misalignment here can collapse deals at LOI. If SBA financing is involved, confirm with your lender that the proposed structure is eligible before submitting the LOI.
Purchase Price and Valuation Basis
States the proposed total enterprise value, the methodology used to arrive at that number, and how it relates to the business's EBITDA or recurring revenue metrics. IT helpdesk businesses in this market typically trade at 3.5x–6x EBITDA depending on MRR percentage, contract quality, and staff depth.
Example Language
Buyer proposes a total purchase price of $[X,XXX,000] ('Purchase Price'), representing approximately [4.5x] trailing twelve-month adjusted EBITDA of $[XXX,000] as reported in the Company's most recent financial statements. This valuation is based on Buyer's preliminary review of the Company's revenue mix, which Seller has represented to be approximately [65%] monthly recurring managed services revenue and [35%] project and break-fix revenue. The Purchase Price is subject to adjustment following completion of financial and operational due diligence as described herein.
💡 Sellers with strong MRR concentration (60%+) should push for multiples at the higher end of the 3.5x–6x range. Buyers should tie the stated multiple explicitly to the MRR percentage — if due diligence reveals that recurring revenue is lower than represented, the purchase price adjustment mechanism should flow automatically from this section. Avoid agreeing to a flat dollar price without an EBITDA adjustment clause.
Deal Structure and Payment Terms
Describes how the purchase price will be funded, including the allocation between cash at close, SBA loan proceeds, seller financing, and any earnout component tied to post-close performance metrics.
Example Language
The Purchase Price shall be funded as follows: (i) approximately [75%] in cash at closing sourced from an SBA 7(a) loan obtained by Buyer; (ii) a seller note of [10–15%] of the Purchase Price bearing interest at [6%] per annum, payable over [36] months following close, subordinated to the SBA lender as required; and (iii) an earnout of up to [15%] of the Purchase Price payable over [18] months post-close, contingent on the retention of monthly recurring revenue at no less than [90%] of the MRR recognized in the trailing three months prior to closing. The earnout shall be calculated and paid quarterly with supporting MRR reports from the Company's PSA billing system.
💡 MRR retention earnouts are standard in MSP deals and protect buyers from contract churn post-close, but sellers should negotiate a clear definition of what constitutes 'MRR' for earnout purposes — ensure project revenue and one-time fees are explicitly excluded from the calculation to avoid disputes. Sellers should also negotiate a cap on their liability if a client churns for reasons unrelated to the transition, such as the client being acquired or going out of business.
Transition and Consulting Agreement
Outlines the seller's expected involvement after closing, including duration, compensation, scope of responsibilities, and any restrictions on competing activity. Critical in MSP deals where the owner holds key client relationships.
Example Language
Seller agrees to provide transition consulting services to Buyer for a period of [12] months following the closing date ('Transition Period') at a rate of $[X,000] per month. During the Transition Period, Seller shall (i) introduce Buyer's designated team members to all managed service clients; (ii) assist in transferring client environment documentation from Seller's current platforms to Buyer's systems; (iii) support staff onboarding and knowledge transfer for all active managed service agreements; and (iv) be available for no less than [20] hours per week for client-facing and internal transition activities. Seller shall not engage in any competing managed IT services or helpdesk business within [50] miles of the Company's primary service area for a period of [3] years following closing.
💡 Sellers should push to limit the consulting obligation to client introduction and knowledge transfer — avoid language that keeps them accountable for sales targets or new client acquisition post-close, as that creates earnout exposure. Buyers should ensure the non-compete radius reflects the actual geographic service area of the MSP's client base, particularly if the seller's clients span multiple metro areas.
Due Diligence Period and Access
Defines the length of the due diligence period, the categories of information Buyer will require, and the cooperation expected from Seller in providing access to systems, staff, contracts, and financial records.
Example Language
Following execution of this LOI, Buyer shall have [60] days ('Due Diligence Period') to conduct a thorough review of the Company's business, including but not limited to: (i) three years of accrual-based financial statements and monthly MRR reconciliation reports from the Company's PSA billing system; (ii) all managed service agreements, including pricing, term, SLA obligations, and renewal provisions; (iii) a complete list of active clients with associated MRR, contract end dates, and termination-for-convenience clauses; (iv) all employee files, offer letters, non-solicitation agreements, and technical certifications; (v) an audit of the Company's PSA, RMM, and documentation platforms for data completeness and system hygiene; and (vi) the Company's cyber liability insurance policy and a summary of any cybersecurity incidents or client data breach events in the prior 36 months.
💡 Sixty days is appropriate for MSP acquisitions given the complexity of PSA and contract reviews. Request access to the live PSA system — reviewing exported spreadsheets is insufficient to assess MRR quality, ticket volume trends, and client activity levels. Flag any managed service agreements with termination-for-convenience clauses early; these represent the highest churn risk post-close and should inform your earnout structure.
Exclusivity and No-Shop Period
Prevents the seller from soliciting or entertaining competing offers during the due diligence period in exchange for the buyer's commitment of time and resources to the acquisition process.
Example Language
In consideration of Buyer's investment of time, resources, and professional fees in conducting due diligence, Seller agrees that for a period of [60] days following execution of this LOI ('Exclusivity Period'), Seller shall not, directly or indirectly, solicit, entertain, negotiate, or accept any offer from any third party for the sale, merger, recapitalization, or other disposition of the Company or its assets. Seller shall promptly notify Buyer in writing if any unsolicited offer is received during the Exclusivity Period.
💡 Sellers should resist exclusivity periods longer than 60 days unless the buyer provides a meaningful deposit held in escrow. If the buyer is seeking SBA financing, the SBA process itself may require 90–120 days — negotiate a conditional extension provision tied to documented SBA lender progress rather than an automatic long exclusivity window.
Employee and Staff Retention Provisions
Addresses the buyer's intentions regarding current technical staff, including key technicians, account managers, and service coordinators, and establishes any pre-close commitments around employment offers or retention incentives.
Example Language
Buyer intends to offer employment to all current full-time technical staff employed by the Company as of the closing date, subject to satisfactory completion of background checks and execution of Buyer's standard employment agreements including non-solicitation provisions. Buyer further agrees that compensation and benefits for retained employees shall be no less favorable than those in effect at closing for a period of [12] months post-close. Seller agrees not to solicit, encourage, or facilitate the departure of any technical staff during the Due Diligence Period or the 90-day period following closing.
💡 Key technician retention is one of the highest-risk elements of any MSP acquisition. Identify your top two or three technicians during due diligence and consider separate retention bonus agreements tied to 12-month post-close tenure. These costs should be factored into your acquisition model, not treated as surprises. Sellers should negotiate that any employee departure initiated by the buyer does not trigger earnout penalties.
Cybersecurity Liability and Representations
Establishes seller representations regarding cybersecurity incidents, insurance coverage, and the condition of client environments, and allocates risk for pre-closing incidents that may surface post-acquisition.
Example Language
Seller represents and warrants that, to Seller's knowledge: (i) neither the Company nor any client environment managed by the Company has experienced a material cybersecurity incident, data breach, or ransomware event in the 36 months prior to the closing date that has not been fully disclosed to Buyer; (ii) the Company maintains current cyber liability insurance coverage of no less than $[1,000,000] per occurrence; and (iii) all managed service clients are subject to written agreements containing limitation of liability and indemnification provisions in favor of the Company. Seller shall indemnify and hold Buyer harmless from any claims, losses, or regulatory actions arising from cybersecurity incidents occurring prior to the closing date for a period of [24] months post-close, subject to a cap of [15%] of the Purchase Price.
💡 This is the most frequently under-negotiated section in MSP LOIs. Buyers must request a full cybersecurity disclosure schedule during due diligence, including any insurance claims filed, client complaints related to security incidents, and the current patching and monitoring posture of the MSP's own environment. Sellers with clean histories should welcome this representation — sellers who resist it warrant additional scrutiny.
Conditions to Closing
Lists the key conditions that must be satisfied before the transaction can close, including financing contingencies, third-party consents for managed service agreement assignments, landlord consents if applicable, and regulatory approvals.
Example Language
The closing of the transaction contemplated herein is conditioned upon: (i) Buyer obtaining SBA 7(a) financing on terms acceptable to Buyer in its reasonable discretion; (ii) the assignment or novation of all material managed service agreements to Buyer, with written consent from clients representing no less than [85%] of total MRR as of the closing date; (iii) the continued employment of [identified key technicians] through the closing date; (iv) no material adverse change in the Company's MRR, client base, or financial condition between the LOI execution date and closing; and (v) execution of final definitive purchase agreements acceptable to both parties.
💡 The MSA assignment condition is critical and often underestimated. Many managed service agreements contain anti-assignment clauses requiring client consent to transfer. Map all contracts against this requirement during due diligence and begin informal client relationship outreach early — do not wait until a week before closing to discover a major client will not consent to assignment.
MRR Definition and Baseline Measurement
Precisely define what counts as monthly recurring revenue for both valuation and earnout purposes. Exclude project revenue, one-time onboarding fees, hardware sales, and any non-contracted recurring billing. The MRR baseline used for the earnout should be measured over three full months immediately prior to closing using the Company's PSA billing data, not a seller-provided summary spreadsheet.
Earnout Retention Threshold and Cure Period
Negotiate the MRR retention percentage required to earn out the full deferred consideration. A 90% retention threshold over 18 months is common but can be aggressive if the client base has natural churn. Include a cure period of 60–90 days to replace churned MRR with new managed service revenue before triggering earnout reductions, and cap total earnout clawback at the deferred payment amount.
Cybersecurity Indemnification Cap and Survival Period
Sellers should push to cap cybersecurity indemnification exposure at 10–15% of the purchase price with a 24-month survival period. Buyers should push for a higher cap if the MSP manages environments with elevated risk profiles such as healthcare, financial services, or legal clients subject to HIPAA, GLBA, or data privacy regulations. Require the seller to maintain tail coverage on their cyber liability policy for the indemnification period.
Key Employee Identification and Retention Obligations
Name specific key technicians and account managers in the LOI as conditions to closing. Agree in advance which employees are critical enough that their departure prior to close would constitute a material adverse change. Structure retention bonuses paid by the buyer — not the seller — at 6 and 12 months post-close to align incentives. Do not allow the seller to pre-negotiate raises or promotions for key staff that inflate the post-close payroll without buyer consent.
PSA and RMM Data Transfer and System Transition
Specify in the LOI whether the buyer is acquiring the Company's existing PSA and RMM platform licenses or migrating to the buyer's existing systems post-close. Data migration from one PSA to another is a significant operational risk and cost. If migrating, negotiate a 90–180 day parallel run period and ensure the seller's transition consulting obligation includes full cooperation with the data migration. Clarify ownership of client environment documentation stored in the documentation platform.
Seller Financing Subordination and SBA Standby Requirements
If SBA 7(a) financing is used, the SBA lender will require the seller note to be fully subordinated and may impose a 24-month standby period during which no principal payments can be made on the seller note. Sellers must understand this restriction before signing the LOI — surprises at this stage frequently kill deals. Buyers should confirm the seller is willing to accept standby note terms before structuring the deal around SBA financing.
Non-Compete Scope, Duration, and Carve-Outs
The geographic scope and duration of the seller's non-compete must reflect the actual service territory of the MSP's client base. A 50-mile radius and 3-year term is typical for single-market operators. If the seller plans to remain active in IT consulting, cybersecurity advisory, or vendor representation, negotiate explicit carve-outs for those activities to avoid post-close litigation. SBA guidelines require non-compete agreements from all sellers holding 20% or more equity.
Find IT Helpdesk & Support Businesses to Acquire
Enough information to write a strong LOI on day one — free to join.
IT helpdesk and managed services businesses in the $1M–$5M revenue range typically trade at 3.5x–6x adjusted EBITDA. The specific multiple depends heavily on the percentage of monthly recurring revenue — businesses with 65% or more MRR from multi-year managed service agreements command multiples at the higher end of the range. Break-fix-heavy businesses with minimal recurring contracts typically see multiples at or below 4x. Additional premium drivers include a diversified client base with no single customer over 15–20% of revenue, certified technical staff under employment agreements, and a clean cybersecurity history.
The majority of IT helpdesk and MSP acquisitions under $5M are structured as asset purchases. This allows the buyer to acquire specific assets — managed service agreements, PSA and RMM data, customer contracts, trade name, equipment, and goodwill — while leaving pre-close liabilities, including unknown cybersecurity incidents and tax obligations, with the seller entity. SBA 7(a) lenders generally prefer asset purchases for these transactions. Sellers sometimes prefer stock sales for capital gains tax treatment, which can create negotiation tension. Any tax benefit to the seller from a stock structure is typically offset by a purchase price adjustment in the buyer's favor, often called a 'gross-up,' to compensate the buyer for the additional inherited liability risk.
An MRR retention earnout in an MSP acquisition typically defers 15–25% of the total purchase price and pays out over 12–18 months post-close based on the percentage of pre-close monthly recurring revenue retained by the business. The LOI should define MRR precisely, establish the baseline measurement period (usually the three months immediately preceding close as recorded in the PSA billing system), set a retention threshold — commonly 85–90% — below which the earnout begins to reduce, and include a cure period of 60–90 days to replace churned clients before triggering penalties. Sellers should negotiate exclusions for client churn caused by events outside their control, such as client business closures or acquisitions.
Cybersecurity due diligence for an MSP acquisition should cover two distinct areas: the MSP's own internal security posture and the security posture of its client environments. For the MSP itself, buyers should review the current cyber liability insurance policy for coverage limits and exclusions, request a summary of any incidents or claims in the prior 36 months, and assess the patching, monitoring, and access control practices of the MSP's own infrastructure. For client environments, buyers should review managed service agreements for limitation of liability and indemnification clauses that protect the MSP from client breach claims, and flag any clients in regulated industries such as healthcare or finance where breach liability exposure is elevated. Engaging a third-party cybersecurity firm to conduct a technical assessment of both environments before close is strongly recommended.
A 60-day exclusivity period is standard for IT helpdesk and MSP acquisitions, but buyers pursuing SBA 7(a) financing should be aware that the full SBA approval and closing process often takes 90–120 days from LOI execution. The most practical approach is to negotiate an initial 60-day exclusivity period with a conditional 30-day extension triggered by documented SBA lender progress — such as a formal credit approval or commitment letter — rather than granting automatic 90-day exclusivity upfront. Sellers should require evidence of SBA lender engagement within the first two weeks of the exclusivity period to confirm the buyer is actively progressing toward financing approval.
Most IT helpdesk and MSP acquisitions include a commitment from the buyer to offer employment to all current full-time technical staff at comparable compensation and benefits for a defined period, typically 12 months post-close. Key technicians — those holding primary relationships with managed service clients or possessing specialized certifications — should be identified in the LOI and treated as conditions to closing. Buyers should budget for retention bonuses paid at 6 and 12 months post-close to reduce turnover risk during the integration period. Sellers should negotiate that any voluntary employee departure during the earnout period does not reduce earnout payments unless the departure was caused by seller conduct or a breach of the transition consulting agreement.
More IT Helpdesk & Support 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