A practical LOI framework built for cloud MSP and managed infrastructure acquisitions — covering MRR valuation, earnout structures, cybersecurity reps, and key person retention in the $1M–$5M revenue range.
A Letter of Intent (LOI) for a cloud services provider acquisition is far more than a price placeholder — it is the document that sets the tone for every due diligence conversation and deal structure negotiation that follows. Cloud businesses are valued on the quality and predictability of their Monthly Recurring Revenue (MRR), meaning a poorly drafted LOI that ignores churn rates, customer concentration, or contract transferability can collapse a deal weeks after signing. For buyers, the LOI must define how purchase price will be adjusted if MRR degrades between signing and close, how earnouts will be structured around net revenue retention targets, and what protections exist if key technical employees resign during the exclusivity period. For sellers, the LOI is the moment to anchor valuation to the defensible strength of long-term customer contracts, compliance certifications like SOC 2 Type II, and proprietary tooling that creates switching costs. Cloud services providers in the lower middle market typically trade at 4x–7x EBITDA, with premiums awarded for high net revenue retention above 110%, diversified customer bases, and documented operational processes that reduce founder dependency. This guide walks through every section of a cloud MSP LOI, provides realistic example language, and highlights the negotiation points that determine whether a deal closes at the high or low end of the valuation range.
Find Cloud Services Provider Businesses to AcquirePurchase Price and Valuation Basis
Establishes the total consideration being offered and the financial metrics used to anchor the valuation, including EBITDA, MRR run rate, and ARR quality adjustments. For cloud services businesses, buyers must explicitly tie the stated price to a defined trailing twelve-month EBITDA figure and a verified MRR baseline, not gross revenue projections.
Example Language
Buyer proposes to acquire 100% of the issued and outstanding equity interests of [Company Name] (the 'Company') for a total purchase price of $[X] (the 'Purchase Price'), representing approximately [5.0x] trailing twelve-month Adjusted EBITDA of $[X] as of [Date]. The Purchase Price is predicated on a verified Monthly Recurring Revenue (MRR) baseline of no less than $[X] as of the LOI date, with at least 70% of total revenue derived from contracted, recurring services. The Purchase Price is subject to adjustment as described in Section [X] if MRR declines by more than 5% between the LOI execution date and the closing date.
💡 Sellers should push to define 'Adjusted EBITDA' explicitly in the LOI to prevent buyers from adding back unusual items during diligence that reduce the effective multiple. Buyers should insist on a clear MRR definition that excludes one-time migration or project revenue, which inflates recurring revenue optics. Agree on the look-back period — 12 months trailing is standard, but buyers may request a 24-month view to assess MRR trend and churn patterns.
Deal Structure and Payment Terms
Outlines how the total consideration will be paid, including cash at close, seller note terms, earnout mechanics, and any equity rollover. Cloud services acquisitions frequently involve deferred consideration tied to customer retention because MRR quality is difficult to fully verify before close.
Example Language
The Purchase Price shall be paid as follows: (i) $[X] in cash at closing, representing approximately [80%] of the total consideration; (ii) a Seller Note in the principal amount of $[X], bearing interest at [6%] per annum, payable over [24] months, with repayment contingent upon the Company maintaining an MRR baseline of no less than $[X] through the note term; and (iii) an earnout of up to $[X], payable over [24] months following close, based on the Company achieving net revenue retention of [105%] or greater measured on a rolling twelve-month basis. The earnout shall be calculated and paid quarterly, with a true-up at the end of the earnout period.
💡 Sellers should negotiate earnout measurement periods shorter than 24 months and push for quarterly earnout payments rather than a single lump sum at the end of the period. Insist on clear definitions of 'net revenue retention' and 'MRR' in the LOI itself to prevent disputes during the earnout period. Buyers should tie any seller note forgiveness provisions to specific, measurable customer retention metrics rather than broad revenue targets, and ensure the note is subordinated to any SBA or senior lender obligations.
Due Diligence Scope and Timeline
Defines the categories of information the buyer will review, the timeline for completing diligence, and the seller's obligations to provide access to systems, contracts, and personnel. Cloud services due diligence is highly technical and typically includes MRR cohort analysis, technology stack audit, cybersecurity review, and contract transferability assessment.
Example Language
Buyer shall have [60] calendar days following execution of this LOI (the 'Due Diligence Period') to conduct a comprehensive review of the Company, including but not limited to: (i) MRR and ARR quality analysis, including churn rate, net revenue retention by customer cohort, and contract term review for the preceding 36 months; (ii) audit of all customer contracts, SLAs, auto-renewal provisions, and change-of-control clauses; (iii) technology stack assessment, including third-party vendor agreements, hyperscaler partnership terms with AWS, Azure, or Google Cloud, and licensing transferability; (iv) cybersecurity posture review, including SOC 2 Type II or equivalent compliance certification status, penetration test results, and incident history for the preceding 48 months; and (v) key person dependency assessment, including review of technical staff roles, compensation, and non-compete or retention agreement status. Seller agrees to provide access to a secure virtual data room within [10] business days of LOI execution.
💡 Sellers should negotiate for a defined diligence scope to prevent open-ended requests that delay closing. Buyers acquiring through SBA financing should build in buffer time — SBA lender due diligence on cloud businesses often adds 30–45 days beyond the buyer's own review period. Both parties should agree upfront on which cybersecurity findings constitute material adverse conditions that allow the buyer to renegotiate price or walk away. Sellers with active SOC 2 Type II certifications should use this as leverage to limit the depth of cybersecurity diligence.
Exclusivity and No-Shop Period
Grants the buyer an exclusive negotiating window during which the seller agrees not to solicit, entertain, or accept offers from other buyers. This protects the buyer's investment in due diligence while giving the seller assurance that the buyer is committed to the process.
Example Language
In consideration of Buyer's commitment to conduct due diligence and incur associated costs, Seller agrees to a no-shop and exclusivity period of [60] calendar days from the date of LOI execution (the 'Exclusivity Period'). During the Exclusivity Period, Seller and its representatives shall not, directly or indirectly, solicit, initiate, encourage, or engage in discussions with any third party regarding the sale, merger, recapitalization, or other disposition of the Company or its assets. Seller shall promptly notify Buyer if any unsolicited acquisition inquiry is received during the Exclusivity Period. The Exclusivity Period may be extended by mutual written agreement in the event the parties are actively negotiating a definitive purchase agreement.
💡 Sixty days is standard for cloud MSP acquisitions given the technical depth of diligence required. Sellers should resist exclusivity periods exceeding 75 days without a corresponding good-faith deposit or break-up fee from the buyer. Buyers should request automatic extension provisions if SBA lender approval is pending at the expiration of the exclusivity period. Consider adding a mutual termination fee if the buyer walks away for reasons other than material diligence findings.
Representations and Warranties Highlights
Identifies the critical representations the seller will be required to make in the definitive agreement, with specific focus on MRR accuracy, contract validity, cybersecurity incident disclosure, and absence of key person departures. Flagging these in the LOI avoids surprises in the purchase agreement negotiation.
Example Language
The definitive purchase agreement shall include, without limitation, Seller representations and warranties regarding: (i) the accuracy of all MRR, ARR, and churn data provided to Buyer, including the completeness of all customer contracts and the absence of side letters or informal pricing arrangements; (ii) the validity, enforceability, and transferability of all customer agreements without requirement of customer consent unless otherwise disclosed; (iii) the absence of any undisclosed cybersecurity incidents, data breaches, or regulatory investigations involving the Company's cloud infrastructure or customer data in the preceding 48 months; (iv) current compliance status with all applicable certifications including SOC 2 Type II, as applicable, and the absence of any material findings in the most recent audit; and (v) no pending or threatened departure of any key technical employee identified on Schedule [X] as of the LOI date.
💡 Sellers should push for a cap on representation and warranty liability equal to 15–20% of the purchase price and a survival period of 18–24 months. Buyers should consider Representations and Warranty Insurance (RWI) for transactions above $3M, which has become increasingly accessible in the lower middle market. Cybersecurity reps are a specific focus area — buyers should insist on a longer survival period (36 months) for cyber-related reps given the delayed discovery nature of breach incidents.
Key Person Retention and Transition
Addresses the critical risk of losing essential technical staff immediately following the transaction, including provisions for employment agreements, retention bonuses, and seller transition obligations. This is one of the highest-risk elements in cloud services acquisitions.
Example Language
As a condition to closing, Buyer requires that [lead engineer / head of infrastructure / named key persons] (the 'Key Technical Employees') execute employment or contractor agreements with terms and compensation acceptable to Buyer, for a minimum engagement period of [24] months post-close. Seller agrees to cooperate with Buyer's efforts to negotiate retention packages, including supporting a retention bonus pool of up to $[X] funded at closing, allocated at Buyer's discretion among Key Technical Employees. Seller shall remain available for a transition period of no less than [12] months post-close, in a consulting capacity at [X] hours per week, at a monthly consulting fee of $[X]. The consulting agreement shall be executed as a condition to closing.
💡 Sellers should negotiate the consulting period duration and hours carefully — 12 months at 10–15 hours per week is reasonable for most cloud MSP transitions. Buyers should resist paying for a consulting agreement that has no deliverables or milestones attached. For PE-backed acquirers doing roll-ups, insist on non-solicitation agreements for all technical staff covering a 24-month post-close period. If the owner holds critical vendor relationships with hyperscalers like AWS or Azure, document the transition of those relationship contacts explicitly in the LOI.
Working Capital and Net Debt Adjustments
Defines the working capital target used to normalize the balance sheet at close, and addresses how deferred revenue, prepaid contracts, and outstanding vendor payments will be treated in the purchase price calculation.
Example Language
The Purchase Price shall be subject to a working capital adjustment based on a target net working capital of $[X] (the 'Working Capital Target'), calculated as current assets minus current liabilities as of the closing date, excluding cash and debt. For purposes of this adjustment, deferred revenue from prepaid annual cloud service contracts shall be treated as a current liability. Any shortfall below the Working Capital Target shall reduce the cash consideration payable at close on a dollar-for-dollar basis. Any excess above the Working Capital Target shall increase the cash consideration payable at close. A preliminary closing balance sheet shall be prepared by Seller no later than [3] business days prior to closing, with a final true-up within [60] days post-close.
💡 Deferred revenue treatment is a common dispute point in cloud services deals — buyers want it treated as a liability (representing future service obligations), while sellers often argue it reflects prepaid cash received. Establish the treatment explicitly in the LOI. For businesses with significant annual prepay contracts, the deferred revenue balance can meaningfully affect effective cash at close. Sellers should confirm that the working capital target is set based on a normalized historical average, not a single month that may be anomalously high or low.
Confidentiality and Announcements
Establishes mutual obligations to keep the transaction confidential during the LOI and due diligence phase, and defines how and when customers, employees, and vendors may be informed of the pending transaction.
Example Language
Both parties agree to maintain strict confidentiality regarding the existence and terms of this LOI and any information exchanged during due diligence, consistent with the Non-Disclosure Agreement dated [Date] previously executed between the parties. Neither party shall make any public announcement, press release, or disclosure to customers, employees, or vendors regarding the proposed transaction without the prior written consent of the other party, except as required by applicable law. Seller acknowledges that premature disclosure to key customers or technical employees could result in customer churn or employee departures that would constitute a material adverse effect on the transaction. The parties agree that customer notification shall occur only after execution of the definitive purchase agreement and as part of a jointly approved communication plan.
💡 Customer notification timing is particularly sensitive in cloud services because enterprise clients may use a change-of-control announcement as an opportunity to rebid their contracts or begin vendor evaluations. Sellers should insist on controlling the narrative and timing of customer communications. Buyers should include a provision allowing them to reach out to key customers as part of diligence, with seller present, once both parties are in advanced negotiations and a definitive agreement is near execution.
MRR Definition and Baseline Verification
The single most important economic term in a cloud services LOI. Buyers and sellers must agree on exactly what constitutes MRR — recurring contracted revenue from managed services, hosting, and cloud infrastructure fees — and explicitly exclude one-time project revenue, migration fees, and variable usage overage charges. Agreeing to a verified MRR baseline in the LOI prevents price renegotiation during diligence when the buyer inevitably discovers revenue that was miscategorized as recurring.
Earnout Metrics and Measurement Methodology
If any portion of the purchase price is contingent on post-close performance, the LOI must define the exact metric — net revenue retention, MRR growth, or EBITDA — along with the measurement period, calculation methodology, and dispute resolution process. Cloud services earnouts most frequently collapse over definitional disputes: whether a customer downgrade counts as churn, how expansion revenue from upsells is credited, and who bears responsibility if a hyperscaler margin change reduces profitability through no fault of the seller.
Customer Concentration Threshold and Price Adjustment Triggers
If any single customer represents more than 15% of total MRR, the LOI should define what happens if that customer provides notice of non-renewal or termination between signing and close. Buyers should negotiate a price adjustment mechanism — or a walk-away right — if a top customer is lost during the exclusivity period. Sellers should push to limit this provision to clients representing more than 20% of MRR to avoid excessive buyer optionality.
Technology Stack and Vendor Agreement Transferability
Hyperscaler reseller agreements with AWS, Azure, and Google Cloud frequently contain change-of-control provisions that require consent or re-credentialing post-acquisition. The LOI should address who bears responsibility for obtaining those consents, what happens if a critical vendor agreement cannot be transferred, and whether failure to obtain a specific consent is a deal-closing condition or merely a post-close obligation. Buyers acquiring businesses with proprietary automation platforms should also negotiate ownership of all associated IP explicitly in the LOI.
Cybersecurity Representation Scope and Survival Period
Given the cybersecurity liability exposure inherent in cloud services businesses — including potential undisclosed breach history, ransomware incidents, or compliance gaps — the LOI should flag that cybersecurity representations will survive closing for a longer period than general reps, typically 36 months. Buyers should specify that the seller must disclose any cybersecurity incidents or regulatory inquiries initiated during the exclusivity period immediately upon occurrence, and that material undisclosed cyber incidents constitute a right to terminate the LOI without penalty.
Seller Consulting Period and Non-Compete Terms
Cloud services founders often hold critical vendor relationships, customer trust, and institutional knowledge about proprietary systems. The LOI should define the consulting period length, weekly hour commitment, and compensation clearly. Non-compete terms — typically 3 years and within the geographic and service scope of the business — should be agreed in principle in the LOI so they do not become a late-stage negotiating issue. Sellers should push back on overly broad non-competes that restrict them from working in the broader technology industry.
Representations and Warranty Insurance Allocation
For cloud services acquisitions above $2.5M, buyers increasingly use Representations and Warranty Insurance to reduce reliance on seller indemnification. The LOI should note whether RWI is contemplated and who bears the cost — typically the buyer pays the premium, which runs 2–4% of the insured limit. Sellers should push for RWI as it effectively eliminates post-close indemnification exposure beyond a small deductible and allows them to receive cleaner, less escrowed proceeds at close.
Find Cloud Services Provider Businesses to Acquire
Enough information to write a strong LOI on day one — free to join.
Cloud services providers in the lower middle market typically transact at 4x–7x trailing twelve-month Adjusted EBITDA. The multiple you achieve depends heavily on MRR quality: businesses with net revenue retention above 110%, multi-year customer contracts, and no single client exceeding 15% of revenue consistently trade at the high end of that range. Businesses with month-to-month contracts, declining MRR trends, or heavy founder dependency typically attract offers at 4x–5x EBITDA or below. Compliance certifications like SOC 2 Type II and proprietary automation tooling are meaningful premium drivers for strategic acquirers and PE-backed roll-up platforms.
The definition and verification of Monthly Recurring Revenue (MRR) is the single most critical term to negotiate in a cloud services LOI. Everything downstream — the purchase price, the earnout structure, the seller note terms — flows from the agreed MRR baseline. Buyers frequently discover during diligence that reported MRR includes one-time migration revenue, variable usage fees, or contracts that are technically month-to-month. Agreeing on an explicit MRR definition and a verified baseline figure in the LOI itself prevents this from becoming a late-stage renegotiation that damages trust and delays closing.
Sixty days is the industry standard for cloud services provider acquisitions in the lower middle market, reflecting the depth of technical due diligence required — including MRR cohort analysis, technology stack audits, hyperscaler agreement review, and cybersecurity posture assessment. If the buyer is using SBA financing, build in a 75–90 day exclusivity window to accommodate lender processing time. Sellers should resist exclusivity beyond 90 days unless the buyer provides a good-faith deposit or break-up fee to compensate for the opportunity cost of staying off the market during an extended period.
The LOI should explicitly flag that cybersecurity-related representations and warranties will survive closing for 36 months — longer than the 18–24 month standard for general reps — given the delayed discovery risk of breach incidents. Sellers should be required to disclose any cybersecurity incidents, regulatory investigations, or compliance findings that arise during the exclusivity period immediately upon discovery. Buyers should treat the absence of SOC 2 Type II certification or any unresolved material security findings as a negotiating lever for price adjustment, not just a post-close remediation item.
Yes. Cloud services providers are SBA-eligible businesses, and SBA 7(a) loans are commonly used by individual operators and searchers to finance acquisitions in the $1M–$5M revenue range. Lenders will scrutinize the quality and predictability of MRR closely, and businesses with documented multi-year customer contracts and low churn rates are most likely to receive favorable terms. SBA lenders will typically require a 10% buyer equity injection, and the SBA loan process adds 30–60 days to the diligence and closing timeline compared to conventional financing — factor this into your LOI exclusivity and diligence period planning.
The departure of a key technical employee between LOI signing and close is one of the most common deal-disrupting events in cloud services acquisitions. Your LOI should include a provision stating that the resignation or termination of any designated Key Technical Employee during the exclusivity period constitutes a material adverse event that gives the buyer the right to renegotiate purchase price or terminate the LOI. Sellers should proactively address this risk by having retention agreements with key staff in place before entering the sale process, and buyers should build retention bonus packages into the deal structure to be funded at close.
Earnouts are common in cloud services acquisitions — typically representing 20–30% of total consideration — particularly when there is uncertainty about MRR quality, customer retention durability, or the seller's role in sustaining key client relationships. The most effective earnouts in this sector are tied to net revenue retention measured quarterly over 12–24 months, rather than EBITDA targets, which are easier for the buyer to influence through post-close cost allocations. Sellers should negotiate for quarterly earnout payments, a cap on the buyer's ability to change pricing or service scope in ways that would suppress retention metrics, and an acceleration clause that pays out the full earnout if the buyer sells the business before the earnout period ends.
More Cloud 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