How to Safely Buy a SaaS Business Using Escrow: Verify Revenue Streams, Churn, and Customer Contracts

Why Use Escrow When Buying a SaaS Business

Purchasing a SaaS company involves transferring not just money but also ongoing revenue streams, customer contracts, and technical assets. Because the value is tied to future performance, buyers face risk if the seller misrepresents metrics or hides liabilities. Escrow acts as a neutral third party that holds the purchase price until all agreed‑upon conditions are satisfied, reducing the chance of fraud or dispute.

Escrows Click provides a streamlined process where funds are deposited, verified, and released only after the buyer confirms that the SaaS business meets the predefined criteria. This protects both parties: the seller knows the money is secured, and the buyer can walk away if the business does not match the representations. You can read more about the basic mechanics how escrow works.

Beyond financial safety, using escrow encourages transparent communication. Both sides agree on milestones—such as traffic validation, contract assignment, or technical hand‑over—before any money changes hands. This structured approach builds trust and makes the transaction smoother for everyone involved.

For example, a buyer might set a milestone requiring the seller to provide a recent Stripe export showing at least $10,000 MRR with churn below 5 %. Only after the buyer validates that export does escrow release the first tranche of funds. This step‑wise verification prevents unpleasant surprises after closing.

Pre‑Deal Preparation: Setting Up Escrow and Defining Milestones

Before transferring any funds, the buyer and seller should agree on a detailed escrow agreement that outlines the purchase price, payment schedule, and conditions for release. Typical milestones include verification of financials, assignment of customer contracts, and delivery of source code or infrastructure access.

Escrows Click allows you to create a customized escrow plan where each milestone is tracked in the platform dashboard. Funds remain locked until the buyer confirms that the seller has satisfied the requirement, at which point the platform releases the agreed portion. This step‑by‑step control prevents surprises at closing.

It is also wise to discuss fees early. Knowing the escrow cost structure helps avoid misunderstandings later. You can review our transparent pricing on the fees page to see how charges are calculated based on transaction size and complexity.

Example milestone structure for a $250,000 SaaS acquisition: 20 % released after financials are validated, 30 % after customer contract assignments are recorded, 30 % after source code and IP transfer are confirmed, and the final 20 % after a 30‑day post‑sale support period ends. This aligns incentives and provides clear checkpoints.

Verifying Financials: Revenue Streams, MRR, and Billing

Start by requesting access to the billing platform (e.g., Stripe, PayPal, or a custom invoicing system). Export raw transaction data for the past 12‑24 months and reconcile it with the reported MRR. Look for discrepancies such as duplicate entries, refunds not accounted for, or revenue recognized before service delivery.

Analyze the concentration of revenue. If a single customer accounts for more than 15‑20 % of MRR, the business may be overly dependent on that relationship. Diversification across many clients reduces risk and is a positive sign for long‑term stability.

Check for any off‑book revenue or side agreements that are not reflected in the official books. These can create unexpected liabilities after the sale. A thorough review of bank statements, tax filings, and merchant processor reports helps uncover hidden income streams or undisclosed expenses.

Practical steps: 1) Export CSV of all charges and refunds; 2) Summarize by customer ID to spot top‑paying accounts; 3) Cross‑refund amounts with the seller’s profit‑and‑loss statement; 4) Verify that any annual pre‑payments are correctly deferred in the financials. Document each step in a due‑diligence checklist.

Analyzing Churn and Retention Metrics

Export customer subscription logs to calculate monthly churn, gross churn, and net revenue retention (NRR). Cohort charts showing how groups of customers behave over time reveal whether retention improves with product upgrades or deteriorates after price changes.

Engage with a sample of customers (with seller permission) to understand their satisfaction levels. Qualitative feedback can highlight issues that numbers alone miss, such as missing features, poor support, or competing alternatives.

Examine the sales and marketing funnel: customer acquisition cost (CAC), payback period, and the ratio of lifetime value (LTV) to CAC. A healthy SaaS business typically shows LTV at least three times CAC and a payback period under 12 months. These metrics help you gauge whether the current growth trajectory is sustainable after the handover.

Example: If your cohort analysis shows that customers acquired via paid search have a 6‑month LTV of $900 and a CAC of $300, the LTV:CAC ratio is 3:1—a healthy benchmark. Conversely, if organic customers have a 12‑month LTV of $1,200 but a CAC of $500 due to high content costs, you may need to reassess marketing efficiency post‑acquisition.

Reviewing Legal and Contractual Obligations

Obtain copies of all master service agreements, data processing addendums, and any third‑party vendor contracts. Verify that the business holds the necessary licenses to use any embedded software, APIs, or open‑source components, and that these licenses are transferable to the new owner.

Check for any pending litigation, intellectual property disputes, or regulatory compliance issues (e.g., GDPR, CCPA). Even a low‑probability claim can become costly if it surfaces after acquisition.

Ensure that the seller has the authority to transfer the business entity or assets. If the SaaS is operated under a subsidiary, confirm that the subsidiary’s shares or assets can be sold without consent from other stakeholders. A clean chain of title prevents future ownership challenges.

Practical tip: request a legal opinion letter from the seller’s counsel confirming that all IP assignments are in place and that no encumbrances exist on the domain names or trademarks. This letter can be held in escrow as part of the closing conditions.

Technical Due Diligence: Code, Infrastructure, and IP

Request access to the source code repository (e.g., GitHub, GitLab) and review the codebase for quality, documentation, and dependency management. Look for signs of technical debt such as lack of unit tests, outdated libraries, or hard‑coded configuration values.

Assess the hosting environment: whether the application runs on AWS, Azure, Google Cloud, or a dedicated server. Verify that infrastructure is described in IaC (Infrastructure as Code) scripts, that backups are automated, and that disaster recovery plans are tested.

Confirm intellectual property ownership. The seller should provide assignment agreements for any custom code, design assets, or proprietary algorithms developed by employees or contractors. Open‑source components must comply with their respective licenses, and any proprietary third‑party SDKs need valid, transferable subscriptions.

Example checklist: 1) Run a dependency‑scan tool (e.g., Snyk or Dependabot) to flag vulnerable libraries; 2) Review the README for setup instructions and verify they work in a fresh environment; 3) Check that CI/CD pipelines are present and that automated tests pass on the main branch; 4) Ensure that environment variables are not hard‑coded and that secrets are stored in a managed secret store. Document any remediation items and negotiate who will address them before closing.

Planning Post‑Acquisition Integration and Handover

Technical verification is only part of the equation; a smooth transition keeps customers satisfied and preserves revenue. Develop a detailed integration plan that outlines data migration, support handover, and communication with end‑users.

Identify key personnel from the seller’s team who will stay on for a transition period—typically 30 to 90 days. Define their responsibilities: answering technical questions, assisting with billing migrations, and helping transfer customer relationships.

Use the escrow platform to allocate a portion of the purchase price (often 10‑15 %) as a retention bonus tied to the completion of these transition tasks. The funds are released only after the buyer signs off that the seller has fulfilled the agreed support obligations.

Communicate the change of ownership to customers via a coordinated email campaign. Include a clear timeline, reassurance about service continuity, and a point of contact for questions. Transparent communication reduces churn risk during the handover window.

Finally, conduct a post‑closing review after 60 days: compare actual MRR and churn against the pre‑close forecasts, document any variances, and adjust your growth strategy accordingly. This review also serves as a lessons‑learned repository for future acquisitions.

Closing the Deal: Fund Release, Post‑Sale Support, and Warranty

Once all milestones are satisfied, the buyer notifies Escrows Click to release the funds. The platform verifies the confirmation and transfers the payment to the seller’s account, completing the transaction. This final step ensures that money moves only after the buyer has validated the business.

Consider negotiating a post‑sale support period where the seller assists with migration, answers technical questions, or helps transfer customer relationships. Escrows Click can hold a portion of the purchase price in escrow for this warranty window, releasing it after the agreed support term ends.

Maintain records of all communications, verification steps, and escrow transactions. These documents are valuable if any disagreement arises later and also serve as a reference for future acquisitions. By following a disciplined escrow‑backed process, you minimize risk and maximize the chances of a successful SaaS purchase.