A practical LOI framework built for recurring revenue software deals — covering ARR-based pricing, retention holdbacks, technical due diligence rights, and earnout structures specific to niche B2B and vertical SaaS businesses.
A letter of intent (LOI) in a SaaS acquisition is more than a price signal — it's the document that defines how both parties will measure value, allocate risk around churn and customer retention, and structure post-close obligations for a founder still holding product and customer relationships. Unlike traditional business acquisitions where revenue is recognized at point of sale, SaaS deals require the LOI to explicitly address how ARR is calculated, what constitutes a qualifying subscription, and how customer attrition between signing and close will affect final consideration. For lower middle market SaaS businesses generating $500K–$5M in ARR, buyers typically negotiate 3.5x–6x ARR multiples depending on net revenue retention, churn rate, gross margin profile, and the degree of founder dependency. This guide walks through each section of a SaaS LOI, provides annotated example language, and explains the negotiation dynamics unique to software acquisitions — including how to handle technical due diligence windows, deferred revenue adjustments, and earnout triggers tied to ARR growth milestones.
Find SaaS/Software Businesses to AcquireParties and Transaction Overview
Identifies the buyer entity, seller entity, and the specific assets or equity interests being acquired. For SaaS businesses, this section should specify whether the transaction is structured as an asset purchase (common for sole proprietors and single-member LLCs) or a stock/equity purchase (more common with C-corps or when IP assignment complexity favors keeping the entity intact). This distinction materially affects how software IP, customer contracts, and domain assets transfer.
Example Language
This Letter of Intent is entered into as of [Date] by and between [Buyer Entity Name], a [State] [LLC/Corporation] ('Buyer'), and [Seller Legal Name], an individual and sole owner of [Company Name], a [State] LLC ('Company'). Buyer proposes to acquire substantially all assets of the Company, including but not limited to all software code, customer contracts, subscription agreements, domain names, trademarks, proprietary data, and associated goodwill, through an asset purchase transaction structured as described herein.
💡 Sellers often prefer stock sales for tax efficiency, while buyers prefer asset purchases to avoid assuming unknown liabilities — particularly important in SaaS where undisclosed security breaches, GDPR violations, or open-source license obligations could create material post-close exposure. If an asset deal is agreed upon, ensure the LOI explicitly lists which liabilities are assumed, particularly deferred revenue obligations to existing subscribers.
Purchase Price and Valuation Methodology
States the proposed total consideration and explains how it was derived. For SaaS businesses, this section should anchor price to a specific ARR figure verified by the seller and define which subscription revenue qualifies — distinguishing between recurring subscription revenue and one-time professional services, setup fees, or legacy perpetual licenses. The LOI should state the ARR multiple explicitly so both parties understand the pricing mechanism, not just the headline number.
Example Language
Buyer proposes a total purchase price of $[X] ('Purchase Price'), representing approximately [X.X]x the Company's trailing twelve-month annual recurring revenue ('ARR') of $[X], as reported in the Company's MRR schedule dated [Date]. For purposes of this LOI, ARR is defined as the annualized value of all active monthly and annual subscription contracts with customers who have not issued a cancellation notice as of the date of this LOI, excluding one-time implementation fees, professional services revenue, and any contracts month-to-month with remaining term under 30 days. The Purchase Price is subject to adjustment at closing based on verified ARR as of the Closing Date, as described in Section [X].
💡 Sellers should push to lock in the ARR definition early to prevent buyers from reclassifying revenue categories during due diligence to justify a price reduction. Buyers should insist on a 'true-up' mechanism where final purchase price is recalculated based on ARR verified at closing, with a collar limiting upward and downward swings to 10–15% of the base figure. Disagreements about whether month-to-month contracts qualify as ARR are common — resolve this in the LOI, not during diligence.
Deal Structure and Payment Terms
Specifies how and when the purchase price is paid, including the breakdown between cash at close, seller notes, earnouts, and retention holdbacks. SaaS deals in the lower middle market frequently involve structured consideration because buyers want protection against customer churn between signing and close, and against overstatement of retention metrics that are difficult to validate without operating the business.
Example Language
The Purchase Price shall be paid as follows: (i) $[X] in cash at closing ('Closing Payment'), representing approximately [X]% of the total Purchase Price; (ii) a seller promissory note in the amount of $[X] ('Seller Note'), bearing interest at [X]% per annum, payable in equal monthly installments over [36/48/60] months, contingent on the Company maintaining ARR of at least $[X] measured on a trailing-three-month basis; and (iii) an earnout of up to $[X] payable over 24 months following closing based on ARR growth milestones as specified in Schedule A. A retention holdback of $[X], representing [10–15]% of the Closing Payment, shall be held in escrow for 12 months post-close and released pro-rata based on customer retention of at least [85]% of ARR as of the Closing Date.
💡 The retention holdback is the most frequently contested element in SaaS LOIs. Sellers should negotiate for a specific measurement methodology — ideally based on ARR retention rather than logo count, since losing a small customer shouldn't trigger the same holdback reduction as losing a 20% ARR anchor client. Buyers should ensure the holdback calculation excludes churn caused by buyer actions post-close, such as price increases or product changes, which sellers will push hard to include. Earnout structures should define ARR measurement frequency (monthly vs. quarterly), who controls product and pricing decisions during the earnout period, and dispute resolution mechanics.
Due Diligence Scope and Timeline
Defines the length, scope, and access rights of the buyer's due diligence investigation. For SaaS businesses, due diligence extends beyond financials to include technical code review, infrastructure assessment, customer contract analysis, and churn cohort validation. The LOI should specify the duration of the exclusivity-protected diligence window and enumerate the categories of materials the seller is obligated to provide.
Example Language
Buyer shall have [45/60] calendar days from the date of this LOI ('Due Diligence Period') to conduct a comprehensive review of the Company, including but not limited to: (i) financial records including MRR/ARR schedules, cohort churn analysis, deferred revenue schedules, and GAAP-reconciled income statements for the trailing 36 months; (ii) technical review of the Company's codebase, hosting infrastructure, third-party API dependencies, security practices, and open-source license compliance; (iii) all customer contracts, subscription agreements, SLAs, and cancellation or non-renewal notices received in the past 24 months; (iv) key person assessment including documentation of the founder's operational role in sales, support, and product development; and (v) intellectual property ownership documentation including IP assignment agreements, contractor work-for-hire agreements, and domain and trademark registrations. Seller shall provide access to a secure data room within 5 business days of LOI execution and shall make the founder reasonably available for management interviews, technical Q&A, and customer reference calls.
💡 Sellers should negotiate to limit live customer reference calls to no more than 3–5 customers and require advance notice before any direct customer contact to protect against transaction leakage. Buyers should insist on the right to engage a third-party code review firm at buyer's expense — this is non-negotiable for any deal above $1M. If the seller resists technical due diligence, treat it as a red flag. Also negotiate the right to extend the diligence period by 15 days if material issues are discovered that require additional investigation.
Exclusivity and No-Shop Provision
Restricts the seller from soliciting or entertaining competing offers during the due diligence period. This section protects the buyer's investment of time and legal fees during diligence and is standard in virtually all LOIs. The exclusivity window should be tied directly to the due diligence timeline.
Example Language
From the date of Seller's execution of this LOI through the earlier of (i) the expiration of the Due Diligence Period or (ii) written termination of this LOI by either party ('Exclusivity Period'), Seller agrees not to directly or indirectly solicit, initiate, encourage, or participate in any discussions or negotiations with any third party regarding the sale, merger, recapitalization, or other disposition of the Company or its assets. Seller shall immediately notify Buyer if any unsolicited approach is received during the Exclusivity Period. This exclusivity obligation shall survive any informal extensions of the Due Diligence Period mutually agreed upon in writing.
💡 Sellers with multiple active buyer conversations should attempt to shorten the exclusivity window to 30 days or tie extensions to milestone payments from the buyer. Buyers should resist paying a 'break-up fee' or exclusivity payment in lower middle market SaaS deals below $3M in enterprise value — it is not market standard at this deal size. If a seller insists on a break-up fee, cap it at 1–2% of the proposed purchase price and make it contingent on the buyer walking away for reasons other than material due diligence findings.
Representations, Warranties, and Indemnification Framework
Outlines the categories of representations the seller will be expected to make in the definitive purchase agreement and describes the general indemnification framework, including survival periods and liability caps. While full rep and warranty language belongs in the definitive agreement, the LOI should signal the buyer's expectations on key SaaS-specific representations to surface disagreements early.
Example Language
The definitive purchase agreement shall include customary representations and warranties from Seller, including without limitation: (i) accuracy of ARR schedules and absence of material misrepresentation in subscription revenue reporting; (ii) absence of known customer cancellation intentions not disclosed to Buyer during due diligence; (iii) ownership and validity of all software IP, with no open-source license conflicts or unresolved third-party IP claims; (iv) compliance with applicable data privacy laws including GDPR, CCPA, and SOC 2 obligations as represented to customers; and (v) absence of material technical vulnerabilities known to the seller as of closing. Indemnification obligations shall survive closing for 18–24 months with a general liability cap of [75–100]% of the Closing Payment and a basket of [0.5–1]% of the Purchase Price for general claims, with fraud and IP representations surviving indefinitely.
💡 SaaS sellers should pay close attention to data privacy representations — if the business has not implemented GDPR-compliant data processing agreements or has informally handled customer data without a documented privacy policy, this will become a negotiated carve-out or an indemnification exposure. Buyers acquiring vertical SaaS businesses handling sensitive customer data (healthcare, legal, financial) should push for a specific data breach indemnification carve-out with no cap or basket. Sellers should push to tie the indemnification cap to the cash consideration received at close rather than total enterprise value to limit exposure from earnout amounts not yet received.
Transition and Post-Close Obligations
Defines the seller's obligations following closing, including transition assistance, non-compete and non-solicitation restrictions, and any consulting arrangements. For founder-operated SaaS businesses, this section is particularly important because the product roadmap, customer relationships, and institutional knowledge often reside with the founder alone.
Example Language
Seller agrees to provide transition assistance for a period of [90/120/180] days following closing ('Transition Period'), including up to [20] hours per month of consulting support for product questions, customer introductions, and operational knowledge transfer, at a rate of $[X] per hour beyond the initial [40] hours included at no charge. Seller shall execute a non-competition agreement restricting Seller from directly or indirectly developing, operating, or investing in a substantially similar software product targeting the same ICP for a period of [3] years following closing within [geographic scope or vertical market definition]. Seller shall also be subject to a non-solicitation covenant prohibiting direct solicitation of Company customers or employees for [2] years post-closing.
💡 Sellers should negotiate hard on the ICP definition in the non-compete to avoid being locked out of adjacent markets — a founder selling a project management tool for construction firms should not be restricted from building tools for other industries. Buyers should ensure the transition period is long enough to absorb institutional product knowledge; 90 days is often insufficient for complex vertical SaaS products. Consider structuring a paid consulting arrangement for an additional 6–12 months at a market rate to incentivize the seller's cooperation during the critical post-close period.
ARR Definition and Qualifying Revenue
The single most impactful negotiation in a SaaS LOI is agreeing on exactly what counts as ARR. Buyers want a conservative definition excluding month-to-month contracts, discounted pilots, and at-risk accounts. Sellers want maximum revenue included. Establish a clear written definition in the LOI covering contract minimums, payment status requirements, and treatment of multi-year prepaid contracts — deferred revenue from prepaid annual subscriptions is often counted differently by each party.
Retention Holdback Measurement Methodology
When a portion of the purchase price is held in escrow pending customer retention, the measurement methodology determines how much of that holdback the seller actually recovers. Negotiate whether retention is measured by ARR value or customer count, how churned revenue from customers who voluntarily cancel versus customers the buyer migrates or discontinues is treated, and what the measurement date and payment schedule looks like. ARR-weighted retention measurement is fairer to sellers with diversified customer bases.
Earnout Trigger Definitions and Control Provisions
Earnouts in SaaS deals are only valuable if the seller retains some influence over the inputs — pricing, product investment, and sales activity — that drive ARR growth. Negotiate specific provisions requiring the buyer to maintain minimum product development spending, prohibiting unilateral price reductions that would suppress ARR, and establishing a joint oversight committee for major product decisions during the earnout period. Without these protections, a seller's earnout is entirely at the buyer's discretion.
Technical Due Diligence Scope and Remediation Obligations
Buyers will commission a third-party code review that almost always surfaces technical debt, dependency risks, or security gaps. Negotiate upfront in the LOI whether these findings can be used to reduce purchase price, trigger deal termination, or require seller-funded remediation before closing. Sellers should push to limit price adjustments to material findings above a defined cost threshold — for example, remediation costs exceeding $50,000 — to prevent buyers from using minor technical debt as a renegotiation lever.
Non-Compete Geographic and Vertical Scope
Non-compete restrictions in software deals should be defined by customer segment and product category rather than geography, since software businesses are borderless. Negotiate the ICP definition precisely — the vertical, company size, and use case the buyer is actually acquiring. A three-year non-compete that bars a founder from the entire software industry is overreaching and potentially unenforceable. A well-scoped restriction covering the specific vertical niche and customer profile for two to three years is both enforceable and fair.
Seller Note Contingency Conditions
If the deal includes a seller note contingent on ARR performance, the conditions triggering payment suspension or acceleration must be negotiated carefully. Sellers should push for notes to be unconditional or tied only to gross ARR — not net revenue after buyer expenses — to prevent accounting manipulation. Buyers should insist on the right to offset indemnification claims against the seller note balance rather than pursuing separate litigation. Agree on a floor ARR threshold below which note payments are suspended and an acceleration clause if the business is sold again within the note term.
Find SaaS/Software Businesses to Acquire
Enough information to write a strong LOI on day one — free to join.
Lower middle market SaaS businesses with $1M–$3M in ARR typically trade at 3.5x–6x ARR, with the specific multiple driven by net revenue retention, gross margin, churn rate, and the degree of founder dependency. A bootstrapped B2B SaaS business with 95% net revenue retention, 75%+ gross margins, and annual churn below 8% can command the upper end of that range. A business with 20% annual churn, a founder-controlled pipeline, and no documented SOPs will land at or below 3.5x regardless of revenue. The LOI should lock in a specific multiple tied to a verified ARR figure rather than a fixed dollar price to protect both parties from measurement disputes.
A retention holdback in a SaaS LOI typically represents 10–20% of the cash consideration at close, held in escrow for 12–24 months and released based on how much of the ARR in place at closing is still active at the measurement date. For example, if the seller has $1.2M ARR at close, $120,000 might be held back and released pro-rata if 85% or more of that ARR is still active at the 12-month mark. Retention below 85% would result in a proportional reduction — the most important negotiation is whether retention is measured by ARR dollars or customer count, and whether churn caused by buyer actions post-close is excluded from the calculation, which sellers should always push for.
Most lower middle market SaaS acquisitions are structured as asset purchases because buyers want to avoid assuming undisclosed liabilities, including potential GDPR violations, data breach claims, open-source license violations, and employment tax issues that may be hidden in the seller's entity. The asset purchase structure also allows buyers to step up the basis of acquired assets for tax purposes. However, if the SaaS business has complex customer contracts with anti-assignment clauses, or if government contracts require the entity to remain intact, a stock purchase may be preferable. The LOI should specify the intended structure early, as changing from asset to stock (or vice versa) after exclusivity is signed creates significant legal friction and delays.
A fair SaaS earnout has three essential components: a clearly defined ARR measurement methodology agreed upon before closing, explicit protections for the seller against buyer actions that would impair ARR growth, and a realistic target based on trailing growth rates rather than aspirational projections. Earnouts representing 25–40% of total consideration are common in lower middle market SaaS deals, typically paid over 24 months based on quarterly ARR snapshots. Sellers should insist on provisions requiring the buyer to maintain minimum product investment levels, prohibiting unilateral price cuts below a threshold without seller consent during the earnout window, and providing the seller with monthly financial reporting access to verify ARR figures independently.
This is why the purchase price in a SaaS LOI should be structured as a multiple of verified ARR at closing rather than a fixed dollar amount. If the LOI specifies a 4.5x multiple of ARR and ARR drops from $1.2M at signing to $1.05M at closing due to customer churn, the purchase price would automatically adjust to reflect the lower ARR figure. Most LOIs include a price collar — typically 10–15% — that limits how far the price can move in either direction, protecting the seller from small fluctuations while giving the buyer protection against material customer attrition during the diligence period. If ARR drops more than the collar allows, either party may have the right to renegotiate or terminate the deal.
Technical due diligence for a SaaS acquisition should cover five core areas: code quality and architecture review to assess maintainability and the cost of scaling or refactoring; infrastructure audit covering hosting architecture, uptime history, disaster recovery, and cloud cost structure; third-party dependency analysis identifying APIs, payment processors, and platforms whose terms or pricing could change post-acquisition; open-source license audit to ensure the codebase does not include GPL-licensed components that could create IP contamination issues; and security assessment covering data encryption, access controls, penetration testing history, and any known vulnerabilities. Buyers should engage a specialized technical due diligence firm rather than relying on internal developers, and the LOI should explicitly grant the buyer the right to conduct this review with reasonable access to the seller's codebase and infrastructure.
More SaaS/Software 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