Deal Structure Guide · Cloud Services Provider

How Cloud Services Provider Acquisitions Are Structured

From seller notes tied to MRR retention to equity rollovers in MSP roll-ups, here is how buyers and sellers structure deals in the $1M–$5M cloud services market.

Cloud services provider acquisitions in the lower middle market present a unique structuring challenge: buyers are paying a premium for recurring revenue that may evaporate if key technical staff leave, a major client churns, or vendor relationships shift after close. Valuations typically range from 4x to 7x EBITDA depending on MRR quality, net revenue retention, contract duration, and customer concentration. Because much of the business value is forward-looking and tied to subscription relationships rather than hard assets, deal structures almost always include mechanisms to protect the buyer from post-close revenue deterioration. Sellers who want maximum proceeds at close need to demonstrate predictable, defensible MRR, documented operations, and a technical team that can run without them. Buyers who understand the cloud services model can use targeted earnouts and retention-linked seller notes to bridge valuation gaps while still offering sellers meaningful upside if the business performs.

Find Cloud Services Provider Businesses For Sale

Full Cash at Close with Seller Note

The buyer pays the majority of the purchase price in cash at closing, with 10–20% held back in the form of a promissory note payable to the seller over 12–24 months. In cloud services deals, the seller note is frequently tied to customer retention milestones — for example, maintaining MRR above a defined threshold — rather than fixed principal payments on a schedule.

80–90% cash at close, 10–20% seller note over 12–24 months

Pros

  • Provides the seller with a clean majority liquidity event at close while giving the buyer meaningful downside protection if key customers churn post-acquisition
  • Retention-linked note terms align seller incentives to support a smooth transition and protect client relationships during the handover period
  • Simpler to negotiate and close than complex earnout structures, making it attractive for SBA-financed acquisitions where lender approval is required

Cons

  • Seller carries credit risk on the note and may face principal reduction or forfeiture if MRR milestones are not met, which can feel punitive if churn is caused by market forces outside their control
  • Buyer still absorbs significant upfront capital risk if due diligence on MRR quality was insufficient to detect underlying churn trends
  • Note terms require careful legal drafting around what constitutes a qualifying MRR event, creating potential for post-close disputes

Best for: SBA-financed acquisitions where the lender requires a seller note as part of the capital stack, and deals where the buyer has high confidence in MRR quality but wants structured protection against near-term customer attrition.

Earnout Structure

A portion of the total purchase price — typically 20–30% — is held contingent on the acquired business hitting defined MRR growth or EBITDA targets over a 12–24 month period after close. Earnouts are common in cloud services deals when the buyer and seller disagree on the sustainability of the current revenue run rate or the trajectory of growth.

70–80% cash at close, 20–30% earnout over 12–24 months

Pros

  • Allows the buyer to pay a higher headline price than they could justify on current financials alone, bridging valuation gaps when the seller believes strongly in near-term growth
  • Directly aligns seller behavior during the transition period — sellers who remain involved post-close are motivated to protect and grow MRR to capture the earnout
  • Protects the buyer from overpaying for a growth story that does not materialize after the seller exits

Cons

  • Earnout disputes are among the most common sources of post-close litigation in technology acquisitions, particularly when MRR definitions, attribution of new contracts, or buyer operational decisions affect results
  • Sellers often feel penalized by earnout structures if the buyer makes platform decisions post-close — such as changing pricing or migrating customers — that negatively impact the earnout metrics
  • Earnouts extending beyond 12 months require sophisticated legal agreements covering what happens if the business is sold again or if the buyer changes its operating model

Best for: Deals where the seller is projecting significant near-term growth based on a signed pipeline or new product launch, and the buyer wants exposure to that upside without paying for it at close.

Equity Rollover

The seller retains a 15–25% equity stake in the acquiring platform or holding entity instead of receiving full cash proceeds at close. This structure is most common in private equity-backed MSP roll-up acquisitions where the sponsor is assembling multiple cloud services businesses into a larger platform for a future exit at a higher multiple.

75–85% cash at close, 15–25% equity rollover in the acquiring entity

Pros

  • Seller participates in the upside of the combined platform, potentially receiving a significantly higher total payout at the eventual platform exit than they would have achieved selling 100% today
  • Creates strong alignment between the seller and the acquirer during the integration period, as the seller has direct financial interest in the success of the broader business
  • Allows the buyer to preserve cash or reduce senior debt requirements at close by substituting equity for a portion of the purchase price

Cons

  • Seller exchanges liquid cash proceeds for illiquid equity in a privately held platform with no guaranteed exit timeline or valuation certainty
  • Minority equity stakes offer limited control or governance rights, meaning the seller's future returns depend entirely on decisions made by the PE sponsor or majority owner
  • Tax treatment of rolled equity can be complex and may not defer the seller's tax liability in the way they expect without careful planning

Best for: Founder-operators who believe in the long-term consolidation thesis of the acquiring platform, have a meaningful financial cushion from the cash received at close, and are comfortable with a 3–5 year horizon to a platform exit.

Sample Deal Structures

SBA-Financed Acquisition of a Regional Managed Cloud Hosting Business

$2,400,000

$300,000 buyer equity injection (12.5%), $1,980,000 SBA 7(a) loan (82.5%), $120,000 seller note tied to MRR retention milestones (5%)

The seller note carries a 6% interest rate and is structured as a 24-month instrument with principal payments contingent on the acquired business maintaining at least 90% of trailing 12-month MRR each quarter. The SBA loan is amortized over 10 years at a variable rate tied to prime. The business was acquired at 5.0x EBITDA of $480,000 with MRR representing 78% of total revenue and a net revenue retention rate of 104%.

PE Roll-Up Acquisition with Equity Rollover for Founder-Operator

$4,200,000

$3,150,000 cash at close (75%), $1,050,000 equity rollover representing a 20% stake in the combined MSP platform (25%)

The seller receives cash at close funded by the PE sponsor's acquisition facility. The rolled equity is valued at the same implied multiple as the cash consideration — 6.0x EBITDA of $700,000 — and carries standard minority equity protections including tag-along rights and information rights. The founder agrees to a 24-month operational role as VP of Cloud Infrastructure. The platform is targeting a 5-year hold with an exit multiple of 8–10x EBITDA on the combined entity, implying significant potential upside on the rolled equity position.

Earnout Deal Bridging a Valuation Gap on a High-Growth Cloud MSP

$3,500,000 (base) with up to $700,000 in earnout payments

$2,800,000 cash at close (80% of base), $700,000 earnout payable over 24 months in two tranches tied to MRR growth thresholds

The first earnout tranche of $350,000 is payable at month 12 if MRR exceeds $165,000 per month (up from $140,000 at close). The second tranche of $350,000 is payable at month 24 if MRR exceeds $195,000 per month. The buyer funded the cash at close through a combination of personal equity and a conventional acquisition loan. The seller, who projected 15% annual MRR growth based on a signed enterprise customer pipeline, accepted the structure to capture the valuation they believed the business would earn post-close.

Negotiation Tips for Cloud Services Provider Deals

  • 1Define MRR precisely in the purchase agreement before negotiating any seller note or earnout — specify exactly which revenue streams qualify as recurring, how one-time project revenue is excluded, and how customer credits or downgrades are treated in the calculation to prevent post-close disputes.
  • 2Request a full customer cohort analysis during diligence showing net revenue retention, expansion revenue, and churn by customer segment for the past 36 months — this data will tell you more about true MRR quality than any income statement and will anchor your earnout or retention milestone thresholds.
  • 3Audit all hyperscaler and third-party vendor agreements for change-of-control provisions before structuring the deal — a contract that terminates or requires renegotiation upon acquisition can materially affect revenue and should either be resolved pre-close or reflected in a purchase price adjustment.
  • 4Negotiate key employee retention agreements with lead engineers and technical staff as a condition of closing rather than a post-close aspiration — offer retention bonuses funded from escrow or seller proceeds and tie a portion of any seller earnout to named employee retention to align the seller's interest in a smooth handover.
  • 5Structure any equity rollover at the same implied valuation multiple as the cash consideration, and insist on clearly defined exit rights including tag-along provisions, a drag-along mechanism, and a put option after year five to ensure the seller has a path to liquidity if the platform exit is delayed.
  • 6For SBA-financed acquisitions, engage an SBA lender experienced in technology and MSP acquisitions early in the process — lenders unfamiliar with recurring revenue models may underwrite on trailing cash flow alone and miss the value of contracted ARR, which can reduce loan proceeds and force a larger equity injection than necessary.

Find Cloud Services Provider Businesses For Sale

Pre-screened targets ready for your deal structure — free to join.

Get Deal Flow

Frequently Asked Questions

What is the typical valuation range for a cloud services provider with $1M–$5M in revenue?

Cloud services providers in this revenue range typically trade at 4x to 7x EBITDA, with the multiple driven primarily by MRR quality, net revenue retention, customer concentration, contract duration, and the strength of the technical team. A business with 80%+ recurring revenue, net revenue retention above 110%, and SOC 2 Type II certification will command the upper end of that range. A business with high customer concentration, month-to-month contracts, and heavy owner dependency will trade closer to 4x or below.

How does a seller note work in a cloud MSP acquisition, and what happens if customers churn?

A seller note in a cloud services deal is a promissory note where the buyer pays a portion of the purchase price to the seller over time after close. In MSP acquisitions, these notes are frequently structured with MRR retention milestones — for example, the principal is reduced or forgiven if monthly recurring revenue falls below a defined threshold within the first 12–24 months. If the seller has represented strong MRR quality and customers churn after close due to factors that were misrepresented or undisclosed in diligence, the buyer can offset those losses against the note. Sellers should negotiate to limit this exposure to churn caused by conditions that existed pre-close rather than operational changes made by the buyer post-acquisition.

Can I use an SBA loan to acquire a cloud services company?

Yes, cloud services providers are SBA-eligible businesses, and SBA 7(a) loans are commonly used to finance acquisitions in this segment. The SBA will require the borrower to inject 10–15% of the purchase price as equity, and lenders will underwrite the deal primarily on historical EBITDA and cash flow. Because MRR-heavy businesses sometimes show lower reported EBITDA due to owner add-backs or growth investment, it is important to work with an SBA lender who understands recurring revenue models and can credit the value of contracted ARR in their underwriting analysis.

What is an earnout and when does it make sense in a cloud services acquisition?

An earnout is a portion of the purchase price that is contingent on the business hitting financial performance targets after close — most commonly MRR growth or EBITDA thresholds over a 12–24 month period. Earnouts make sense in cloud services deals when the seller is projecting meaningful near-term growth based on a signed customer pipeline or new service offering, and the buyer is unwilling to pay for that growth at close. They bridge valuation gaps but require careful legal drafting to define exactly how metrics are calculated, who controls decisions that affect those metrics, and what happens in dispute scenarios.

What is an equity rollover and why would a seller agree to one?

An equity rollover means the seller reinvests a portion of their sale proceeds — typically 15–25% — back into the acquiring platform as a minority equity stake instead of receiving full cash. Sellers agree to rollovers primarily in PE-backed roll-up acquisitions where the sponsor is building a larger MSP platform. The appeal is the potential to earn a significantly higher total payout at the platform's eventual exit, when the combined business may sell at a higher multiple than any individual company could command alone. The risk is that the equity is illiquid, the exit timeline is uncertain, and the seller has little control over how the platform is managed.

How do buyers protect themselves against key person risk in a cloud services acquisition?

Buyers address key person risk through a combination of deal structure and contractual protections. Common approaches include requiring the seller to sign a 12–24 month transition and employment agreement, funding retention bonuses for lead engineers and technical staff from escrow, mapping all institutional knowledge during diligence and requiring the seller to document runbooks and operational processes before close, and tying a portion of the seller note or earnout to named employee retention milestones. Buyers should also assess whether the business can operate without specific individuals by running tabletop scenarios during diligence that test whether the team can respond to a major incident or onboard a new enterprise client without the founder's direct involvement.

More Cloud Services Provider Guides

More Deal Structure Guides

Start Finding Cloud Services Provider Deals Today — Free to Join

Find the right target, structure the deal, and close with confidence.

Create your free account

No credit card required