Structure your MSP acquisition LOI to protect MRR quality, address key-man risk, and set the stage for a clean SBA or strategic close — with industry-specific language built for IT services deals.
An LOI for an IT Managed Services Provider acquisition is not a generic business purchase document — it must address the unique commercial dynamics that define MSP deal value and risk. The LOI is the foundational document that locks in your purchase price, deal structure, exclusivity period, and the key conditions that will govern due diligence. In MSP transactions, the LOI stage is where sophisticated buyers protect themselves against the most common value destroyers: inflated MRR figures that include informal month-to-month agreements, key-man dependency baked into client relationships, and cybersecurity liability that may not surface until deep in due diligence. For sellers, the LOI is the moment to clarify how earnout targets will be measured, whether equity rollover is expected, and what transition obligations the owner will carry post-close. Whether you are an entrepreneurial buyer using SBA 7(a) financing, an independent sponsor, or a PE-backed MSP roll-up platform, this guide and template provide the specific language, negotiation context, and structural guidance you need to execute a well-protected letter of intent for an IT services acquisition in the $1M–$5M revenue range.
Find IT Managed Services Provider Businesses to AcquireParties and Transaction Overview
Identifies the buyer entity, seller entity, and the legal structure of the proposed transaction — whether an asset purchase or stock/membership interest acquisition. Most MSP acquisitions under $5M are structured as asset purchases to allow buyers to step up basis and avoid inheriting unknown liabilities, including cybersecurity incidents or vendor disputes. However, stock deals may be preferred when key vendor contracts, Microsoft partner agreements, or client MSAs are not assignable without consent.
Example Language
This Letter of Intent ('LOI') is submitted by [Buyer Name], a [state] LLC ('Buyer'), to [Seller Name], a [state] S-Corporation ('Seller'), regarding Buyer's proposed acquisition of substantially all of the operating assets of [MSP Business Name] ('the Business'), including all managed service contracts, customer relationships, PSA and RMM platform configurations, vendor agreements, intellectual property, and goodwill associated with the Business. The parties intend to structure the transaction as an asset purchase. Buyer reserves the right to designate an acquisition subsidiary as the purchasing entity prior to closing.
💡 Sellers should scrutinize asset vs. stock structure carefully. If the MSP holds a Microsoft Cloud Solution Provider (CSP) designation, Datto partner status, or other vendor-tier relationships that are not assignable, a stock deal may preserve more value. Buyers using SBA 7(a) financing should confirm with their lender early, as SBA has preferences on deal structure that affect eligibility. Confirm whether existing managed service agreements contain change-of-control clauses that require client consent upon an asset transfer.
Purchase Price and Valuation Basis
States the proposed total enterprise value, the basis for that valuation (typically a multiple of trailing twelve-month EBITDA or annual recurring revenue), and the allocation between cash at close, seller note, and earnout. MSP valuations typically range from 4x–7x EBITDA, with premium multiples awarded to businesses with high MRR concentration (80%+ of revenue), low churn, multi-year contracts, and cybersecurity service lines. Break-fix or project-heavy MSPs trade at the lower end of the range.
Example Language
Buyer proposes a total purchase price of $[X] ('Purchase Price'), representing approximately [5.0x] times the Business's trailing twelve-month adjusted EBITDA of $[X], as presented in Seller's financial statements and add-back schedule provided to Buyer on [date]. The Purchase Price shall be payable as follows: (i) $[X] in cash at closing ('Cash at Close'), subject to a working capital adjustment; (ii) a Seller Note in the amount of $[X], bearing interest at [6]% per annum, with a [24]-month term and monthly amortization; and (iii) an earnout of up to $[X] payable over [24] months post-close based on MRR retention thresholds defined in Section [X] of the definitive agreement. The Purchase Price is subject to adjustment based on findings during due diligence, including reclassification of informal month-to-month agreements as non-contracted revenue.
💡 Buyers must define 'MRR' precisely in the LOI to avoid disputes at closing. Insist that MRR used to compute the purchase price includes only revenue from signed, written managed service agreements — not verbal renewals, informal project retainers, or co-terminus hardware refresh arrangements. Sellers should push back on any LOI language that allows the buyer unilateral discretion to reclassify revenue without an agreed-upon methodology. Both parties should agree in the LOI on the treatment of hardware resale margins, third-party software licensing pass-throughs, and vendor rebates in the EBITDA calculation.
Earnout Structure and MRR Retention Mechanics
Defines the earnout payment schedule, the specific MRR retention metrics that trigger payments, measurement methodology, and seller remedies if the buyer takes actions post-close that impair MRR. Earnouts are common in MSP deals — typically 10–20% of purchase price — and are almost always tied to client retention rather than revenue growth, since the primary concern is that clients exit after the owner departs. This section is the most heavily negotiated in MSP LOIs.
Example Language
Buyer shall pay Seller an earnout of up to $[X] ('Earnout'), contingent on MRR retention measured against a baseline MRR of $[X] per month ('Baseline MRR') established as of the closing date. Earnout payments shall be calculated and paid quarterly as follows: (i) 100% of the quarterly Earnout tranche if retained MRR equals or exceeds 95% of Baseline MRR; (ii) 75% if retained MRR is between 85%–94.9%; (iii) 50% if retained MRR is between 75%–84.9%; and (iv) $0 if retained MRR falls below 75%. MRR shall be measured on a client-by-client basis using the Business's PSA platform ([ConnectWise/Autotask]) as the system of record. Seller shall not be penalized for MRR attrition caused by (a) client bankruptcy or acquisition, (b) Buyer's unilateral changes to service pricing or scope, or (c) Buyer's failure to maintain minimum staffing levels agreed at closing.
💡 The carve-out protections for the seller are critical and frequently omitted in buyer-drafted LOIs. Sellers should insist that earnout calculations exclude churn events caused by buyer-side actions such as price increases, service quality degradation, or key technician terminations. Buyers should require the seller to actively participate in client retention efforts during the earnout period — including introductory calls, co-managed service reviews, and client communications — as a condition of earnout eligibility. Both parties should agree on which PSA reports constitute official MRR measurement and who has audit rights.
Key-Man Transition and Consulting Agreement
Defines the seller's post-close obligations, including a transition consulting period, client introduction requirements, and the parameters of any employment or consulting agreement. Key-man risk is the single most significant valuation discount factor in MSP acquisitions. Buyers will require a structured transition to ensure that client relationships, vendor partnerships (especially Microsoft CSP), and institutional knowledge transfer successfully to the new ownership team.
Example Language
As a condition of closing, Seller agrees to enter into a Transition Services and Consulting Agreement ('TSA') with Buyer for a period of [12] months following the closing date ('Transition Period'). During the Transition Period, Seller shall: (i) perform no fewer than [20] hours per week of consulting services at a rate of $[X] per month; (ii) personally introduce Buyer or Buyer's designated representative to all clients representing individually more than [5]% of total MRR within the first [60] days post-close; (iii) transfer all vendor portal credentials, PSA administrator access, RMM configuration documentation, and Microsoft Partner Center access within [10] business days of closing; and (iv) cooperate fully with Buyer's efforts to assign or novate client MSAs. Following the Transition Period, Seller shall be subject to a [3]-year non-compete and [2]-year non-solicitation covenant covering the Business's current geographic service area and client base.
💡 Sellers should negotiate the consulting fee as a distinct, non-contingent obligation — separate from and not offset against the earnout. A seller who is providing genuine transition value should be compensated for that time regardless of MRR performance. Buyers should ensure the non-compete covers not only direct MSP competition but also the seller providing informal IT support to former clients outside a formal business structure. Both parties should specify what happens if the seller becomes ill or is otherwise unable to fulfill TSA obligations, and whether a reduced-hour accommodation is permissible.
Due Diligence Period and Access
Establishes the length of the due diligence period, the scope of information to be provided, confidentiality obligations, and the process for raising material issues discovered during diligence. MSP due diligence is technical and commercial — buyers must review managed service contracts, PSA data exports, RMM platform configurations, cybersecurity posture, and vendor agreements in addition to financial statements.
Example Language
Buyer shall have [45] business days from the date of full execution of this LOI ('Due Diligence Period') to complete its review of the Business. Seller shall provide Buyer and its advisors with reasonable access to the following during the Due Diligence Period: (i) three years of financial statements including profit and loss, balance sheet, and cash flow statements with owner add-back schedules; (ii) a complete client MRR schedule including contract start dates, renewal terms, notice periods, and monthly billing amounts exported from [ConnectWise/Autotask]; (iii) copies of all executed managed service agreements, including any amendment, addendum, or scope-of-work documents; (iv) employee census including titles, compensation, certifications (CompTIA, Microsoft, Cisco), and employment agreement status; (v) all vendor agreements, licensing arrangements, and partner program documentation; and (vi) documentation of any prior cybersecurity incidents, client data breaches, insurance claims, or pending litigation. Buyer agrees to maintain strict confidentiality of all information received and to use such information solely for the purpose of evaluating the proposed transaction.
💡 Sellers should resist providing full access to client contract details or employee compensation data until the LOI is fully executed and a Non-Disclosure Agreement is in place. Consider a tiered disclosure approach — provide aggregated MRR data and financial summaries first, then full contract-level detail only after the buyer has passed preliminary diligence milestones. Buyers should build in a due diligence extension right of [15] additional business days if material issues are discovered that require further investigation, such as a cybersecurity incident history or vendor contract assignability complications.
Exclusivity
Grants the buyer an exclusive negotiating period during which the seller agrees not to solicit, entertain, or negotiate with other potential acquirers. Exclusivity is standard in LOIs and protects the buyer's investment in due diligence and legal fees. For MSP sellers, the exclusivity period should be balanced against the risk of losing other buyer interest if the deal falls through.
Example Language
In consideration of Buyer's commitment to invest significant resources in due diligence and transaction preparation, Seller agrees that for a period of [60] days from the date of full execution of this LOI ('Exclusivity Period'), Seller shall not, directly or indirectly, solicit, initiate, encourage, or engage in discussions or negotiations with any third party regarding the sale, transfer, or disposition of the Business or any material portion of its assets or equity. Seller shall promptly notify Buyer if any unsolicited inquiries are received from third parties during the Exclusivity Period. The Exclusivity Period may be extended by mutual written agreement of the parties.
💡 Sellers should negotiate a 45-day initial exclusivity window rather than 60–90 days, with a single extension right of 15–30 days contingent on the buyer demonstrating meaningful progress in diligence. Sellers should also include a termination right if the buyer has not delivered a formal purchase agreement draft by day 30 of the exclusivity period. Buyers financing with SBA 7(a) should account for lender timelines — SBA processing can add 30–45 days to deal timelines, which may require a longer exclusivity period to be realistic.
Conditions to Closing
Lists the material conditions that must be satisfied before the buyer is obligated to close, including financing contingencies, third-party consents, and absence of material adverse changes. For MSP deals, conditions typically address SBA loan approval, Microsoft partner consent, key employee retention agreements, and the absence of undisclosed cybersecurity incidents.
Example Language
Buyer's obligation to consummate the proposed transaction is subject to satisfaction of the following conditions prior to closing: (i) Buyer's receipt of SBA 7(a) financing approval in an amount sufficient to fund the Cash at Close component of the Purchase Price; (ii) execution of employment or retention agreements with [names or titles of key technical staff, e.g., Lead Systems Engineer and Service Desk Manager] on terms acceptable to Buyer; (iii) receipt of all necessary third-party consents for assignment of material managed service contracts, vendor agreements, and partner program designations, including Microsoft CSP agreement and [Datto/Kaseya/NinjaRMM] partner status; (iv) confirmation that no client representing more than [10]% of MRR has provided notice of termination or non-renewal; (v) no material adverse change in the Business's MRR, client relationships, or workforce between the LOI date and closing; and (vi) Seller's delivery of all required transition documentation including PSA and RMM administrative credentials, runbooks, and client onboarding/offboarding SOPs.
💡 Sellers should push to narrow the definition of 'material adverse change' to specific, quantifiable thresholds — for example, a loss of MRR exceeding 10% of Baseline MRR — rather than broad subjective language that could allow a buyer to exit the deal on a technicality. Buyers should not waive the key employee retention condition; the departure of a lead engineer or service manager between LOI and close is a legitimate deal-stopper in an MSP acquisition. Both parties should agree upfront on the consequences if a vendor consent is refused — whether the deal restructures as a stock purchase or the affected revenue is excluded from the purchase price calculation.
Confidentiality and Non-Disclosure
Reaffirms the parties' confidentiality obligations and addresses the seller's particular concern about deal information reaching clients, employees, or competitors. MSP sellers are especially sensitive to confidentiality because even a rumor of a sale can trigger client anxiety, employee departures, and competitive poaching.
Example Language
The parties acknowledge that all information exchanged in connection with this LOI and the proposed transaction, including the existence of negotiations, financial data, client lists, employee information, and technical documentation, is strictly confidential ('Confidential Information'). Neither party shall disclose Confidential Information to any third party without the prior written consent of the other party, except to legal counsel, financial advisors, and lenders who have agreed to equivalent confidentiality obligations. Buyer specifically agrees not to contact Seller's clients, employees, or vendors directly without Seller's prior written consent during the Due Diligence Period. Seller shall not disclose the existence of this LOI or the proposed transaction to clients, staff, or vendors unless mutually agreed in writing. These confidentiality obligations shall survive termination of this LOI for a period of [24] months.
💡 The prohibition on direct buyer contact with clients and employees without seller consent is a non-negotiable protection for most MSP sellers. Buyers should agree to this restriction — premature disclosure to a top client or a key technician can derail a deal entirely. However, buyers should negotiate a carve-out allowing them to contact prospective lenders and equity partners (under NDA) without seller consent, and to conduct reference checks on vendor relationships through publicly available partner directories.
MRR Definition and Baseline Calculation
The definition of Monthly Recurring Revenue used to compute the purchase price and earnout baseline is the single most important negotiated term in an MSP LOI. Buyers should insist that MRR includes only revenue from signed, written managed service agreements with specified notice periods — typically 30–90 days — and excludes project revenue, hardware sales, co-terminus software licensing renewals, and informal retainer arrangements. Sellers should ensure that recurring security services, cloud backup subscriptions managed through Datto or Acronis, and Microsoft 365 licensing margins are included in MRR if they are billed monthly and contractually obligated.
Earnout Trigger Thresholds and Seller Protections
The MRR retention thresholds that trigger earnout payments, and the carve-outs protecting sellers from buyer-caused churn, are intensely negotiated. Buyers typically want a high-threshold, all-or-nothing structure; sellers want graduated payments and explicit protections against churn caused by price increases, service degradation, or staff terminations. Both parties should agree in the LOI on which events constitute 'buyer-caused' churn and how disputes will be resolved, ideally through a neutral third-party accountant familiar with MSP financials.
Key Employee Retention Agreements as a Closing Condition
Buyers should make the execution of retention or employment agreements with named technical staff a hard closing condition rather than a best-efforts obligation. In an MSP, the departure of a lead engineer, NOC manager, or Microsoft-certified architect between signing and close can materially impair the business's ability to deliver services. Sellers should understand that this condition works in their favor too — it signals to the buyer that the team is committed and reduces post-close service disruption that would otherwise trigger earnout penalties.
Non-Compete Geography and Scope
Non-compete covenants for MSP sellers must be carefully scoped to be enforceable and fair. Buyers need protection against the seller launching a competing MSP or poaching clients; sellers need the ability to work in technology after the transition period. Negotiate the geographic scope (service area of the business at time of closing rather than a broad regional restriction), duration (3 years is market standard), and carve-outs for employment at a non-competing technology firm, internal IT roles, or technology consulting outside the MSP model.
Cybersecurity Liability Indemnification Tail
MSPs carry heightened cybersecurity liability because they have privileged access to client networks. Buyers should negotiate a specific indemnification provision covering any cybersecurity incidents, data breaches, or client claims arising from events that occurred pre-close, with a tail period of at least 3 years. Sellers should ensure the indemnification is capped at the purchase price and that claims are subject to a basket (deductible) to avoid trivial disputes. Both parties should confirm that the seller's existing E&O and cyber liability insurance can be extended on a claims-made basis or converted to a run-off policy to cover the tail period.
Vendor and Partner Agreement Assignability
Microsoft CSP agreements, Datto partner designations, ConnectWise or Autotask licensing, and security vendor partnerships (SentinelOne, Huntress, Acronis) may not be freely assignable in an asset purchase. The LOI should identify all material vendor relationships and specify whether each requires affirmative consent to assign, whether assignment is automatic in a stock purchase, and what happens to deal pricing or structure if a consent is withheld. Losing a Microsoft CSP tier designation at close can have immediate and material impact on licensing margins, making this a genuine deal-structuring issue rather than a back-office formality.
Working Capital Peg and Adjustment Mechanism
The working capital adjustment determines whether the seller delivers the business with a normalized level of current assets minus current liabilities. In an MSP, this primarily affects prepaid vendor contracts, deferred revenue from annual contracts billed upfront, and accounts receivable aging. Buyers should establish a target working capital peg based on a trailing average and negotiate the timing and dispute resolution process for post-close adjustments. Sellers should be aware that prepaid annual managed service contracts billed to clients create a deferred revenue liability on the balance sheet that buyers may attempt to count against the working capital target.
Find IT Managed Services Provider Businesses to Acquire
Enough information to write a strong LOI on day one — free to join.
MSPs in the lower middle market typically transact at 4x–7x trailing twelve-month adjusted EBITDA, with the specific multiple driven by several key factors. Businesses with 80%+ of revenue under multi-year managed service contracts, sub-5% annual churn, EBITDA margins above 20%, and a cybersecurity service line tend to command 5.5x–7x. MSPs that rely heavily on project revenue, have a single client representing 25%+ of MRR, or are deeply dependent on the owner for technical delivery typically close at 4x–5x. Revenue multiples are less commonly used but typically range from 1.0x–1.5x ARR for high-quality businesses. In an SBA-financed deal, the lender's willingness to underwrite the purchase price is also a practical ceiling — SBA lenders will scrutinize EBITDA quality, add-backs, and MRR contractual strength before approving a loan at a given multiple.
Most MSP acquisitions under $5M are structured as asset purchases because buyers want to step up the tax basis of acquired assets, avoid inheriting unknown liabilities (including pre-close cybersecurity incidents or vendor disputes), and selectively acquire only the assets that create value. However, a stock purchase may be preferable when the MSP holds critical vendor agreements — such as a Microsoft Cloud Solution Provider designation, a Datto Elite partner status, or specialty security vendor contracts — that are non-assignable in an asset deal but transfer automatically with the legal entity in a stock transaction. Buyers using SBA 7(a) financing should confirm their lender's structural requirements early, as some SBA lenders have preferences or restrictions on stock purchases. The LOI should explicitly address which structure is proposed while preserving the right to restructure if due diligence uncovers assignment restrictions.
Earnouts in MSP deals are almost universally tied to MRR retention rather than revenue growth, because the primary post-close risk is that clients leave when the owner departs. A typical structure places 10–20% of the purchase price into an earnout paid quarterly over 24 months based on how much of the closing-date MRR baseline is retained. Sellers can protect themselves by negotiating: (1) explicit carve-outs excluding churn caused by buyer-initiated price increases, service scope reductions, or key employee terminations; (2) a graduated payment scale rather than a cliff structure, so partial MRR retention still generates partial earnout; (3) buyer obligations to maintain minimum staffing levels and service quality during the earnout period; and (4) audit rights over the PSA data used to calculate MRR so the seller can verify the numbers independently. Sellers should treat the earnout as contingent compensation — plan financially assuming you receive only the base cash at close.
The five highest-priority due diligence areas for an MSP acquisition are: (1) MRR quality — obtain a full client-by-client MRR schedule from the PSA platform, verify every agreement is in writing with defined notice periods, and calculate trailing 12-month churn; (2) customer concentration — confirm no single client exceeds 15–20% of total MRR and assess the depth of relationship ownership (owner vs. staff); (3) key employee risk — review employment agreements, compensation benchmarking, non-competes, and technical certifications to assess post-acquisition retention probability; (4) cybersecurity liability — review all client MSAs for indemnification and liability cap language, obtain certificates of insurance for E&O and cyber liability, and ask directly about any prior breach incidents, insurance claims, or client disputes; and (5) vendor and partner agreement transferability — document every material vendor relationship and determine assignability before signing the definitive agreement, especially Microsoft CSP, RMM platforms, and security vendors.
A 45–60 day exclusivity period is market standard for MSP acquisitions in the $1M–$5M range. However, if the buyer is using SBA 7(a) financing, the lender's processing timeline of 30–60 days post-submission means a 60–75 day exclusivity window is more realistic. Sellers should insist on milestone-based extensions rather than automatic rollovers — for example, agreeing to a 15-day extension only if the buyer has delivered a complete due diligence request list and submitted an SBA loan application by day 30. Sellers should also include a mutual termination right if the buyer has not delivered a draft purchase agreement by a specified date within the exclusivity period. For PE or strategic buyers not using SBA financing, 45 days with one 15-day extension tied to demonstrated progress is a reasonable and fair structure.
This is one of the most common deal complications in MSP acquisitions and must be addressed in the LOI before due diligence begins. If critical vendor agreements — particularly Microsoft Cloud Solution Provider, Datto partner status, or security vendor discount tiers — cannot be assigned without vendor consent or re-application, the parties have several options: (1) restructure as a stock purchase so the legal entity (and its agreements) transfers intact; (2) negotiate a temporary vendor services agreement under which the seller's entity continues to provide licensing and vendor services to the buyer's entity during a transition period of 60–90 days while the buyer re-applies for partner status; or (3) exclude the affected revenue from the MRR baseline and purchase price, reducing the overall deal value. The LOI should specify which of these remedies applies by default and give the buyer a defined period — typically 30 days after receiving vendor response — to elect a remedy before either party can terminate the deal.
More IT Managed Services Provider 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