with Conversion rate optimization SaaS in Poland · Conversion rate optimization SaaS in Poland
LenderHawk analysis. Not affiliated with or endorsed by Acquisitions Anonymous.
A 13-customer software business can still generate $388K of trailing revenue if the contracts are enterprise-sized and annualized.
A listing that asks for a limited license so the seller can keep servicing clients is a strong clue that the business is really a founder-dependent service wrapper around software.
Polish-language customer relationships materially reduce the buyer pool for this company because operating it well appears to require local language and market familiarity.
The hosts thought the asset was priced more like a fragile lifestyle business than a clean, transferable SaaS asset.
A buyer likely needs to re-sign customer contracts after closing, which makes the apparent cash flow less certain than the trailing numbers suggest.
A one-person operation with 96% of the equity held by the founder creates continuity risk even when the product itself looks profitable.
The best buyer for this deal is probably someone already embedded in the same software ecosystem and willing to work inside the business rather than simply own it.
A deal can be attractive in the abstract but still be unbuyable if the buyer lacks the language, technical skills, or domain context required to run it. The hosts use this lens to argue that the right operator matters as much as the asset itself.
When to use: Use this when a business depends on local expertise, founder know-how, or deep operational context.
The buyer effectively learns the business by working inside it while gradually taking over economics and control. The hosts frame this as a practical structure when the company is too founder-dependent to sell cleanly.
When to use: Use this for services-heavy or highly bespoke businesses where transition risk is high.
The listing asked $950,000 for a business reported at 2.9x profit and 2.4x revenue.
Hosts read the Acquire.com teaser and immediately questioned whether the valuation fit the business model.
Trailing 12-month revenue was $388,000 and trailing 12-month profit was $324,000.
These were the seller-stated financials for the Polish CRO SaaS.
The business had 70% year-over-year growth.
The listing used this growth rate to justify the valuation.
The company had 13 paying clients, with fees ranging from $450 to $12,000 per month.
Hosts used the small customer count to infer concentration and transferability risk.
About 90% of revenue came from enterprise contracts, while licensing fees accounted for about 74% of trailing revenue.
The seller positioned the mix as evidence of recurring, higher-value accounts.
Less than 15% of trailing revenue came from outside Poland.
This geographic concentration was a major reason the hosts thought an American buyer would struggle.
The founder said the company previously raised $320,000 in a seed round, EU subsidies, and research grants.
The seller disclosed prior capital and ownership history near the bottom of the listing.
The founder said he now owns 96% of the company after buying out investors at $500,000 and $800,000 valuations.
The hosts highlighted this as important because it reveals the seller's basis and likely price expectations.
Only pursue this kind of listing if you speak the local language and can personally support the customer base.
Why: The hosts believed Polish customer communication and context were central to keeping revenue intact.
Assume re-signing risk when a seller implies clients may need to be transferred or re-executed after closing.
Why: The hosts thought the post-close contract transfer process could materially disrupt cash flow.
Structure a deal with seller carry or an earnout when the business depends on the founder's ongoing technical and customer support.
Why: Shared downside is necessary when the asset is not fully transferable on day one.
Treat founder-dependent SaaS listings as apprenticeship deals rather than passive investments.
Why: The buyer may need to learn the product, the market, and the operating cadence before the business can stand on its own.
Do not pay a clean SaaS multiple for a business that behaves like a productized consultancy.
Why: The hosts believed the economics and operational dependence were closer to services than to software.
The seller offered to reduce price in exchange for a limited license to keep serving existing clients until they re-signed under new ownership. The hosts read this as evidence that customers might not transfer cleanly and that the seller's ongoing involvement was likely embedded in revenue retention.
Lesson: When a seller wants to keep servicing clients after closing, the asset may be more of a transitional service business than a clean software acquisition.
Despite nearly $388,000 of trailing revenue, the company only had 13 paying customers, with ticket sizes ranging from a few hundred dollars to $12,000 per month. The hosts used that fact to argue the business was small, concentrated, and hard to scale without the founder.
Lesson: High revenue with a tiny customer count can signal concentration risk rather than product-market fit.