with SaaS payment platform · SaaS payment platform
LenderHawk analysis. Not affiliated with or endorsed by Acquisitions Anonymous.
The business is attractive on paper because it is small, profitable, and recurring, but the hosts think the real value depends on whether it has a niche distribution moat beyond being a payment wrapper on Stripe. They repeatedly return to the question of how quickly the cash flows could erode if the platform, or competitors inside the vertical, offer the same functionality natively.
A recurring-billing SaaS can generate exceptional margins and still be fragile if it sits on top of a platform the buyer does not control.
Monthly churn must be translated into annual customer loss before you judge durability; 2.6% per month is a meaningful drain over a year.
A business that has been around since 2013 and is still being sold now should trigger a hard question about why the seller is exiting at this moment.
Broker claims of SBA prequalification should be treated as sales language unless a real lender has underwritten the file.
If the value proposition depends on a niche vertical, the buyer needs to determine whether the niche is protected by distribution or merely by inertia.
Technical diligence on the codebase matters when the listing hints that the owner is also the developer and the product runs on a modern Rails stack.
For declining SaaS, long-duration amortization can be a bad fit even when the business is profitable, because the loan can outlast the cash-flow decline.
A buyer who can improve payment processing economics may unlock more value than a buyer who focuses only on growing revenue.
The hosts evaluate whether a software business is a shrinking cash generator that should be priced as a declining asset, or a durable recurring-revenue platform worth premium SaaS multiples.
When to use: Use this when a SaaS listing has strong current margins but signs of declining revenue or rising competitive pressure.
Gross churn alone is not enough; the real question is whether acquisition and expansion can outpace customer loss over time.
When to use: Use this when a SaaS listing gives monthly churn, MRR, and customer counts but not retention cohorts.
The listing was priced at about $7 million on roughly $2.07 million of EBITDA, or 3.38x EBITDA.
Heather reads the Quiet Light teaser and Bill frames the valuation as unusually low for SaaS.
The business reported about $2.4 million in revenue and $186,522 of monthly recurring revenue.
The hosts use the listing’s headline metrics to assess size and profitability.
The platform served about 3,600 paying customers with a 23% free-to-paid conversion rate.
Heather summarizes the listing’s customer base and funnel statistics.
The company processed about $200 million in annual transaction volume.
The hosts use transaction volume to think about Stripe economics and potential rate renegotiation.
Monthly churn was listed at 2.6%, which the hosts translate into roughly 30% annual customer loss.
Bill converts the churn figure into a more intuitive annualized retention problem.
The business had been founded in 2013 and was being sold more than a decade later.
The hosts use the age of the company to question seller motivation.
The seller’s ask implied a little over three years of cash flow for the business.
Bill frames the valuation relative to earnings to judge whether the price is low enough for the risk.
The business had only one full-time support employee and one part-time contractor.
Heather cites the operating model to show how lean the business is.
Translate monthly churn into annual retention before you underwrite a SaaS deal.
Why: A small monthly percentage can still produce a large yearly customer loss.
Do real technical diligence on the codebase before buying a founder-built software business.
Why: If the founder is the developer, hidden maintenance and dependency risk can become the buyer’s problem.
Treat SBA prequalification as a marketing claim until a lender has actually underwritten the deal.
Why: Broker-side prequalification does not mean a bank will fund the acquisition.
Negotiate payment-processing economics aggressively if the business runs large Stripe volume.
Why: Even a small rebate or lower processing rate can materially increase earnings in a high-volume payments business.
Avoid stretching long-term debt onto a business whose revenue is visibly declining.
Why: A 10-year loan can outlive the cash flow if the business is a melting ice cube.
Pressure-test whether the real moat is distribution inside a niche rather than the software itself.
Why: If the software is easy to copy, the moat may vanish as soon as the upstream platform adds native features.
Travis described a deal in his fund where the buyer was processing a very large amount of Stripe volume and then renegotiated with Stripe for a kickback or better rate. He said the economics improved materially with little operational effort, showing how payment-processing leverage can create value in the right software business.
Lesson: In payments-heavy businesses, processor negotiations can be a meaningful EBITDA lever.
Bill described keeping an old Stripe account after selling a prior company, then using the grandfathered rate for a different business because Stripe let the account remain open. The anecdote showed how much value can hide in legacy payment-processing terms.
Lesson: A favorable processing rate can survive beyond the original business and remain economically valuable.