Buying a SaaS/Software Business

Loan options

• SBA 7(a) Standard Loan

  Full SaaS business acquisitions including goodwill, customer relationships, IP, and working capital injection — the most commonly used structure for software deals in the $1M–$5M range

• SBA 7(a) Small Loan

  Micro-SaaS acquisitions or add-on software tool purchases where the enterprise value is under $500K and the buyer needs faster approval with lighter documentation overhead

• SBA 504 Loan

  Software acquisitions that include significant tangible assets such as proprietary hardware infrastructure, owned data center equipment, or real estate — less common in pure SaaS deals but applicable for hybrid software-hardware platforms

Eligibility

• The target SaaS or software business must be a for-profit U.S.-based operating company with at least 2 years of verifiable operating history and documented ARR or MRR schedules
• The buyer must inject a minimum 10% equity down payment at close, though most SBA lenders require 15–20% for software acquisitions given intangible asset concentration
• The business must demonstrate sufficient cash flow to cover annual debt service with a minimum 1.25x debt service coverage ratio based on seller's discretionary earnings or adjusted EBITDA
• Neither the buyer nor the seller can be on the SBA's ineligible borrower list, and the buyer must demonstrate relevant operational or technology management experience

Step by step

1. Define Your Acquisition Criteria and Financial Profile2–4 weeks

   Before approaching lenders, establish clear acquisition criteria aligned with SBA underwriting standards.

2. Source and Evaluate SaaS Acquisition Targets4–12 weeks

   Identify software businesses through SaaS-focused brokers, Acquire.com, MicroAcquire, investment bankers specializing in lower middle market software, or direct outreach to bootstrapped founders.

3. Select an SBA Lender with SaaS Acquisition Experience1–2 weeks

   Not all SBA lenders are equipped to underwrite software acquisitions. Seek out SBA Preferred Lender Program (PLP) banks or non-bank SBA lenders that have closed multiple software or technology business acquisitions.

4. Complete Due Diligence and Submit Loan Application4–8 weeks

   Conduct full due diligence in parallel with the SBA loan application process to avoid timeline gaps.

5. Receive Conditional Approval and Satisfy Underwriting Conditions2–4 weeks

   SBA lenders will issue a conditional approval letter specifying remaining documentation requirements before final commitment.

Other financing

• SBA 7(a) LoanPrime + 2.75%–3.5% (currently 11–12.5%)

  The SBA 7(a) program is the most common financing vehicle for SaaS acquisitions under $5M. Lenders will underwrite based on historical EBITDA, MRR stability, and net revenue retention above 90%.

  • + Low down payment requirement of 10–15% preserves acquisition capital for post-close product investment
  • + Long amortization up to 10 years reduces monthly debt service pressure on SaaS cash flows
  • − Lenders unfamiliar with SaaS metrics may undervalue recurring revenue or misinterpret deferred revenue schedules
  • − Personal guarantee and collateral requirements can be challenging for asset-light software businesses
• Seller Financing6–8% annually, typically interest-only in year one

  A seller note covering 20–30% of the purchase price is common in SaaS deals. Sellers defer a portion of proceeds contingent on ARR maintenance, reducing buyer risk during transition.

  • + Bridges valuation gaps when buyers and sellers disagree on churn risk or growth assumptions
  • + Reduces upfront capital requirement and improves acquisition DSCR for senior lender approval
  • − Sellers may require ARR maintenance covenants that constrain pricing strategy or customer mix decisions
  • − Note subordination requirements from SBA lenders limit seller repayment priority and negotiation leverage

Lender tips

• Target SBA Preferred Lender Program banks with dedicated technology or software vertical underwriting teams — these lenders have approved frameworks for evaluating ARR quality, churn normalization, and intangible asset valuations that generalist community banks lack
• Prepare a one-page SaaS metrics summary before your first lender conversation — include trailing 12-month MRR trend, net revenue retention percentage, gross margin, annual churn rate, customer count, and top 5 customer concentration as a percentage of ARR — this signals sophistication and accelerates pre-qualification
• Ask each lender candidate for their specific overlay policies on intangible asset concentration and goodwill as a percentage of total enterprise value — some lenders cap goodwill at 50% of the total loan amount while others have no hard cap, and this single policy difference can affect how much you can borrow
• Consider non-bank SBA lenders such as Live Oak Bank, Newtek, or Celtic Bank which have developed specific software and technology acquisition lending programs with underwriters trained on SaaS metrics — they often move faster than traditional banks on software deals

• All-Cash at Close with Customer Retention Holdback80–90% paid at close; 10–20% held in escrow released upon meeting ARR or customer retention milestones over 12–24 months

  The buyer pays the majority of the purchase price at closing and withholds 10–20% of total consideration in escrow, releasing it to the seller over 12–24 months contingent on key customers remaining active and ARR not declining below a defined threshold.

  • + Provides the seller with substantial immediate liquidity while aligning post-close incentives around customer retention
  • + Reduces buyer risk from customer churn or contract cancellations that may occur during ownership transition
  • − Seller bears post-close risk for churn events that may be outside their control once the buyer takes over operations
  • − Escrow release disputes can arise if the buyer's operational decisions contribute to customer attrition
• Earnout Tied to ARR Growth Targets

  A portion of the total purchase price — typically 25–40% — is deferred and paid to the seller only if the business achieves defined ARR growth milestones over a 1–2 year period post-close.

  • + Bridges valuation gaps between buyers who underwrite conservative ARR growth and sellers who believe in near-term upside
  • + Motivates sellers to remain actively involved post-close during a defined transition or growth period
  • − Earnout disputes are among the most litigated elements of M&A transactions, particularly when the buyer controls operational decisions that affect ARR
  • − Sellers bear significant risk that buyer decisions around pricing, sales investment, or product direction suppress earnout achievement

Negotiation tips

• Anchor holdback and earnout triggers to ARR or net revenue retention metrics rather than EBITDA — in SaaS transactions, EBITDA is easier to manipulate post-close through expense decisions, while ARR is a more objective and tamper-resistant measure of business health.
• If you are a seller, negotiate explicit operational guardrails into any earnout agreement that restrict the buyer from making pricing reductions, eliminating sales headcount, or discontinuing product features without your consent during the earnout measurement period — these decisions directly impact your ability to hit ARR targets you no longer control.
• Request cohort-level churn data broken out by customer acquisition year and contract size before finalizing holdback thresholds — if the 2021 and 2022 cohorts are churning at 18% annually while newer cohorts hold at 6%, structuring a single blended ARR holdback masks the real risk profile of the renewal schedule.
• For SBA-financed acquisitions, confirm with your lender early in the process whether the seller note structure meets equity injection requirements — most SBA 7(a) lenders require the seller note to be on full standby for 24 months with no principal or interest payments, which affects seller cash flow planning.

Revenue Quality & Retention Metrics

• Request cohort-level churn analysis by contract vintage and customer segment for the past 24 months.critical

  Cohort data exposes whether churn is accelerating among newer customers, signaling weakening product-market fit.

• Calculate net revenue retention (NRR) independently using raw subscription data, not seller-provided summaries.critical

  NRR above 100% confirms expansion revenue offsets churn; NRR below 90% erodes valuation basis significantly.

• Verify MRR reconciles to bank deposits and invoiced amounts across a trailing 12-month period.critical

  Discrepancies between MRR schedules and actual cash receipts indicate revenue recognition errors or inflated reporting.

Technical Infrastructure & Code Quality

• Commission an independent technical audit covering code quality, architecture, test coverage, and deployment practices.critical

  Technical debt invisible to non-engineers can require $200K–$500K in post-acquisition remediation investment.

• Audit all third-party API dependencies, SaaS infrastructure vendors, and licensing agreements for continuity risk.critical

  Platform dependency on AWS, Stripe, or niche APIs can create existential risk if vendor terms change post-close.

• Review system uptime history, incident logs, and SLA performance records for the trailing 24 months.important

  Chronic downtime or unresolved incidents indicate infrastructure instability that will surface as churn post-acquisition.

• Confirm all IP, proprietary code, and software components are owned by the business entity, not the founder personally.critical

  Unassigned IP creates legal exposure and can block deal closing or require costly post-acquisition remediation.

Customer Contracts & Commercial Terms

• Collect all active customer contracts and verify auto-renewal clauses, notice periods, and cancellation provisions.critical

  Weak auto-renewal language allows customers to cancel immediately post-close, collapsing the ARR you paid for.

• Review all SLAs, uptime guarantees, and data security obligations for financial exposure and compliance requirements.important

  Aggressive SLAs with financial penalties or HIPAA/SOC 2 obligations create undisclosed post-acquisition liability.

• Verify all contracts are assignable to the acquiring entity without requiring individual customer consent.critical

  Non-assignability clauses require customer re-signing at close, creating churn risk and deal execution delays.

• Audit payment history for all customers exceeding $10K ARR, noting late payments, disputes, or credits issued.important

  Chronic late payers or credit-heavy accounts inflate gross ARR while masking effective net revenue quality.

Financial Reporting & Revenue Recognition

• Reconcile reported ARR to GAAP revenue by reviewing deferred revenue schedules and subscription billing cycles.critical

  Cash-basis SaaS businesses often overstate revenue by recognizing annual prepayments immediately rather than ratably.

• Request trailing 3 years of P&L statements, balance sheets, and bank statements prepared or reviewed by a CPA.critical

  Unaudited financials with no third-party review increase the risk of misstated expenses, owner perks, and add-backs.

• Analyze gross margin composition, separating true software margin from hosting costs, support labor, and implementation fees.important

  Reported 80% gross margins can compress to 60% when support headcount and infrastructure costs are properly allocated.

• Evaluate owner compensation, related-party transactions, and discretionary expenses against market-rate benchmarks.important

  Inflated add-backs that normalize owner salary to unrealistic levels artificially boost adjusted EBITDA and purchase price.

SaaS/Software-specific checks

• Verify MRR reconciles to bank deposits by cross-referencing Stripe or payment processor reports against the MRR schedule provided in the CIM.
• Confirm all intellectual property — including code, trademarks, and domain assets — is assigned to the legal entity being acquired, not held personally by the founder.
• Assess AI displacement risk by mapping core product features against emerging AI-native tools that could replicate functionality and erode the competitive moat within 24 months.
• Request NPS scores, login frequency data, and feature adoption metrics to build a customer health baseline and identify accounts at elevated churn risk post-acquisition.
• Evaluate whether the product roadmap is documented and prioritized independently of the founder, and whether a technical lead or contractor can execute development post-transition.

Red flags

• Net revenue retention below 85% when independently calculated from raw subscription data rather than seller summaries
• Single customer representing more than 25% of total ARR with a contract renewal date within 18 months of close
• Founder is sole engineer with no documented codebase, version control, or third-party technical continuity plan
• More than 30% of ARR on month-to-month subscriptions with no contractual notice or cancellation requirement
• MRR growth trend is declining or flat for more than 6 consecutive months in the 12–24 months prior to listing

What the LOI covers

• Purchase Price and Valuation Methodology

  States the proposed total consideration and explains how it was derived.

• 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.

• Due Diligence Scope and Timeline

  Defines the length, scope, and access rights of the buyer's due diligence 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.

• 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.

Terms to negotiate

• 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.

• 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.

• 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.

• 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.

Target profile

• Vertical B2B SaaS with an identifiable ICP serving a niche industry where the software is deeply embedded in core workflows and switching costs are high
• Net revenue retention above 90% with annual churn below 10%, demonstrating strong product-market fit and customer dependency beyond surface-level convenience
• Gross margins above 70% with a predominantly subscription-based revenue model — minimal professional services or custom development revenue that would compress platform margins
• Founder-operated with 1–10 employees, limited institutional capital raised, and an owner actively seeking liquidity within 12–24 months due to fatigue, retirement, or growth plateau

Platform and add-on criteria

• Minimum $1.5M ARR with Positive Cash FlowPlatform

  The platform company must generate at least $1.5M ARR with EBITDA margins above 20%, providing sufficient cash flow to fund add-on acquisitions and integration costs without excessive leverage.

• Net Revenue Retention Above 100%Platform

  Platform NRR above 100% confirms expansion revenue through upsells or seat growth, signaling strong product-market fit and a customer base capable of absorbing additional modules from future add-ons.

• Vertical Specialization with Defensible ICPPlatform

  The platform must serve a clearly defined vertical — such as legal, healthcare, or construction — where domain-specific compliance, terminology, and workflows create switching costs generalist software cannot replicate.

• Documented Processes and Reduced Founder DependencyPlatform

  Sales, onboarding, support, and product release cycles must be documented in SOPs with non-founder staff executing key functions, enabling repeatable integration of add-on acquisitions post-close.

Acquisition sequence

1. Deep Diligence and Integration Playbook DevelopmentBuilding a repeatable integration system that reduces time-to-value for each add-on acquisition from 12 months to 60–90 days

   Before acquiring your second target, conduct a full post-acquisition operational audit of the platform company: cohort-level churn analysis by customer vintage, technical debt assessment, SOP documentation gaps, and customer health scoring.

2. Centralized GTM and Product IntegrationDriving NRR expansion across the platform through cross-sell motions, usage-based upsells, and unified customer success that reduces churn below 7% annually

   After two or more add-on acquisitions, consolidate go-to-market infrastructure: unified HubSpot or Salesforce CRM, shared SDR and AE team, combined content and SEO strategy targeting shared buyer personas, and a unified customer success team with consistent QBR and health scoring processes.

Value creation levers

• Cross-Sell Revenue Expansion Across Acquired Customer Bases

  The most immediate value creation lever in a SaaS roll-up is selling add-on products to existing platform customers.

• Operational Cost Consolidation Across Portfolio Companies

  Bootstrapped SaaS founders typically pay retail rates for every operational tool: separate Stripe or payment processing fees, individual Intercom or Zendesk accounts, redundant AWS infrastructure, and duplicated bookkeeping and accounting costs.

• Churn Reduction Through Professional Customer Success

  Founder-operated SaaS businesses often have reactive customer support rather than proactive customer success.

• Pricing Optimization and Tiered Packaging

  Bootstrapped SaaS founders frequently underprice their products relative to the value delivered, particularly in niche B2B verticals with limited competitive pricing data.

Day one

• Audit all active customer subscriptions, payment methods, and auto-renewal dates in Stripe or billing platform to confirm ARR accuracy at close.
• Secure access to all critical systems: GitHub repositories, AWS or hosting accounts, domain registrars, DNS records, and third-party API credentials.
• Send a warm, founder-endorsed customer communication announcing ownership transition and reaffirming SLA commitments and support continuity.
• Conduct a two-hour recorded knowledge transfer session with the seller covering top 10 customers, open support issues, and active product roadmap items.
• Establish a shared integration Slack channel or project workspace with the seller to document daily handoff items during the transition period.

Stabilize (Days 1–30)

• Map all customer health signals including login frequency, support ticket volume, NPS scores, and feature adoption using existing analytics tools.
• Audit all third-party software dependencies, API integrations, and hosting contracts to flag renewal dates, vendor concentration, and platform risks.
• Schedule one-on-one calls with your top 10 customers by ARR to introduce yourself, listen for concerns, and reinforce continuity of service.

Document and Systematize (Days 31–60)

• Build a customer onboarding SOP documenting every step from signup to activation, incorporating any undocumented steps the seller handled manually.
• Implement or consolidate customer success tooling to track health scores, renewal risk flags, and expansion opportunity signals in a single dashboard.
• Set up automated code testing, staging environments, and deployment documentation if none exist to reduce risk of production incidents.

Optimize and Grow (Days 61–90)

• Analyze cohort-level churn data from the past 24 months to identify which customer segments, geographies, or contract sizes retain best and target them for expansion.
• Negotiate or restructure contracts with your top five customers to introduce annual prepay options, reducing churn risk and improving upfront cash flow.
• Hire or contract a part-time developer familiar with the existing stack to own ongoing maintenance, freeing you to focus on growth and customer success.

Pitfalls

• Delaying Customer Communication

  Waiting weeks to notify customers of new ownership creates distrust and elevates churn risk. A prompt, founder-endorsed message reassuring customers of continuity is the single highest-ROI day-one action.

• Underestimating Technical Debt Costs

  Bootstrapped SaaS businesses often carry undocumented codebases, outdated dependencies, and zero test coverage. Buyers who skip a pre-close technical audit frequently face costly emergency fixes within 60 days of acquisition.

• Losing the Seller Too Early

  Releasing the founder from their transition obligations before SOPs are documented and top customers are introduced creates irreversible knowledge gaps. Maintain structured seller involvement for at least 60 to 90 days post-close.

• Accepting Surface-Level MRR Without Cohort Analysiscritical

  Buyers rely on headline MRR figures without examining cohort retention, expansion revenue, and contraction trends. Flat MRR can mask severe underlying churn offset by new customer acquisition.

• Underestimating Technical Debt and Legacy Code Riskcritical

  A profitable SaaS product can run on unmaintained code with no test suite, outdated dependencies, and zero documentation. Post-close rewrites can cost hundreds of thousands and delay roadmap execution.

• Ignoring Founder Dependency in Sales and Productcritical

  Many bootstrapped SaaS founders own the customer relationships, close every deal, and hold all product context in their heads. Without them, revenue erodes rapidly after transition. How to avoid it: Map every revenue-generating activity to a person.

• Miscalculating Customer Concentration Riskmajor

  When two or three enterprise clients represent over 40% of ARR, the business carries binary risk. Losing one account can immediately breach loan covenants or eliminate operating profit entirely.

• Misunderstanding Revenue Recognition and Deferred Revenuemajor

  SaaS businesses collecting annual subscriptions upfront carry deferred revenue obligations. Buyers who ignore GAAP reconciliation may inherit refund liabilities or overstate acquired cash flow.

• SBA

  Presenting lenders with only top-line revenue or MRR figures without cohort-level churn analysis — SBA underwriters for software deals increasingly require net revenue retention calculations and customer-level ARR aging to validate income sustainability

Warning signs

• MRR is growing but the seller cannot provide cohort-level churn data broken out by customer segment or contract vintage
• The founding team handles all inbound sales, onboarding, and tier-one customer support with no documented processes or delegation
• A single customer accounts for more than 25% of ARR and is operating on a month-to-month contract with no auto-renewal clause
• The codebase has no version control history, no deployment documentation, and relies on deprecated third-party APIs or unsupported frameworks
• Financial statements mix cash and accrual accounting with no deferred revenue schedule and inconsistent MRR figures across reporting periods

Phase 1: Financial Foundation & Metrics Clarity (Months 1–4)

• Compile 3 years of GAAP-reconciled financial statements with MRR/ARR scheduleshigh

  Buyers and quality of earnings providers will reconstruct your revenue from scratch. Proactively prepare monthly MRR bridge schedules showing new ARR, expansion ARR, contraction ARR, and churned ARR for each of the past 36 months.

• Build cohort analysis and churn reporting by customer segment and contract vintagehigh

  Net revenue retention (NRR) above 100% is one of the most powerful valuation drivers in SaaS M&A. Segment your churn data by customer acquisition year, contract size, and industry vertical.

• Document all revenue recognition policies and deferred revenue scheduleshigh

  If your SaaS business collects annual or multi-year subscriptions upfront, buyers need to understand how much of your cash receipts represent earned versus unearned revenue.

Phase 2: Technical Infrastructure & IP Documentation (Months 3–7)

• Conduct a technical audit to identify critical technical debt, security vulnerabilities, and dependency riskshigh

  Hire an independent software engineering firm to audit your codebase before buyers do.

• Establish version control, deployment documentation, and infrastructure-as-code standardshigh

  If your codebase lacks consistent Git branching conventions, CI/CD pipelines, or documented deployment runbooks, buyers will assume the worst.

• Confirm all IP assignment agreements, work-for-hire contracts, and open-source license compliancehigh

  Every developer — employee or contractor — who contributed to your codebase must have signed an IP assignment agreement transferring ownership to the company. Buyers will reject clean offers or require significant escrow holdbacks if IP ownership is ambiguous.

Phase 3: Customer & Contract Documentation (Months 5–9)

• Compile all customer contracts, subscription agreements, SLAs, and auto-renewal provisions in a data roomhigh

  Every active customer relationship must be documented with a signed agreement — verbal or implicit arrangements are a serious diligence red flag.

• Assess and document customer concentration risk across your ARR basehigh

  Calculate the percentage of total ARR represented by your top 1, 3, and 5 customers.

• Build a customer health dashboard tracking NPS, login activity, feature adoption, and support trendsmedium

  Buyers want forward-looking indicators of retention risk, not just trailing churn data.

Phase 4: Operational Systems & Founder Dependency Reduction (Months 6–12)

• Create detailed SOPs for customer onboarding, support escalation, product release cycles, and sales processeshigh

  Founder-dependent operations are the single most common reason SaaS acquisitions are structured with aggressive earnouts or extended transition requirements.

• Delegate key functions to employees or contractors and document the transitionhigh

  Begin actively transferring founder responsibilities to team members 12–18 months before your target sale date. Priority delegation targets: sales pipeline management, first-line customer support, and product sprint planning.

• Build a documented sales and marketing playbook covering ICP, lead sources, and conversion benchmarkshigh

  Even if your SaaS business grew primarily through word-of-mouth or founder-led outbound, buyers need to understand how growth is reproducible post-acquisition.

Quick wins before a sale

• Export your MRR and churn data from your billing platform (Stripe, Chargebee, or Paddle) into a clean spreadsheet and calculate your trailing 12-month net revenue retention rate — this single number will define your initial valuation conversation with every serious buyer
• Audit your top 10 customers by ARR and confirm each has a signed, current subscription agreement with no ambiguous cancellation or assignment provisions — unsigned relationships do not count as transferable ARR
• Write down every task you personally perform each week that the business cannot function without — this list is your founder-dependency risk inventory and your SOP priority roadmap for the next 12 months
• Run a search of your codebase repository for the five oldest and most-called dependencies and check their current maintenance status — deprecated or unmaintained libraries are the first thing technical due diligence firms flag

Questions to ask a broker

• How many SaaS businesses in the $1M–$5M ARR range have you successfully closed in the last 24 months?

  Validates real transaction experience with recurring revenue models, not just familiarity with general business brokerage in adjacent sectors.

• How do you present churn, net revenue retention, and cohort data to buyers to maximize perceived business quality?

  Reveals whether the broker can translate SaaS metrics into buyer-friendly narratives that support premium valuation rather than triggering unnecessary risk discounts.

• Which buyer types are in your active network — search funds, PE roll-ups, individual operators, or strategics?

  Determines whether the broker's buyer network actually matches your business profile, directly impacting deal speed, competitive tension, and final multiple achieved.

Broker red flags

• Broker cannot explain the difference between gross revenue retention and net revenue retention when discussing your SaaS business valuation or buyer marketing strategy.
• Broker proposes listing your SaaS business on general marketplace platforms without a targeted outreach strategy to qualified software buyers in your vertical.
• Broker has no relationships with SBA lenders experienced in approving loans for SaaS acquisitions, limiting your buyer pool to all-cash purchasers only.